WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: role=navigation

for

From: Birkir R. Gunnarsson
Date: Oct 12, 2016 8:55AM

It ultimately boils down to the type of user agents you wish to support.
If you are happy supporting browsers/screen readres (current version -
2) the<nav> element is mapped to role="navigation" in all of them (I
think).
To be extra sure, add an accessible name to the <nav> element using
aria-label or aria-labelledby (it is good practice anyway).
If you need to support some older versions that understand
role=Navigation" but not the <nav> element, yu can add the role
explicitly, it is, in the words of the Hitchhiker's Guide to the
Galaxy "Mostly harmless".
Cheers
-B





On 10/12/16, Trafford, Logan < <EMAIL REMOVED> > wrote:
> Is the redundancy of using role=-navigation- on the <nav> tag still
> relevant? The info supporting the need for the redundancy (on the w3.org
> site) seems to be a couple of years old and I saw a more current thread on
> the drupal site that leads one in the opposite direction.
>
> Secondly, can anyone point me in the direction of a good (working) example
> of accessible pagination?
>
> thanks
>
> Logan Trafford
> City of Ottawa
> 613-580-2424 16936
>
>
> This e-mail originates from the City of Ottawa e-mail system. Any
> distribution, use or copying of this e-mail or the information it contains
> by other than the intended recipient(s) is unauthorized. Thank you.
>
> Le présent courriel a été expédié par le système de courriels de la Ville
> d'Ottawa. Toute distribution, utilisation ou reproduction du courriel ou des
> renseignements qui s'y trouvent par une personne autre que son destinataire
> prévu est interdite. Je vous remercie de votre collaboration.
> > > > >


--
Work hard. Have fun. Make history.