W3C home > Mailing lists > Public > public-aria@w3.org > February 2017

RE: Updated menubar examples for ARIA authoring practices guide

From: Matt King <a11ythinker@gmail.com>
Date: Mon, 6 Feb 2017 16:01:37 -0800
To: "'White, Jason J'" <jjwhite@ets.org>, "'Gunderson, Jon R'" <jongund@illinois.edu>, "'ARIA Working Group'" <public-aria@w3.org>
Message-ID: <002601d280d5$5ab868f0$10293ad0$@gmail.com>
Jason, we have a vertical menubar in the plan.

-----Original Message-----
From: White, Jason J [mailto:jjwhite@ets.org] 
Sent: Monday, February 6, 2017 11:21 AM
To: Matt King <a11ythinker@gmail.com>; 'Gunderson, Jon R' <jongund@illinois.edu>; 'ARIA Working Group' <public-aria@w3.org>
Subject: RE: Updated menubar examples for ARIA authoring practices guide

> -----Original Message-----
> From: Matt King [mailto:a11ythinker@gmail.com] The simple answer is 
> that we don’t use labels or characters to duplicate what states and 
> properties communicate. If a screen reader is not supporting a state 
> or property, then that is a screen reader issue.
[Jason] I agree, and (with the combination that I tested) the relevant aria-expanded state is treated appropriately by the screen reader.
As an aside, I would be interested to know how screen readers respond to aria-orientation="vertical", applied to a vertical menu with role="menubar" (i.e., the non-default case).


This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

Thank you for your compliance.

Received on Tuesday, 7 February 2017 00:02:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 7 February 2017 00:02:14 UTC