Menu Styling page: Consider using aria-current

[carmacleod]

http://w3c.github.io/wai-tutorials/menus/styling/
This page has a section describing how to indicate the current page.
For AT, the best way moving forward will be to use the aria-current attribute:
https://rawgit.com/w3c/aria/master/aria/aria.html#aria-current

So, the following sentence and the "visuallyhidden" class in the example probably should be rewritten using aria-current="page".
"A visually hidden text “Current Page:” indicates the current page for screen readers and other assistive technologies."

[yatil]

Do you know how well this is implemented in browsers/AT?

[carmacleod]

Good question.
Seems to be done for (most of) Chrome: https://bugs.chromium.org/p/chromium/issues/detail?id=609362
and Webkit/VO: https://bugs.webkit.org/show_bug.cgi?id=155469
Not done yet for FF: https://bugzilla.mozilla.org/show_bug.cgi?id=1104947 (please feel free to add a comment to the FF bug saying it would be nice to have this in the tutorial ).

As for Windows AT, it's not there yet. I opened the following for NVDA: nvaccess/nvda#6358
and I am pretty sure that JAWS does not support it yet, but I did not test.

[carmacleod]

Update: I have it on good authority that JAWS 18 (still in beta) supports aria-current. FYI. :)

[yatil]

I feel it is a bit too unreliable to put it in the tutorial as the sole way to indicate the current item, but I think we should make sure to mention it somehow.

[carmacleod]

Awesome! That's perfect. Thanks!

[AndrewArch]

Makes me wonder if our tutorials should make more of a point about
solutions being 'accessibility supported'.

On Friday, 9 September 2016, Carolyn MacLeod [email protected]
wrote:

Awesome! That's perfect. Thanks!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#354 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGzo7waj4Rh5ne4eY8gSBfMGIp1bzxa_ks5qoDBZgaJpZM4J3A32
.

"You have to take on challenges to experience living."
Boris von Engelbrechten

[yatil]

@AndrewArch: I usually shy away from using “accessibility supported” with developers, as they are not used to the squishiness of that term. If I say “accessibility supported”, they say “then give me a table of ALL THE COMBINATIONS of OS, Browsers and AT so I can compare”. And the reality is that even if something is supported, it might be badly supported (like aria-described by in older VoiceOver when it took 10 seconds until it was read – Accessibility Supported or not?). While it would be great to have a http://caniuse.com/ for accessibility feature, I don’t think a lot of people have really hard data for putting this in place and the resources to update it constantly.

[yatil]

… Oh, that said, of course we need to talk about general support :-)

[AndrewArch]

Yes, at least ... talk about general support :-)

On Friday, 9 September 2016, Eric Eggert [email protected] wrote:

… Oh, that said, of course we need to talk about general support :-)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#354 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGzo72mCSBdeakosRvAPRHLbzySK5X51ks5qoQ8cgaJpZM4J3A32
.

"You have to take on challenges to experience living."
Boris von Engelbrechten

[carmacleod]

FYI, aria-current is getting closer to being supported across the board.
Here's a recent blog post from Leonie: http://tink.uk/using-the-aria-current-attribute/
And NVDA has now prioritized aria-current support as P2: nvaccess/nvda#6358

[carmacleod]

Thanks, @yatil !