3 ms·

There are some things, such as putting text inside a bitmap image with no alt tags, that are fairly objectively going to make any sort of accessibility software

There are some things, such as putting text inside a bitmap image with no alt tags, that are fairly objectively going to make any sort of accessibility software much less reliable and more complicated. But what about things like "most screen readers don't support the new WebX API that came out six months ago?" Where's the line between what website developers need to do to be compatible with screen readers, and what screen reader developers need to do to work with the websites their users want to use?

runarberg 5y ago
If you are providing a service it should be accessible. If you are using a fancy API that is not accessible (yet) you should provide a fallback, or—better yet—use the fancy API to progressively enhance the service. If, however, you are making a fun little game which relies on Web Audio API, and there is no point in playing the game without headphones, then your good. The line is pretty obvious in most cases. Or at least you—as a web developer—should know it when you see it.