- From: <bugzilla@jessica.w3.org>
- Date: Tue, 12 Oct 2010 15:49:34 +0000
- To: public-html-a11y@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10914
Rich Schwerdtfeger <schwer@us.ibm.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |schwer@us.ibm.com
--- Comment #14 from Rich Schwerdtfeger <schwer@us.ibm.com> 2010-10-12 15:49:33 UTC ---
This is an override of the WAI-ARIA Implementation guide that is normative and
is inconsistent with what we agreed on from the HTML working group:
http://www.w3.org/WAI/PF/aria-implementation/#mapping_role
Henri was involved in these discussions in fact. The implementation guide is
quite clear on how the role attribute is mapped.
In future version of WAI-ARIA we want to be able to expand on the fact that a
role can take mulitiple values. While, like any specification, this would
require us to work with user agent manufacturers. We do not want to be
unnecessarily restricted by HTML on this point. The ARIA specification clearly
states how the role attribute is processed and HTML must not restrict its
implementation.
So, in essence the validator must allow multiple roles to be passed and user
agents must defer to the ARIA implementation guide to ensure proper processing
of the role attribute. So, I would agree with Ian's comments that HTML 5 should
defer to ARIA on this one and the validator be corrected. Should ARIA.next
decide to change the processing of the role value passed it must clearly define
how to process them. However, it should not be a validation error if multiple
values are passed.
Since the specification defers to ARIA on the use of role I see no issue with
the HTML 5 specification here. The validator implementation is however
incorrect. It must allow for multiple role values.
--
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 Tuesday, 12 October 2010 15:49:35 UTC