Accessible Web Design
Web Accessibility Standards and Guidelines
Why standards are important.
Standards and guidelines explain the what, why, and how of making web content accessible. Web content comprised of text, images, sound, video, and other media includes markup languages or code to define structure, presentation, and alternatives for people with disabilities. Accessibility standards and guidelines are documented as follows:
- What: A statement of the access issue to be addressed by the standard and guideline
- Why: Explanation as to why the accessibility issue is important
- How: A short statement of how access can be successfully achieved
- Known Issues: Any known concerns not fully addressed by the standard and guideline
-
AccessVT: guideline reference
WCAG 1.0 guideline reference(s) when applicable
Section 508 standard reference(s) when applicable
Standards and Guidelines and Access Performance Criteria
These include:
- Standards and Guidelines - the procedures that will implement university access policies for web accessibility. These procedures require the use of development and maintenance tools and techniques that validate markup language (coding) and evaluate website accessibility throughout the lifetime of the website or web-based application.
- Access Performance Criteria - a concise list of functional goals that must be achieved for a website or web-based application to be considered accessible.
Individuals with disabilities use a variety of abilities, access techniques, and assistive technologies to utilize web-based information. From a practical standpoint, accessible websites must therefore be compliant with accessibility standards and guidelines, as well as being compatible with adaptive or assistive technologies. From this perspective, the following functional performance criteria can be used to judge whether accessibility is effectively achieved.
All information and functionality presented in a website or web-based applications shall be available in a manner that is:
- Compliant with university supported browsers
- Completely operable with system font sizes and colors set by the user
- Completely operable using a keyboard only
- Completely operable using leading screen magnification software
- Completely operable using leading screen or synthesized speech reading software
- Completely operable using leading speech recognition software
- Completely understandable without sound
- Completely understandable without color
- Clearly and consistently navigable
- Unlikely to trigger photosensitive seizures
External References based on Virginia Tech Access Policies
Standards and Guidelines and Access Performance Criteria are user based and technology dependent and will be updated as user needs and technologies evolve and change. The web technologies that are considered relevant for the current standards and guidelines are aligned with external references that include:
- World Wide Web Consortium (W3C) Web Content Accessibility Guidelines WCAG 1.0 Table of Contents for the W3C Recommendation as of 5-May-1999
- U.S. Access Board Section 508 Web Standards and Guide to the (Full) Section 508 Standards for Electronic and Information Technology
Virginia Tech web accessibility standards and guidelines are designed to comply with the Americans with Disabilities Act (ADA) and Federal Section 508 requirements of the Rehabilitation Act of 1973. Virginia Tech meets and/or exceeds the minimum requirements of WCAG version 1.0 Level "A" conformance by incorporating most "Priority 1" checkpoints and a number of WCAG "Priority 2" and "Priority 3" checkpoints. AccessVT guidelines are also cross-referenced to WCAG 1.0 guidelines and Section 508 standards that have comparable accessibility objectives.
Format of Web Accessibility Standards and Guidelines
Virginia Tech web accessibility standards and guidelines are formatted in two versions. They are:
-
Default Version is organized for reading and printing by section.
Navigation is byTable of Contents
,Quick Reference
, and the use of previous or next section arrows. The default version permits you to focus on and print one section of the university guidelines at a time. Future editions will have interactive training materials. - Booklet Version is organized for reading and printing as one document.
Navigation is byTable of Contents
,Quick Reference
, and byGo to Table of Contents
links. The booklet version can be read sequentially (top-to-bottom) by scrolling or by use of the Go to Table of Contents link at the end of each section. The booklet version can be printed in its entirety.
Navigational note: The use of hypertext links in the Table of Contents and Quick Reference sections will navigate only within their respective versions, default or booklet, unless specified otherwise.
Table of Contents
-
1. Coding
- 1.1 - Use valid, standard web programming code.
- 1.2 - Use the correct DOCTYPE declaration at the top of each page.
- 1.3 - Use appropriate markup to convey document structure.
- 1.4 - Use style sheets for formatting whenever possible
-
2. Text
- 2.1 - Avoid using images to display text.
- 2.2 - Avoid using absolute sizes for fonts.
- 2.3 - Specify the language attribute for all text.
- 2.4 - Avoid using "ASCII art."
-
3. Colors
- 3.1 - Do not convey information with color alone.
- 3.2 - Use contrasting foreground and background colors.
-
4. Images
- 4.1 - Provide "alternate text" for all images.
- 4.2 - Provide full descriptions for graphs, diagrams, and other meaningful images.
-
5. Image Maps
- 5.1 - Provide alternate text for each area in client-side image maps.
- 5.2 - Avoid using server-side image maps.
-
6. Audio
- 6.1 - Do not convey information with sound alone.
- 6.2 - Provide text transcripts for audio containing speech.
-
7. Multimedia
- 7.1 - Provide synchronized captions for multimedia containing speech.
- 7.2 - Provide audio descriptions for multimedia with significant video.
-
8. Animation
- 8.1 - Avoid flickering, blinking, and unnecessary animation.
- 8.2 - Avoid uncontrolled animation and/or loop elements.
-
9. Links
- 9.1 - Make sure that links are understandable out of context.
- 9.2 - Provide a means of skipping past repetitive navigation links.
- 9.3 - Avoid using small images and text as links.
-
10. Forms
- 10.1 - Associate labels with all form fields.
- 10.2 - Position labels as close as possible to form fields.
- 10.3 - Include any special instructions within field labels.
- 10.4 - Make sure that form fields are in a logical tab order.
-
11. Data Tables
- 11.1 - For simple data tables, explicitly identify headings for all columns and rows.
- 11.2 - Avoid using complex data tables.
-
12. Frames
- 12.1 - Provide meaningful names and page titles for all frames.
- 12.2 - Avoid using empty or non-essential frames.
-
13. Scripts
- 13.1 - Make sure that significant interactions can be performed with both keyboard and mouse.
- 13.2 - When client-side scripts are used, make sure that essential content and functionality are available and accessible to assistive technologies...
-
14. Applets and Plug-Ins
- 14.1 - Use accessible applets or plug-ins whenever possible.
- 14.2 - Make sure that essential content and functionality are available when an inaccessible applet or plug-in must be used.
-
15. Downloadable Documents
- 15.1 - Provide accessible versions of downloadable documents whenever possible.
- 15.2 - If a downloadable document cannot be provided in an accessible electronic format, provide information on how to request an alternate format.
-
16. Window Control
- 16.1 - Notify users of actions that will open a new window.
- 16.2 - Do not automatically refresh the current page.
- 16.3 - Notify users of time limits and provide a means to extend time if needed.
-
17. Page Layout
- 17.1 - When using tables for layout, make sure that reading order is logical.
- 17.2 - When using style sheets for layout, make sure that reading order is logical when style sheets are not supported.
- 17.3 - Minimize the need for horizontal scrolling (by using relative widths).
- 17.4 - Utilize pages dimensions that are safe for graphics and printing.
-
18. Page Content
- 18.1 - Use the clearest and simplest language appropriate for a page's subject matter.
-
19. Alternate Accessible Versions
- 19.1 - Use separate accessible versions only as a last resort.
-
20. Contact Information
- 20.1 - Provide contact information.
-
21. Accessibility Testing
- 21.1 - Test for accessibility.
Copyrights and Permissions: Web Content Accessibility Guidelines (WCAG) 1.0 of the Web Access Initiative (WAI) are a product of the World Wide Web Consortium (W3C) Copyright © 1994-2003. Portions of guidelines reproduced with additional permissions from the Commonwealth of Virginia, the State of Illinois, and the State of Maine with W3C Copyright © reserved.
Quick Reference
Virginia Tech
Web Accessibility
Standards and
Guidelines
Version 2007-001
Reference Section:
- Coding
- Text
- Colors
- Images
- Image Maps
- Audio
- Multimedia
- Animation
- Links
- Forms
- Data Tables
- Frames
- Scripts
- Applets and
Plug-Ins - Downloadable
Documents
- Window Control
- Page Layout
- Page Content
- Alternate Access-
ible Versions - Contact Information
- Accessibility Testing
Contact Information
Request for Comments
Send an e-mail to assist@vt.edu