E-mail List Archives
Thread: Accessible sub menu items
Number of posts in this thread: 6 (In chronological order)
From: Sean Curtis
Date: Wed, Jun 11 2014 1:52AM
Subject: Accessible sub menu items
No previous message | Next message →
Hi List,
I've run into a stumbling block while undertaking some development work I'm
doing to improve the accessibility of a dropdown menu component we use. How
are sub menus handled? We are using the menu and menuitem roles, but there
doesn't seem to be anything in the spec relating to sub menus. I've not had
any luck with Google either, all accessible dropdown menus I find are only
single-level.
Any info would be greatly appreciated.
Cheers,
Sean
From: Bryan Garaventa
Date: Wed, Jun 11 2014 8:02AM
Subject: Re: Accessible sub menu items
← Previous message | Next message →
This is controlled by the aria-haspopup attribute, which is documented in
the menuitem role section at
http://www.w3.org/TR/wai-aria/roles#menuitem
Live demo:
http://whatsock.com/tsg/Coding%20Arena/ARIA%20Menus/Vertical%20(Internal%20C
ontent)/demo.htm
Best wishes,
Bryan
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Sean Curtis
Sent: Wednesday, June 11, 2014 12:52 AM
To: = EMAIL ADDRESS REMOVED =
Subject: [WebAIM] Accessible sub menu items
Hi List,
I've run into a stumbling block while undertaking some development work I'm
doing to improve the accessibility of a dropdown menu component we use. How
are sub menus handled? We are using the menu and menuitem roles, but there
doesn't seem to be anything in the spec relating to sub menus. I've not had
any luck with Google either, all accessible dropdown menus I find are only
single-level.
Any info would be greatly appreciated.
Cheers,
Sean
messages to = EMAIL ADDRESS REMOVED =
From: Sean Curtis
Date: Wed, Jun 11 2014 10:55PM
Subject: Re: Accessible sub menu items
← Previous message | Next message →
Bryan,
Thanks for the example. We used aria-haspopup on the submenus, but this
only announced for NVDA. JAWS and VO both ignored this. We are looking at
adding an aria-label on these submenus with the content of the node + "
submenu". In our testing this has announced much more consistently across
the screen readers. However it feels like it is a bug that JAWS and VO
don't correctly announce the haspopup correctly. I'll be raising this issue
once we create a reduced test case.
Cheers,
Sean
On Thu, Jun 12, 2014 at 12:02 AM, Bryan Garaventa <
= EMAIL ADDRESS REMOVED = > wrote:
> This is controlled by the aria-haspopup attribute, which is documented in
> the menuitem role section at
> http://www.w3.org/TR/wai-aria/roles#menuitem
>
> Live demo:
>
> http://whatsock.com/tsg/Coding%20Arena/ARIA%20Menus/Vertical%20(Internal%20C
> ontent)/demo.htm
>
> Best wishes,
> Bryan
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Sean Curtis
> Sent: Wednesday, June 11, 2014 12:52 AM
> To: = EMAIL ADDRESS REMOVED =
> Subject: [WebAIM] Accessible sub menu items
>
> Hi List,
>
> I've run into a stumbling block while undertaking some development work I'm
> doing to improve the accessibility of a dropdown menu component we use. How
> are sub menus handled? We are using the menu and menuitem roles, but there
> doesn't seem to be anything in the spec relating to sub menus. I've not had
> any luck with Google either, all accessible dropdown menus I find are only
> single-level.
>
> Any info would be greatly appreciated.
>
> Cheers,
>
> Sean
> > > messages to = EMAIL ADDRESS REMOVED =
>
> > > >
From: Bryan Garaventa
Date: Thu, Jun 12 2014 2:40AM
Subject: Re: Accessible sub menu items
← Previous message | Next message →
The issue describe may be a bug in VO, which should be explored, but JAWS
has supported aria-haspopup on ARIA Menus since version 11 using IE8.
Are you just setting focus to the container element, or to each child within
the menu?
Both of these are handled differently, but focus movement and the
positioning of the requisite ARIA attributes is critical for this to work
correctly.
For example, if you set focus to each child, but the element that you set
focus to is not the same element that includes role=menuitem, then this and
its supporting attributes like aria-haspopup will not work correctly.
Similarly, if you set focus to the container element and control selection
without moving focus, then aria-activedescendant must be used to handle
which menuitem is active. As with child node navigation however, if you are
pointing to the ID of an element that is not the same element that includes
role=menuitem, then this will not work correctly either.
Please test the sample I sent using JAWS, and you will hear 'submenu' when
you arrow up and down within the menu items. Confirmed using JAWS 11 through
15 in IE 8 through 11, and in FF.
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Sean Curtis
Sent: Wednesday, June 11, 2014 9:55 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Accessible sub menu items
Bryan,
Thanks for the example. We used aria-haspopup on the submenus, but this only
announced for NVDA. JAWS and VO both ignored this. We are looking at adding
an aria-label on these submenus with the content of the node + "
submenu". In our testing this has announced much more consistently across
the screen readers. However it feels like it is a bug that JAWS and VO don't
correctly announce the haspopup correctly. I'll be raising this issue once
we create a reduced test case.
Cheers,
Sean
On Thu, Jun 12, 2014 at 12:02 AM, Bryan Garaventa <
= EMAIL ADDRESS REMOVED = > wrote:
> This is controlled by the aria-haspopup attribute, which is documented
> in the menuitem role section at
> http://www.w3.org/TR/wai-aria/roles#menuitem
>
> Live demo:
>
> http://whatsock.com/tsg/Coding%20Arena/ARIA%20Menus/Vertical%20(Intern
> al%20C
> ontent)/demo.htm
>
> Best wishes,
> Bryan
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Sean Curtis
> Sent: Wednesday, June 11, 2014 12:52 AM
> To: = EMAIL ADDRESS REMOVED =
> Subject: [WebAIM] Accessible sub menu items
>
> Hi List,
>
> I've run into a stumbling block while undertaking some development
> work I'm doing to improve the accessibility of a dropdown menu
> component we use. How are sub menus handled? We are using the menu and
> menuitem roles, but there doesn't seem to be anything in the spec
> relating to sub menus. I've not had any luck with Google either, all
> accessible dropdown menus I find are only single-level.
>
> Any info would be greatly appreciated.
>
> Cheers,
>
> Sean
> > > list messages to = EMAIL ADDRESS REMOVED =
>
> > > list messages to = EMAIL ADDRESS REMOVED =
>
messages to = EMAIL ADDRESS REMOVED =
From: Bryan Garaventa
Date: Thu, Jun 12 2014 2:48AM
Subject: Re: Accessible sub menu items
← Previous message | Next message →
Apologies, for some reason Outlook broke up the link. The demo url is
http://whatsock.com/tsg/Coding%20Arena/ARIA%20Menus/Vertical%20(Internal%20C
ontent)/demo.htm
Hopefully this one will paste correctly.
The same demos can be found at
http://whatsock.com/tsg
Best wishes,
Bryan
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Bryan Garaventa
Sent: Thursday, June 12, 2014 1:40 AM
To: 'WebAIM Discussion List'
Subject: Re: [WebAIM] Accessible sub menu items
The issue describe may be a bug in VO, which should be explored, but JAWS
has supported aria-haspopup on ARIA Menus since version 11 using IE8.
Are you just setting focus to the container element, or to each child within
the menu?
Both of these are handled differently, but focus movement and the
positioning of the requisite ARIA attributes is critical for this to work
correctly.
For example, if you set focus to each child, but the element that you set
focus to is not the same element that includes role=menuitem, then this and
its supporting attributes like aria-haspopup will not work correctly.
Similarly, if you set focus to the container element and control selection
without moving focus, then aria-activedescendant must be used to handle
which menuitem is active. As with child node navigation however, if you are
pointing to the ID of an element that is not the same element that includes
role=menuitem, then this will not work correctly either.
Please test the sample I sent using JAWS, and you will hear 'submenu' when
you arrow up and down within the menu items. Confirmed using JAWS 11 through
15 in IE 8 through 11, and in FF.
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Sean Curtis
Sent: Wednesday, June 11, 2014 9:55 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Accessible sub menu items
Bryan,
Thanks for the example. We used aria-haspopup on the submenus, but this only
announced for NVDA. JAWS and VO both ignored this. We are looking at adding
an aria-label on these submenus with the content of the node + "
submenu". In our testing this has announced much more consistently across
the screen readers. However it feels like it is a bug that JAWS and VO don't
correctly announce the haspopup correctly. I'll be raising this issue once
we create a reduced test case.
Cheers,
Sean
On Thu, Jun 12, 2014 at 12:02 AM, Bryan Garaventa <
= EMAIL ADDRESS REMOVED = > wrote:
> This is controlled by the aria-haspopup attribute, which is documented
> in the menuitem role section at
> http://www.w3.org/TR/wai-aria/roles#menuitem
>
> Live demo:
>
> http://whatsock.com/tsg/Coding%20Arena/ARIA%20Menus/Vertical%20(Intern
> al%20C
> ontent)/demo.htm
>
> Best wishes,
> Bryan
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Sean Curtis
> Sent: Wednesday, June 11, 2014 12:52 AM
> To: = EMAIL ADDRESS REMOVED =
> Subject: [WebAIM] Accessible sub menu items
>
> Hi List,
>
> I've run into a stumbling block while undertaking some development
> work I'm doing to improve the accessibility of a dropdown menu
> component we use. How are sub menus handled? We are using the menu and
> menuitem roles, but there doesn't seem to be anything in the spec
> relating to sub menus. I've not had any luck with Google either, all
> accessible dropdown menus I find are only single-level.
>
> Any info would be greatly appreciated.
>
> Cheers,
>
> Sean
> > > list messages to = EMAIL ADDRESS REMOVED =
>
> > > list messages to = EMAIL ADDRESS REMOVED =
>
messages to = EMAIL ADDRESS REMOVED =
messages to = EMAIL ADDRESS REMOVED =
From: Jonathan C. Cohn
Date: Sun, Jun 15 2014 2:19PM
Subject: Re: Accessible sub menu items
← Previous message | No next message
One other possibility is your virus protection software. WindowEyes has had specific issues when their apps interact with native objects and a specific virus protection suite. I dont know if this is because of VBS as their scripting language or if the virus protection is actually verifying access to application objects.
Jonathan
Best wishes,
Jonathan
On Jun 12, 2014, at 4:48 AM, Bryan Garaventa < = EMAIL ADDRESS REMOVED = > wrote:
> Apologies, for some reason Outlook broke up the link. The demo url is
> http://whatsock.com/tsg/Coding%20Arena/ARIA%20Menus/Vertical%20(Internal%20C
> ontent)/demo.htm
> Hopefully this one will paste correctly.
>
> The same demos can be found at
> http://whatsock.com/tsg
>
> Best wishes,
> Bryan
>
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Bryan Garaventa
> Sent: Thursday, June 12, 2014 1:40 AM
> To: 'WebAIM Discussion List'
> Subject: Re: [WebAIM] Accessible sub menu items
>
> The issue describe may be a bug in VO, which should be explored, but JAWS
> has supported aria-haspopup on ARIA Menus since version 11 using IE8.
>
> Are you just setting focus to the container element, or to each child within
> the menu?
>
> Both of these are handled differently, but focus movement and the
> positioning of the requisite ARIA attributes is critical for this to work
> correctly.
>
> For example, if you set focus to each child, but the element that you set
> focus to is not the same element that includes role=menuitem, then this and
> its supporting attributes like aria-haspopup will not work correctly.
>
> Similarly, if you set focus to the container element and control selection
> without moving focus, then aria-activedescendant must be used to handle
> which menuitem is active. As with child node navigation however, if you are
> pointing to the ID of an element that is not the same element that includes
> role=menuitem, then this will not work correctly either.
>
> Please test the sample I sent using JAWS, and you will hear 'submenu' when
> you arrow up and down within the menu items. Confirmed using JAWS 11 through
> 15 in IE 8 through 11, and in FF.
>
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Sean Curtis
> Sent: Wednesday, June 11, 2014 9:55 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] Accessible sub menu items
>
> Bryan,
>
> Thanks for the example. We used aria-haspopup on the submenus, but this only
> announced for NVDA. JAWS and VO both ignored this. We are looking at adding
> an aria-label on these submenus with the content of the node + "
> submenu". In our testing this has announced much more consistently across
> the screen readers. However it feels like it is a bug that JAWS and VO don't
> correctly announce the haspopup correctly. I'll be raising this issue once
> we create a reduced test case.
>
> Cheers,
>
> Sean
>
>
> On Thu, Jun 12, 2014 at 12:02 AM, Bryan Garaventa <
> = EMAIL ADDRESS REMOVED = > wrote:
>
>> This is controlled by the aria-haspopup attribute, which is documented
>> in the menuitem role section at
>> http://www.w3.org/TR/wai-aria/roles#menuitem
>>
>> Live demo:
>>
>> http://whatsock.com/tsg/Coding%20Arena/ARIA%20Menus/Vertical%20(Intern
>> al%20C
>> ontent)/demo.htm
>>
>> Best wishes,
>> Bryan
>>
>> -----Original Message-----
>> From: = EMAIL ADDRESS REMOVED =
>> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Sean Curtis
>> Sent: Wednesday, June 11, 2014 12:52 AM
>> To: = EMAIL ADDRESS REMOVED =
>> Subject: [WebAIM] Accessible sub menu items
>>
>> Hi List,
>>
>> I've run into a stumbling block while undertaking some development
>> work I'm doing to improve the accessibility of a dropdown menu
>> component we use. How are sub menus handled? We are using the menu and
>> menuitem roles, but there doesn't seem to be anything in the spec
>> relating to sub menus. I've not had any luck with Google either, all
>> accessible dropdown menus I find are only single-level.
>>
>> Any info would be greatly appreciated.
>>
>> Cheers,
>>
>> Sean
>> >> >> list messages to = EMAIL ADDRESS REMOVED =
>>
>> >> >> list messages to = EMAIL ADDRESS REMOVED =
>>
> > > messages to = EMAIL ADDRESS REMOVED =
>
> > > messages to = EMAIL ADDRESS REMOVED =
>
> > >