-
Notifications
You must be signed in to change notification settings - Fork 176
Update Display of accessibility metadata following Guide 2.0 #2536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
For implementation & testing: |
Also, there is a localization JSON available from W3C: https://github.com/w3c/publ-a11y/blob/main/UX-Guide-Metadata/draft/localizations/en-US/display_guide_vocabulary_w3c_en-US.json Future localizations to be added. It is intended to work with the techniques documents (Code IDs of the techniques are Keys of the JSON). Example: A display of JSON values is available at https://rawcdn.githack.com/w3c/publ-a11y/91141c948fcb1b40ed13dc0b58567307a44474a4/UX-Guide-Metadata/draft/localizations/index.html |
Thorium should use Compact sentences with no titles for categories and keep things as simple as a list. Example:
|
The guide is still being refined by editors. An exemple processor is available from a dedicated daisy repo Our Rare_EPUB_test_suit/package.opf
|
IMHO our implementation should differ to avoid titles with only one element and include
Additional accessibility information |
We could even get ride of titles (Reading modes, Navigation, etc.) |
Should we have a Readium component for that? |
I suggest assigning myself to update locals for now ( thorium-reader/src/resources/locales/en.json Line 247 in 704c10e
|
Very partial update implementation of display guide 2.0. See #2536
Swift implementation mapping for reference. |
Choices made on the way:
|
User Experience Guide for accessibility metadata 2.0 first public draft is available. The set of documents includes:
Thorium pioneered the display of such information in a reading system, but the way it is presented is now outdated.
We should implement this significant update so it can be used to test and provide feedback.
The text was updated successfully, but these errors were encountered: