RE: Apparent conflict between ARIA 1.1 documents.

Hey Joe

 

Always nice to see fresh faces. Welcome aboard.

Please open issues for these on Github, then we can discuss them in the
weekly ARIA APG meetings (next meeting is scheduled for next Monday).

As for this particular suggestion. There are times where the explicit role
needs to be added for assistive technology/user agent support, the implicit
ARIA ARIA semantic alone is not enough yet.

Try e.g.

<h2 aria-level="3">This is an h3 heading</h2>

(screen readers should announce this as an h3 heading) Has not worked in any
user agent/A.T. combination I have tested, however

<h2 role="heading" aria-level="3">This is an h3 heading</h2>

Works in most combinations.

 

Ditto if you try to assign an accessible name to a form element using
aria-label or aria-labelledby, barely announced in any combination, but if
you add role="form" to the <form> element the support is pretty good.

 

The "ARIA in HTML spec" is correct, it shouldn't be needed, but in practice
there are still instances where it is needed.

From: Joe Stephen [mailto:JStephen@vfo-group.com] 
Sent: Wednesday, July 27, 2016 11:15 PM
To: public-aria@w3.org
Cc: Nataliya Ivanova <NIvanova@vfo-group.com>
Subject: Apparent conflict between ARIA 1.1 documents.

 

Dear committee,

 

Section 2.13 in the document "WAI ARIA Authoring Practices 1.1" at
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/.

 

"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

 <mailto:jstephen@vfo-group.com> jstephen@vfo-group.com

 <http://www.vfo-group.com> www.vfo-group.com

 



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.