Eric Eggert (@yatil) on web accessibility and more.

Testing with assistive technologies is an important part of any accessibility review.

First things first: Yes, WCAG (the Web Content Accessibility Guidelines) are not easy to read.

A notion that I always hear and have heard for a long time is that meeting the Web Content Accessibility Guidelines (WCAG) feels like not doing enough for accessibility[^ Specimen 1, Specimen 2, Specimen 3, Specimen 4].

I really wished I could sit back and let the whole “AI” frenzy play out without speaking up or getting involved.

It’s no secret: I like the Web Content Accessibility Guidelines.

Craig Abbott wrote about the term “best practice” today.

I frequently see the word “help” used in accessibility, and I don’t like it.

Auf der Seite barrieren-gutachten.de hat die wundervolle Casey Kreer Gutachten zum Stand der Barrierefreiheit in Deutschland erstmals übersichtlich aufgelistet.

The deadline of the European Accessibility Act (EAA) is near (June 28 is just 20 days away as I write this), and you just realized that your website or apps will not meet the requirements by then.

Steve Faulkner tagged me in this chain letter/interview style post, and I foolishly agreed in advance to respond.

Last weekend, I launched WAI A Day, the daily random WAI resource fun and information.

When I worked for W3C’s Web Accessibility Initiative, we often discussed ways to spread the good word of our resources better.

Normally, I reserve these more introspective texts for my newsletter, which I send out occasionally.

In accessibility, “focusable” UI elements are represented by two separate yet equally important concepts: the elements who can be focused sequentially and those who can only receive focus programmatically.

Just to preemptively state it: I appreciate what the Accessibility Guidelines Working Group (AGWG) is trying to do with the “In Brief” sections in WCAG’s Understanding documents.

On Mastodon, Steve Faulkner shared a link to a GitHub discussion around the A, AA, and AAA levels of WCAG (Web Content Accessibility Guidelines).

Accessibility audits are the bread and butter of every accessibility consultancy.

The Web Content Accessibility Guideline’s (WCAG) Success Criterion 1.4.11 Non-Text Contrast is one of the harder to understand requirements.

In our tech-focused society, there is this ever present notion that “accessibility will be solved by some technology”.

In the last couple of weeks, I had some encounters that made me think about the state of ableism.

Accessibility, especially on the web but also elsewhere, is a complicated combination of people with different roles working together.

I place the start of my career in accessibility to some time in 2008.

After the yearly theme of 2022 spilled over into 2023, it’s time for a new theme for 2024: “The Year of Focus on Focus”.

In a stunning press release, Level Access has revealed that it plans to buy accessibility overlay company UserWay for about $99 Million.

I’m not a good “retro” person.

The name “Web Content Accessibility Guidelines” (WCAG) has always been a source of misunderstanding and contention.

My friend Nicolas Steenhout has published an article about the impossibility of specificity in accessibility recommendations.

You might not have noticed it, mainly because it was so quick, but a new HTML functionality is due to arrive in Chromium and WebKit browsers: Exclusive Accordions.[^ Yes, from starting the explainer, which has no serious exploration of the accessibility i…

This was my submission for axe-con 2024, which unfortunately did not make it to the conference.

While it is often sufficient to test the mobile view of websites and applications on the desktop, with desktop browsers, it’s sometimes not enough: Some websites use device sniffing to hash out which device is used and deliver different code to users.

You can switch VoiceOver (and Voice Control) on in the iOS settings on iPhone and iPad.

This is a repost of a Twitter thread from August 2022.

Time and time again, I come across accessibility solutions in which teams have put a massive amount of work.

Every few months, the discussion comes up that you cannot make accessibility work if you are not fighting for disability rights or practicing inclusive design.

Earlier this week, W3C/WAI announced that Web Content Accessibility Guidelines (WCAG) 2.2 is now at the last hurdle before becoming a standard.

When writing about HTML, especially in the context of accessibility audits, you always need to be very clear in what you mean.

About two weeks ago, the WCAG WG released a new version of the Candidate Recommendation for WCAG 2.2.

The latest WebAIM Million has come out.

Over the past few years, accessibility companies have started to develop tools that claim to find accessibility problems automatically.

It’s January 2023 and there is a new WCAG 2.2 Candidate Recommendation Draft (which apparently is a different type of document from the September Candidate Recommendation Snapshot).

Year in review blog posts are very en vogue this year.

Twitter was and is (for now) an integral part of my web presence.

Many people think about moving or at least establishing a presence in the so-called Fediverse.

Thanks to Shelly for inviting me to talk about all things WCAG 2.2 on the Parallel Podcast, Episode 75!

Thanks to Christian, Hans, and Vanessa for having me on the German language Working Draft Podcast Episode 540!

The previous incarnation of this website had a dark theme option, but when I did the redesign a year or so ago I did not get around to implementing it.

JAWS, Job Access With Speech, is the world’s most popular screen reader, developed for computer users whose vision loss prevents them from seeing screen content or navigating with a mouse.

This post is basically a short addendum to my article about text resize and reflow.

There seems to be a confusion about the relationship and how to test for the WCAG 2.1 Success Criteria 1.4.4 Resize Text and 1.4.10 Reflow.

Last week, I received a big box with something that I hoped to buy for a long time.