Quote:
Originally Posted by elibrarian
As the man said in the original question, its all about accessibility (for people needing screenreaders and such to use ebooks).
You can read something about it here:
https://inclusivepublishing.org/tool...ty-guidelines/
where there are also links to the specs. (WCAG 2.0, or a subset is among the criteria.)
You might also want to consider KevinH's brilliant plugin for Sigil (Access-Aide) and Doitsus ACE-validation plugin.
Regards,
Kim |
Kim:
Thank you, I'm more than acquainted with accessiblity--with what CAN be done in eBooks. Which has
almost NOTHING to do with WACG.
There is actually quite LITTLE that a bookmaker can do. We already do the primary aspects:
- Text should fit all screensizes (Yup);
- adjustable text font, color (sometimes) font size and line-spacing (sometimes). The "sometimes" have to do with the device/software reading it, not our ebooks.
- Options to skip footnotes, etc. when reading wtih text-to-speech--those have NOTHING to do with the ebook file and everything to do with the reader.
- work with different input methods--NOTHING to do with the ebookmaker.
- Contain image captions and text descriptions for charts and graphis. YUP.
- Videos should be captioned or accompanied by text transcript. Yes, but really? Tell Youtube that, before somebody climbs on some eBookmaker's back. I think Google can afford to implement that more quickly than I can.
- Readable on multiple platforms and devices, such as computers, mobile phones, tablets, refreshable braille (no idea) and digital book readers. YUP.
- Page numbers should match the print version of the same book.Mostly, nope.
Most of the biggest "needs" for accessibility have nothing to do with the eBooks and
everything to do with the devices and readers. So, let's lecture those companies, shall we?
Hitch