4 ms·
i built once an free viz tool for accessbility problems and yeah HN is not great, see for example this thread: https://allyviz.com/?url=https%3A%2F%2Fnews.ycomb
by jcmp 2y ago
i built once an free viz tool for accessbility problems and yeah HN is not great, see for example this thread: https://allyviz.com/?url=https%3A%2F%2Fnews.ycombinator.com%2Fitem%3Fid%3D40983994 https://allyviz.com/?url=https%3A%2F%2Fnews.ycombinator.com%...
- Infolektuell 2y agoRight, not great, but really not the worst candidate. ;-) Such validator tools can provide a quick overview, but they have an efficiency problem. It is more efficient for devs to think about a11y in terms of workflows instead of a large ruleset that has to be fulfilled perfectly. Automated validators are not aware of the intended workflows in the app or website and thus cannot identify the critical parts. It's not about being perfect, but it's about how easy we can get the workflows done. Fixing the critical problems first and making progress step by step should be a good strategy. Validator tools tend to complain e.g. about every missing alt tag on images. Many devs think they have to invent a label for every image to make the validator happy. Most images on the web could simply get an empty alt attribute which hides them from screen readers, because their content is not critical. If the image is the only content of a link or button, it might convey critical information for the workflow and needs meaningful alt text.