Accessibility WG Teleconference Minutes 04-04-2013
Attendees
Joe Humbert
Gonzalo Silverio
Neal Caidin
Agenda
Sakai 2.9 Accessibility Review
A11y Jiras that need testing/review
Jira issues the AWG needs to review:
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
Joe will verify by next teleconference
SAK-23342 - Create a Table of Contents Style view for Syllabus - https://jira.sakaiproject.org/browse/SAK-23342
Joe will verify by next teleconference
SAK-22618 - Updated preferences Success message is not apparent to users of screen reading software on the Notifications page of the Preferences tool - https://jira.sakaiproject.org/browse/SAK-22618
Joe will verify by next teleconference
SAK-22718 - Multiple date selection combo boxes Announcements, Resources, Assignments and Calendar are unlabeled - https://jira.sakaiproject.org/browse/SAK-22718
Joe will verify by next teleconference
PRFL-773 - Numerous form controls are unlabeled on the My Profile page of the Profile2 tool - https://jira.sakaiproject.org/browse/PRFL-773
Jira needs additional work. This may be closed and a new JIRA may be created
Jira filter for resolved accessibility issues that need testing for 2.9.2:
New filter - https://jira.sakaiproject.org/issues/?filter=13696
Giant list of A11y Jira issues:
Any Other Business
Sakai A11y Help Documentation
Comparing current help documents with draft updated documents
Statement for Help Documentation:
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
i18n Process
i18n Group had some concerns with moving the help documentation out of Sakai
The are concerned about non-English using being able to access the translations
Joe and Neil will have a teleconference with members of the i18n group to work on a possible solution
Joe will seek out comments from user of screen reading software who is not familiar with Sakai
We missed cut off date for 2.9.2. We will target 2.9.3
Sakai Accessible Content Creation Guidelines
Gonzalo suggested we focus on content created through the rich text editor (CKeditor)
A big concern will be HTML files/code directly uploaded
Gonzalo suggested the Guidelines should be based on the capabilities of the CKeditor
Use the CKeditor help files as a starting point
Joe will research capabilities
create a skeleton structure and send it out to the AWG listserv
WCAG 2.0 as basis for guideline?
How to demarcate Jira issues for A11y across projects
Current Sakai of how to Demarcate Jiras
based around Sakai performance issue Jiras
3 month study of the effectiveness of "labels"
Results in June
Downside of using labels is that adding them to Jira tickets does not automatically assign the Jira ticket, unlike a component
Joe biggest concerns
Hard to search for A11y issues across tools and projects
We need consistency across projects
We need to make sure we are capturing all A11y issues and addressing them
Suggestions to accomplish
A11y group tag
Come up with policy
Create components
Joe suggested we wait to create A11y components until label study is done
Add both a label and component
Label to use if we decide to use a label
A11y
Neil cautioned labels are free form and can't be controlled
Sakai Accessibility Working Group Email List
First Topic: ARIA application role
We need to develop or publicize Guidelines for use of the application role
Concrete examples of problems application role
Gonzalo: Lesson Builder
Top level wrapper of tool
Joe will send out starter email before next teleconference
Next Meeting is April 18th, 2013