2 People, technologies, and fundamental techniques
This chapter covers
- Introducing potential users and real-world barriers.
- An overview of adaptive strategies and assistive technologies.
- Challenges with accessibility overlays.
- Establishing the importance of semantic HTML and, if needed, ARIA.
- Leveraging browser support to enhance accessibility.
In the previous chapter, we established what accessibility is and why it matters. We also introduced WCAG as a shared set of guidelines that defines what accessible products are expected to achieve. This chapter shifts focus from laws and standards to people and technologies. We’ll take a closer look at who we’re building for, the real-world barriers they encounter, and the strategies and technologies they use to overcome them. Understanding these realities helps us make informed engineering decisions, rather than relying on assumptions or quick-fix solutions. We will explore why accessibility plugins and overlays often fall short, why plain, semantic HTML provides a substantial level of accessibility out of the box, and when ARIA is beneficial (and when it isn’t). We’ll also examine how browsers interpret your code and communicate it to assistive technologies. This knowledge becomes especially important when working with complex interfaces or legacy systems, as it directly impacts users.
Let’s get started then.