Expand scope of accessibility features beyond keyboard-accessibility

Issue #4 resolved
greiner12 created an issue

The spec already references section 2.1 "Make all functionality available from a keyboard." of the WCAG 2.0 Guidelines but #2407 and its subtickets (e.g. #2411 which is the only ticket that's still open), we specified more than keyboard accessibility.

More specifically, we've been referring to WAI-ARIA Authoring Practices 1.1 for the standard as well as referenced W3C's Using ARIA and MDN's Using ARIA guides to help with the implementation.

I do see a few options on how we could tackle those:

  • Refer to WAI-ARIA instead or in addition to WCAG 2.0
  • Include more sections from WCAG 2.0 (e.g. section 2.4 "Provide ways to help users navigate, find content, and determine where they are.")
  • A combination of the above two
  • Don't expand the scope beyond keyboard-accessibility

Comments (3)

  1. Manvel Saroyan
    • Sounds like it requires windows.
    • I do use ChromeVox for current iteration ( http://www.chromevox.com/ ).
  2. Log in to comment