Integrate accessibility testing into your existing automated testing process with Axe DevTools. Toolkits available for web, iOS, and Android.
recommended techniques for accessibility champions - A11y Toolkit
An open-source library of techniques to avoid the most common accessibility failures.
Playwright Accessibility Testing: What axe and Lighthouse Miss
axe and Lighthouse miss 60–70% of WCAG violations. Learn the limitations of automated accessibility testing and how to write smarter Playwright tests.
lukeslp/awesome-accessibility
Curated list of accessibility resources, tools, and best practices for creating inclusive digital experiences
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
brief history of browser accessibility support
Author: steve faulkner The Paciello Group contact: [email protected]
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...
Library Guides: Accessibility Toolkit for Open Educational Resources (OER): Home
Accessibility guide for creating OER
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.
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.
WAVE Web Accessibility Evaluation Tools
WAVE® is a suite of evaluation tools that helps authors make their web content more accessible to individuals with disabilities. WAVE can identify many accessibility and Web Content Accessibility Guideline (WCAG) errors, but also facilitates human evaluation of web content. Our philosophy is to focus on issues that we know impact end users, facilitate human evaluation, and to educate about web accessibility.
zats/permiso
Permission dialog for accessibility settings as seen in Codex Computer Use https://x.com/lexrus/status/2044929029334245819
a11y.quest - 128 questions to level up your accessibility game
128 questions to level up your web accessibility game. Practice WCAG 2.2, ARIA, semantic HTML, keyboard, and contrast, with plain-English answers.
Inclusive Design for a Digital World
In this book, readers will learn the Web Content Accessibility Guidelines (WCAG) 2.1 requirements, emerging technologies such as VR and AR, best practices for web development, and implementation of inclusive design. Begin understanding the immense opportunities in designing for accessibility.
Skeleton — UI Toolkit for Svelte + Tailwind
Skeleton is a fully featured UI Toolkit for building reactive interfaces quickly using Svelte and Tailwind.
UI/UX Guidelines - User Experience Design & Technology
The Web Content Accessibility Guidelines (WCAG) are a set of internationally recognized standards for making web content accessible to people with disabilities. Created by the Web Accessibility Initiative (WAI) of the World Wide Web Consortium (W3C), WCAG provides a framework for designing inclusive digital platforms that cater to diverse user needs, including those with visual, auditory, cognitive, and physical impairments.
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.