Developing Organization 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.

1. 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.
2. All multimedia content with meaningful dialogue must have captions (video) or a transcript (audio).
3. Content with meaningful sections or topics must be structured using properly sequenced HTML headings.
4. If a series of items looks like a list, use proper list markup to format those items.
5. 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>).
6. 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.
7. Ensure that the cursor’s focus is easily visible when navigating through elements of the page with the Tab key.
8. When using colour to represent meaning, ensure that something other than colour also represents that meaning.
9. 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.
10. Ensure that all features that operate with a mouse, also operate with a key press.
11. Provide ways to skip past repetitive content using bypass links and ARIA landmarks.
12. Ensure that link text describes what would be found if the link were followed.
13. 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.
14. Ensure that all form fields are explicitly labelled using the HTML Label element.
15. Ensure that all functional elements whose operation is not immediately obvious, includes instructions on how to use them.
16. Describe the accessibility features of an application or website, and position a link to those details in the interface that will be easy to find for assistive technology users.

Web Content Accessibility Guidelines

The Web content accessibility guidelines will be very similar to those for web development listed above, though differing in that content typically tends to be less interactive than a user interface. As such, these guidelines focus more on the accessibility aspects of content.

1. 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.
2. If images cannot be effectively described in alt text of 125 characters or less, provide a full description in the surrounding text, with a short description and a reference to the full description in the alt text.
3. Avoid using images of text, and where unavoidable, reproduce the meaningful text of the image as actual text in the image’s surroundings.
4. All multimedia with meaningful dialogue must have captions (video) or a transcript (audio).
5. Content with meaningful sections or topics must be structured using properly sequenced HTML headings.
6. If a series of items looks like a list, use proper list markup to format those items.
7. When using colour to represent meaning, ensure that something other than colour also represents that meaning.
8. 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.
9. 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>).
10. Ensure that all form fields are explicitly labelled using the HTML Label element.

PDF Accessibility Guidelines

PDF accessibility guidelines are similar to web content accessibility guidelines, though there are PDF specific requirements such as reading order, reading language, and document tagging that also need to be addressed to create an accessible PDF. Documents are typically created with Microsoft Word, saved as a PDF, then opened in Adobe Acrobat Pro to adjust the document’s accessibility.

1. When creating a Word document to be converted to PDF, use proper headings to organize sections/topics in the document.
2. When creating a Word document to be converted to PDF, ensure all images have alt text describing the meaningful elements of the image.
3. When creating a Word document to be converted to PDF, ensure that any document with data tables have the “Repeat as header row at the top of each page” option checked in the table properties.
4. Use the Windows version of Word 2010+ to save Word documents as PDF with the “Document structure tags for accessibility” option checked when saving. (This is not supported on Macs.)
5. Use the Make Accessible tools of the Action Wizard in Adobe Acrobat Pro 11+ or Acrobat Pro DC to assess the accessibility of the converted Word document, and make accessibility adjustments.
6. Use the Reading Order tool in the Acrobat Pro toolbar on the left to arrange the elements in the PDF in a logical reading order.