WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [External] making a toolbar a landmark

for

From: Jon Bodnar
Date: Mar 9, 2025 3:12PM

Hi,

I'm not familiar with the application(?) you're referencing. But if the navigation is more like an application menu than site navigation, maybe the menu role? Or just a clear accessible name on the nav element would be an improvement.

--Jon

From: WebAIM-Forum < <EMAIL REMOVED> > on behalf of Jeff Gutsell via WebAIM-Forum < <EMAIL REMOVED> >
Sent: Sunday, March 9, 2025 4:11:27 PM
To: <EMAIL REMOVED> < <EMAIL REMOVED> >
Cc: <EMAIL REMOVED> < <EMAIL REMOVED> >
Subject: [External] [WebAIM] making a toolbar a landmark

Hi All,

Yesterday, I stumbled across code I wrote in the summer of 2000 for an
online help system that was required to mimic the look and feel of the old
Microsoft compiled HTML Help. I have been shaking my head at how little
accessibility my creation showed. Such were the times.

While pondering the many ways I would change this now, I got to thinking
about the toolbar at the top of every page. This toolbar was not in a
landmark. These days, if the top of the page had a popup navigation menubar,
that almost certainly would be a page landmark using the <nav> element.

Would it be worthwhile to put such a toolbar in a landmark? Is there a rule
of thumb for how to decide this?

I am thinking the landmark would be a section element with an aria label.



Jeff Gutsell




CAUTION: This email was sent from someone outside of the university. Do not click links or open attachments unless you recognize the sender and know the content is safe.
s61A4ef3l74X5Sa77QJi