Carolyn MacLeod explains how accessibility considerations in the HTML specification connect developers to ARIA rules and accessibility API mappings. Explore how HTML elements, roles, states, and properties are mapped to support accessible web development and assistive technology.
Tag: aria
Accessible Rich Internet Applications (ARIA) can make dynamic, interactive web experiences more accessible when used correctly, but it can also introduce barriers when applied unnecessarily or incorrectly.
This collection of 24 Accessibility articles explores Accessible Rich Internet Applications from practical and strategic perspectives, covering roles, states, properties, widgets, assistive technology support, common implementation mistakes, and the relationship between ARIA and semantic HTML. Whether you are a developer, designer, accessibility specialist, or product professional, these articles provide practical guidance for using ARIA to create more inclusive, robust, and accessible digital experiences.
<select> Your Poison Part 2: Test All the Things
In “<select> Your Poison Part 2,” Sarah Higley tests native select, combobox, and multi-select patterns with people using assistive technologies. The study shows why native selects generally provide the best single-selection experience, while custom controls require careful design and real-user testing.
<select> Your Poison
Sarah Higley explores the challenges of building accessible custom select controls, comparing native <select> behavior across platforms with ARIA combobox and listbox patterns. The article examines semantics, keyboard interaction, multi-select, autocomplete, and the accessibility tradeoffs of custom UI.
Building an Accessible Bingo Web App
Cordelia McGee-Tubb explains how she built an accessible bingo web app with React and Firebase, using ARIA grids, keyboard navigation, toggle states, live regions, responsive design, and user testing to create an inclusive experience for keyboard, touchscreen, and screen reader users.
8 Weird Tips Accessibility Specialists Don’t Want You to Know!
Erik Kroes exposes 8 misguided accessibility tips with humor, challenging common assumptions about WCAG, ARIA, automated testing, focus indicators, accessible alternatives, and inclusive design. Learn why meeting technical requirements is only part of creating truly accessible digital experiences.
Read 8 Weird Tips Accessibility Specialists Don’t Want You to Know! …
Taking Accessibility Beyond Compliance
Dennis Deacon explores why WCAG Level AA compliance should be a starting point, not the finish line. The article examines headings, link text, focus indicators, abbreviations, and other areas where going beyond minimum requirements can create more usable and accessible digital experiences.
Web Components and the Accessibility Object Model (AOM)
Léonie Watson explores the accessibility challenges of Web Components and how the Accessibility Object Model (AOM) could address them. Discover how AOM features such as default semantics, ARIA reflection, assistive technology events, and virtual accessibility nodes could make accessibility first-class.
Read Web Components and the Accessibility Object Model (AOM) …
ARIA 1.1 – What’s New?
In today’s article, Birkir Gunnarsson tells us what’s new in ARIA 1.1, the new roles and properties that excite him, and the others that disappoint, due to their lack of support.
A Developer’s Guide to Better Accessibility
Melanie Sumner and Sean Massa explain how developers can build more accessible web applications through semantic HTML, appropriate ARIA, keyboard support, accessible names, automated testing, and screen reader testing, while integrating accessibility into their teams and development communities.
Providing Alternate Content for Screen Reader Users
Sam Joehl explores techniques for providing equivalent content to screen reader users when visual information lacks a direct programmatic alternative. The article covers visible alternatives, ARIA, visually hidden text, and choosing appropriate techniques to create more accessible web experiences.
The Three Developers and the Insightful User Tester
Scott O’Hara uses a Three Little Pigs-inspired story to show how developers can create accessibility barriers through poor HTML, CSS, JavaScript, and ARIA choices. He highlights semantic HTML, keyboard access, accessibility testing, and learning from users with disabilities.