RE: Would incorrectly implemented landmarks constitute a WCAG failure?

It appears to me that every automated testing tool flags multiple landmarks/regions that do not have unique names/labels as a violation.

1.3.1 Info and Relationships has the use of Landmarks under https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA11

It has this text with the examples as best practice:

There are cases when a particular landmark role could be used more than once on a page, such as on primary and secondary navigation menus. In these cases, identical roles should be disambiguated from each other using a valid technique for labelling regions (see examples below).

Example 2: Multiple landmarks of the same type and aria-labelledby
The following example shows a best practice of how landmarks might be added to an HTML4 or XHTML 1.0 document in situations where there are more than two of the same type of landmark on the same page. For instance, if a navigation role is used multiple times on a Web page, each instance may have a unique label specified using aria-labelledby: 
<div id="leftnav" role="navigaton" aria-labelledby="leftnavheading">
<h2 id="leftnavheading">Institutional Links</h2>
<ul><li>...a list of links here ...</li> </ul></div>
<div id="rightnav" role="navigation" aria-labelledby="rightnavheading">
<h2 id="rightnavheading">Related topics</h2>
<ul><li>...a list of links here ...</li></ul></div>


Alan Smith

From: Jonathan Avila
Sent: Wednesday, May 8, 2019 3:48 PM
To: w3c-wai-ig@w3.org
Subject: RE: Would incorrectly implemented landmarks constitute a WCAG failure?

Many organizations seem to flag multiple nav elements without accessible names as it can be difficult to tell without vision which nav is which especially when they are at the same section level.  I think I've also seen folks flagging multiple asides within the same section if they don't have accessible names.

Jonathan

-----Original Message-----
From: Jan Hellbusch <jan@hellbusch.de> 
Sent: Wednesday, May 8, 2019 11:41 AM
To: 'Lisa Louise Davis (Aquent LLC)' <v-lidav@microsoft.com>; w3c-wai-ig@w3.org
Subject: RE: Would incorrectly implemented landmarks constitute a WCAG failure?

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


> Is there any kind of landmark failure that you'd consider a hard WCAG failure?

* Incorrect markup would be something like coding a navigation bar as <main> or using <header> for content, where the actual header (<h1> ...) is somewhere else.
* Using more than one <header> and/or <footer> for a sectioning or root element.

Besides that, there are a couple of other issues, which may cause problems, but are not necessarily violations:

* unnecessary nesting, e.g.
<nav><nav>
... list of links ...
</nav></nav>
* Identical labelling or not labelling identical elements (mostly <nav> and <aside>). There may be exceptions when two or more regions contain identical content.
* I would also consider omitting content from any region a problem in certain situations. All content should be contained in a region. There may be exceptions.

Jan


--
Hellbusch Accessibility Consulting
Chemnitzer Str. 50, 44139 Dortmund
Tel.: +49 (231) 58054815 Mobil: +49 (163) 3369925
--
Accessibility-Consulting seit 2000

Leistungen, Bücher, Artikel: https://www.barrierefreies-webdesign.de
Blog: https://www.hellbusch.de