The language we use to talk about accessibility is very different from the language most developers and designers use when designing websites, building websites, or building applications. This language barrier is closely related to why accessibility is often missing from most development lifecycles.
This document is designed to help translate accessibility barriers and challenges into language that developers and designers can understand. If we can present accessibility issues in ways that can be understood, that means the appropriate actions can be taken to resolve and eliminate them.
We will start by breaking down some of the technology including the Document Object Model and the Accessibility Tree. Then we will dive into the assistive technology side of things and how we can explore the back end (code) behind the website or app. We will wrap things up by going over some of the most common accessibility issues, how to report accessibility issues using common language, and where our feedback should be sent to ensure it reaches the right person.
Following this guide will help drive the change towards a more accessible, equitable, and inclusive online experience for everyone, regardless of the technology, user settings, or assistive technology in use.