- From: Sailesh Panchang <spanchang02@yahoo.com>
- Date: Tue, 5 May 2015 09:21:02 -0700
- To: public-pfwg-comments@w3.org
Greetings WG, Ref: http://www.w3.org/TR/wai-aria/roles Statement#1: When a WAI-ARIA role is provided, user agents MUST use the semantic of the WAI-ARIA role for processing, not the native semantic, unless the role requires WAI-ARIA states and properties whose attributes are explicitly forbidden on the native element by the host language. Statement #2: When a host language declares a WAI-ARIA attribute to be in direct semantic conflict with a native attribute for a given element, user agents MUST ignore the WAI-ARIA attribute and instead use the host language attribute with the same implicit semantic. Confusing: "unless the _role_ requires WAI-ARIA states and properties whose attributes are explicitly forbidden on the native element ": Q1. The "role" in above statement refers to WAI-ARIA role? I suppose so. Q2. What does "WAI-ARIA states and properties whose attributes" mean? The term "attributes" generally refers to "states and properties", no? Refer to statement#2 which is cleaner and clearer insofar as use of the term "WAI-ARIA attributes" is concerned. Q3. One reason for placing an ARIA-role on a native element may be to repurpose the native element and employ ARIA states/properties that are not supported by the native element, no? If this is so, is it necessary to include the "unless ..." clause in Statement#1 at all? Or does it mean if the native element forbids the attributes, then user agent are supposed to ignore the ARIA-role placed on the element? Note: I have included statement#2 solely to contrast usage of states and properties / attributes. I understand the terms are sort of interchangeable, but I find the manner the terms are placed in the statement#1 is confusing. Thanks and regards, Sailesh Panchang
Received on Tuesday, 5 May 2015 16:24:30 UTC