WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Instructions for Custom Keyboard Shortcuts

for

From: glen walker
Date: Jan 11, 2020 10:03AM

WCAG is the "low bar", so to speak, of what we're trying to achieve.
Anything you can do to make the user experience better for everyone is
always a bonus.

On Fri, Jan 10, 2020 at 11:08 PM Bossley, Peter A. < <EMAIL REMOVED> >
wrote:

> This came up when we were having a similar discussion at my institution
> about top-level menu items with both sub menus and pages themselves. Where
> I landed with this is that if a widget requires non-expected keyboard
> interaction patterns (for whatever reason) the information about that
> shortcut had to be available programmatically associated with the first
> control of that type and also visually present for keyboard reliant users.
>
> Perhaps a strict interpretation of WCAG 2.0 might be argued, but on the
> other hand we specifically adopt expected interaction patterns from Aria
> Authoring Practices in our technical standard for this very reason.
>
> Just my .02.
>
>
>