w3c/wbs-design or
by mail to sysreq.
W3C
Site Navigation
Nearby
Results of Questionnaire ACT TF - Rule Review: iframe element 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-22 to 2020-01-09.
8 answers have been received.
Jump to results for question:
- Instructions
- Consistency with ACT Rules Format
- Rule assumptions
- Implementation data
- Consistent with WCAG
- Remaining open issues
- Other questions or concerns
- Readiness for publishing
1. Instructions
Review the rule iframe element 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
| Choice | All responders |
|---|---|
| Results |
Details
| Responder | Instructions |
|---|---|
| Romain Deltour | |
| Trevor Bostic | |
| Maureen Kraft | |
| Mary Jo Mueller | |
| Sailesh Panchang | |
| Charu Pandhi | |
| Wilco Fiers | |
| Kathy Eng |
2. Consistency with ACT Rules Format
Does the rule follow the ACT Rules Format 1.0?
Summary
| Choice | All 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. |
Details
| Responder | Consistency with ACT Rules Format | Comments |
|---|---|---|
| Romain Deltour | Yes | |
| Trevor Bostic | Yes | |
| Maureen Kraft | Yes | |
| Mary Jo Mueller | Yes | |
| Sailesh Panchang | Yes | |
| Charu Pandhi | Yes | |
| Wilco Fiers | Yes | |
| Kathy Eng | Yes |
3. Rule assumptions
Are the assumptions acceptable?
Summary
| Choice | All responders |
|---|---|
| Results | |
| Yes | 6 |
| No. I have opened an issue in GitHub or have documented my comments below. | |
| I don't know. My questions are documented below. | 2 |
Details
| Responder | Rule assumptions | Comments |
|---|---|---|
| Romain Deltour | I don't know. My questions are documented below. | I'm not sure I understand this assumption: what would be an iframe that is *not* used as a UI component? Maybe an example would help disambiguate that? |
| Trevor Bostic | Yes | |
| Maureen Kraft | Yes | |
| Mary Jo Mueller | Yes | |
| Sailesh Panchang | Yes | |
| Charu Pandhi | I don't know. My questions are documented below. | It is not clear what exactly is conveyed by the assumption statement "The rule assumes that the target iframe is used as a user interface component." what other ways can an iframe be used? What about iframe with role of presentation? |
| Wilco Fiers | Yes | I think the assumption can be made a little clearer though. Not a blocker. There's an issue open on the ACT-R repo to clarify the assumptions. |
| Kathy Eng | Yes |
4. Implementation data
Is the implementation data correct?
Summary
| Choice | All 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. | 3 |
Details
| Responder | Implementation data | Comments |
|---|---|---|
| Romain Deltour | I don't know. My questions or comments are documented below. | |
| Trevor Bostic | Yes | |
| Maureen Kraft | Yes | |
| Mary Jo Mueller | I don't know. My questions or comments are documented below. | |
| Sailesh Panchang | Yes | |
| Charu Pandhi | I don't know. My questions or comments are documented below. | Example 3 and example 7 are kinda duplicates. Should we add an example when iframe is used for presentation? or with role=presentation. |
| Wilco Fiers | Yes | Although more implementors would be preferable. I'm reaching out to the implementors to update. Used to have more of them. |
| Kathy Eng | Yes | PR #6 is Trusted Tester implementation (https://github.com/act-rules/act-rules-implementation-trusted-tester/pull/6) |
5. Consistent with WCAG
Is the rule consistent with existing WCAG documents?
Summary
| Choice | All 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. |
Details
| Responder | Consistent with WCAG | Comments |
|---|---|---|
| Romain Deltour | Yes | |
| Trevor Bostic | Yes | |
| Maureen Kraft | Yes | |
| Mary Jo Mueller | Yes | |
| Sailesh Panchang | Yes | |
| Charu Pandhi | Yes | |
| Wilco Fiers | Yes | |
| Kathy Eng | Yes |
6. Remaining open issues
Are there any remaining open issues for this rule that were opened prior to this review?
Summary
| Choice | All 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 |
(1 response didn't contain an answer to this question)
Details
| Responder | Remaining open issues | Comments |
|---|---|---|
| Romain Deltour | No, there are no open issues. | |
| Trevor Bostic | 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. | Use proper case in Applicability section. Applicability The rule applies to iframe elements that are included in the accessibility tree. Note: The frame element is deprecated. This rule does not consider frame or frameset elements. <==Added the before frame element and separated into two sentences both starting with uppercase. |
| Mary Jo Mueller | No, there are no open issues. | |
| Sailesh Panchang | ||
| Charu Pandhi | Yes, there are open issues but they don't need to be resolved for the rule to be published. | |
| Wilco Fiers | No, there are no open issues. | |
| Kathy Eng | No, there are no open issues. |
7. Other questions or concerns
Do you have any further questions or concerns about this rule?
Summary
| Choice | All responders |
|---|---|
| Results | |
| Yes, I have questions or concerns, described below. | 3 |
| No, I have no further questions or concerns. | 5 |
Details
| Responder | Other questions or concerns | Comments |
|---|---|---|
| Romain Deltour | Yes, I have questions or concerns, described below. | The accessibility support section says there are no major issues known; however, the glossary entry for "accessible name" describes some interoperability issues with the name and description computation. Shouldn't these issues be mentioned in the rule’s accessibility support? |
| Trevor Bostic | Yes, I have questions or concerns, described below. | From the background section, how is this rule relevant to section 2.4.1? I don't use iframes much, but I am just not sure what the design pattern is that links them to bypass blocks is. -- After a bit of digging I found this: https://www.w3.org/WAI/WCAG21/Techniques/html/H70 which answers my question. |
| Maureen Kraft | Yes, I have questions or concerns, described below. | I think you should expand upon or explain why "All passed outcomes: further testing needed." It makes sense when you see passed example 4, <iframe title=":-)" src="/test-assets/SC4-1-2-frame-doc.html"> </iframe>. You need to validate that the accessible name is meaningful and describes the element. But would be good to state this explicitly maybe in the passed examples. |
| Mary Jo Mueller | No, I have no further questions or concerns. | |
| Sailesh Panchang | No, I have no further questions or concerns. | |
| Charu Pandhi | No, I have no further questions or concerns. | |
| Wilco Fiers | No, I have no further questions or concerns. | |
| Kathy Eng | No, I have no further questions or concerns. |
8. Readiness for publishing
Do you think this rule is ready to be published?
Summary
| Choice | All responders |
|---|---|
| Results | |
| Yes, it is ready to publish as-is. | 5 |
| Yes, it is ready to publish with the following changes. | 3 |
| No, it is not ready to publish and the reason is documented below. |
Details
| Responder | Readiness for publishing | Comments |
|---|---|---|
| Romain Deltour | Yes, it is ready to publish with the following changes. | If my concern above is relevant, the accessibility support section needs to be edited. |
| Trevor Bostic | Yes, it is ready to publish as-is. | |
| Maureen Kraft | Yes, it is ready to publish with the following changes. | I think you should expand upon or explain why "All passed outcomes: further testing needed." It makes sense when you see passed example 4, <iframe title=":-)" src="/test-assets/SC4-1-2-frame-doc.html"> </iframe>. You need to validate that the accessible name is meaningful and describes the element. But would be good to state this explicitly maybe in the passed examples. Github issue: https://github.com/act-rules/act-rules.github.io/issues/1078 |
| Mary Jo Mueller | Yes, it is ready to publish as-is. | |
| Sailesh Panchang | Yes, it is ready to publish as-is. | |
| Charu Pandhi | Yes, it is ready to publish with the following changes. | concerns raised above. |
| Wilco Fiers | Yes, it is ready to publish as-is. | |
| Kathy Eng | Yes, it is ready to publish as-is. |
More details on responses
Non-responders
The following persons have not answered the questionnaire:
- Katie Haritos-Shea
- David MacDonald
- Detlev Fischer
- Chris Loiselle
- Jonathan Avila
- Rachael Bradley Montgomery
- Charles Adams
- Daniel Montalvo
- Todd Libby
- Thomas Brunet
- Catherine Droege
- Suji Sreerama
- Shane Dittmar
- 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