







With billions of Android devices in use around the world and millions of apps available on the Play Store, it might seem difficult to drive change across the entire ecosystem, but the Accessibility Developer Infrastructure team is doing just that. Every time a developer uploads an APK or app bundle to the open or closed tracks, Play tests this upload on various device models running different versions of Android and generates a pre-launch report to inform the developer of issues. One year ago, the team added accessibility suggestions to the report based on industry best practices and Google’s own experience. These tests check for common issues that can make an app harder to use by people with disabilities. For example, they check that buttons are large enough to be comfortable for people to press, and that text has enough contrast with the background to be easier to read.
Appt.org | A guide for making apps accessible | Appt
Appt.org empowers developers and organizations to build accessible apps for everyone by offering current stats on the use of accessibility features, code documentation for iOS, Android and other platforms, guidelines, tips and how-to's.

Appt.org | A guide for making apps accessible | Appt
Appt.org empowers developers and organizations to build accessible apps for everyone by offering current stats on the use of accessibility features, code documentation for iOS, Android and other platforms, guidelines, tips and how-to's.

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.

Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments
The Department of Justice published a Notice of Proposed Rulemaking (NPRM) on July 20, 2023 explaining how we propose updating the regulations for Title II of the Americans with Disabilities Act (ADA) to add more specific requirements about web and mobile application accessibility. This fact sheet gives a plain language summary of the technical standards that state and local governments would have to follow to meet their existing obligations under Title II of the ADA.
recommended techniques for accessibility champions - A11y Toolkit
An open-source library of techniques to avoid the most common accessibility failures.
The Road to Good Intentions Is Paved with Hell: A Deep Dive into Accessibility APIs, Part 2 — Knowbility
This post is the second in a three-part series about how screen readers obtain what users need from applications and operating systems.

Substrates via Accessibility
The social model of disability holds that disability is produced by environments, not by bodies — that when software fails to accommodate a person’s needs, the environment is disabling them. We argue that the dominant organization of computing produces such interaction mismatches structurally: the commodity form of software requires a standardized consumer, and everyone whose needs diverge from this imagined subject is disabled by the software environment. The substrates research community has identified properties — disclosure, composability, malleability — that would address this, but the commodity form actively selects against these properties because they dissolve the boundaries on which exchange value depends. This raises a question: how can infrastructure organized against the grain of commodity logic be made durable? We find a precedent in accessibility infrastructure — sustained not by patronage but by the organized counter-power of disability rights movements. Through Allio, a system for cross-application augmentation built on accessibility APIs, we illustrate both what this foundation makes possible and where its limits lie. We argue that the accessibility case reframes the substrates programme’s central challenge as political-economic: the question of who sustains substrate infrastructure, and through what social mechanisms, is as important as the question of what properties it should have.
Substrates via Accessibility
The social model of disability holds that disability is produced by environments, not by bodies — that when software fails to accommodate a person’s needs, the environment is disabling them. We argue that the dominant organization of computing produces such interaction mismatches structurally: the commodity form of software requires a standardized consumer, and everyone whose needs diverge from this imagined subject is disabled by the software environment. The substrates research community has identified properties — disclosure, composability, malleability — that would address this, but the commodity form actively selects against these properties because they dissolve the boundaries on which exchange value depends. This raises a question: how can infrastructure organized against the grain of commodity logic be made durable? We find a precedent in accessibility infrastructure — sustained not by patronage but by the organized counter-power of disability rights movements. Through Allio, a system for cross-application augmentation built on accessibility APIs, we illustrate both what this foundation makes possible and where its limits lie. We argue that the accessibility case reframes the substrates programme’s central challenge as political-economic: the question of who sustains substrate infrastructure, and through what social mechanisms, is as important as the question of what properties it should have.
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.

They finally did it: Reddit made it impossible for blind Redditors to moderate their own sub
3.9K votes, 275 comments. Since the latest "accessibility" update to the Reddit app , the amount and magnitude of new accessibility related bugs has…
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.

Ubiquitous Accessibility for People with Visual Impairments: Are We There Yet?
Ubiquitous access is an increasingly common vision of computing, wherein users can interact with any computing device or service from anywhere, at any time. In the era of personal computing, users with visual impairments required special-purpose, assistive technologies, such as screen readers, to interact with computers. This paper investigates whether technologies like screen readers have kept pace with, or have created a barrier to, the trend toward ubiquitous access, with a specific focus on desktop computing as this is still the primary way computers are used in education and employment. Towards that, the paper presents a user study with 21 visually-impaired participants, specifically involving the switching of screen readers within and across different computing platforms, and the use of screen readers in remote access scenarios. Among the findings, the study shows that, even for remote desktop access—an early forerunner of true ubiquitous access—screen readers are too limited, if not unusable. The study also identifies several accessibility needs, such as uniformity of navigational experience across devices, and recommends potential solutions. In summary, assistive technologies have not made the jump into the era of ubiquitous access, and multiple, inconsistent screen readers create new practical problems for users with visual impairments.

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.
The Curb-Cut Effect and the Perils of Accessibility without Disability
By Blake Reid, Published on 01/01/24