Reposting Robert's comment from Bug 1259685:
This roadmap for the jQuery UI datepicker is interesting so I'll a link to it here http://wiki.jqueryui.com/w/page/12137778/Datepicker It sounds like they are trying to get some usability issues sorted out. If we can get Datepicker and timepicker plugin (possible option) http://trentrichardson.com/examples/timepicker/ going with keyboard accessibility that would be most useful. Question is should we wait until others have sorted this issue - or should we take a look at sorting this ourselves? As I understand it, the current date/time picker is not keyboard accessible, so something will need to be done. -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1267239 Title: Datepicker is not keyboard-accessible Status in Mahara ePortfolio: In Progress Bug description: Currently the DHTML date picker widget (for example the date field on /artefact/plans/edit/task.php) is not easy to navigate using a keyboard since it opens below all other elements and does not have focus set to it - this is confusing for screen reader users since activating the button appears to do nothing. The current date picker could be modified to be made accessible, or it could be replaced with another library (such as a variant of jQuery UI datepicker) Note that screen readers users can still enter dates manually so this is not essential for WCAG compliance. Affects latest master (using Orca 3.4.2) To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1267239/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
