E-mail List Archives
Thread: ARIA-Multiselectable and JAWS?
Number of posts in this thread: 8 (In chronological order)
From: Hunziker, Dawn A - (hunziker)
Date: Tue, Jun 09 2020 3:36PM
Subject: ARIA-Multiselectable and JAWS?
No previous message | Next message →
Hi all,
I've run into an issue where our sites are using an ARIA property of "Multiselectable". It is being used to create expand/collapse menu items such as the ones shown at https://www.arizona.edu/faculty-awards-honors
These expand/collapse options work great with simple keyboard access and work as expected with NVDA. However, when using JAWS, the options do not expand/collapse and JAWS jumps to a link that is displayed prior to that section. I did find a GitHub page that shows that multiselectable as questionable for support... https://freedomscientific.github.io/VFO-standards-support/aria.html
Has anyone else seen this issue?
Bear Down,
Dawn
Dawn Hunziker
IT Accessibility Consultant, Sr. | Disability Resources
The University of Arizona | = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
drc.arizona.edu<http://drc.arizona.edu/>; | itaccessibility.arizona.edu<http://itaccessibility.arizona.edu/>;
520-626-9409
From: Jonathan Avila
Date: Tue, Jun 09 2020 4:26PM
Subject: Re: ARIA-Multiselectable and JAWS?
← Previous message | Next message →
Hi Dawn, I believe a more simple Accordion pattern would likely suffice hear rather than a tab pattern. Then multi-selectable would not be needed.
Jonathan
-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Hunziker, Dawn A - (hunziker)
Sent: Tuesday, June 9, 2020 5:36 PM
To: = EMAIL ADDRESS REMOVED =
Subject: [WebAIM] ARIA-Multiselectable and JAWS?
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi all,
I've run into an issue where our sites are using an ARIA property of "Multiselectable". It is being used to create expand/collapse menu items such as the ones shown at https://www.arizona.edu/faculty-awards-honors
These expand/collapse options work great with simple keyboard access and work as expected with NVDA. However, when using JAWS, the options do not expand/collapse and JAWS jumps to a link that is displayed prior to that section. I did find a GitHub page that shows that multiselectable as questionable for support... https://freedomscientific.github.io/VFO-standards-support/aria.html
Has anyone else seen this issue?
Bear Down,
Dawn
Dawn Hunziker
IT Accessibility Consultant, Sr. | Disability Resources The University of Arizona | = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
drc.arizona.edu<http://drc.arizona.edu/>; | itaccessibility.arizona.edu<http://itaccessibility.arizona.edu/>;
520-626-9409
From: glen walker
Date: Tue, Jun 09 2020 4:30PM
Subject: Re: ARIA-Multiselectable and JAWS?
← Previous message | Next message →
I like to consider myself pretty familiar with most of the ARIA attributes
but I must say I've never used aria-multiselectable. The spec (
https://www.w3.org/TR/wai-aria/#aria-multiselectable) does say you can use
the attribute with role="tablist", which you are using, but your menu items
look like an accordion to me, and a simple aria-expanded should suffice,
https://www.w3.org/TR/wai-aria-practices/#accordion
From: glen walker
Date: Tue, Jun 09 2020 4:40PM
Subject: Re: ARIA-Multiselectable and JAWS?
← Previous message | Next message →
I also noticed (although you didn't ask :-) ), that your "About" menu has
some items with an indicator (triangle) meaning they open in separate pages
and others that don't have an indicator. From a pure AA conformance
perspective, you don't necessarily have to convey that a link opens a new
tab (although some might say that 2.4.4 implies an "opens in new page" is
necessary to convey the "purpose" of the link). However, the fact that you
have a visual clue that a link opens in a new page *would* require that you
convey that same information to assistive technology because there's a
"relationship" conveyed through presentation (1.3.1).
That is, if none of the links had the triangle indicator but some of them
opened in new pages, you don't necessarily have to convey that to assistive
technology (because it's not conveyed to anyone). But if you have a visual
clue that something different will happen, that "something different"
should be conveyed to everyone.
From: Birkir R. Gunnarsson
Date: Tue, Jun 09 2020 7:22PM
Subject: Re: ARIA-Multiselectable and JAWS?
← Previous message | Next message →
Yeap, you're definitely overcomplicating this a lot here.
A simple accordion pattern will do.
You can even use the HTML5 <details>/<summary> attributes to create it
without hardly any ARIA whatsoever (granted IE11 support is not good,
but outside of that browser support is pretty good).
A multi-selectable tab pattern is definitely not what you want to do here.
In Iceland we call this "crossing the river to get water", when you
over complicate stuff, but the good news is that simpler is easier.
On 6/9/20, glen walker < = EMAIL ADDRESS REMOVED = > wrote:
> I also noticed (although you didn't ask :-) ), that your "About" menu has
> some items with an indicator (triangle) meaning they open in separate pages
> and others that don't have an indicator. From a pure AA conformance
> perspective, you don't necessarily have to convey that a link opens a new
> tab (although some might say that 2.4.4 implies an "opens in new page" is
> necessary to convey the "purpose" of the link). However, the fact that you
> have a visual clue that a link opens in a new page *would* require that you
> convey that same information to assistive technology because there's a
> "relationship" conveyed through presentation (1.3.1).
>
> That is, if none of the links had the triangle indicator but some of them
> opened in new pages, you don't necessarily have to convey that to assistive
> technology (because it's not conveyed to anyone). But if you have a visual
> clue that something different will happen, that "something different"
> should be conveyed to everyone.
> > > > >
--
Work hard. Have fun. Make history.
From: Hunziker, Dawn A - (hunziker)
Date: Tue, Jun 09 2020 7:46PM
Subject: Re: [EXT] ARIA-Multiselectable and JAWS?
← Previous message | Next message →
Thank you, everyone! I appreciate the feedback and have passed this information on to our developers. I appreciate the quick responses and I was hoping it would be something easy!
Thank you,
Dawn
Dawn Hunziker
IT Accessibility Consultant, Sr. | Disability Resources
The University of Arizona | = EMAIL ADDRESS REMOVED =
drc.arizona.edu | itaccessibility.arizona.edu
520-626-9409
-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Birkir R. Gunnarsson
Sent: Tuesday, June 9, 2020 6:23 PM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: [EXT]Re: [WebAIM] ARIA-Multiselectable and JAWS?
External Email
Yeap, you're definitely overcomplicating this a lot here.
A simple accordion pattern will do.
You can even use the HTML5 <details>/<summary> attributes to create it without hardly any ARIA whatsoever (granted IE11 support is not good, but outside of that browser support is pretty good).
A multi-selectable tab pattern is definitely not what you want to do here.
In Iceland we call this "crossing the river to get water", when you over complicate stuff, but the good news is that simpler is easier.
On 6/9/20, glen walker < = EMAIL ADDRESS REMOVED = > wrote:
> I also noticed (although you didn't ask :-) ), that your "About" menu
> has some items with an indicator (triangle) meaning they open in
> separate pages and others that don't have an indicator. From a pure
> AA conformance perspective, you don't necessarily have to convey that
> a link opens a new tab (although some might say that 2.4.4 implies an
> "opens in new page" is necessary to convey the "purpose" of the link).
> However, the fact that you have a visual clue that a link opens in a
> new page *would* require that you convey that same information to
> assistive technology because there's a "relationship" conveyed through presentation (1.3.1).
>
> That is, if none of the links had the triangle indicator but some of
> them opened in new pages, you don't necessarily have to convey that to
> assistive technology (because it's not conveyed to anyone). But if
> you have a visual clue that something different will happen, that "something different"
> should be conveyed to everyone.
> > > archives at http://webaim.org/discussion/archives
> >
--
Work hard. Have fun. Make history.
From: glen walker
Date: Tue, Jun 09 2020 9:20PM
Subject: Re: ARIA-Multiselectable and JAWS?
← Previous message | Next message →
I like that! Can you say it in Icelandic, Birkir?
I'm going to work that saying into my next presentation.
On Tue, Jun 9, 2020 at 7:22 PM Birkir R. Gunnarsson <
= EMAIL ADDRESS REMOVED = > wrote:
>
> In Iceland we call this "crossing the river to get water", when you
> over complicate stuff, but the good news is that simpler is easier.
>
>
From: Birkir R. Gunnarsson
Date: Wed, Jun 10 2020 6:30AM
Subject: Re: ARIA-Multiselectable and JAWS?
← Previous message | No next message
The exact wording is
"sækja vatn yfir lækinn"
(literally, crossing the brook to fetch water", means to over
complicate or put unnecessary effort into something.
On 6/9/20, glen walker < = EMAIL ADDRESS REMOVED = > wrote:
> I like that! Can you say it in Icelandic, Birkir?
>
> I'm going to work that saying into my next presentation.
>
> On Tue, Jun 9, 2020 at 7:22 PM Birkir R. Gunnarsson <
> = EMAIL ADDRESS REMOVED = > wrote:
>
>>
>> In Iceland we call this "crossing the river to get water", when you
>> over complicate stuff, but the good news is that simpler is easier.
>>
>>
> > > > >
--
Work hard. Have fun. Make history.