Archive for the 'accessibility' Category

How can sites make their content more accessible to the blind?

Monday, July 31st, 2006

Some of the basic recommendations on how to make a website more useable and accessible include keeping Web pages easy to read, avoiding visual clutter – especially extraneous content – and ensuring that the primary purpose of the Web page is immediately accessible with full keyboard navigation.

There are many organizations and online resources that offer Website owners and authors guidance on how to make websites and pages more accessible for the blind and visually impaired. The W3C publishes numerous guidelines including Web Content Access Guidelines that are helpful for Website owners and authors. Broad adherence to these guidelines is one way of ensuring that sites are universally accessible.

Enter Google labs Accessible Search

http://labs.google.com/accessible/

Called the Google Accessible Search, the search adds a small twist to the familiar Google search and finds the most relevant results as measured by Google’s search algorithms, but also sorts results based on the simplicity of their page layouts. So when users search from the site, they’ll receive results that are prioritized based on their usability.

In its current version, Google Accessible Search looks at a number of signals by examining the HTML markup found on a web page. It tends to favor pages that degrade gracefully – pages with few visual distractions and pages that are likely to render well with images turned off. Google Accessible Search is built on Google Co-op’s technology, which improves search results based on specialized interests.

We look forward to this developing and making the web more accessible. And the Co-op developing into making algorithms more favourable toward accessible web sites, like the ones we make at Callender Creates.

PAS78 – free web site accessibility guide

Monday, July 3rd, 2006

We would like to let you know that the “PAS 78: a guide to good practice in commissioning accessible websites” can be downloaded free from the Disability Rights Commission.

It offers guidance on how to develop a website which is user-friendly for disabled people.

“The ‘PAS 78: A guide to good practice in commissioning accessible websites’ (published March 2006) is for those responsible for commissioning or maintaining public-facing websites and web-based services. It was developed by the British Standards Institution (BSI) and sponsored by the DRC.”

These guidelines will not tell you how to make an accessible web site, however PAS 78 covers areas such as:

  • How disabled people use websites
  • Defining the accessibility policy for the website
  • Web technologies
  • Accessibility testing and maintenance
  • Contracting web design and accessibility auditing services.

It gives recommendations for:

  • The management of the process of, and guidance on, upholding existing W3C guidelines and specifications
  • Involving disabled people in the development process and using the current software-based compliance testing tools that can assist with this.

It is applicable to all public and private organizations that wish to observe good practice under the existing voluntary guidelines and the relevant legislation on this subject and is intended for use by those responsible for commissioning public-facing websites and web-based services.

For more reading on PAS 78 and WCAG2.0 check out the @media2006 Notes: The New Accessibility Guidelines: WCAG 2.0 over at Muffin Research

User Interface – Site Check

Monday, July 3rd, 2006
A great testing resource all from one web site - http://uitest.com/en/check/

Site Check saves you time – You fill out only one form instead of dozens when checking a web site. Site Check lists the test results provided by important validators and accessibility tools.

You will be please to know we carry out these tests to our sites as standard testing procedures.

Why dont you type in the address of your favourite web site and see how it looks for different users?

@media 2006:after

Thursday, June 22nd, 2006

A report on the seminars and the nice people I met in London for @media 2006.

It was the second year for this event, the audience grew to a large 800 people to come and learn about the new and emerging web applications and new accessibility guidelines for web 2.0.

>> Eric Meyer started the event with a historic look at the last ten years of the web, there were a few hands up for “who remembers netscape 3?”.

His main point was “Sharing information is the only way to move a new technology forward”. and “with every problem in web language you should write an essay or report to share this and help others move forward”.

and reconfirming that CSS is a simple and powerful language which is increasingly helping to push the web forward. For example at: CSS Destroy and CSS Playground

Full transcript for Eric Meyer’s Keynote

>> Good Vs. Great Design with Veerle, Jon Hicks and Cameron Moll – showed that that design is not just about pretty design, it’s about the effective communication of content too, and there is no one solution.

They discussed individually typography, colour and grid design. And how some colours and type work with some web themes, where as others are just wrong!

Download the presentation slides (PDF file – 3.5 MB)

>> Chris Wilson of Microsoft reported on the new IE7 browser. And whats in store for the future. It’s been five years since a new version of Internet Explorer, and he explained what they had been up to all this time!

Full transcript for IE7 and Beyond

>> WCAG 2.0 – The new web accessibility guidelines by the W3C, was relevant to new web technologies. The panel mentioned a new book on this subject and referred to PAS78 being a way to implement accessibility and not guidelines themselves. Web pages compliant to WCAG should be POUR:

  • Percievable
  • Operable
  • Understandable
  • Robust

Full transcript for WCAG 2.0

>> Jeff Veen is always a good speaker. His topic “The next generation of web apps” showed that powerful tools in the hands of people with passion for the web is changing the way we view the media now. Blogs, wikis are all diverting our attention away from mainstream media.

He also covered what the elements should be for a Web 2.0 application – “Surface – Skeleton – Structure – Scope – strategyâ€?

  • Surface, typography color layout grids, iconography. Things that give desirability, brand. Blogger as an example of something I worked on with doug bowman who is also at Google now.
  • Skeleton: About the web application and how it works. what you can poke at
  • Structure: how is all the stuff organised in the site.
  • Scope: What of all of this what can we do now? What is out organisation going to focus on?
  • Strategy: What is our reason for being?

Full transcript of The Next Gen of Web Apps
Download the presentation slides (PDF file – 18.5 MB)

>> Dan Cederholm carried on his excellent hands on topic of Bulletproof web design. He mentioned his 10 second usability test where you: take away the CSS, images > can you still read the page?. An unscientific way, but easy to add to site analysis workflow.

He also covered validation techniques and new bulletproof concepts such as link and bullet list examples.

The bulletproof concept.

  • A catchy phrase
  • The positive power of buzzwords.
  • Embrace flexibility
  • Let go of pixel precision
  • Plan ahead for worst case scenarios.

Means >> Great Web design.

Full transcript Bulletproof web design
Download the Presentation Slides (PDF File – 20MB)

>> And finally a superhero panel – Hicks, Holzschlag, Celik, Meyer and Keith (see pic below) discussing “Hot” Topics.

Full transcript of Hot Topics

@media panel

All in all a great conference for the front end web developer and any web team who wants to increase their learning and experience with web standards and Web 2.0 applications.
I should have taken more photos, how ever there are some good pics up on Flickr.

Meanwhile the speaker list has just been added to this years d.construct 2006.

Colorblind Web Page Filter – web page testing

Tuesday, May 23rd, 2006

We found this brilliant Colorblind Web Page Filter on the web and have incorporated this as part of our testing our draft HTML designs, before launching our web sites.

Other testing procedures include:
  • Browser testing – does it display the same in all modern browsers?
  • Screen resoluton – does it display in 800 X 600, as well as 1280 x 1024?
  • Operating systems – how does it look here?
  • Accessibility testing – how do the access keys work, and how does it comply with the WAI guidelines?
  • CSS and Javascript – when these are turned off, can you still read the web page?
  • Spiderability - how does a search engine spider view the site, also good for predicting how text readers will cope with the page?
  • Images turned off - can you still navigate the site?
With all these tests we are confident we know our web code and web sites better. We work with the latest industry standards to make sure we comply with the latest accessibilty guidelines, as well as using web standards in our web code.Make sure yours is one of them too. Considering a new web site or a re design? Speak to Callender Creates today

Top Accessibility Resources

Tuesday, May 2nd, 2006

Accessibilty Myths

Tuesday, May 2nd, 2006

Tackling myths & assumptions

Accessibility is also about avoiding myths & assumptions about how & why people use the web. It may surprise you to learn that accessibility benefits everyone who uses your website, not just people who have a disability.

Some examples of the types of assumptions & mistakes that are commonly made:

  • Everyone can use a mouse.
  • Everyone can upgrade to the latest browser or download the required plugin
  • “Blind people can’t drive, so they won’t be interested in a website about carsâ€?.

Accessibility only benefits blind

Eyesight problems & blindness are not the only forms of disability affecting people who use your website. Accessible pages work better for everyone who uses the web, not just those with a special need or limited ability. Making a site fully accessible can increase its usability dramatically.

You must provide text only pages on your site

If care is taken making your page accessible, a text only page is very rarely required. The World Wide Web Consortium (W3C) recommend that only if after best efforts your site cannot be made accessible, should you even consider providing a text only version.
The RNIB recommend against providing a text only version as much as possible, simply because being treated differently can reinforce the feeling of marginalisation that someone with a disability experiences. From a business perspective it also leads to dual maintenance of content, which is far from ideal.

I will be prosecuted if my website is not made accessible by October 2004

Not necessarily a myth in itself, but there are a number of myths surrounding it. It is important to set a couple of facts straight here.
Some confusion exists around the date of October 2004. Some people think that there is a new piece of legislation coming into force which states websites should be accessible. This is not the case. The legislation coming into force in October 2004 is in fact the final part of the act that was implemented in 1996, & applies to the accessibility of physical spaces such as buildings. In fact, your website should have been made accessible since 1996.

Although the legislation has been place since 1996, & clearly states that websites must not discriminate against people with disabilities, there has been no case brought to test how the law will be interpreted & applied.

This does not mean that you should not take your responsibilities under the act seriously. What is clear is that website owners should have already begun to implement an accessibility programme, & should be seen to be making what the act refers to as “reasonable adjustments”.

You cannot use images

Although for example, blind users cannot see your images, it would be pointless to disadvantage sighted users by not including graphics at all. In fact, graphics can enhance the accessibility of a website for people who have low levels of literacy, the elderly or children.

Adding a simple “altâ€? attribute to the image in the coding of the page can go a long way to helping your site become more accessible. The “alt” attribute can be used to insert a description of the contents of the image. This description will be read out to a blind person using a screen reader & even though they cannot see the image, they will have enough information to underst& what is going on in it.

You have to use a large font

This is not necessary at all. If you use relative font sizes, someone who has a low level of vision can resize the text to suit their needs, & therefore you do not need to use big fonts.

Red & green cannot be used

Red & green are perfectly acceptable colours to use! Just do not use them alone to convey information. For example, a timetable which makes a statement such as “All trains highlighted in red have been cancelled” relies solely on the readers ability to perceive & distinguish colour. This could be simply fixed by saying “All trains that are highlighted in red & bold have been cancelled”, that way someone who has difficulty distinguishing the colour red can look for the bold information.

Accessibility is time-consuming, expensive & very technical

Retro-fitting a site for accessibility can be all of the above, but ultimately these investments pay for themselves in terms of a greater customer base & a generally improved visitor experience. Building accessibility into the design & build of a new site is not necessarily time consuming & technical. You’ll find that it contributes to the usability of the site & cuts down on maintenance costs once the site is up & running.

Conclusion

Design for all

Accessibility is about flexibility in design. Designers need to think in terms of providing more than one way of doing things on a website, so that if a user is unable to use one method, other options are available to them.

A better web experience for everyone

Accessibility is about understanding & supporting the needs of the people who visit your website. A well-designed site will remove the barriers that may prevent people from entering & using it.
A website that is accessible will provide the same level of experience to everyone who visits it, regardless of his or her level of ability or disability.