Accessibility WG Teleconference Minutes 03-21-2013

Attendees

Joe Humbert
Gonzalo Silverio
Neal Caidin
Mary Stores

Agenda

Sakai 2.9 Accessibility Review

A11y Jiras that need testing/review

Jira issues the AWG needs to review:
- SAK-22031 - Accessibility: Provide Accessibility page descriptions - https://jira.sakaiproject.org/browse/SAK-22031
  - Joe: is this a good idea? adding a hidden description of the page
  - Joe: Brian said this was a direct request lucy greco (UC berkley) and University of Cincinati. I will reach out to requestors and indicate the AWg feelings. The will need to commit resources. Joe will resolve as no resources and idicated that we cannot tackle the issue, but we are willing to accept patches.
  - Gonzalo: Contacts are Eli Cochran for Berkely (if not him, he should know who). Neal should know about Cincinatti. (I don't :-( - Neal) - I will dig a bit. Looks like Cincinnatti uses Blackboard 9.
- !!!!The below issues were tabled for a future teleconference due to time constraints!!
- PRFL-640 - Accessibility label for wall is identical to the kudos label - https://jira.sakaiproject.org/browse/PRFL-640
- SAK-23188 - Roster - Search - https://jira.sakaiproject.org/browse/SAK-23188
- https://jira.sakaiproject.org/browse/SAK-23342
- Jira filter for resolved accessibility issues that need testing by Wednesday March 27th, 2013:
  - New filter - https://jira.sakaiproject.org/issues/?filter=13696
- Giant list of A11y Jira issues:
  - http://bit.ly/current-a11y-jiras
- Joe: Neil, could an accessibility component be added to all tools so that this group can easily track down all A11y issues. Particularly those that are entered by non-members or non-active members.
- Note: Please add other jira issues if you find them

Any Other Business

Sakai A11y Help Documentation

Comparing current help documents with draft updated documents
- Current: http://kb.iu.edu/data/arkn.html
- Draft: https://docs.google.com/document/pub?id=1m-kAuXkIbXBgXbAsMLOrgY2irI8yM9rQjnWkjnXL30E
  - Changes needed?
  - Comments?
URL to include in place of current help documents
- full URL
  - https://confluence.sakaiproject.org/display/2ACC/Sakai+2.9+Accessibility+Help+Documentation
- Shortened URL
  - bitly? possibly http://bit.ly/sak-a11y-help
  - other services
Changes need to be finished by April 18th
Joe: neil will talk to Matt Jones about the Procedures. What should the URL be?
Statement for Knowledge base:
- The following URL is provided for people with disabilities who would like to experience the accessibility enhancements of Sakai.
- https://confluence.sakaiproject.org/display/2ACC/Sakai+2.9+Accessibility+Help+Documentation

!! This Topic was postponed for lack of time!!

Sakai Accessible Content Creation Guidelines

WCAG 2.0 as basis for guideline?
- WCAG 2.0: http://www.w3.org/TR/WCAG/
- WebAIM
  - http://webaim.org/standards/wcag/checklist
  - http://webaim.org/resources/designers/
    - text version: http://webaim.org/resources/designers/#text
CK Editor A11y Content Creation Guidlines
- Headings
- Lists
- Tables
- Alternative Text

!! This Topic was postponed for lack of time!!

Sakai Accessibility Working Group Email List

Potential Topics
- Problem/ solution conversations
- Documentation
- Sakai tool specific ARIA landmarks
- ARIA application role
- ARIA live regions
Let's decide on our first topic

Draft agenda Items for next teleconference

Discussion of progress on updating Sakai a11y help documentation
How to demarcate Jira issues for A11y across projects
A11y Jiras that need testing/ review
CK Editor content creation guidelines

Next Meeting is April 4th, 2013