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 issues with pickadate module #2406

Open
wohnlice opened this issue May 10, 2018 · 1 comment
Open

Accessibility issues with pickadate module #2406

wohnlice opened this issue May 10, 2018 · 1 comment
Labels
99 tag: UX Accessibility Issues that specifically impact a11y
Projects

Comments

@wohnlice
Copy link

We recently had an accessibility 508/WCAG2 review performed on our sites for compliance with HHS contracts and the reviewer made two notes pertaining to the pickadate jquery module used on Date/Time Dexterity fields. In my testing, this applies to both 5.0.5 and 5.1, out of the box.

I am copying his issues verbatim as I have no expertise in this area. If the Plone team believes that the current implementation is not in violation of WCAG2 for some reason, would it be possible to provide an explanation why?

Visual Focus is Missing
Description: Available days are selected after a mouse click on the date field. When tabbing and using the arrow keys, there is not a visual focus indicator to let keyboard users know which day currently has focus. This issue is a violation of 1194.21 (c) in Section 508 and Success Criterion 2.4.7 in WCAG 2.0.
Remediation Suggestion: Currently the year and month can be selected via keyboard. Add support so that keyboard-only users can use the arrow keys to select the day.
My note: He is referring to the date/time z3c form fields used by Dexterity and other z3c forms. This applies both to selecting the day and selecting the time.

@polyester polyester added the 99 tag: UX Accessibility Issues that specifically impact a11y label May 17, 2018
@gp54321
Copy link

gp54321 commented May 17, 2018

since the whole widget is meant to be axed and replaced, you may want to take a look at
#2150
If you could build the project in a test setup and look if it fits the norm that is interesting you, I'm sure your input on the eventual missing points could be of more interest there. That's a work in progress, now is the appropriate time to weigh in.

@polyester polyester added this to low prio in a11y Apr 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
99 tag: UX Accessibility Issues that specifically impact a11y
Projects
a11y
  
low prio
Development

No branches or pull requests

3 participants