WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Screen reader instructions specefic to forms mode

for

From: Jonathan Cohn
Date: Jan 3, 2019 7:51AM

Ah, there is no such thing as virtual PC mode in most screen readers, try not to implement things based on a single vendors solution unless you are building for a specific client that sole sources that product. And as was already stated if your widget fits into the paradigm of one of the existing ARIA patterns your best bet for operational success is to use that pattern. Personally I get very annoyed if I am reminded overtime I get focus on an element to click on this element to enable typing, or other such instruction. Assuming your interface is fairly intuitive but does have some extra keystrokes doing something like what Google and twitter do whereby if you type a question mark to the app a popup describing keystrokes available is presented. Or you might have an off-screen focusable element near the top of the DODOM or just before the widget that provides a link to instructions for screen reader users.
> On Jan 3, 2019, at 5:32 AM, Ajay Sharma < <EMAIL REMOVED> > wrote:
>
> Hey All,
>
> We have a custom widget that we want to make compatible in both VPC
> and forms mode.
>
> Currently it is easily accessible in VPC but for forms mode
> compatibility there is slightly different keyboard operation.
>
> So the requirement is to provide this instruction to screen reader
> users, only when they are navigating in forms mode.
>
> An alternative is to provide this instruction by marking the widget
> container as region and providing instruction inside aria-label, but
> in this way SR read it in VPC as well which is not required.
> Please share your thoughts on it.
>
> Happy New Year!
> Ajay
> > > >