Closed Eonasdan closed 10 months ago
@kiliczsh The icons have title
attributes but I haven't done much with accessibility. That's a good idea though.
The thing is that "keyboard accessibility" is mandatory requirement in various places, just due to legalize rrequirements (like ADA in USA).
Hello there's a new branch: https://github.com/Eonasdan/tempus-dominus/tree/feature/accessibility that features keybindings. It's not done but some progress has been made. The keybindings only seem to work via the input field not when focus is on the widget div. If you want to take a look, feel free!
Please check the progress of this feature here: https://stackblitz.com/edit/tempus-dominus-v6-accessibility?file=index.html
I could use some feedback on what's missing and what's working.
I will try to look into it
First notice, if input group with button, is used also to open popup, it must be accessible also via that (FYI, also "button" must be implemented as button, span is fail in ADA tests). Not it seems that when popup is opened via button then keyboard access won't work. Perhaps should move focus back to input field when opening popup (?). I.e. end user most likely tries TAB, not SHIFT+TAB.
"toolbar" at top and "time select" at bottom are not TABable seemingly currently, while actionable via mouse (yep, counted as "fail" in ADA tests).
i.e. basic rule is that everything accessible via mouse must be accessible also via keyboard (and yes, been there and there can be thus cases, which don't make much sense, but when audit is done by external auditor, they just do it with "brains turned off").
This could be useful for "how it should work": https://www.w3.org/TR/wai-aria-practices/examples/dialog-modal/datepicker-dialog.html
This could be useful for "how it should work": https://www.w3.org/TR/wai-aria-practices/examples/dialog-modal/datepicker-dialog.html
This page moved to https://www.w3.org/WAI/ARIA/apg/example-index/dialog-modal/datepicker-dialog.html
@Eonasdan What's the status of this feature? I see you marked it as complete in December but the branch doesn't appear to have been merged and released.
@chardin1 I'm no longer working on this project. I've moved on to other things. If someone wants to discuss sponsoring this issue, I'd be open to that.
@Eonasdan We are interested in sponsoring accessibility improvements. What is the best way to contact you about the specifics? My email address is mriese@dimagi.com, if you want to use email.
Hi @Eonasdan, I have checked docs but couldn't find anything related. Is v6 will support WCAG2.1? In other words will it be an accessible tool?
Originally posted by @kiliczsh in https://github.com/Eonasdan/tempus-dominus/discussions/2384#discussioncomment-1275978