Simplifying the Standards
So we know that WCAG Standards exist, and we have the tools to check if our webpages and documents meet these standards--but what about building accessible documents and webpages in the first place? What makes a document or webpage accessible?
As previously mentioned, the WCAG 2.0 standards layout the basics very well. From the Web Accessibility Initiative, we are able to see a very straightforward list of WCAG 2.0 "At a Glance":
Perceivable
- Provide text alternatives for non-text content.
- Provide captions and other alternatives for multimedia.
- Create content that can be presented in different ways,
including by assistive technologies, without losing meaning. - Make it easier for users to see and hear content.
Operable
- Make all functionality available from a keyboard.
- Give users enough time to read and use content.
- Do not use content that causes seizures.
- Help users navigate and find content.
Understandable
- Make text readable and understandable.
- Make content appear and operate in predictable ways.
- Help users avoid and correct mistakes.
Robust
- Maximize compatibility with current and future user tools.
(Above list pulled from the Web Accessibility Initiative website on 8/19/2015.)
Personally, the two that stand out as the easiest to follow or adapt to, but most often overlooked, are document structure and alternative formats. Documents that lack designated headings, paragraphs, and other features are not navigable. A good metaphor for users that aren't low-vision, blind, or otherwise using a screen reader is to imagine trying to navigate multiple, complex plain text emails with no way to search for key words or to scan the page--each word, regardless of importance, must be read. For someone using a screen reader, this is what each unstructured document or webpage encounter is like.
Likewise, imagine being able to watch a video that includes important audio instructions, but you do not have access to speakers or headphones--or you are a member of the deaf and hard of hearing community. It can get pretty frustrating! Including multimedia content without alternative formats (such as captions on videos, transcripts of speeches and songs, alt tags for images, or descriptive text for diagrams) is not accessible, period.
For the purpose of this blog, I will be breaking down the different techniques to create accessible documents through several types of files and web options: Microsoft Office (including Word, Powerpoint, and Outlook), PDFs, HTML, among others. Each post will focus on easy techniques for less experienced users, but will include links to resources that go even further for advanced users.
