W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2010

[Bug 10618] New: Use "unmapped" rather than "no role" in the weak/strong ARIA tables

From: <bugzilla@jessica.w3.org>
Date: Mon, 13 Sep 2010 02:04:50 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-10618-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10618

           Summary: Use "unmapped" rather than "no role" in the
                    weak/strong ARIA tables
           Product: HTML WG
           Version: unspecified
          Platform: PC
               URL: http://dev.w3.org/html5/spec/content-models.html#table
                    -aria-strong
        OS/Version: All
            Status: NEW
          Keywords: a11y
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: xn--mlform-iua@xn--mlform-iua.no
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html@w3.org
            Blocks: 10066


In ARIA 1.0 draft, role="presentation" is as synonym for "no role": [*]

]] the presentation role causes a given element to be treated as having no
role
    [ snip ] 
<!-- 2. There is no implicit role for span, so only the contents are exposed.
-->
<span> Sample Content </span>

<!-- 3. This role declaration is redundant. -->
<span role="presentation"> Sample Content </span> [[ 

[*] http://www.w3.org/WAI.new/PF/aria/complete#presentation

However, looking at the weak and strong ARIA tables [*][#],  (and also, having
followed your justifications in the bugs), it is clear that "no role" in those
tables are used in another meaning of the word, namely to indicate that ARIA
does not have a fitting role to offer.

[*] http://dev.w3.org/html5/spec/content-models#table-aria-weak
[#] http://dev.w3.org/html5/spec/content-models#table-aria-strong


To have no role is, in ARIA's terminology, equal to be a <span> element or
perhaps a <div>. Thus, in order to avoid misunderstanding and mixing of
concepts, consider using another wording. My proposal is "unmapped" or
"unmappable".

Note that it is not possible to say "presentation", as "presentation" is used
in order to negate an implicit role: ]] An element whose implicit native role
semantics will not be mapped to the accessibility API. [[

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 13 September 2010 02:04:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:24 UTC