2 ms·
That has been what I have mostly done so far, but the fact that big sites do it and there are no apparent complaints or pushback makes me doubt my approach. Two
by graemep 3y ago
That has been what I have mostly done so far, but the fact that big sites do it and there are no apparent complaints or pushback makes me doubt my approach. Two of the sites I mentioned are trying quite hard, and the other does at least have alt tags.
With regard to using screen readers, do I need to use multiple screen readers if they differ?
- seanwilson 3y agoThere's some examples here of websites getting in trouble for not being accessible (the Domino's Pizza one is well known) if that helps: https://en.wikipedia.org/wiki/Web_accessibility#United_States https://en.wikipedia.org/wiki/Web_accessibility#United_State... > With regard to using screen readers, do I need to use multiple screen readers if they differ? Unfortunately, they all have their own quirks. Alt tags and other basics that are built into HTML should be pretty simple and consistent between screen readers. More custom things like modals and JavaScript interactivity and also random things you'd expect to be simple can be a headache though and require you to research what quirks screen readers have (random example: https://www.powermapper.com/tests/screen-readers/labelling/iframe-title/ https://www.powermapper.com/tests/screen-readers/labelling/i...). It's very similar to how IE, Firefox and Chrome can render and behave differently on the same web page. If you're testing on one screen reader though, you'll still be doing better than most and it'll catch a large portion of potential problems. It'll help with your alt tag dilemma as you'll experience first-hand how annoying useless alt tags are even if big websites are using them.