W3C

Results of Questionnaire ACT TF - Rule Review: aria-* attribute is defined in WAI-ARIA

The results of this questionnaire are available to anybody. In addition, answers are sent to the following email addresses: team-wcag-act-surveys@w3.org,maryjom@us.ibm.com,wilco.fiers@deque.com

This questionnaire was open from 2020-03-25 to 2020-04-09.

6 answers have been received.

Jump to results for question:

  1. Instructions
  2. Consistency with ACT Rules Format
  3. Rule assumptions
  4. Implementation data
  5. Consistent with WCAG
  6. Remaining open issues
  7. Other questions or concerns
  8. Readiness for publishing

1. Instructions

Review the rule aria-* attribute is defined in WAI-ARIA and answer the questions in this survey.

If there are issues with the rule, you may either open an issue in GitHub or provide details in the entry fields for the applicable question.

Summary

ChoiceAll responders
Results

Details

Responder Instructions
Sailesh Panchang
Wilco Fiers
Jey Nandakumar
Trevor Bostic
Charu Pandhi
Mary Jo Mueller

2. Consistency with ACT Rules Format

Does the rule follow the ACT Rules Format 1.0?

Summary

ChoiceAll responders
Results
Yes 5
No. I have opened an issue in GitHub or have documented my comments below. 1
I don't know. My questions are documented below.

Details

Responder Consistency with ACT Rules FormatComments
Sailesh Panchang No. I have opened an issue in GitHub or have documented my comments below. 1. Why is this rule under consideration as it states:
Accessibility Requirements Mapping: This rule is not required for conformance.
An incorrect ARIA-* attribute nothing for accessibility testing. If an element has aria-unchecked="true", that element will get flagged while doing a test for SC 4.1.2 (manual / automated) as it may not have its state exposed (assuming state is not exposed via a correct property). And if it has another correct property set, presence of aria-unchecked is just a poor code, a matter of code quality.
Such coding issues do not have to be highlighted by a tool. (Note: during a recent call this view was highlighted too: best practices for coding is not what this effort is about).
2. Perhaps a different example should be used if this rule is retained in place of passed-example#3 .
An alert does not need aria-live=assertive.
<div role="alert" aria-live="assertive"> Your session will expire in 60 seconds.</div>
Wilco Fiers Yes
Jey Nandakumar Yes
Trevor Bostic Yes
Charu Pandhi Yes
Mary Jo Mueller Yes

3. Rule assumptions

Are the assumptions acceptable?

Summary

ChoiceAll responders
Results
Yes 5
No. I have opened an issue in GitHub or have documented my comments below.
I don't know. My questions are documented below.

(1 response didn't contain an answer to this question)

Details

Responder Rule assumptionsComments
Sailesh Panchang
Wilco Fiers Yes
Jey Nandakumar Yes
Trevor Bostic Yes
Charu Pandhi Yes
Mary Jo Mueller Yes

4. Implementation data

Is the implementation data correct?

Summary

ChoiceAll responders
Results
Yes 4
No. I have opened an issue in GitHub or have documented my comments below. 1
I don't know. My questions or comments are documented below.

(1 response didn't contain an answer to this question)

Details

Responder Implementation dataComments
Sailesh Panchang
Wilco Fiers Yes
Jey Nandakumar Yes
Trevor Bostic Yes
Charu Pandhi No. I have opened an issue in GitHub or have documented my comments below. Should there be more passing examples with HTML elements with implicit roles for example <button> has role of a button and can use all the attributes allowed for button role.
Mary Jo Mueller Yes

5. Consistent with WCAG

Is the rule consistent with existing WCAG documents?

Summary

ChoiceAll responders
Results
Yes 3
No. I have opened an issue in GitHub or have documented my comments below.
I don't know. My questions or comments are documented below. 2

(1 response didn't contain an answer to this question)

Details

Responder Consistent with WCAGComments
Sailesh Panchang
Wilco Fiers I don't know. My questions or comments are documented below. This rule doesn't map to WCAG. We need to discuss how we want to handle this rule.
Jey Nandakumar Yes
Trevor Bostic Yes
Charu Pandhi Yes
Mary Jo Mueller I don't know. My questions or comments are documented below. Agree with Wilco. Is this rule intended to be an atomic rule to help with testing 4.1.2 Name, Role, Value? In and of itself it doesn't map to WCAG, but if it's part of the tests needed to check that 4.1.2 is met then I can see that.

6. Remaining open issues

Are there any remaining open issues for this rule that were opened prior to this review?

Summary

ChoiceAll responders
Results
Yes there are open issues that need to be resolved. I have listed them below.
Yes, there are open issues but they don't need to be resolved for the rule to be published.
No, there are no open issues. 5

(1 response didn't contain an answer to this question)

Details

Responder Remaining open issuesComments
Sailesh Panchang
Wilco Fiers No, there are no open issues.
Jey Nandakumar No, there are no open issues.
Trevor Bostic No, there are no open issues.
Charu Pandhi No, there are no open issues.
Mary Jo Mueller No, there are no open issues.

7. Other questions or concerns

Do you have any further questions or concerns about this rule?

Summary

ChoiceAll responders
Results
Yes, I have questions or concerns, described below. 1
No, I have no further questions or concerns. 4

(1 response didn't contain an answer to this question)

Details

Responder Other questions or concernsComments
Sailesh Panchang
Wilco Fiers No, I have no further questions or concerns.
Jey Nandakumar No, I have no further questions or concerns.
Trevor Bostic No, I have no further questions or concerns.
Charu Pandhi Yes, I have questions or concerns, described below. I would think it would map to 4.1.2 WCAG rec, if not what?
Mary Jo Mueller No, I have no further questions or concerns.

8. Readiness for publishing

Do you think this rule is ready to be published?

Summary

ChoiceAll responders
Results
Yes, it is ready to publish as-is. 5
Yes, it is ready to publish with the following changes.
No, it is not ready to publish and the reason is documented below.

(1 response didn't contain an answer to this question)

Details

Responder Readiness for publishingComments
Sailesh Panchang
Wilco Fiers Yes, it is ready to publish as-is.
Jey Nandakumar Yes, it is ready to publish as-is.
Trevor Bostic Yes, it is ready to publish as-is.
Charu Pandhi Yes, it is ready to publish as-is.
Mary Jo Mueller Yes, it is ready to publish as-is.

More details on responses

Non-responders

The following persons have not answered the questionnaire:

  1. Katie Haritos-Shea
  2. David MacDonald
  3. Romain Deltour
  4. Alastair Campbell
  5. Detlev Fischer
  6. Chris Loiselle
  7. Jonathan Avila
  8. Rachael Bradley Montgomery
  9. Charles Adams
  10. Kathy Eng
  11. Daniel Montalvo
  12. Helen Burge
  13. Todd Libby
  14. Thomas Brunet
  15. Catherine Droege
  16. Suji Sreerama
  17. Shane Dittmar
  18. Nayan Padrai
  19. Sage Keriazes

Send an email to all the non-responders.


Compact view of the results / list of email addresses of the responders

WBS home / Questionnaires / WG questionnaires / Answer this questionnaire