Quote:
Originally Posted by Hitch
I've simply reached my limit on educating people who read something that they don't understand, "on the net" and then think that they should interrogate me about it.
|
Toss another thing in the FAQ, write an article, point them to it. I'm sure they'll read it.
Quote:
Originally Posted by Hitch
Or how they want "PDF3" or "Kimble" or any of the other 50 things I've heard, just in the last 3 months.
|
What, you've never heard of this amazing Amozan Kimble?
Quote:
Originally Posted by FrustratedReader
WCAG is irrelevant for books and ebooks. It's not even very good for web sites.
|
Again, while many of the recommendations may not be applicable to ebooks-specifically, you can make your code more future-proof by pick-and-choosing from WCAG + WebAIM.
On the reader side, people may take your HTML and read in non-EPUB readers: DAISY, NVDA, JAWS, and who-knows-what-future-reader. For example, while all EPUB readers/apps don't display <title> in the header,
it's still a good idea to include meaningful titles.
On the production side, new enhancements are happening all the time. For example, Multi-Language Spellchecking in Calibre (absolutely fantastic use of lang + xml:lang).
Quote:
Originally Posted by FrustratedReader
Tables as <table>, not pictures of data
Yes, text but not Tables because they work poorly or not at all
|
What?
Quote:
Originally Posted by FrustratedReader
Foreign letters as actual text, not as little images.
Sadly doesn't work on many ereaders, though it could have years before release
|
What?
Quote:
Originally Posted by FrustratedReader
Use proper lang + xml:lang
Sadly doesn't work on many ereaders, though it could have years before release
|
What?
Quote:
Originally Posted by FrustratedReader
Proper alt text
Sadly doesn't work on many ereaders, though it could have years before release.
|
What?
Quote:
Originally Posted by FrustratedReader
Proper alt text
You need a text caption under the image if it's important for Text to Speech
|
Yes, also good to have that as backup. But alt text serves a different purpose:
https://webaim.org/techniques/alttext/
Quote:
Originally Posted by FrustratedReader
A few examples of talks:
Snipped, mostly a waste of time.
|
They explain real-life Accessibility issues from consumers, problems that exist with many current ebooks, plus things you should keep in mind for the future (like the potential legal requirements, etc.).
And as discussed in those talks, library (and academic) purchases are tending towards requiring some base level of Accessibility. If your ebooks won't meet that base level, no purchase.
Quote:
Originally Posted by FrustratedReader
9) Only footnotes in reference works, try an inline right justified paragraph in sans rather than linked footnotes.
|
??? Can you show me an example of this?
Quote:
Originally Posted by FrustratedReader
12) No page numbers except as right margin "notes" as actual pages in a copy of a reference work that's only ever one paper layout (e.g. Hebrew Bible)
|
Best to just use standard page-map/page-list and leave the rendering up to the reader.
Using the standard methods also allows users to jump to the exact page, plus navigate through the document per page.