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

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 28 Sep 2010 13:28:07 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1P0aE3-0001BN-H8@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10449

--- Comment #14 from Rich Schwerdtfeger <schwer@us.ibm.com> 2010-09-28 13:28:06 UTC ---
The implementation I posted fails wcag 2 but is perfectly allowable in HTML.
Since it is allowable in HTML it is conforming. The heading tag is not used as
a heading. It would pass any HTML validation test yet it does not convey the
intent of the author and a screen reader user would have difficulty
understanding that the header was used to launch an alert as this is not what
heading should be used for. It would also incorrectly appear in the TOC per the
HTML 5 spec. when it should not. 

It is not the act of placing proper role of the element in HTML that should
make it non-conforming. This is the JavaScript accessibility problem that has
plagued Web 2.0 developers. The editor is undoing what we have fixed with ARIA
re-introducing the JavaScript accessibility problem which is:

Authors are allowed to repurpose HTML elements without the specification
allowing the author to accurately convey the semantics of their work - in
essence producing non compliant WCAG 2 content. 

I agree with Steve. This now needs to be escalated.

-- 
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 Tuesday, 28 September 2010 13:28:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 28 September 2010 13:28:11 GMT