- https://jira.sakaiproject.org/browse/SAK-22813 (new jira - all gradebook headers should be h3 ) h1 reserved for navigation, h2 for portlet titles - Matt open seperate JIRA re heading hierarchy
- Apereo / Ian still having conversations about funding an accessibility audit - good
- Got feedback on research to support https://jira.sakaiproject.org/browse/SAK-19124 from Sakai Core team
Notes on Dialogues
Good sources of info https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_dialog_role
Dialogs can be modal or non-modal
Even though it is not required for the dialog itself to be able to receive focus, it still needs to be labeled
When the dialog appears on the screen, keyboard focus should be moved to the default focusable control inside the dialog.
Tab order should be contained by the dialog.
If the dialog can be moved or resized, ensure that these actions must be performable by keyboard users as well as mouse users.
Note that for non-modal dialogs there will have to be a global keyboard shortcut that allows focus to be moved between opened dialogs and the main page.
It is important the a dialogue both ket focus, but not present a keyboard trap once it is dismissed. Focus should be returned appropriately when the dialogue is dismissed.
Notes on Tooltip
Good Sources of Information http://heydonworks.com/practical_aria_examples/ -- reading through http://webaim.org/discussion/mail_thread?thread=5041
Directives we could consider:
Should we suggest that it always be a <a>,<img>,<abbr>?
Tip content be derived or at least mired in title attribute - or hidden text?
Example that works well with Chromevox http://websemantics.co.uk/resources/styled_accessible_tooltips/
http://jqueryui.com/tooltip/ ’s example did not work well.
Commonly used technologies/libraries in Sakai:
Bootstrap:tooltips (which are directional)
Growl based https://jira.sakaiproject.org/browse/SAK-25330 - https://github.com/ifightcrime/bootstrap-growl?
Morpheus project - time to review it? https://confluence.sakaiproject.org/display/REL/Sakai+11+straw+man
Any eyes available to look at
Accessibility / i18n: Statistics Frame Default Human Language is Not Set, Should Match User Language Preference
https://jira.sakaiproject.org/browse/SAM-2342 extended matching type seems inaccessible
There's more with SAMIGO that anyone's welcome to take a look at if there's interest - recent activity on https://jira.sakaiproject.org/browse/SAM-1988 (worth considering https://confluence.sakaiproject.org/pages/viewpage.action?pageId=75667040 )
Matt's JIRA Filter https://jira.sakaiproject.org/issues/?filter=14292
https://jira.sakaiproject.org/browse/SAM-1649 Accessibility: Remove onkeypress handlers from "Open" and "Close" links on Test/Quiz Settings page