Re: Apparent conflict between ARIA 1.1 documents.

Joe,


I just looked at the section in the ARIA in HTML and ANY role is allowed on a <tr>. 

The ARIA spec. says you should not need to have a role=“row” on a <tr> because they mean the same thing. It is not a MUST NOT and it is not illegal to do so. We want to encourage authors to use the native host langage semantics to reduce their footprint where ARIA is not needed.

Rcih


> On Jul 27, 2016, at 10:14 PM, Joe Stephen <JStephen@vfo-group.com> wrote:
> 
> Dear committee,
>  
> Section 2.13 in the document "WAI ARIA Authoring Practices 1.1" at http://w3c.github.io/aria/practices/aria-practices.html <http://w3c.github.io/aria/practices/aria-practices.html>,
> the third note on setting role on TR to ROW seems to contradict section "3. Document conformance requirements for use of ARIA attributes in HTML" in the document "ARIA in HTML" at http://www.w3.org/TR/html-aria/ <http://www.w3.org/TR/html-aria/>.
>  
> "Each row should be clearly marked using a <TR> from HTML and by using a role of 
> row"
> and "Whenever a row is selected, set its role to
> Row and its aria-selected="true".
>  
> The ARIA in HTML section 3 states that a TR should not have a role of ROW, or, more generally, that an HTML element with native semantics should not be given a role with the same semantics.
> Please clarify or fix instances of such contradictions between the documents.
>  
> Joseph Stephen
> VFO | Software Developer
> 11800 31st Court North, St. Petersburg, FL 33716
> T +61 416090232
> jstephen@vfo-group.com <mailto:jstephen@vfo-group.com>
> www.vfo-group.com <http://www.vfo-group.com/>
>  
> <image001.png>
> The contents of this message may be privileged and confidential.  Therefore, if this message has been received in error, please delete it without reading it.  Your receipt of this message is not intended to waive any applicable privilege..  Please do not disseminate this message without the permission of the author.
>