Accessibility Notes

4/27 Rough Notes:

rcremona [9:48 AM] This is the Safari feature I was describing so incoherently the other day: https://support.apple.com/kb/PH21467?locale=en_US, https://www.google.com/amp/s/mobile.nytimes.com/2017/02/14/technology/personaltech/safari-reader.amp.html. I use it often when reading to strip down complex pages with a lot of text, especially on mobile. Here's a dated discussion trying to work out how to support it (guidelines have not been published). https://mathiasbynens.be/notes/safari-reader I suspect it boils down to: keep your markup clean, using the article tag around the text you want in the reader if possible, using only one article tag, and without so much other content on the page that Reader doubts your intention. H20 shouldn't have trouble, but it's worth checking, since if it works in safari, it will likely work with other similar readers and browser plugins. Here's an example of a decent site that does not work: http://flask.pocoo.org/docs/0.12/

rcremona [10:00 AM] Setting preferred font sizes, etc. right inside H20 is probably unnecessary, unless you want people to habitually read content via the website view for long periods, or make short but frequent visits. For instance: Slack and other messaging services offer customizable font sizes because it's a pain to resize every time you get a message, even if it only takes 5s to read.

[10:01] (Modern browsers like Chrome remember your preferred zoom level by domain, so that isn’t the only mechanism for ‘saving’ preferences)

[10:03] Having a web view in addition to epub/pdf exports etc. is a clear win for accessibility: assistive technology is much more likely to cooperate with the web version, and, if paired with good navigation, is likely to be much easier for keyboard-only users.

rcremona [10:10 AM] For the most mileage: maybe consider having a toggle that switches on demand to an in-browser js e-book reader, something like https://sample-2fab1ebe4b811063d0ae76e2e948a910.read.overdrive.com/?p=harry-potter-and-3d4d6c, if possible, jumping to the page where the user clicked the toggle. Since these books are so big, I don’t know if that is unmanageable from a bandwidth perspective, but the UX would be pretty awesome.

[10:11] (I’m not up on in-browser ebook readers, that’s just the first one that popped up on google.)

[10:20] I’d love to see what kinds of materials are being incorporated into these textbooks too, other than paragraphs of text. (charts? tables? anything fancy?)

[10:22] Perhaps especially the CAP ingests, which I imagine can have complex internal structure.