Accessible Web Design: What It Means and How To Comply

There’s been a lot of talk about digital accessibility lately. Much of this talk comes in response to a lawsuit against Domino’s Pizza, who was recently sued for their website not being accessible enough and failing to meet ADA standards. All the buzz is causing many companies to take a closer look at their own products, to ensure they comply with standards and offer fair access to all users.

Accessibility In A Digital World

Accessibility refers to whether or not a product is usable by someone with disabilities, which today is nearly 20% of the US population. Digital accessibility can refer to any digital technology type, but is commonly used to describe websites or applications. Company W3 describes web accessibility specifically as meaning “websites, tools and technologies are designed and developed so that people with disabilities can use them.” They go on to further stipulate that all must be able to understand, navigate, and interact with these sites. W3C, an international community that collaborates on web standards, offers Web Content Accessibility Guidelines to provide a universal standard for web content accessibility. These guidelines include information (text, images, sounds) and code or markup that defines structure or presentation.

Despite efforts, many sites do not meet these standards for accessibility in web design. Companies struggle to understand how to create accessible products and platforms, as well as what obligations, both moral and legal, they have to do so. Additionally, frequent updates and changes make things difficult, as do associated development costs.

Web Accessibility Checklist

The following checklist is designed as a resource for product managers or product owners. It provides web accessibility guidelines to help guide development teams in building with accessible standards. It can also be used to help determine if pre existing software meets requirements or not. When designing new software, it’s important to build accessibility in up front, to ensure it makes its way into the timeline and budget from the start.

Web Accessibility Guidelines

Alternatives

Ensure all media types - text, video and audio - include alternate ways to be consumed.

• Alternative text for images
• Transcripting and/or closed captioning for videos
• Descriptions for media
• Visual cues and format options in addition to audio files, plus show sounds functionality

Presentation

Ensure websites are built in a logical way, and use appropriate HTML elements and markup.

• Website structure and content in logical order
• Attention to the use of color and contrast in differentiation and navigation
• Text resizing
• Images as text
• Appropriate audio controls and sensory characteristics
• Logical tabbing order
• Descriptions and labels for screen elements, placed nearby
• Orientation

User Control

Ensure all users are able to navigate and approach the site in an accessible manner.

• Option for keyboard only and no keyboard trap, keyboard equivalents for mouse actions, and documentation for keyboard functions
• Tme considerations including adjustable time and pause/stop/hide
• Less than three flashes and option to remove patterns or flashing elements
• “Skip navigation” link

Understandable

Ensure the software is understandable to any user by including multiple ways to access information.

• Link anchor text
• Use descriptive headings and labels
• Include focus indicator
• Accommodate language and language changes

Predictability

Build software or sites in a way that is predictable to the end user.

• No focus change, no input change
• Consistent navigation and identification
• Error identification, suggestions and prevention on important forms
• Form labels and instructions
• Parsing and name/role/value

Documentation and Testing

It’s also important to include manuals and documentation in electronic format and as an ASCII text file. Then, once you’ve built your software, it’s essential to test and ensure it meets the standards desired. It’s always helpful to conduct tests using common assistive technologies, such as screen readers. Don’t forget to check on different devices, and include tools such as screen enlargement or voice recognition software.

Check out our full accessibility checklist for more details and a full list of items to consider.

Download the Accessibility Checklist