The Web should be made accessible to as many people as possible, regardless of any disabilities they might have.
Remember that many people do not use a mouse to interact with the web, so you have to make sure that the sites or applications you build work independent of input device.
There is no way to specify alternate text for CSS background images. This is not a problem since background images should be used for presentational purposes only.
Only use the fieldset and legend elements to group logically related form controls, always use both elements together, and keep legend texts short.
Don’t make your users waste their time by hiding links. If you can’t stand the look of blue and underlined links, there are other ways of making them obvious. But do not rely on colour alone.
Always make sure that any links you create have actual text content, or they will be unusable to some of your visitors.
Even if you do not have a disability, there are some things you can do to gain a better understanding of the obstacles some people with disabilities run into on the web.
Making web sites and web applications accessible is more than making them possible to access - it also means making them usable.
The title attribute can be used to provide advisory information about an HTML element, but do not use it for essential information since not all users will notice the title text.
Testing your web sites and web applications with a screen reader is good. Screen readers can be expensive, but NVDA is a completely free alternative that has WAI-ARIA support.
WebAIM’s WCAG 2.0 Checklist condenses the guidelines into an easy-to-use and understandable checklist that will help you get started with WCAG 2.0.
Using p elements instead of multiple br elements to create paragraphs in HTML makes your documents more accessible and easier to style.
While it is important for all web developers to have access to a screen reader for testing, setting one up may prove a little tricky. Fortunately there are instructions that will help.
The European Accessibility Forum Frankfurt on 27 March 2009 offers an impressive line-up of speakers that will discuss current accessibility topics.
Apple recently released a public beta of Safari 4. Among the news is support for WAI-ARIA, but I can’t figure out how to make it work.
To make sure that people who need larger text can use your size, increase text size to 200 percent and check that the content is still readable and functional.
The Accessible Rich Internet Applications (WAI-ARIA) specification has reached Last Call Working Draft status, and the W3C wants your feedback.
Internet Explorer’s text resizing behaviour is different from that of other browsers since IE does not allow the end user to (easily) resize text whose size has been specified in pixels.
With WCAG 2.0 now being a W3C recommendation it is time to check that the tool you use to check colour contrast supports the luminosity contrast ratio algorithm recommended by WCAG 2.0.
The alt attribute is valid only for images and provides alternative text used when the image cannot be rendered. Do not use it with links and other non-image HTML elements.