-
Notifications
You must be signed in to change notification settings - Fork 125
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
DPUB pagelist role not necessary for accessibility; just use ARIA 1.0 navigation landmark. #58
Comments
Actually, we have had a lot of discussion about this. The collection of page numbers is essential for A11Y. In classroom environments, for example, an instructor will say "turn to page 25". Users relying upon Assistive Technologies need a consistent way to do this. |
Why is it better than ??Is it expected that AT or specially designed accessible readers will provide a special mechanism for going to page list? In such cases, wouldn't most students use a reader function for jumping to a specific page instead of picking from a list? That is how I do it in most readers... I use the "go to page" function. Matt King From: Shane McCarron notifications@github.com Actually, we have had a lot of discussion about this. The collection of |
All the more reason for them to do it the same way everyone else does it. Using VoiceOver on iBooks for example, you can flip the page, use the page chooser at the bottom, or navigate via the table of contents. |
The page list is not a list of reflowable pages in the current document, but a list of references to the pagebreak markers corresponding to a print source. |
Still seems like a standard navigation landmark to me. What special behavior or semantics do you expect a screen reader would have for this? What special behavior do you expect for a mainstream user of this section of book content? |
Thank you for your feedback. This issue has been resolved by editing the document to comply with the rules for extending ARIA (https://www.w3.org/WAI/PF/wiki/ARIAExtensions). |
DPUB pagelist role not necessary for accessibility; just use ARIA 1.0 navigation landmark.
The text was updated successfully, but these errors were encountered: