E-mail List Archives
Thread: Screen reader instructions specefic to forms mode
Number of posts in this thread: 3 (In chronological order)
From: Ajay Sharma
Date: Thu, Jan 03 2019 3:32AM
Subject: Screen reader instructions specefic to forms mode
No previous message | Next message →
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
From: Sean Murphy
Date: Thu, Jan 03 2019 4:13AM
Subject: Re: Screen reader instructions specefic to forms mode
← Previous message | Next message →
Suggestions:
Aria-describeby is a better attribute to use for ARIa if you need to give instructions on a form element. The aria-describeby should only trigger when focus is placed on the forms mode. Thus might not interfer with the VPc. You must also test on the Mac and mobile platforms to verify if they work or not.
What type of widget are you designing here? The ARIa 1.0, 1.1 and 1.2 have good design patterns you could look at.
ARIa should be the last resort by the way as most times it causes more issues than not if incorrectly used.
Native HtML is always reocmmended. If you have example code, this would help to give suggestions.
Sean
My experience is the part
> On 3 Jan 2019, at 9:32 pm, Ajay Sharma < = EMAIL ADDRESS 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
> > > >
From: Jonathan Cohn
Date: Thu, Jan 03 2019 7:51AM
Subject: Re: Screen reader instructions specefic to forms mode
← Previous message | No next message
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 ADDRESS 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
> > > >