Accessibility Guidelines
Web accessibility means that websites, tools, and technologies are designed and developed so that people with disabilities can use them. Web Content Accessibility Guidelines (WCAG) 2.1 define how to make web content more accessible to people with disabilities. The video below from W3C provides a good summary of web accessibility.
The following guidelines are based on the W3C’s Web Content Accessibility Guidelines (WCAG) 2.1, but is not a substitute for the WCAG specification. It was created to assist the TCS community, including web designers, developers, content creators, and purchasing agents, in creating accessible content and procuring accessible applications. Our intent in creating it is to present accessibility information in a way that we feel is easier to understand.
It is organized loosely using the four main principles of WCAG. In order to be accessible, content must be perceivable, operable, understandable, and robust (POUR). Many of the items in these guidelines apply to multiple technologies (e.g., websites, documents, videos, online courses, online meetings).
The four main principles of accessibility are:
Perceivable: Makes content and controls perceivable by all users.
- Do headings form an outline of the page content?
- Are lists used to identify all content that can be described as a list of something?
- Are common regions of the web page properly identified (e.g., as banner, main content, or navigation)?
- Does video have captions and audio description? Does audio have a transcript?
- Do form fields within web pages and documents have appropriately coded labels and prompts, and do they provide helpful, accessible error and verification messages?
- Do images have alternative text?
- Are tables used solely for presenting rows and columns of data (not for layout), and are the column and row headers identified?
- Is the tab order and read order logical and intuitive?
- Have you avoided using visual characteristics to communicate information (e.g., “click the circle on the right” or “required fields are in red”)?
- Does the interface have sufficient contrast between text color and background color?
- Does the content scale well when text is enlarged?
- Are pop-ups such as menus, dialogs, and tooltips accessible?
- Is content accessible on mobile devices?
Operable: Make content and controls operable by all users.
- Can all menus, links, buttons, and other controls be operated by keyboard, to make them accessible to users who are unable to use a mouse?
- Are links and buttons used appropriately and labeled correctly?
- Does the web page or document have a title that describes its topic or purpose?
- Are mechanisms in place that allow users to bypass blocks of content (e.g., a “skip to main content” link on a web page or bookmarks in a PDF)?
- Do features that scroll or update automatically (e.g., slideshows, carousels) have prominent accessible controls that enable users to pause or advance these features on their own?
- Do pages that have time limits include mechanisms for adjusting those limits for users who need more time?
- Have you avoided using content that flashes or flickers?
Understandable: Make content and user interfaces understandable to all users.
- Has the language of the web page or document (or individual parts of a multilingual document) been defined?
- Have you avoided links, controls, or form fields that automatically trigger a change in context?
- Does the website have consistent navigation, including two or more ways of finding content?
Robust: Make content robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
- Is the web page coded using valid HTML?
- Do rich, dynamic, web interfaces include ARIA markup?
What are the benefits of web accessibility?
Web accessibility benefits all users, including those without a disability. Web Accessibility Initiative (WAI) has great resources showing how accessibility benefits everyone. Web Accessibility Perspectives: Explore the Impact and Benefits for Everyone.