A11y

An examination of how aria-label behaves on static elements across browsers, and why real-world support differs from common assumptions.

A long time ago (2008) I wrote an article: Screen Readers lack emphasis. At the time, 15 years ago, the screen readers tested did not signify the semantics of text level elements and did not signify, by default, font styles associated with such elements. Notes: I am not suggesting either behaviour is required or desirable. […]

Outline: Feature Queries Proprietary, or Internet Explorer Only Standards Track, or Edge Only Frankenquery’s Monster System Colors CSS2 System Color Keywords WHCM Proprietary Feature Query Color Mappings CSS4 System Color Keywords Browser Support Internet Explorer Legacy Edge (Ledgacy) Chromium Edge (Chromiedge) Firefox Chrome Examples Backgrounds Inline SVGs SVGs via imgs…

ARIA provides an attribute which allows to hide elements from screen readers. It works pretty uniformly on non-focusable elements in modern browsers and screen readers, but it still has some very odd peculiarities. So you better try to create solutions that do not need it.

Accessibility resources free online from the international standards organization: W3C Web Accessibility Initiative (WAI).

Beispiele, wie die Information zur Barrierefreiheit für Websites, Apps und Hardware-Produkte aussehen könnte. Außerdem ein umfangreicher Bereich mit Fragen und Antworten zum Thema.

A collection of bad practices in HTML, copied from real websites.

Die Anforderungen an barrierefreie IT sind vielfältig und lassen sich in verschiedensten Standards, Normen, Verordnungen und Gesetzen wiederfinden. Umsetzerinnen und Umsetzer stoßen dabei zwangsläufig auf den Begriff der "unverhältnismäßigen Belastung" im Behindertengleichstellungsgesetz (BGG). Doch was bedeutet „unverhältnismäßige Belastung“ in diesem Zusammenhang und wann greift diese Ausnahmeregelung?

I’ve written about why we probably shouldn’t use header elements for headings, but what should we use instead? The hgroup element is back!

Automation misses most issues, and can make teams think they’re done

A woman standing at a whiteboard in front of numerous pieces of paper and sticky notes, displaying a design that incorporates sticky navigation. “Sticky...

Verify the contrast between the foreground and background colors of text and graphic elements on any webpage, software or PDF. Simply use the pipette tool or type in your HEX code.

BAAT allows you to perform automated accessibility tests, even when installing additional software or plug-ins is not possible. It is suitable for any organization dedicated to developing accessible websites.

Master ARIA live regions for inclusive web experiences. Discover implementation best practices and practical examples.

Master NVDA keyboard shortcuts for web developers. Navigate content, test forms, and build more accessible websites with this essential guide.

Leichte Sprache ist besonders wichtig, damit alle Menschen die gleichen Informationen erhalten. Wir geben Ihnen nützliche Tipps und Informationen!

Die Leichte Sprache hat besondere Regeln. Wir wollen Ihnen diese Regeln erklären.

Dieses Wörter-Buch erklärt schwere Wörter. Die schweren Wörter sind zum Thema: Digitale Barriere-Freiheit, Informations-Technik (IT) und Behinderungs-Arten von Menschen

Prüftools können nützliche Helfer sein und die Lesbarkeit von Texten auf quantitativer Ebene überprüfen.

Inhalte in und über Leichte Sprache

Seit der BITV 2.0 sind Leichte Sprache für Internetauftritte öffentlicher Stellen verpflichtend. Doch, was ist Leichte Sprache? Wie grenzt sie sich von Einfacher Sprache ab?

Accessibility resources free online from the international standards organization: W3C Web Accessibility Initiative (WAI).

The Inclusive Design Principles (IDP) were first published in 2016 by myself, Ian Pouncey, Léonie Watson, and Heydon Pickering. We felt that while the Web Content Accessibility Guidelines (WCAG) set out what to do to meet technical compliance, many design decisions fall outside the scope of WCAG but still determine whether an interface is inclusive, usable, and welcoming. The principles were developed to plug that gap with people-centred guidance that helps teams make better design decisions without adding unnecessary complexity. In this post, we'll look at who the principles are for, what they can be applied to, how they help people, and how you can integrate them into your own practices.

A collection of bad practices in HTML, copied from real websites.