Accessibility Audit for Ramp

[joncameron]

Description

In order to replace Avalon's media element player with Ramp, we need to do a basic accessibility audit of Ramp to determine where it stands with accessibility and potentially identify any blockers that must be fixed. For example, it seems that it must be possible to navigate the player with keyboard?

Past accessibility review of Avalon notes numerous features relevant to the media player: https://samvera.atlassian.net/wiki/spaces/AVALON/pages/1957953669/Accessibility

May be use to connect with accessibility community of practice on campus for suggestions for tools, etc.

Definition of Done

• [x] Review past accessibility features here and note whether Ramp provides those features or not In comparison with accessibility review of Avalon from before;
  • Ramp provides keyboard navigation within the player, structure navigation, and transcript component
  • Hot-keys work with player functionality (e.g. 'f' key => turn on/off full-screen mode)
• [x] Identify one (or more) tools recommended for basic accessibility audit
  • WAVE – Browser extension for Chrome & Firefox
  • Mozilla Firefox Accessibility assessment
  • Chrome VOX – Screen reader browser extension for Chrome
• [x] Run those tool(s) on the Ramp demo page with content that has multiple sections, captions, and transcript
• [x] Document the major accessibility issues identified
  • Document created for accessibility audio performed for WCAG 2.1 guidelines

[elynema]

Ramp can have hot keys enabled; some work is needed to make sure hotkeys don't take over when the player is not selected (ex: space bar shouldn't control video when typing in search box).