There are no console errors for malformed ARIA. There’s also no alert dialog, beeping sound, or flashing light for your operating system, browser, or assistive technology. This fact is yet another reason why it is so important to test with actual assistive technology.

This talk, article, is for anyone who’s ever said “we need to make this accessible,” and got ignored, brushed off, or told, “We’ll do that later.” If you’re not in a leadership role, if you’re not officially “the accessibility person,” but you still want to drive change, this is for you.

So, there you have it. CSS Carousels are highly experimental, not currently accessible, and therefore, not ready for production.

NOBODY is saying that automated tools are not useful, only that they cannot provide comprehensive coverage of WCAG 2.2 criteria.

The ARIA tooltip role is functionally useless and semantically meaningless. The only legitimate use-case for tooltips is to show information that’s already accessibly defined. So tooltips only benefit sighted users, and are therefore presentational.

I get very frustrated with people that try and tell me I am wrong that PDFs are not the problem because frankly it’s always someone that makes a living teaching PDF remediation and or creating PDFs for others that are the ones saying this. They do not live with the inaccessible documents I have in my everyday life. It’s hard to always have to fight to read something and I am Telling you we need to solve this problem now.

Perfection is the enemy By default or death Parity is paramount Design for implementation Structure first Use your words Tools are not identities Less is less Fishing, not fish No points for performance Help evil to fail

You might think this feels like vindication, but it does not.

Sure, it’s nice to be validated by the FTC after 5 years of shouting to anyone who will listen that accessiBe is a net harm for the disability community. But the settlement is a pittance.

Reports put accessiBe’s 2024 revenue at $51.3 million. The settlement has a fine of $1 million. Subtracted from its 2024 revenue, that leaves accessiBe with $50.3 million dollars for the year. Dollars earned by lying to customers, misrepresenting itself to the community, and arguably harming disabled users.

TL;DR: Description list support continues to be generally good (with VoiceOver still the outlier), even if you may not like how it is supported.

According to the FTC, accessiBe not only fell short of its promises to clients, but engaged in misleading marketing. accessiBe “deceptively formatted third-party articles and reviews” to appear as if they were independent opinions by impartial authors, said the agency in a press release, and failed to reveal “material connections” to supposedly objective reviewers.

AI is not impacted by inaccessibility. It is not a disabled person. It cannot explain web accessibility from the perspective of a disabled person.

Removing the human factor of inaccessibility stories does not build empathy. It dehumanizes the stories. It dehumanizes US.

Additionally, inaccessibility is not a result of a lack of empathy. It’s a result of ableism. To still position lack of empathy as the main problem in almost 2025, is a failure to consider vital historical context.

Creating AI caricatures of disabled people does not help us dismantle systemic ableism.

I also take issue with the alleged need for comments to be “appealing” or “humorous.” Nothing appealing nor humorous about inaccessibility. Inaccessibility is PAINFUL in every single sense of the word. When disabled people encounter inaccessibility, we are harmed every. single. time.