







We tend to think of performance in terms of latency, code optimization, and things like the critical rendering path, but what happens when the browser creates an accessibility tree as well as the DOM? The answer is of course “it depends...”. Different browsers take different approaches, but they all have an impact on performance and the Time To Interactive in particular. In this talk we’ll consider the purpose of the accessibility tree, the ways its constructed in different browsers, and the ultimate impact that has on both performance and experience for people who use assistive technologies like screen readers. About Léonie: https://tink.uk More about performance.now(); https://perfnow.nl or https://twitter.com/perfnowconf Receive conference announcements in your inbox: https://perfnow.nl/subscribe
A Deep Dive into Accessibility APIs, Part 1 — Knowbility
In this first Deep Dive into Accessibility APIs installment, we'll start from absolute scratch and recount the widely available basic story. It's written for beginners, but the fact that I describe web accessibility in the broader context of software accessibility might offer a different twist for current practitioners as well. Parts 2 and 3, on the other hand, are more technical. Although those discussions may largely be of interest only to "inquiring minds that want to know", understanding the history and variety of the specialized protocols at the heart of this process sheds light on why screen readers sometimes perform differently in the same application or on the same web site while also providing a glimpse of a likely future.

brief history of browser accessibility support
Author: steve faulkner The Paciello Group contact: [email protected]
Foundations: the accessibility tree - TetraLogical
There's a common misconception that when browsing the web using a screen reader, it's reading the actual screen. This is not really surprising, as the name suggests that's exactly what it's doing. And, this is what early screen readers did, so, we can't really blame anybody for thinking that!
Making Content Accessible | Web Browser Engineering
So far, we’ve focused on making the browser an effective platform for developing web applications. But ultimately, the browser is a user agent. That means it should assist the user in whatever way it can to access and use web applications. Browsers therefore offer a range of accessibility features that take advantage of declarative UI and the flexibility of HTML and CSS to make it possible to interact with web pages by touch, keyboard, or voice.
Helping to get everyone in their element
Element is now more accessible by design and by default, thanks to more than 40 accessibility improvements.


A new accessibility architecture for modern free desktops
My name is Matt Campbell, and I’m delighted to announce that I’m joining the GNOME accessibility team to develop a new accessibility architecture. After providing some brief background information on myself, I’ll describe what’s wrong with the current Linux desktop accessibility architecture, including a design flaw that has plagued assistive technology developers and users on multiple platforms, including GNOME, for decades. Then I’ll describe how two of the three current browser engines have solved this problem in their internal accessibility implementations, and discuss my proposal to extend this solution to a next-generation accessibility architecture for GNOME and other free desktops.

A threat model for accessibility on the web - Alice
A explanation of the primary threat to accessibility on the web, and a call to action for the web standards community

Introducing the Accessible Components Library - TetraLogical
We've open-sourced our Accessible Components Library, and, as you might expect, this includes the HTML, CSS, and JavaScript code. But, we thought, "Why stop there?" So, we've also published our documentation, including the accessibility requirements, test scenarios, and even the working automated tests which validate each one.

Usability/UX/Accessability Research? · Issue #819 · w3c-fedid/FedCM
I'm curious if this work has any usability, UX, or accessibility research that supports the designs here? Are there non-goals, or handling of failure case scenarios that have been envisioned an...
GitHub repository landing pages now show an accessibility tab, if provided
I’m excited to see how people use this new addition to the platform.

WebAIM: The WebAIM Million - The 2026 report on the accessibility of the top 1,000,000 home pages
For the eighth consecutive year, WebAIM conducted an accessibility evaluation of the home pages for the top 1,000,000 web sites. The evaluation was conducted using the WAVE stand-alone API (with additional tools to collect site technology and category data). The results provide an overview of and insight into the current state of web accessibility for individuals with disabilities as well as trends over time.
Your Browser May Be Having a Secret Relationship with a Screen Reader: A Deep Dive into Accessibility APIs, Part 3 — Knowbility
The final installment of the three-part saga on the technical details of how screen readers communicate with other software.

Designing for accessibility is not that hard
Seven easy-to-implement guidelines to design a more accessible web ❤️


Building the DOM faster: speculative parsing, async, defer and preload – Mozilla Hacks - the Web developer blog
In 2017, the toolbox for making sure your web page loads fast includes everything from minification and asset optimization to caching, CDNs, code splitting and tree shaking. Understanding what goes ...
