W3C

Site Navigation

Nearby

Results of Questionnaire ACT TF - Rule Review: Object element has non-empty 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 2020-07-23 to 2020-08-06.

7 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 defined standards
  6. Remaining open issues
  7. Other questions or concerns
  8. Readiness for publishing

1. Instructions

Review the rule Object element has non-empty 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
Wilco Fiers
Kathy Eng
Charu Pandhi
Mary Jo Mueller
Detlev Fischer
Maureen Kraft
Trevor Bostic

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.

Details

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

Details

Responder Rule assumptionsComments
Wilco Fiers No. I have opened an issue in GitHub or have documented my comments below. Seems to me object might be decorative, in which case an empty accessible name is appropriate. I can't think why someone might have a decorative object in their page, so I think it's a reasonable assumption, but it needs to be documented.
Kathy Eng Yes
Charu Pandhi Yes
Mary Jo Mueller No. I have opened an issue in GitHub or have documented my comments below. Agree with Wilco. Should document the assumption that the object being injected is not decorative.
Detlev Fischer Yes
Maureen Kraft Yes
Trevor Bostic Yes

4. Implementation data

Is the implementation data correct?

Summary

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

Details

Responder Implementation dataComments
Wilco Fiers Yes
Kathy Eng Yes
Charu Pandhi I don't know. My questions or comments are documented below. Seems like implementation data can be improved with more examples of different ways alternative text can be added.
Mary Jo Mueller Yes
Detlev Fischer Yes
Maureen Kraft Yes
Trevor Bostic Yes

5. Consistent with defined standards

Is the rule consistent with existing accessibility standards (e.g. WCAG, ARIA, etc.)?

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

Details

Responder Consistent with defined standardsComments
Wilco Fiers I don't know. My questions or comments are documented below. Seems to me like the type of content should effect what SC this is applied to. If you load in an HTML page, it seems to me like this shouldn't be treated as non-text content.
Kathy Eng Yes
Charu Pandhi Yes
Mary Jo Mueller I don't know. My questions or comments are documented below. Would screen readers expect the object element to have a text alternative (short description) even if an HTML object was injected? I think that's the only outlier here. If not, then the rule would have to detect when HTML is being injected and consider that an inapplicable case (if that's possible) or have an accompanying manual rule to check and make that object inapplicable.
Detlev Fischer Yes
Maureen Kraft Yes
Trevor Bostic 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. 5

Details

Responder Remaining open issuesComments
Wilco Fiers No, there are no open issues.
Kathy Eng No, there are no open issues.
Charu Pandhi No, there are no open issues.
Mary Jo Mueller No, there are no open issues.
Detlev Fischer Yes, there are open issues but they don't need to be resolved for the rule to be published. I wonder whether an example fallback content should appear - but note https://github.com/w3c/wcag/issues/1138
Would using fallback content pass this role?
Maureen Kraft Yes, there are open issues but they don't need to be resolved for the rule to be published. Grammatical error in Accessibility Support
"Non supported" should be "Non-supported"
Trevor Bostic 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

Details

Responder Other questions or concernsComments
Wilco Fiers No, I have no further questions or concerns.
Kathy Eng Yes, I have questions or concerns, described below. H53: Using the body of the object element (https://www.w3.org/WAI/WCAG21/Techniques/html/H53.html) to provide the text alternative. None of the test cases have text or text alternatives (all are .mp3). It would be good to include different types of content in the objects.
Charu Pandhi No, I have no further questions or concerns.
Mary Jo Mueller Yes, I have questions or concerns, described below. I agree with Kathy and Charu that more variety of objects are needed for the test cases, including one that embeds a document object. To Kathy's point, this web page (https://www.htmlquick.com/reference/tags/object.html) has examples of using the object element to embed various things: HTML document types, Flash, and an image with alternative text. So examples could draw from that.
Detlev Fischer Yes, I have questions or concerns, described below. See above.
Maureen Kraft Yes, I have questions or concerns, described below. It would be help in Failure examples 1, 2, and 4 to give a further explanation as to why the example fails.
1. because title is empty
2. because the span element with id="label" is empty
4. because it does not provide an accessible name in it's title, an aria-label or aria-labelledby
Trevor Bostic 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. 1
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

Details

Responder Readiness for publishingComments
Wilco Fiers No, it is not ready to publish and the reason is documented below.
Kathy Eng Yes, it is ready to publish with the following changes. Add more variety in test cases (#7 comment)
Charu Pandhi Yes, it is ready to publish with the following changes. improve implementation data
Mary Jo Mueller No, it is not ready to publish and the reason is documented below. Need to address the comments from this survey. I think they're all important.
Detlev Fischer Yes, it is ready to publish with the following changes. Cover the use of fallback content either in the intro text or an explicit (pass? Fail?) example.
Maureen Kraft Yes, it is ready to publish with the following changes.
Trevor Bostic 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
  18. Shunguo Yan

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.