Hacker News new | ask | show | jobs
by tweetle_beetle 5 days ago
> My client was a utility company

> Adding a lot of pressure, this was a regulated monopoly

> Some requirements I derived: > ... > We had to meet WCAG accessibility (the team settled on AA rather than AAA)

The author doesn't doxx their employer by giving any dates, but if we take the story at face value and assume it took place in last few years, it is pretty shocking.

How does it take a single hero to be fighting for AA compliance as an afterthought for a project with this scope in the 2020s?

I've worked on much more niche projects that treated this with the respect it deserves as a quasi-legal requirement.
1 comments
dlcarrier 4 days ago
It didn't say anyone was fighting for it just that they had to. Whoever fought for the least possible compliance is the real hero. The less of that feel-good nonsense that is implemented, the easier it is for a text-only browser to parse, and the better a graphical browser works with the keyboard navigation that has been built into pretty much all web browsers since their conception.

Ideally, they ignore WCAG altogether, then throw on an overlay if compliance is required, which can be easily blocked by a dedicated blocker (e.g. https://www.accessibyebye.org/) or I just add a list of overlay domains to my ad blocker.

link