Why Accessibility Shouldn’t Have to Rely on Batteries
How the Components of Web Accessibility Benefit My Mouse and Everyone Else
Are you a creator of web content? Have you ever considered what components are involved in making the web accessible? Do you even know what components and web accessibility are?
No judgment if you haven’t because let’s be honest, it can be a real head spinner.
So what exactly are components and web accessibility?
Web accessibility isn’t just for people with disabilities. In this day and age, designers and developers create for so many technologies, from smartwatches, smart TVs, smart cars, to tablets, and more, we need to make sure that when we’re designing for these products, they’re accessible for the device that they are compatible with, not just for people with disabilities. As designers and developers, we need to consider the barriers to accessing and interacting with websites, tools, and technologies. Accessibility is for all, it enables people to perceive, understand, navigate, interact, and contribute to the web.
Don’t make me look for batteries!
A perfect example (maybe you can relate)! I have two teenage boys, and I’m starting to think they just eat batteries. No, seriously, they go through batteries like they go through cereal. Anyway, there have been multiple times I’ve sat down at my computer and my mouse isn’t working. I check the Bluetooth connection every time, although I already know that one of my boys robbed my mouse of its life. At this point, it’s just more efficient to utilize my keyboard to navigate than it would be to find more batteries, but it becomes extremely difficult when sites are not keyboard accessible. I bet you can guess my only option in order to get my work done. If you thought scavenger hunt, call yourself a winner!
This example applies to someone who may use assistive technology or rely on a keyboard only. Just follow the WCAG guideline 2.1 for keyboard accessibility and no creator will leave a user behind.
If you’re interested in taking a deep dive into the accessibility principles, W3C has your back. Deep dive here.
Components
Now that you have a good understanding of what web accessibility is, I need to bring you up to speed on that other part… Components!
No, no, not those components, the components I’m talking about are the ones web accessibility depends on to work together to make this possible. But what are components?
The components of web accessibility are content, user agents, assistive technology, users, authoring tools, and evaluation tools.
Here are some definitions of the different components:
Content is the information on a web page or web application, such as text, images, sounds, code, or markup that defines the structure.
User agents include browsers, browser extensions, media players, readers, and applications that render content.
Assistive technology can include screen readers, alternative keyboards, switches, and scanning software, to name a few.
Users are people who create web content and people who use the web. People who create web content include developers, designers, authors, or anyone involved with developing content. People who use the web all have different knowledge bases and experiences.
Authoring tools are services and software used to create and edit websites.
Evaluation tools are used to ensure the websites meet the W3C standards.
Great stuff, right! But what exactly does this mean?
Alternative Text
In order for the web to be accessible, the components need to work together. I know, I keep saying they need to work together and haven’t given you anything to connect the pieces yet. Well, thanks to the wonderful Web Accessibility Initiative (W3C) they’ve provided us the components necessary to render alternative text.
Technical specifications address alternative text
WAI guidelines define how to implement alternative text for accessibility in the different components
Developers provide the alternative text wording
Authoring tools enable, facilitate, and promote providing alternative text on a web page
Evaluation tools are used to help check that alternative texts exist
User agents provide human and machine interface to the alternative text
Assistive technologies provide human interface to the alternative text in various modalities
Users know how to get the alternative text from the user agent and assistive technology as needed
The Web Accessibility Initiative (W3C) gives us a visual example of the myriad components involved in rendering alternative text:
In Conclusion
If you want to ensure that anyone and everyone can easily locate, navigate and understand the content or services you are providing, be kind and keep this in mind. Also, I won’t have to look for batteries! I’ll be able to use my keyboard to its maximum when my kids steal my mouse batteries.
Guidelines and standards developed by W3C can be found below:
Authoring Tool Accessibility Guidelines (ATAG) — addresses authoring tools
Web Content Accessibility Guidelines (WCAG) — addresses web content, used by developers, authoring tools, and accessibility evaluation tools
User Agent Accessibility Guidelines (UAAG) — address web browsers and media players, including some aspects of assistive technologies
Accessible Rich Internet Applications (ARIA) — defines a way to make applications more accessible to people with disabilities.
