WebAIM - Web Accessibility In Mind

September 2025 Newsletter

Upcoming WebAIM Events

Resources

Testing Methods: Resize Text

WCAG 1.4.4 Resize Text is a Level AA conformance level Success Criterion. Users must be able to resize text up to 200% of its original size without loss of content or functionality.

Add an Accessibility Nutrition Label

Apple is about to drop Accessibility Nutrition labels on the App Store, offering users transparency about which accessibility features apps support. I’ve just completed an audit for one of these labels. Here’s what I learned.

Focus on the people that make things happen

Buy-in from the top makes things easier, but isn’t a prerequisite for building accessible digital products. The people who do are the ones that make the difference.

How to Create an Accessible Table with Clickable Rows

Tables on websites usually display static information in rows and columns. But what if you want to make the rows clickable, e.g., to show more information about the thing that the row is about?

Making Content Accessible for People with Limited English Proficiency

This article explores how thoughtful content and inclusive design can make digital experiences more accessible for people with limited English proficiency.

Accessibility Statements are not Legal Contracts. They're Value Signals.

Accessibility statements help users understand where a company stands, and how they can speak up when something’s broken.

Why does big tech not run Accessibility bug bounties?

The biggest names in tech, from Google to Netflix, invest millions paying ethical hackers, also known as researchers, to find vulnerabilities. So why not for Accessibility bugs?

Understanding Focus Indicators for Web Accessibility

Master focus indicator design for web accessibility. Learn WCAG-compliant techniques for clear visual feedback and keyboard navigation.

A11y 101: 2.4.3 Focus Order

Only active controls should be in the focus order. Static content should never be, unless it is receiving it via JavaScript for a page jump. Focus order should follow the language’s reading order. But it will also follow the code order.

How to make complex data accessible for users with disabilities

How you present data shapes how people understand it and ultimately act on it. Simple data can often be conveyed in a straightforward list or table, but complex data needs more. Sharing data requires careful consideration to ensure it is accessible to users with disabilities.

WCAG 3 September 2025 Update

The Accessibility Guidelines Working Group (AG) has updated the W3C Content Accessibility Guidelines (WCAG) 3 Working Draft.

August accessibility focus: Headings

This is a 101 post on when and how to use the slash content property syntax in CSS to provide alt text for CSS-generated content, and why it is important.

AI1y (AI and A11y) – Part III: Can I Trust AI to Be Right 100% of the Time for Accessibility?

The short answer is no. The better question is: does it matter?

Screen readers do not need to be saved by AI

What needs fixing is the way we, as humans, use language and iconography online. Accessibility is a shared responsibility, and the most powerful tool we have isn't artificial intelligence, it's empathy.

Screen Reader HTML Support – Lookup

A nifty tool for readily checking screen reader support for HTML elements.

Creating a truly accessible Flip Card

This article describes an approach for creating accessible Flip Cards — small blocks of content designed to resemble a playing card or business card, or similar two-sided thing.

Quick Tip: Contrast is About More than Text

While text contrast is important, icons and graphics convey meaning too, so be sure to remember WCAG 1.4.11 (Non-Text Contrast). It applies to icons, graphical objects, and interactive component boundaries that convey meaning. A light grey checkbox against a white background may fail, even if its associated text passes. Non-text contrast requires a contrast ratio of 3:1 or greater, which can be measured with WebAIM's free Contrast Checker.