A11y

Part 1 of this series focuses on the way screen readers read (or don't read) punctuation and typographic symbols.

Karl Groves-Sandbox

This document is a practical guide for developers on how to add accessibility information to HTML elements using the Accessible Rich Internet Applications specification [WAI-ARIA-1.1], which defines a way to make Web content and Web applications more accessible to people with disabilities. This document demonstrates how to use WAI-ARIA in [HTML51], which especially helps with dynamic content and advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies.

Landmarks can be quite useful to people who use screen readers, as they can be used to help orient someone to, and help navigate, a properly structured websi...

Scalable Vector Graphics (SVGs) have been around since 1999, but they have seen a real resurgence in use as design interactions have become more complex Let's focus on the accessibility of Scalable Vector Graphics (SVGs) by diving into the basics and code examples.

In September of 2017 Gerard K. Cohen of Unfettered Thoughts posted an article on the how VoiceOver and Safari (Webkit) (macOS and iOS) remove list element se...

Related Other posts in this accidental series: Layout as a Clue to Semantics Display: Contents Is Not a CSS Reset Tables, JSON, CSS, ARIA, RWD, TLAs… Tables, CSS Display Properties, and ARIA A Responsive Accessible Table Hey, It’s Still OK to Use Tables When I presented my talk CSS Display…

Remove list styles in CSS without preventing VoiceOver from announcing them in Safari - jonathantneal/postcss-list-style-safari-fix

You may think of layouts has being a primarily visual concern. Let's rethink that.

Ihr Ansprechpartner für digitale Barrierefreiheit! Barrierefreie Websites, Zertifizierungen, WCAG, Web Content Accessibility Guidelines, Accessibility Reviews, Accessibility Audits, Accessibility, E-Accessibility, Inklusion, Inclusion, eInclusion

Shows how different WAI-ARIA attributes behave in commonly used screen readers

Many web pages today have their content dynamically changed using Javascript. An example of this is the search page on this blog. When the page is initially loaded, the only content in the section of the page is a search form. But, when you type in a

Eric Bailey explains why developers need to consider accessible web components in their work, and not to needlessly reinvent the wheel.

Animated interfaces can cause headaches, nausea, dizziness, and other health problems for many people. The most affected groups are people with vestibular disorders, epilepsy, and migraine...

Accessibility is an Adopter’s Job Too, and They’ve Got Work To Do

Alan Dalton reaches for the glistening box of accessibility guidelines under the tree and unwraps them, taking his time to explain each carefully as he does so. Born unto you is a new guideline, and its name shall be called WCAG.

In today's article, Denis Boudreau explains that web accessibility is hard, complicated and you don’t need to care about all of that WCAG stuff.

Manuel Matuzovic shares how he ditched his mouse, going keyboard-only. He shares the results of his research and the issues that impact keyboard-only users.