Accessibility WG Teleconference Minutes 04-04-2013

• 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 
•  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
  
   

• 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?
  
  • 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

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
    

• 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