Web Accessibility Reports
- Provide equivalent alternatives to auditory and visual content.
- Don’t rely on color alone.
- Use markup and style sheets and do so properly.
- Clarify natural language usage.
- Create tables that transform gracefully.
- Ensure that pages featuring new technologies transform gracefully.
- Ensure user control of time-sensitive content changes.
- Ensure direct accessibility of embedded user interfaces.
- Design for device-independence.
- Use interim solutions.
Report 1
Guideline 1: Provide equivalent alternatives to auditory and visual content.
Original Source: http://www.w3.org/TR/WAI-WEBCONTENT/#gl-provide-equivalents
Standard Summary
Equivalent alternatives allow messages to be conveyed via audio or video content to be distributed to individuals without access to such media. Equivalents such as alternative text and synthesized speech can enable users with disabilities or low access to understand a page’s content without actually viewing or accessing the media content. Alternative text can be useful where users are unable to download or access images.
How the standard must be implemented
In order to implement this standard, every element should have a text/audio equivalent providing a description of the element’s content. All alternatives should also be synchronized to the presentation of the media.
< Back
Report 2
Guideline 2: Don’t rely on color alone.
Original Source: http://www.w3.org/TR/WAI-WEBCONTENT/#gl-color
Standard Summary
Guideline two is in place to ensure that users visiting a web site are able to obtain visual information in spite of visual handicaps. When using images in a site, it is important for developers to consider users who may not be able to distinguish colors. Some devices inaccurately display color, while others may not display color at all.
To limit problems a user may encounter, images with stark contrast between foreground and background hues should be used. This allows users viewing content in a monochrome display to see the images clearly.
How the standard must be implemented
Web developers should make sure that anything expressed in color on their site is also available without color. Users should be able to understand the site’s content with or without color. Testing images in a grayscale or monochrome display for contrast ahead of time will prove that users can see images visibly.
< Back
Report 3
Guideline 3: Use markup and style sheets and do so properly.
Original Source: http://www.w3.org/TR/WAI-WEBCONTENT/#gl-structure-presentation
Standard Summary
The idea behind a Web page is to provide quick easy access to important information. Users should have little to no problem navigating your page. Therefore, it is important to provide structure and organization which are easy to follow.
In order to achieve this, Web developers should use structural elements and style sheets, and avoid the use of presentation elements. Similarly, markup misuse should be avoided. Presentation markup should not be used for structural purposes when CSS is available. Be aware also that using constructs for formatting effects may cause some users to lose accessibility to your document.
How the standard must be implemented
- Use markup, not images where possible
- Follow formal grammar
- Use stylesheets and CSS
- Relative units in language and style sheet values
- Use header elements accurately for structure
- Mark-up lists and order list elements correctly
- Avoid quotation markup for formatting effects
Report 4
Guideline 4: Clarify natural language usage.
Original Source: http://www.w3.org/TR/WAI-WEBCONTENT/#gl-abbreviated-and-foreign
Standard Summary
Updating natural language changes can allow accessibility devices (like Braille and speech synthesizers) to alter content into the new language, providing access to users of multiple languages. Natural language can help search engines find key words and documents written in a specific language, and can be extremely useful in readability for those with disabilities.
How the standard must be implemented
As developers, it is important to specify which natural language a document is primarily geared to reaching, using headers or markup. Developers should include expansions of any shortened language used in the document. Neglecting to identify these aspects of a document may make it impossible for individuals using accessibility devices to understand the document’s content.
- Identify changes in natural language text or equivalents
- Specify expansions of each abbreviation or acronym where it first occurs
- Identify primary natural language of document.
Report 5
Guideline 5: Create tables that transform gracefully.
Original Source: http://www.w3.org/TR/WAI-WEBCONTENT/#gl-table-markup
Standard Summary
Typically tables should be avoided in website design, particularly for structural layout purposes. Tables are difficult for screen readers and other devices to comprehend, and may cause problems for some users if not presented correctly. However there are times when table use is appropriate for Web site design. If data needs to be presented in a logical fashion, there is correct markup that will allow users with agents to read the tables.
How the standard must be implemented
- Identify row and column headers
- Use markup to associate data and header cells
- Do not use tables for layout. Provide alternative equivalents for data that does not make sense.
- If a table is used for layout, do not use any structural markup for the purpose of visual formatting.
- Provide table summaries.
- Provide header label abbreviations.
Report 6
Guideline 6: Ensure that pages featuring new technologies transform gracefully.
Original source: http://www.w3.org/TR/WAI-WEBCONTENT/#gl-new-technologies
Standard Summary
Using new technology can be good, but it is important to consider people who use old browsers and have newer features turned off. As a content developer, it is important to make sure that pages created with new technology are compatible with older browsers.
How the standard must be implemented
- Documents should be readable without stylesheets.
- When content changes, update content equivalents.
- Make sure pages work when not supported or when features are off. Otherwise, give alternative information on another accessible page.
Report 7
Guideline 7: Ensure user control of time-sensitive content changes.
Original source: http://www.w3.org/TR/WAI-WEBCONTENT/#gl-movement
Standard Summary
Because some users may not be able to view or comprehend moving or dynamic text, it is important that the content of your page not be displayed in such a manner unless it can be controlled by the user. Remember that moving, blinking or scrolling objects should have the ability to be stopped or paused to suit the user’s preference.
How the standard must be implemented
- Avoid flickering or blinking screens when users can’t control the content behavior.
- Content movement should be avoided until user agents are more effectively adapted to control content.
- Do not use auto-refreshing or re-directing pages until user agents have the ability to stop it from doing so.
Report 8
Guideline 8: Ensure direct accessibility of embedded interface to users.
Original source: http://www.w3.org/TR/WAI-WEBCONTENT/#gl-own-interface
Standard Summary
Interfaces must be functional without dependence on outside devices. If the interface is not accessible, an additional alternative must be made available.
How the standard must be implemented
- Make elements suited for assistive technologies.
Report 9
Guideline 9: Design for device-independence.
Original source: http://www.w3.org/TR/WAI-WEBCONTENT/#gl-device-independence
Standard Summary
Make pages compatible for a variety of input devices. Users may not have access to all devices and may not be able to access elements on a site without them.
How the standard must be implemented
- Provide client-side image maps
- Make sure all elements have their own interface and work free from devices
- Links, form controls, and objects should be ordered logically
- Use keyboard shortcuts
Report 10
Guideline 10: Use interim solutions
Original source: http://www.w3.org/TR/WCAG10/#gl-interim-accessibility
Standard Summary
Assistive technology and old browsers should have the ability to function correctly and read links and navigation properly. For this reason, it is important to use temporary solutions to allow accessibility for users who may be unable to access them on their own.
How the standard must be implemented
- Do not use pop-ups or change windows.
- Ensure labels are positioned properly.
- Provide linear alternatives for side-by-side text
- Use default place-holding characters
- Include non-link, printable characters between bordering links
