E-mail List Archives
Re: Landmark and HTML 5
From: Max Starkenburg
Date: Mar 16, 2020 8:59AM
- Next message: Swift, Daniel P.: "Re: Chrome 80 Bug"
- Previous message: Reinhard Stebner: "Re: Chrome 80 Bug"
- Next message in Thread: None
- Previous message in Thread: glen walker: "Re: Landmark and HTML 5"
- View all messages in this Thread
Hi Ritu,
Others have already responded with what I think is sound feedback on this.
For what it's worth, I also wondered about such roles, but only because our
SiteImprove account would flag these redundancies as a supposed "issue" on
sites crawled for us, and because certain folks couldn't be convinced
things like this were actually a non-issue, and/or were overly concerned
with raising our SiteImprove score for the sake of higher-ups incapable of
digesting anything beyond an overly simplistic score, we wasted developer
time "fixing" our pages to remove the redundancies.
Others out there have also told me that continuing to use such redundant
roles encourages others to keep needlessly doing so, allowing makers of
assistive technology or browsers to rest on their non-standard laurels, or
propagating myths about their continued usefulness, but I thought it was
overly flattering to assume anybody would ever look at my code as a paragon
of best practices, haha.
With regard to your second bullet about making the different navigations
uniquely identifiable, my understanding is that, indeed, having different
labels (e.g. via aria-label or aria-labelledby) for the different navs is
quite important/appreciated for screen reader users.
Max
--
Maxwell M. Starkenburg
<EMAIL REMOVED>
https://maxwell.fyi
On Mon, Mar 9, 2020 at 2:21 PM Jayakar, Ritu < <EMAIL REMOVED> > wrote:
> Hello Everyone,
>
>
>
> I find contradictory information on using "role" for the HTML elements
> main, nav, aside and header footer. Some say these elements should be used
> in conjunction with aria role e.g.: <main role="main"> so that screen
> readers which do not recognize HTML 5 can read the role tag to recognize
> the section. My site needs to be tagged with landmark, I need to decide if
> it useful to implement, if yes what is the best practice to implement
> landmarks, add the role to HTML 5 elements or not.
>
>
>
> I plan to main do two things:
>
> 1. Contain all elements/content in landmarks
> 2. Add uniquely identifiable landmarks especially for navigation- we
> have top site navigation, left bar for section navigation, breadcrumbs and
> repeat bottom navigation
>
>
>
> Looking forward to hear your thoughts on this.
>
> Thank you everyone for sharing your expertise with the community.
>
>
>
> Kind Regards
>
> Ritu Jayakar
>
> > > > >
- Next message: Swift, Daniel P.: "Re: Chrome 80 Bug"
- Previous message: Reinhard Stebner: "Re: Chrome 80 Bug"
- Next message in Thread: None
- Previous message in Thread: glen walker: "Re: Landmark and HTML 5"
- View all messages in this Thread