W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > December 2012

[Bug 20420] Clarify, with ARIA language, if role of <main> can be overridden.

From: <bugzilla@jessica.w3.org>
Date: Tue, 18 Dec 2012 17:43:44 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-20420-2486-KMeM9oPFlq@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20420

Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |xn--mlform-iua@xn--mlform-i
                   |                            |ua.no
         Resolution|FIXED                       |---

--- Comment #2 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> ---
(In reply to comment #1)
> I have updated the spec:
> 
> "The Strong native semantics and default implicit ARIA semantics for the
> main element is the ARIA landmark role of main. Conforming ARIA role
> attribute tokens for the main element are main and presentation."

I think this resolution is self-contradicting. I understand you to say that
<main> should have strong semantic. However, in that case, then it *cannot* be
allowed to have the role presentation.

At least, when I look at the two ARIA tables that HTML5 has, then for the
elemetns of strong semantics, they are not allowed to take any other semantics
than those which are listed in that table.

http://w3.org/html/wg/drafts/html/master/dom#sec-strong-native-semantics

Wheras for the other table, then all elements/features defaults take the
semantics that are listed in that table *but* in addition to that - says the
text below the table - they can also take presentation role. 

http://w3.org/html/wg/drafts/html/master/dom#sec-implicit-aria-semantics

So if <main> authors are supposed to - *conformingly* – give <main> the
presentation role, then <main> *cannot* have strong native semantics (since
storng native semantics implies that the role can not conformingly be overruled
by the author).

I think the text becomes correct if you just delete "Strong native semantics"
from it.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 18 December 2012 17:43:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 18 December 2012 17:43:45 GMT