Accessibility WG Teleconference Minutes for Wednesday March 15, 2017

Accessibility WG Teleconference Minutes for Wednesday March 15, 2017

Attending: Matt Clare, Adam H., Jeff P., Kyle B., Amy N., Dave E.,  SAm O. , Matt J.

    

Regrets:  Neal Caidin

Agenda:

Follow-Up on Offer from NYU for hours from an accessibility/usability firm, TPG.

  • We're working to plan a workshop on developing for proper keyboard naviagtion.

  • Thinking of hosting event  Wednesday March 29th, some time after 3:00PM Eastern (1900GMT) 

  • We can talk through the idea with SAWG (that's us) and follow-up with Core Team - then we’ll have a plan.

  • Our current a11y issues tagged with keyboard related issues are (worth refining)

  • Putting together additional thoughts/questions for TPG in prep for presentation, tentatively scheduled for Wed, 3/29 at 3pm or later

  • Infusion 2.0 includes significant framework improvements and is not backwards compatible with previous versions of Infusion. 

  • e.g., reordering/sorting component (jQuery UI didn't have this, at least some point)

  • We'd like Hans's input on making decisions around what to use for different needs

  • thinking about different frameworks in sakai

  • SAK-31628

  • Ensure simulated controls are keyboard accessible

  • SAK-31629

  • Ensure simulated controls are keyboard accessible

  • SAK-31610

  • Ensure keyboard focus is indicated visually

  • SAK-31616

  • Ensure that keyboard focus remains within modal simulated dialogs

  • SAK-31615

  • Ensure simulated controls are keyboard accessible - Morpheus

  • SAK-31619

  • Ensure all active elements receive keyboard focus

  • SAK-31621

  • Ensure keyboard focus is not provided to inactive elements

  • DASH-395

  • Ensure ARIA roles, states, and properties are valid-Dashboard

  • SAK-31573

  • Ensure ARIA roles, states, and properties are valid - Assignments

Working through accessibility issues with Samigo question types from a high-level perspective- We decided to delay this activity for 2 weeks.

Things to basis analysis upon:

    WCAG 2 article-by-article (Quick ref https://www.w3.org/WAI/WCAG20/quickref/ )

    Or

    Simple POUR-based analysis (Perceivable, Operable, Understandable, Robust)  http://webaim.org/articles/pour/

Start of GSheet  with all Sakai Question Types

JIRAs discussed

https://jira.sakaiproject.org/browse/SAK-31899        Accessibility block for visually impaired users - Attachments picker        Open        Needs Verification        

https://jira.sakaiproject.org/browse/SAK-32173        Accessibility block for visually impaired users - Syllabus        Awaiting Review 

  •  -- MC to follow-up