RE: Updated menubar examples for ARIA authoring practices guide

Hi Jon,

Using the same software combination as described before, I currently receive an indication of the expanded state when I open one of the vertical submenus. There is presently no indication of whether a submenu has another menu within it. So, I assume from this observation that the aria-expanded property is being announced when it is set to true on the element of role menubar, but not when it is set to false.

Under these conditions, I think the Unicode characters (arrows) are largely redundant, at least with this screen reader/browser combination.

> -----Original Message-----
> From: Gunderson, Jon R [mailto:jongund@illinois.edu]
> Sent: Monday, February 6, 2017 10:05 AM
> To: White, Jason J <jjwhite@ets.org>; Matt King <a11ythinker@gmail.com>;
> 'ARIA Working Group' <public-aria@w3.org>
> Subject: Re: Updated menubar examples for ARIA authoring practices guide
>
> Jason,
>
> Do you find these entity characters distracting since they are redundant with the
> aria properties being announced through speech or are they useful to you (e.g.
> Maybe because they show up in refreshable Braille)?
>
> Jon
>
>
>
>
> On 2/6/17, 9:00 AM, "White, Jason J" <jjwhite@ets.org> wrote:
>
> >
> >
> >> -----Original Message-----
> >> From: Gunderson, Jon R [mailto:jongund@illinois.edu] This was one of
> >> my questions I had in making the changes.  Does using entities a good
> >> or bad practice.
> >[Jason] On the Windows machine at work (running JAWS 18 and Chrome), the
> screen reader speaks the entities but they are either (1) represented on the
> braille display as unknown characters if contracted braille is enabled, or (2)
> omitted entirely from the braille output if computer braille is enabled (i.e.,
> translation is turned off).
> >
> >I haven't tested across different screen readers/operating systems yet (I have
> access to a variety of combinations), but I would expect inconsistent results.
> Thus, I think the answer, for now, is that these Unicode characters can't be
> relied upon to convey information, at least so far as screen readers are
> concerned. This issue should be addressed by screen reader developers.
> >
> >
> >________________________________
> >
> >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.
> >
> >________________________________

________________________________

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 Monday, 6 February 2017 16:04:27 UTC