4. Creating Digital Accessibility Culture
Developing Organization Accessibility Guidelines
To ensure consistency in the accessibility of the company’s digital content, the accessibility committee has decided there needs to be a set of simple guidelines staff can follow. You start by creating three guidelines:
- Web Development Accessibility Guidelines
- Web Content Accessibility Guidelines
- PDF Accessibility Guidelines
Web Development Accessibility Guidelines
Though you could just have your developers review WCAG to understand what needs to be done to ensure the company’s presence on the Web is accessible to everyone, there would be a great deal of “interpretation” required, and many aspects of WCAG that may not be relevant. Instead, you may want to identify the specific issues that need to be addressed in the company’s websites, and develop a set of guidelines specific to those issues.
Use the 10 Key Guidelines [PDF] as your starting point. These guidelines can be distilled to create a brief list of issues developers must keep in mind when developing for the Web. These guidelines might be as follows, though depending on the organization, may require minor adapting to fit its needs. They should be easy to learn and memorize.
- All images must have an alt attribute that describes the meaningful elements of the image, or the alt attribute is left empty if the image is decorative or otherwise meaningless.
- All multimedia content with meaningful dialogue must have captions (video) or a transcript (audio).
- Content with meaningful sections or topics must be structured using properly sequenced HTML headings.
- If a series of items looks like a list, use proper list markup to format those items.
- Where data is being presented in a table, the first row (and sometimes the first column) should be formatted as proper table header cells (i.e., <th>).
- Ensure that when navigating through web content using the Tab key, the cursor moves from left to right, top to bottom, and does not veer from that pattern.
- Ensure that the cursor’s focus is easily visible when navigating through elements of the page with the Tab key.
- When using colour to represent meaning, ensure that something other than colour also represents that meaning.
- Ensure that contrast between foreground (text) colours and background colours provide sufficient contrast, at a ratio of 4.5:1 minimum for smaller text, 3:1 for larger text.
- Ensure that all features that operate with a mouse, also operate with a key press.
- Provide ways to skip past repetitive content using bypass links and ARIA landmarks.
- Ensure that link text describes what would be found if the link were followed.
- Ensure that accessible error or success feedback is provided after completing an action such as submitting a form or logging in, typically using the ARIA alert role with the element containing the feedback.
- Ensure that all form fields are explicitly labelled using the HTML Label element.
- Ensure that all fu