[PavlovsCat]

About all this meta-discussion about gauges: What if an application requires constant real-time updates of a lot of little values? Say, a music sequencer? What if you have bars for things where the resolution matters, and then little gauges where you just need a rough ballpark estimate that doesn't take up a lot of screen space? Yes, you can make an accessible music sequencer, and good headphones and hearing are probably more useful than look at a spectrograph or level meters. But still.

What about games? There should be more accessible games. But there will always be inaccessible ones and that's fine, too. Let them have gauges, too, why not.

These gauges can be used irresponsibly, yeah. You know what that reminds me of? Every other web thing. Imagine every time any program or article relating to images on the web is published discussion of it devolved into how images without alt tags are bad, and that images should just be a bonus on top of an accessible description. I'm exaggerating, but to make a point.

I think these gauges look really neat, and while I can't think of a use for them for myself right now either, well, let's come up with some, or don't. Let's look at the code and iterate on it if we want and post our findings. But all this "oh, thing X! all the best practices related to X, let me tell you them" should be a thing on the side, not the predictable main event.