WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: ARIA landmark roles and HTML 5 sectioning elements


From: Laura Fathauer
Date: Jul 23, 2020 7:58AM

What patrick said!

This used to be recommended particularly for IE compatibility, so
you'll probably continue to see this in the wild for some time.

On Thu, Jul 23, 2020 at 9:27 AM Andrews, David B (DEED)
< <EMAIL REMOVED> > wrote:
> The first rule of ARIA is only use ARIA when you can't do something via HTML.
> Dave
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Alan Zaitchik
> Sent: Thursday, July 23, 2020 7:44 AM
> Subject: [WebAIM] ARIA landmark roles and HTML 5 sectioning elements
> This message may be from an external email source.
> Do not select links or open attachments unless verified. Report all suspicious emails to Minnesota IT Services Security Operations Center.
> >
> With recent releases of JAWS, NVDA, and VoiceOver and recent releases of Chrome, Firefox, and Safari, is there any benefit from doubling up with code like <nav role="navigation"> or <footer role="contentinfo"> or even <form="form" >? Are there (still) some popular screen reader-browser combinations, perhaps on mobile devices, that benefit from having both HTML5 elements and also the ARIA roles? (I mean, of course, just in those cases where you do have equivalence.) Is there a downside to doubling up?