WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: automatic tab activation sample from ARIA Practices document with current Jaws behaviour

for

From: Clare O'Keeffe
Date: May 17, 2023 12:10PM

I have auto forms mode set to auto as well, and I get the same experience
with ARIA tablists, of not automatically entering forms mode when tabbing
to one with JAWS. I just hit Enter when focused on one of the tabs and that
triggers forms mode. From there things work as expected. I feel like it has
behaved this way for some time for me.

On Wed, May 17, 2023 at 1:31 PM David Farough < <EMAIL REMOVED> >
wrote:

> Thanks for the link.
>
> When I tab to the tabs list I do not hear the sound to indicate the switch
> to focus mode.
> Pressing Insert + z does turn off the virtual cursor,and then I can move
> from tab to tab using the right or left arrow keys. The tab panel does
> change when the focus changes
> But when tabbing to the active panel, I cannot read the content unless I
> turn on the virtual cursor again using insert + z.
> I do have my auto forms mode setting set to auto (the default). .
>
> Maybe it's time to repair Jaws.
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> glen walker
> Sent: Wednesday, May 17, 2023 12:53 PM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] automatic tab activation sample from ARIA Practices
> document with current Jaws behaviour
>
> Both JAWS and NVDA are working ok for me on Chrome and Firefox. I hear an
> audible change when I TAB (key) to the tablist because it automatically
> switches between browse mode and forms mode (or whatever your favorite
> terms are for the two modes). I get the same audible sound when tabbing to
> an input field.
>
> I'm using the default settings in both screen readers which is automatic
> switching between modes. As Jonathan said, you can switch modes manually
> with Ins+Z for JAWS and Ins+space for NVDA.
>
> Here is a partial list of when the mode should automatically switch.
>
> https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/#fundamentalkeyboardnavigationconventions
>
> These are elements that require you to manage the focus and it happens to
> map to the same elements that switch modes automatically. (The input
> element is not in that list because it doesn't require focus management but
> it does switch modes.)
> > > > > > > > >


--
Clare O'Keeffe