News for hackers. Stuff that matters.
Re:Building the most inaccessible site with a perfect Lighth... by choxi on Saturday June 06, 2020 @06:37PM (#23442916)
Cool, but this article would have been more useful with some practical examples of things Lighthouse doesn't catch. If the point is "this automated metric isn't perfect", no automated metric is but how bad is it exactly?

I still don't have a sense for how bad Lighthouse is because I've never disabled all keyboard events, disabled all mouse events, or changed the high contrast stylings. The article almost makes the opposite point to me -- how bad can Lighthouse be if the only loopholes are things that would pretty obviously have accessibility issues?

The only useful examples I could see were the ones at the bottom of the article, which show up in Lighthouse next to the score.

Re:Building the most inaccessible site with a perfect Lighth... by imtringued on Saturday June 06, 2020 @08:09PM (#23443497)
You didn't understand the article. The article doesn't contain a single loophole. Each of those features has legitimate use cases and it is impossible to detect whether they are illegitimate.

Just look at the first example. It straight up denies access to the content and the reason why lighthouse accepts it is because hiding content just hides content. Usually when content is marked hidden the user is not supposed to see it. It is therefore not a concern if a user can't see hidden content. Imagine if you had a hidden dialog that is only shown on user interaction. Any automated tool cannot tell if this is an accessibility issue or not. It's like deciding if your car should be blue or black. There is no objective answer and choosing the wrong color won't reduce your score.

All the other tricks in the article follow the same pattern.

Re:Building the most inaccessible site with a perfect Lighth... by aidenn0 on Saturday June 06, 2020 @08:46PM (#23443694)
Mostly; I can't think of a good reason for 1px sized text.
Re:Building the most inaccessible site with a perfect Lighth... by darekkay on Sunday June 07, 2020 @05:11AM (#23445937)
The only thing I can imagine are screen reader-only labels (although you're usually achieving this with a special "sr-only" or "visually-hidden" utility class that doesn't touch the font size)
Re:Building the most inaccessible site with a perfect Lighth... by Izkata on Sunday June 07, 2020 @12:55PM (#23448677)
Part of a CSS animation where the font size grows into place from invisible (such as for an info toggle), instead of simply popping into place?
Re:Building the most inaccessible site with a perfect Lighth... by joan_kode on Saturday June 06, 2020 @07:33PM (#23443300)
The article repeatedly states that it's not about Lighthouse and that there's nothing wrong with Lighthouse. The point is that your website can be completely inaccessible and no amount of automated testing will detect it. You need user testing, that's all. The "practical examples" to take away are simple: for a start, make sure that your (human) testers can read and navigate your website. Seems practical enough.