| |||||||||
|
1. #22954 Ask anyone who has had to fix a Website that's littered with accessibility howlers, and top-most in their list of problems encountered will be forms, closely followed by tables. These two topics always seem to present the most difficulties, but they needn't be a problem. For the most part, forms are a problem because the extra accessibility tags are simply not known to the Web designer -- after all, it looks right, it seems to work... what's the problem? Only by switching off the monitor and using a screen-reader can our oblivious Web developer understand the issues. Lloyd, Ian. SitePoint (2003). Design>Web Design>Accessibility>Forms 2. #22959 When we talk about the accessibility of forms, we are usually referring about their accessibility to screen readers and the visually impaired. People with other types of disabilities generally are less affected by 'faulty' forms that are missing some of the HTML accessibility features. WebAIM (2003). Design>Web Design>Accessibility>Forms 3. #27482 To demonstrate an example of some accessibility issues in HTML Forms, the following content intentionally has accessibility errors. Abou-Zahra, Shadi. W3C (2004). Articles>Web Design>Accessibility>Forms 4. #27855 Forms are a pain. You can make them pretty, make them accessible, or go a little crazy trying to achieve both. Nick Rigby offers a happy solution. Rigby, Nick. List Apart, A (2006). Design>Web Design>Accessibility>Forms
| |||||||||
| |||||||||
Click here to learn how to embed the RSS feed of this category in your website.