W3C

Site Navigation

Nearby

Results of Questionnaire ACT TF - Rule Review: Button has an accessible name

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 2019-11-19 to 2019-12-05.

9 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 Button has an accessible name 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
Detlev Fischer
Kathy Eng
Trevor Bostic
Charu Pandhi
Mary Jo Mueller
Wilco Fiers
Maureen Kraft
Sailesh Panchang
Kasper Isager Dalsgarð

2. Consistency with ACT Rules Format

Does the rule follow the ACT Rules Format 1.0?

Summary

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

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

Details

Responder Consistency with ACT Rules FormatComments
Detlev Fischer I don't know. My questions are documented below.
Kathy Eng Yes
Trevor Bostic Yes
Charu Pandhi Yes
Mary Jo Mueller Yes
Wilco Fiers Yes
Maureen Kraft Yes
Sailesh Panchang I believe an element with a semantic role of button is more robustly tested by a rule for SC 1.1.1 that requires validation of the purpose conveyed by the text equivalent. Essentially for a native HTML button it is the button content or value or title.
The mere presence of an accessible name may not be satisfactory. It still needs to pass SC 1.1.1.
Even a custom element with role=button will need to pass SC 1.1.1.
Maybe this rule should reference this info and SC 1.1.1 and a rule that supports that.
I apologize if this aspect is already covered ... I could not find it easily.
2. SC 4.1.2 can also kick in to test the state of a button when it is important in certain situations, like pressed or not.
3. Is there a need for this assumption: "The rule assumes that all buttons are user interface components as defined by WCAG 2".
Essentially this rule applies to elements that are confirmed button elements.
If something that is exposed as a button is not one, then the role assigned to the element is incorrect. An element with a semantic role of a button is meant to be an UIC.


Kasper Isager Dalsgarð Yes

3. Rule assumptions

Are the assumptions acceptable?

Summary

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

(2 responses didn't contain an answer to this question)

Details

Responder Rule assumptionsComments
Detlev Fischer
Kathy Eng Yes
Trevor Bostic Yes
Charu Pandhi Yes
Mary Jo Mueller Yes
Wilco Fiers Yes
Maureen Kraft No. I have opened an issue in GitHub or have documented my comments below. Applicability is not clear. "The rule applies to elements that are included in the accessibility tree with the semantic role of button, except for input elements of type="image"." It is not clear if this rule applies or does not apply to input elements of type="image". Would be better to state "The rule applies to elements that are included in the accessibility tree with the semantic role of button. This rule does not apply to input elements of type="image"." Github issue opened, https://github.com/act-rules/act-rules.github.io/issues/1061
Sailesh Panchang
Kasper Isager Dalsgarð Yes

4. Implementation data

Is the implementation data correct?

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 or comments are documented below. 2

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

Details

Responder Implementation dataComments
Detlev Fischer I don't know. My questions or comments are documented below. Should there be an example with disabled state? maybe nit necessary...
Kathy Eng Yes
Trevor Bostic Yes
Charu Pandhi Yes
Mary Jo Mueller I don't know. My questions or comments are documented below.
Wilco Fiers Yes
Maureen Kraft No. I have opened an issue in GitHub or have documented my comments below. Passed Example 1 should state why the element is accessible as opposed to "Regular button". Restate to something like, "Button element name is the accessible name." Opened Github issue https://github.com/act-rules/act-rules.github.io/issues/1062
Sailesh Panchang
Kasper Isager Dalsgarð Yes

5. Consistent with WCAG

Is the rule consistent with existing WCAG documents?

Summary

ChoiceAll responders
Results
Yes 8
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.

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

Details

Responder Consistent with WCAGComments
Detlev Fischer Yes
Kathy Eng Yes
Trevor Bostic Yes
Charu Pandhi Yes
Mary Jo Mueller Yes
Wilco Fiers Yes
Maureen Kraft Yes
Sailesh Panchang
Kasper Isager Dalsgarð Yes

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. 1
Yes, there are open issues but they don't need to be resolved for the rule to be published. 3
No, there are no open issues. 3

(2 responses didn't contain an answer to this question)

Details

Responder Remaining open issuesComments
Detlev Fischer
Kathy Eng Yes, there are open issues but they don't need to be resolved for the rule to be published. PR 1029
Trevor Bostic No, there are no open issues.
Charu Pandhi Yes, there are open issues but they don't need to be resolved for the rule to be published.
Mary Jo Mueller Yes there are open issues that need to be resolved. I have listed them below. Trusted tester has implementation results - see issue 1047. So the question I have is, as we keep moving along will we have to have the task force's additional review and approval as well as the AG WG review and approval any time we have a new implementation to add? Or can we simply update published rules with the implementation info?
Wilco Fiers No, there are no open issues.
Maureen Kraft Yes, there are open issues but they don't need to be resolved for the rule to be published. Update link to HTML Core Mappings to button section. https://github.com/act-rules/act-rules.github.io/issues/1063
Sailesh Panchang
Kasper Isager Dalsgarð 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. 4
No, I have no further questions or concerns. 3

(2 responses didn't contain an answer to this question)

Details

Responder Other questions or concernsComments
Detlev Fischer
Kathy Eng No, I have no further questions or concerns.
Trevor Bostic Yes, I have questions or concerns, described below. I think there is some duplication that could be reduced. Failed example 1 and 3 both have the value attribute in a button, but I think it is clearer to only have the value attribute in example 1. Similarly, inapplicable examples 2 and 4 both revolve around the aria-hidden attribute. I am wondering if inapplicable example 2 should be removed. I think it might only cause more confusion since it not being visible really has no effect on it being inapplicable (though perhaps its good with symmetry for the passed and failed examples). .
Charu Pandhi No, I have no further questions or concerns.
Mary Jo Mueller Yes, I have questions or concerns, described below. Should there also be a test case for a div with ARIA role="button"? What about a link with an ARIA role="button"?
Wilco Fiers Yes, I have questions or concerns, described below. Inapplicable example 2 is problematic. That button is still focusable, this may not fail the rule, but arguably this fails 4.1.2.
Maureen Kraft Yes, I have questions or concerns, described below. Text at top of window overwrites rule text making it difficult to read, "A Community Group of theWorld Wide Web Consortium.

Developed with the support of the EU-funded WAI-Tools Project."
https://github.com/act-rules/act-rules.github.io/issues/1064
Sailesh Panchang
Kasper Isager Dalsgarð 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

(3 responses didn't contain an answer to this question)

Details

Responder Readiness for publishingComments
Detlev Fischer
Kathy Eng 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.
Wilco Fiers No, it is not ready to publish and the reason is documented below. I've opened a pull request to update the examples. They need some tweaks. Pretty minor stuff:

https://github.com/act-rules/act-rules.github.io/pull/1028/files
Maureen Kraft
Sailesh Panchang
Kasper Isager Dalsgarð 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. Chris Loiselle
  6. Jonathan Avila
  7. Rachael Bradley Montgomery
  8. Charles Adams
  9. Daniel Montalvo
  10. Helen Burge
  11. Todd Libby
  12. Thomas Brunet
  13. Catherine Droege
  14. Suji Sreerama
  15. Shane Dittmar
  16. Nayan Padrai
  17. 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

Report issues on GitHub project w3c/wbs-design or by mail to sysreq.