IT Careers -Web and Application Accessibility

Skip to main content
Skip to career navigation

IT Careers

Getting Started

References

The W3C's Web Content Accessibility Guidelines (WCAG), from which the 508 checkpoints come, do encourage the use of CSS style sheets. The idea they're promoting is to completely separate structure from presentation.

Tips

There are 65 checkpoints under the W3C's Web Content Accessibility Guidelines, but only 5 can be accurately checked with an automated tool. All the rest require manual input of some kind. When to use automated tools article

Where there are items to fill out, and they say "the items in red are required fields" that's a non accessibility statement, where if it says "the items marked with a star are required fields" and the stars do indeed show up on the correct items to be filled out, that's accessible,

sites with graphical links that read like this "link graphic 21279-1.jpg, link graphic 21279-2.jpg" and the like qualify as non accessible while "link graphic21232home.jpg and link graphic21232cont.jpg" can be considered accessible since they contain a clue, or at least a partial clue as to what they are in the graphic name.

Some websites use an "Orientation Guide" to describe format, ket strokes and navigation help.

Windows Eyes is available as a free
30-minutes-per- every-Windows- session demo to developers.

Web and Application Accessibility

Contents

ValidatorsTesting

References

Accessibility Sites/Forums

Tips


Skip to main content Skip to career navigation Home IT Initiative IT Careers Operations Support Network Support Database Support Programming Web Systems Analysis Development Cross IT Functions Getting Started Introduction Java/Eclipse C,C++,C# JAWS SQL Visual Basic Web Accessibility References Assistive Tech Programming Links Contact Us
	Web and Application Accessibility Contents Validators/Testing References Accessibility Sites/Forums Accessibility Tips ValidatorsTesting Total Validator IBM Software Accessibility Checklist References The W3C's Web Content Accessibility Guidelines (WCAG), from which the 508 checkpoints come, do encourage the use of CSS style sheets. The idea they're promoting is to completely separate structure from presentation. w3c consortium, the site with the standards lists: Web Content Accessibility Guidelines 1.0 and Web Content Accessibility Guidelines 2.0 W3C Working Draft A site for section 508 referencing: www.section508.gov Online validation tools for web page testing: http://CynthiaSays.com A free PDF book "Understanding Accessibility" http://www.hisoftware.com/uaen/ua.pdf An excellent HTML-based instruction on Section 508 web standards is at http://jimthatcher.com/webcourse1.htm An excellent, all-around site on this subject is http://webaim.org Accessibility Sites/Forums Accessify and AccessifyForum - Home of the Accessibility Toolset Webaim and WebAIM Accessibility Forums - Making the web more accessible to individuals with disabilities (documentation and resources) Top Tips There are 65 checkpoints under the W3C's Web Content Accessibility Guidelines, but only 5 can be accurately checked with an automated tool. All the rest require manual input of some kind. When to use automated tools article Where there are items to fill out, and they say "the items in red are required fields" that's a non accessibility statement, where if it says "the items marked with a star are required fields" and the stars do indeed show up on the correct items to be filled out, that's accessible, sites with graphical links that read like this "link graphic 21279-1.jpg, link graphic 21279-2.jpg" and the like qualify as non accessible while "link graphic21232home.jpg and link graphic21232cont.jpg" can be considered accessible since they contain a clue, or at least a partial clue as to what they are in the graphic name. Some websites use an "Orientation Guide" to describe format, ket strokes and navigation help. Windows Eyes is available as a free 30-minutes-per- every-Windows- session demo to developers. Top