-
-
Notifications
You must be signed in to change notification settings - Fork 188
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 review: meta-ticket #627
Comments
@vangheem @bloodbare actually, these are all very manageable points. Would need to confer with you if they are acceptable, but they all seem like stuff we should be taking onboard and have our accessibility rock. |
Any references on why Skip to links are outdated? Brazilian Gov doesn't know about that yet and their removal would mean a severe loss on the already fragile choosing of Plone as a default CMS down here (a11n, security and productivity are, in order, the key Plone differentiators from competition). |
Feedback from screenreader users, mostly. They are an outdated mechanism that nowadays mostly hinders more than it helps.
Using both of them gives dual navigation for screenreader-users, which means more links to tab through before you get anywhere. There is no conclusive 'rule to end all rules' here: WCAG 2.0 only says you should "have a mechanism to bypass blocks". http://www.w3.org/TR/2008/REC-WCAG20-20081211/#navigation-mechanisms-skip There is one case where skip-links are still useful: not for screenreader users, but for sighted users who prefer to use a keyboard, although there is Aria support via a Firefox plugin. Even then, it would need a discussion on how to implement them: you need browserhacks for IE9, IE10+, Safari and Chrome. And more if your site wants to support IE below 9. The most robust way is to have both HTML5 and Aria (https://dequeuniversity.com/assets/html/jquery-summit/html5/slides/landmarks.html). If sites still need the outdated 'skip-links', they are of course easy to add back with Diazo. But our current simplistic version of them does nothing to help screenreader users; the only thing it does is maybe tick a few boxes for outdated specifications. They are not needed for WCAG 2.0, and are difficult to maintain properly. Of course this is open for debate. There is, unfortunately, a tension between actually helping disabled users and complying with outdated specs that governments like to keep around for ages. So it's a debatable call... Some more links: |
Thanks for the write-up! |
I would, of course, be very much in favour of having clear documentation on how to add the links back in via Diazo if your jurisdiction requires/wants it, and will write those docs in Arnhem. But it is a bit like maintaining IE6 compatibility ;-) |
As a note to future sprinters, a nice to have would be setting up a11n (headless) automated testing: As shown in: Also see: |
Looks like that an audit on plone 5 coredev returns 15 text elements that should have more contrast ratio (most barceloneta errors) We can solve this small issues on next sprint! |
plone/mockup#522 for folder contents fixes |
@polyester for the /accessibility-info page, I've made this PR in which I removed the access keys info and changed the two mentions of WCAG 1.0 to 2.0. Not sure what to do about the part that says "We have used XHTML 1.0 and CSS". For now hopefully this at least gets the most important fixes done. #675 |
@tkimnguyen thanks. I'll embellish a bit more, with ATAG 2.0 info and some more links and further explanation. |
Some summary on the work I did this morning:
|
…ronym, and use p tag instead of br
for #627 minor extra space issue between open parenthesis and acronym…
@polyester I made two PR for Accessibility issues. Please check it. |
I've checked, and they look fine. I'll get on with getting them merged. Thanks, @terapyon |
I will close this given it seems to me quite a lot of activity was done and @terapyon PRs were merged. |
Meta ticket for tasks identified at Tokyo Symposium 2015: we tested together with Max Nakane, developer and highly experienced screenreader user.
Overall considerations
Plone 5 should focus on modern a11y methods, and drop support for outdated ways.
That means the following should be removed:
If site owners need outdated features like access keys, they are easy to insert back using Diazo. This should be documented.
Specific points.
The text was updated successfully, but these errors were encountered: