Explore practical, intermediate-level digital accessibility guidance for improving websites, applications, and digital experiences. This series goes beyond accessibility basics to examine WCAG, accessible design and development, testing strategies, assistive technology, and real-world accessibility implementation.
HTML is often underestimated – it isn’t complicated and it isn’t strict, and you can start producing results with just a handful of elements. It isn’t creative like CSS, or energetic like JavaScript, but it quietly teams up with the browser to make a lot of the web work – much more than many people […]
Read Web Components and the Accessibility Object Model (AOM) …
In the last article for the 2018 series, Steve Faulkner provides the results of one beer worth of screen reader testing of simple tables.
In today’s article, John Sweet describes how captchas have been viewed as a complete barrier to access for individuals with disabilities but with Google’s latest reCaptcha solution, access has taken a major, positive leap forward.
In today’s article, Zoë Bijl explains how it’s easier for users to enter a phone number or a credit card number into a single field, but other scenarios may require properly labeled multiple fields.
Read Benefits of a Single Text Field Versus Multiple Text Fields …
In today’s article, Eric Bailey explains why developers need to consider accessibility when creating custom web components and use semantic HTML when it makes sense, as to not needlessly reinvent the wheel.
In today’s article, Jennifer Dailey explains how the iOS Accessibility Properties relate to the WCAG 2.0 success criteria 4.1.2: Name, Role, Value, and how to properly use them.
Read iOS Accessibility Properties: How They Relate to WCAG, and How to Correctly Use Them …
In today’s article, Hampus Sethfors uses a switch control for a day and shares his discoveries and insights, while encouraging you to give it a go.
In today’s article, Manuel Matuzovic shares how he ditched his mouse, going keyboard-only. He shares the results of his research on 200 different pages and the issues that impact keyboard-only users.
In today’s article, Glenda Sims addresses the value in obtaining Accessibility Professional Certification, what it takes to become an accessibility professional and how the supply of accessibility professionals has yet to keep up with the demand.
Diane Ko and Julia Fu explain how Airbnb scaled Android accessibility by building accessibility expertise across engineering teams. They share lessons on TalkBack, custom views, reusable components, accessibility training, automated enforcement, page titles, and testing with blind users.
Wilco Fiers explains how W3C ACT Rules can harmonize accessibility testing tools by establishing shared, transparent testing methods. The initiative helps organizations understand differences between automated tools, create consistent WCAG interpretations, and establish reliable testing baselines.
Steve Barnett and Nicola du Toit explore disability as a spectrum rather than a binary, showing how abilities and environmental barriers interact. They explain how inclusive design practices, including plain language, keyboard accessibility, and color contrast, can make digital experiences better for everyone.
Gerard Cohen explores how to build accessible and usable calendar widgets. He covers efficient date selection, keyboard navigation, semantic controls, accessible labels, screen reader feedback, and responsive design, offering practical guidance for creating better calendar experiences for everyone.
Eric Bailey explains how to build a cloud-hosted Windows computer with Amazon WorkSpaces for accessibility testing. The guide addresses barriers to Windows access, explains why browser testing services may be insufficient, and provides step-by-step instructions for creating a virtual accessibility testing environment.
Read How to Build a Cloud-Hosted Accessibility Testing Windows Computer using Amazon WorkSpaces …
Marcy Sutton explains how automated accessibility testing can strengthen development workflows, prevent regressions, and free teams for complex testing. She explores unit and integration tests, keyboard interactions, axe-core, and why automation must complement manual and user testing.