AccessKit

recommended techniques for accessibility champions - A11y Toolkit

An open-source library of techniques to avoid the most common accessibility failures.

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.

Axe DevTools | Automate accessibility testing

Integrate accessibility testing into your existing automated testing process with Axe DevTools. Toolkits available for web, iOS, and Android.

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.

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.

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.

lukeslp/awesome-accessibility

Curated list of accessibility resources, tools, and best practices for creating inclusive digital experiences

Library Guides: Accessibility Toolkit for Open Educational Resources (OER): Home

Accessibility guide for creating OER

Cracking the cocoa nut: user interface programming at runtime

As part of the Digital Library's transition to Open Access, new features for researchers are available in the Premium Edition. Click here to learn more.

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.

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...

brief history of browser accessibility support

Author: steve faulkner The Paciello Group contact: [email protected]

Digital accessibility is real and tangible

A workshop using real-life examples and first-hand experience of how assistive technology works can result in a deeper understanding of accessibility needs