Accessibility Testing for Hyrax

Oct meeting time: Thursday, Oct 5th, 2017, 10am EST

Location: Google Hangout: https://hangouts.google.com/hangouts/_/c4dvatljlzeofeapgzlljsok2ie

Attendees

deibel

Michael Tribone

jrudder

Kate Lynch

Harsh Parekh

Tracy MacMath

Agenda: 

• Update on Hyrax testing and release process/timeline.
• Answer these questions:

1. 1. What is the first phase of testing needed?
      1. Tab through keyboard testing
         1. What am I looking for?
      2. turn off style sheets, 
         1. tab through keyboard
         2. what am i looking for?
            1. page structure
      3. Wave test
      4. screen reader - 
      5. turn around and voice over (software that comes on a mac)
      6. What is first phase? 
         1. Depends on what you are targeting?
         2. Multiple ways (tab vs mouse user)
         3. Hard to answer
            1. Some places focus on screen reader usage
               1. http://accessibility.psu.edu/blockers/
      7. So the questions are?
         1. What testing should we do? 
            1. First Phase
            2. Second Phase
   2. When should it be done?
   3. Who can/should do it?
      
      

• Other topics, next steps.
  
  

Links of interest: 

• Hyrax Testing and Release Process
• Planning and Managing Web Accessibility - https://www.w3.org/WAI/impl/Overview
• Best practices for making accessible mobile and web apps

Tools for testing:

http://wave.webaim.org/

https://www.deque.com/products/axe-core/

Testing spreadsheet for 2.0 beta 4: Does not yet have accessibility testing listed

https://docs.google.com/spreadsheets/d/1as8uiM0ofEd_2u2ThFYJQu5IdJ8ipHOOH9NUOngjlj8/edit?usp=sharing 

Test site: https://nurax.curationexperts.com

Issue reporting https://github.com/curationexperts/nurax/issues

hyrax: https://github.com/samvera/hyrax/labels