A11y

Accessibility isn’t just a legal requirement—it’s a fundamental part of inclusive design that ensures everyone, regardless of ability, can access and interact with digital content. If you’re looking to improve the accessibility of your website or application, an accessibility audit is the best place to start. An accessibility audit systematically evaluates a digital product against […]

When was the last time you navigated a website without using your eyes? For millions of people who are blind, have low vision, or experience other disabilities, screen readers provide access to digital content by converting text into speech or braille. Ensuring that your website is fully compatible with screen readers isn’t just a nice-to-have—it’s […]

How I develop software at 800 words per minute with a screen reader

Accessible Rich Internet Applications (ARIA) is one of the most powerful tools in a developer’s accessibility toolkit—but it’s also one of the most misunderstood. While ARIA can improve accessibility when used correctly, misuse can actually make things worse for users who rely on assistive technologies (AT), such as screen readers. So, how do you use […]

With the addition of Gez Lemon to the editing team, work continues on expanding and improving the HTML and screen reader support information.

Testing mobile apps can be difficult, so here are some techniques and tools that will make it easier. Part 1 of a 2-part series looks at iOS apps.

Testing mobile apps can be difficult, so here are some techniques and tools that will make it easier. Part 2 of a 2-part series looks at Android apps.

accessibility-statements - A list of accessibility statements

We're excited to announce the availability, as a developer and origin trial, of ARIA Notify, a new API that's designed to make web content

This document describes how Web Content Accessibility Guidelines (WCAG) 2.2 [WCAG22] principles, guidelines, and success criteria can be applied to mobile applications, including native mobile apps, mobile web apps and hybrid apps using web components inside native mobile apps. It provides informative guidance (guidance that is not normative and does not set requirements).

Complications can arise with JavaScript event handling in screen readers, because the virtual cursor intercepts or modifies page events.

List of WCAG success criteria requiring manual testing

HTML Accessibility API Mappings (HTML-AAM) defines how user agents map HTML [HTML] elements and attributes to platform accessibility application programming interfaces (APIs). It leverages and extends the Core Accessibility API Mappings 1.2 and the Accessible Name and Description Computation 1.2 for use with the HTML host language. Documenting these mappings promotes interoperable exposure of roles, states, properties, and events implemented by accessibility APIs and helps to ensure that this information appears in a manner consistent with author intent.

Für Sehende kann es ab und zu nützlich sein, einen Screenreader einzusetzen, zum Beispiel um Programme oder Webanwendungen zu testen. Natürlich ist es sinnvolle

In diversen Anleitungen wie dem DIAS-Test sehe ich wie nebenbei, dass der Screenreader NVDA für Tester:Innen empfohlen wird. Es ist aber eher zweifelhaft, dass

Understanding the flow of page contents from browser to screenreader caused me to radically rethink accessible markup.

Ein kognitives Modell beschreibt, wie etwas wahrgenommen wird. Um komplexe Objekte verabeiten zu können, benötigen wir eine Repräsentation davon, wie es aufgeba

People new to accessibility often find WCAG conformance levels confusing and unclear about what each level requires.

The output HTML element is an ARIA live region by default.

Eine Auswahl an Bookmarklets, Browser-Erweiterungen und Tools zum Testen von Barrierefreiheit.

ARC Toolkit – Quickly uncover and resolve accessibility issues on any web page with TPGi’s single-page, on-demand, accessibility testing tool

Who doesn’t love emojis? I’m willing to bet that the recent 10 messages you sent or received from different people on your phone, there…

Aspekte der Webseiten-Barrierefreiheit, die getestet werden müssen, und die entsprechenden Features in Microsoft DevTools.

To reach as many users as possible, it's a pragmatic approach to support the most widely used combinations of browsers and screen readers. Here you learn, which those are. Other requirements may only apply in closed environments that are only open to a specific, deterministic group of users.