W3C home > Mailing lists > Public > public-html@w3.org > January 2013

Re: Context of the main element

From: Jeremy Keith <jeremy@adactio.com>
Date: Thu, 31 Jan 2013 18:47:10 +0000
Cc: "HTML WG (public-html@w3.org)" <public-html@w3.org>
Message-Id: <6D06D303-7F0D-4D72-B7DA-5D2BAAFEB0AB@adactio.com>
To: Cameron Jones <cmhjones@gmail.com>
Cam asked:
> But what is the main-main content of the page then? I need to direct accessibility users to the "main" content of the *whole* page. How can that be determined if there are more than one of them?

In *exactly* the same way that user agents determine which footer element corresponds to the role "contentinfo", or which header element corresponds to "banner", or which nav element corresponds to "navigation" …by its context!

> That definition is also against the ARIA specification

So is allowing header to appear more than once in a document. So is allowing footer to appear more than once in a document. So is allowing nav to appear more than once in a document.

And yet user agents are able to figure out *which* occurrence of those elements corresponds to ARIA landmark roles: By. Its. Context.

Following your logic, header and footer should also only be allowed once per document, because when they are scoped to the document body, they correspond to ARIA landmark roles that can only be used once per document (banner, contentinfo). And yet we allow them to be used within sectioning content because user agents can easily figure out their scope.

The same goes for main.


Jeremy Keith

a d a c t i o

Received on Thursday, 31 January 2013 18:47:38 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:30 UTC