Blog

WCAG 3.0 will not replace WCAG 2.x overnight. Learn why organizations will need to manage both standards for years and how to prepare for the transition.

I have a newsletter now. Talking about a variety of topics. And adding illustrations. Please do subscribe.

HelloFresh, a meal service, has switched to relying on AI for creating recipes, generating images of dishes, and preparing packing lists. There's no way to signal food allergies. We're cancelling our subscription.

You don't get a good website or app when you deprioritize accessibility while paying attention to security and performance.

Relying on WCAG isn't enough to ensure accessibility. Conducting usability testing with disabled users is the only way. And is required by regulations such as the European Accessibility Act.

Adding alt text on images you post on social media is important for blind people to access your content. Here's a short guide to help you get started.

User photos and avatars are informational images. Do use clear and concise alternate text to describe them. Otherwise blind screen reader users won't have access to the same information as sighted people.

Morgan's has announced a hotel that is more accessible than required by law. This is encouraging but there are several problems with the claim.

AI cannot fix accessibility until those who program it understand that accessibility is about disabled people, and as long as systemic ableism continues to exist, AI won't be able to fix accessibility.

It isn't an MVP without accessibility - it's just an MP, a Minimum Product. It's not viable...

Transcripts and captions are useful for deaf and hard of hearing people, and many more. Relying on automated, or artificial intelligence to generate them leads to inacuracies.

VPATs are document outlining accessibility of a site or product at a point in time.

Link styling and colors matter if you want your links to be perceived.

Red text often has negative implications. Be careful when you use it.

I explain the difference between headers and headings.

I review the accessibility impact of text in italics, and offer some alternatives.

I deconstruct AccessiBe's apology about toxic communications with the disability community.

I explain some important aspects of using skip links correctly to improve accessibility and usability.

Staff and administrators could be disabled. It's critical for admin dashboards to be accessible. Not just the parts used by consumers.

Complete dev work at least 2 months ahead of client deadlines to give accessibility auditors time to validate your remediation work.

The role menubar is not meant to be used to build navigation on the web. It should be used if you need to copy how menubars work on desktop applications.

Pay people you want working with you. Free accessibility advice isn't good for anyone. Don't be pushy. I won't work with toxic clients!

I argue that accessibility is good for everyone because it helps people embrace accessibility. It doesn't erase the disability experience, if done well.