Sami MäättäAccessibility metadata and accessibility features, part 2
Published Tags: English, Accessibility, Metadata, WebDev.
This is a continuation to my previous post on accessibility features.
I am lifting a few relevant accessibilityFeature values from schema.org's accessibility metadata on accessibilityFeatures.
You can check more in-depth explanation and code snippets on Daisy's definition on accessibilityFeature.
6. Index
Value index can be used if the publication has an index for the user. Prodiving an index makes it easier to navigate in a large publication.
An index can be a list of words and where they appear or an index of related terms.
7. MathML
Value MathML indicates that the publication uses MathML markup to encode mathematical content.
Check out MathML knowledge base for in-depth stuff.
8. Printed page numbers
Value printPageNumbers indicates that the publication has page breaks according to a printed book's page numbers.
This is especially important at Celia, because almost all of the ebooks are based on printed books. It's common place to reference a book's contents according to its page numbers.
9. Page navigation (not yet implemented)
Value pageNavigation would indicate that the publication has a page list.
This hasn't been implemented yet (at the time of writing), but it would be useful. It is comparable to printed page numbers, but in the use case of purely digital publishing there really aren't any page numbers.
People are so used to referencing books by their page numbers that even virtual ones would be really helpful.
10. Linear reading order
Value readingOrder tells the user that the publication has a logical reading order.
Imagine a fixed layout page with content at different parts of the page. Depending on the markup it might appear to be logical, but for somebody using assistive techonologies the content might be all jumbled up.
Providing correct reading order makes the content logical for any reader.