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

[Bug 10449] Consider allowing various command-like ARIA roles for h1-h6

From: <bugzilla@jessica.w3.org>
Date: Fri, 10 Sep 2010 05:11:52 +0000
To: public-html-a11y@w3.org
Message-Id: <E1Otvtw-0001RY-UV@jessica.w3.org>

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|WONTFIX                     |

--- Comment #5 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>  2010-09-10 05:11:52 ---
(In reply to comment #4)
> Could you give an example of <h1> being validly used in ways that these roles
> would be suitable for?

yes, <summary>

HTML5 has role="heading" as strong native semantics for  <summary>.
And yet, <summary> is an intereactive element.

(PS: We probaly need a bug to track whether role="heading" is correct for
<summary> The aria-html5-proposal suggest no default role. )

However, unless HTML5's strong semantics <summary role="heading"> was an error
on your part, then it seems to me that you are fully able to imagine that
element can serve a double purpose - as button and as heading.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Friday, 10 September 2010 05:11:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:55:44 UTC