Skip to content
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

Accessibility audit: page turning status #3123

Closed
cbeer opened this issue Jun 16, 2020 · 2 comments · Fixed by #3132
Closed

Accessibility audit: page turning status #3123

cbeer opened this issue Jun 16, 2020 · 2 comments · Fixed by #3132

Comments

@cbeer
Copy link
Collaborator

cbeer commented Jun 16, 2020

Once a digitised item is open, users can navigate through the pages/views of the digitised material using the arrow buttons "Previous item" and "Next item/Next item". While sighted users perceive the "turning of pages" directly, blind users are not informed that the view has changed.
To change this, a live region could be created using the role="status" attribute. After paging, the text (e.g., the text below the digitized page number and name) should be placed inside the element with the role="status" attribute. This would mean that the text would be read by the screen reader after turning the page without shifting the focus.

@cbeer cbeer added the Mirador3 label Jun 16, 2020
@cbeer
Copy link
Collaborator Author

cbeer commented Jun 16, 2020

I'm not clear what text is expected; "5 of 10"? the new canvas label?

@jvine
Copy link
Collaborator

jvine commented Jun 16, 2020

Clarified by Google Translate:

To change this, a live region could be created using the attribute role = "status". After turning the page, the text below the digitized material (page number and description) should be placed within the element with the attribute role = "status".

A new region and role don't seem to be necessary; the problem is effectively solved by adding aria-live="polite" to the <section> that contains the <canvas>.

`

However there is duplication between the aria-label on this <section> and the requirements of #3107. It looks like this will resolve that - or in any case, it works in my test on VO:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants