W3C

Site Navigation

Nearby

Results of Questionnaire ACT TF - Rule Review: Image button has 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 Image button has 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
Wilco Fiers
Kathy Eng
Trevor Bostic
Jonathan Avila
Charu Pandhi
Mary Jo Mueller
Maureen Kraft
Kasper Isager Dalsgarð

2. Consistency with ACT Rules Format

Does the rule follow the ACT Rules Format 1.0?

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 are documented below. 1

Details

Responder Consistency with ACT Rules FormatComments
Detlev Fischer I don't know. My questions are documented below.
Wilco Fiers Yes
Kathy Eng Yes
Trevor Bostic Yes
Jonathan Avila Yes
Charu Pandhi Yes
Mary Jo Mueller Yes
Maureen Kraft Yes
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

Details

Responder Rule assumptionsComments
Detlev Fischer Yes
Wilco Fiers Yes
Kathy Eng Yes
Trevor Bostic Yes
Jonathan Avila I don't know. My questions are documented below.
Charu Pandhi I don't know. My questions are documented below. Should the rule specify someplace with a note that the rule does not check if the accessible name is meaningful?
Mary Jo Mueller Yes
Maureen Kraft No. I have opened an issue in GitHub or have documented my comments below. Applicability is very confusing. "The rule applies to any HTML input element with a type attribute in the Image Button state, that is included in the accessibility tree.

Note: The specification of the type attribute describes in detail how to map the value of the attribute to its corresponding state."

Examples all show input elements with type="image", not sure what you mean by "ype attribute in the Image Button state,"
https://github.com/act-rules/act-rules.github.io/issues/1065
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. 1

(2 responses 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. If this is the same as "Test cases" (cnnot find a heading implementation data) I noted that Failure example 2 and 4 seem identically described (not sure whether there is a significant difference between alt="" and alt=" " in any UA/AT context of use that really needs to be pointed out - if not, one example would suffice)
Wilco Fiers Yes
Kathy Eng Yes
Trevor Bostic Yes
Jonathan Avila
Charu Pandhi Yes
Mary Jo Mueller There's a Trusted Tester implementation in issue 1046
Maureen Kraft No. I have opened an issue in GitHub or have documented my comments below. Similar to applicability, Inapplicable Example 2, is confusing.

"The input element with type with a type attribute in the Button state is not an image button. Success Criterion 1.1.1 Non-text Content can not fail text buttons. Only non-text content is applicable."

type is an attribute and not a state. I would simplify to read

"The input element with type with a type attribute in the Button is not applicable to this rule. The rule [Button has accessible name](https://act-rules.github.io/rules/97a4e1#applicability) applies to Button elements. Success Criterion 1.1.1 Non-text Content can not fail text buttons. Only non-text content is applicable."
Kasper Isager Dalsgarð Yes

5. Consistent with WCAG

Is the rule consistent with existing WCAG documents?

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

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

Details

Responder Consistent with WCAGComments
Detlev Fischer Yes
Wilco Fiers Yes
Kathy Eng Yes
Trevor Bostic Yes
Jonathan Avila
Charu Pandhi Yes
Mary Jo Mueller Yes
Maureen Kraft
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.
Yes, there are open issues but they don't need to be resolved for the rule to be published. 2
No, there are no open issues. 4

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

Details

Responder Remaining open issuesComments
Detlev Fischer
Wilco Fiers No, there are no open issues.
Kathy Eng No, there are no open issues.
Trevor Bostic No, there are no open issues.
Jonathan Avila Yes, there are open issues but they don't need to be resolved for the rule to be published. I posted a comment in github related to whether the fallback name provided by browsers (and recommended in the AAM) should or should not be used in the calculation.
Charu Pandhi Yes, there are open issues but they don't need to be resolved for the rule to be published.
Mary Jo Mueller Multiple issues - 1046, 1057, and 1054.
Maureen Kraft
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.
No, I have no further questions or concerns. 6

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

Details

Responder Other questions or concernsComments
Detlev Fischer
Wilco Fiers No, I have no further questions or concerns.
Kathy Eng No, I have no further questions or concerns.
Trevor Bostic No, I have no further questions or concerns.
Jonathan Avila
Charu Pandhi No, I have no further questions or concerns.
Mary Jo Mueller No, I have no further questions or concerns.
Maureen Kraft
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. 3
Yes, it is ready to publish with the following changes. 4
No, it is not ready to publish and the reason is documented below.

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

Details

Responder Readiness for publishingComments
Detlev Fischer Yes, it is ready to publish with the following changes. Possibly simplify by merging Failure example 2 and 4 (but there may be a difference that I fail to appreciate) - or clarify the difference ( "Image button element with empty accessible name." and "accessible name is empty." fail to clarify the difference IMO.)
Wilco Fiers Yes, it is ready to publish with the following changes. I've opened two pull requests for this. Fairly minor stuff. I can certainly live with publishing the rules the way they are now, but I suspect AG is going to want these fixes to the examples.

- https://github.com/act-rules/act-rules.github.io/pull/1032
- https://github.com/act-rules/act-rules.github.io/pull/1033
Kathy Eng Yes, it is ready to publish with the following changes. PR 1033, https://github.com/act-rules/act-rules.github.io/pull/1033
Trevor Bostic Yes, it is ready to publish as-is.
Jonathan Avila
Charu Pandhi Yes, it is ready to publish as-is.
Mary Jo Mueller Yes, it is ready to publish with the following changes. I like the changes Wilco proposed in PR 1033 (though we should resolve Jonathan Avila's concerns where he commented on the pull request). I think PR 1032 should also be merged in. These will make it better for the next review by the AG WG.
Maureen Kraft
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. Chris Loiselle
  5. Rachael Bradley Montgomery
  6. Charles Adams
  7. Daniel Montalvo
  8. Todd Libby
  9. Thomas Brunet
  10. Catherine Droege
  11. Suji Sreerama
  12. Shane Dittmar
  13. Nayan Padrai

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.