4 ms·
I worked in the web accessibility space a decade ago. It really wasn't hard back then. However, for something as simple as a providing prescriptions, there is
by BeetleB 6y ago
I worked in the web accessibility space a decade ago.
It really wasn't hard back then.
However, for something as simple as a providing prescriptions, there is no argument that whatever was easy a decade ago won't work. They could either make a separate link/interface for accessibility purposes[0], or have done the right thing and designed it to be accessible from the get go, instead of trying to shoehorn an existing design into an accessible one. I'd bet money that the real problem here is that they built the site with little regard to accessibility, and are now dealing with the fallout. I'd wager that had they planned for an accessible site from the get-go, they would have built a site as good as it is now, and be accessible, with little extra cost.
[0] Frankly, some ordinary people like me might actually prefer the non-fancy accessible UI. I bet most of their non-accessible stuff has little benefit to me.
- throwawayboise 6y agoIsn't that the approach? I'm not much in front-end work these days. I thought it was: 1. Build a simple HTML/Forms implementation that works (but obviously is not feature-rich). 2. Enhance (1) with JavaScript/CSS to add all your fancy UI cosmetics. If there's no JavaScript or CSS, then you get the unenhanced version by default. Clearly for some things (e.g. Maps) that are inherently visual this isn't possible, but for the typical customer/business transactions we are talking about here, seems to me it should work.
- extra88 6y agoYou're basically describing "progressive enhancement." People with disabilities aren't really more likely to load a site without JavaScript or CSS though, a site can still require JavaScript and CSS to operate. It does take at least a little more work to make a form work through POST and as AJAX-submitted JSON. To be accessible, a site should be robust enough to work even when everything isn't the same as when the web author uses it (users use keyboard and other inputs instead of a cursor, have different screen sizes, zoom or enlarge text, use Windows High Contrast Mode to replace the site's colors with their own choices, etc.). > Clearly for some things (e.g. Maps) that are inherently visual this isn't possible The first interactive online maps were static images with North, South, East, West arrows (links) to load the next image; having to load the whole web page again for the next part of the map is not nearly as nice as loading image tiles dynamically but it does work. Dyanamic tile loading also doesn't have to be done only by cursor or touch, you can still have on-screen arrows that can be tapped or keyboard operated to load more tiles (plus loading tiles based on keyboard arrow keys, WASD, etc. while the map is focused).