-
-
Notifications
You must be signed in to change notification settings - Fork 182
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: keyboard shortcuts #348
Comments
@polyester do you know how to use the shortcuts on the accessibility page? |
current state-of-the-art is to not use these anymore, as they interfere with the shortcuts that people have set up in their own screenreaders. It is being actively discouraged, actually. The discussion within the a11y community is not 100% stable yet, but is definitely trending towards not having site-specific shortcuts anymore, but switch completely to correct, tested, WAI-aria roles so people can have their own shortcuts. I fully believe this is what we should be striving to as well. I will try do to a PLIP on this in the next few weeks. |
To make this even more stern: most modern a11y checkers will actually deduct points for having site-specific keyboard shortcuts. Not that those checkers are always right, but in this case they do have a point. We should get rid of the accessibility page, basically, and instead switch to treating a11y users as first-class citizens, having the roles in place, working and tested. Not even that old favorite of Plone's, "skip to content", should stay. We have ways now of marking the main content as, well, the main content. It's up to the client to define their own preferred way of getting there, may that be a keyboard shortcut, a voice command, or whatever people need. The server provides the semantics, the client acts upon that according to the user's wishes or needs. |
good ideas. we should get at least the accessibility page right for plone 5. |
duplicate of #627 |
i've been wondering since long, how the keyboard shortcuts on Plone's accessibility page ( /accessibility-info ) are supposed to work. how is this implemented? is it implemented at all?
Pressing 1,2,3...0 does not work, nor
<alt><1..0>
or<ctrl><1...0>
. futhermore, there are browser and desktop/window manager shortcuts, which come in conflict with the ones proposed at the accessibility page.trac seems to have an option to configure if the shortcuts should be available: https://dev.plone.org/wiki/TracAccessibility
The text was updated successfully, but these errors were encountered: