w3c/wbs-design or
by mail to sysreq.
W3C
Site Navigation
Nearby
Results of Questionnaire ACT TF - Rule Review: HTML page language is valid
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-02-10 to 2020-02-19.
6 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
The rule HTML page language is valid and Pull request 1106 to resolve comments in Issue 429 from the previous survey.
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 |
|---|---|
| Wilco Fiers | |
| Charu Pandhi | |
| Kathy Eng | |
| Mary Jo Mueller | |
| Jonathan Avila | |
| Jey Nandakumar |
2. Consistency with ACT Rules Format
Does the rule follow the ACT Rules Format 1.0?
Summary
| Choice | All 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 Format | Comments |
|---|---|---|
| Wilco Fiers | No. I have opened an issue in GitHub or have documented my comments below. | There's something buggy in the way the changelog is created. This rule has been updated, but the date and changelog do not reflect this. Should not stop us from publishing this rule though. |
| Charu Pandhi | Yes | |
| Kathy Eng | Yes | |
| Mary Jo Mueller | Yes | Agree with Wilco that the issue with the change log not being current shouldn't affect publication. However, an issue should be opened to get the change log generation code fixed. |
| Jonathan Avila | Yes | |
| Jey Nandakumar | 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. |
Details
| Responder | Rule assumptions | Comments |
|---|---|---|
| Wilco Fiers | Yes | |
| Charu Pandhi | Yes | |
| Kathy Eng | Yes | |
| Mary Jo Mueller | Yes | |
| Jonathan Avila | Yes | |
| Jey Nandakumar | Yes |
4. Implementation data
Is the implementation data correct?
Summary
| Choice | All responders |
|---|---|
| Results | |
| Yes | 4 |
| No. I have opened an issue in GitHub or have documented my comments below. | 2 |
| I don't know. My questions or comments are documented below. |
Details
| Responder | Implementation data | Comments |
|---|---|---|
| Wilco Fiers | Yes | |
| Charu Pandhi | Yes | |
| Kathy Eng | No. I have opened an issue in GitHub or have documented my comments below. | Failed Ex 2 should pass since rule is only looking at the primary language subtag. Failed Example 2 This html element has a lang attribute whose value is not a valid language subtag. Even though the primary language subtag is valid, the region subtag is not. <html lang="en-US-GB"></html> If this is changed to pass, implementations (other than Axe) currently fail this. |
| Mary Jo Mueller | No. I have opened an issue in GitHub or have documented my comments below. | Once the issue is merged, there will be 2 passing examples, so the implementation table will need updating before publishing. We have the test results, they just have to be adjusted so the result showing for the old "Failed example 2" is shown for the new "Passed example 2" and the failed examples 3 and 4 need to be renumbered to 2 and 3. Easy fix if someone can do it before the AG WG survey. |
| Jonathan Avila | Yes | |
| Jey Nandakumar | Yes |
5. Consistent with WCAG
Is the rule consistent with existing WCAG documents?
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 or comments are documented below. |
Details
| Responder | Consistent with WCAG | Comments |
|---|---|---|
| Wilco Fiers | Yes | |
| Charu Pandhi | Yes | |
| Kathy Eng | Yes | |
| Mary Jo Mueller | Yes | |
| Jonathan Avila | Yes | |
| Jey Nandakumar | 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. | 2 |
| Yes, there are open issues but they don't need to be resolved for the rule to be published. | 1 |
| No, there are no open issues. | 3 |
Details
| Responder | Remaining open issues | Comments |
|---|---|---|
| Wilco Fiers | Yes, there are open issues but they don't need to be resolved for the rule to be published. | There's a pull request resolving this. |
| Charu Pandhi | No, there are no open issues. | |
| Kathy Eng | Yes there are open issues that need to be resolved. I have listed them below. | https://github.com/act-rules/act-rules.github.io/issues/1105 |
| Mary Jo Mueller | Yes there are open issues that need to be resolved. I have listed them below. | The issue 1105 listed by Kathy has a pull request that was included in this survey that fixes the issue. The pull request was in final call in the CG which is now complete so the changes can be merged and the issue closed (although, not sure if the update to the implementations should also be fixed using this issue or a new one opened). |
| Jonathan Avila | No, there are no open issues. | |
| Jey Nandakumar | 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. | |
| No, I have no further questions or concerns. | 6 |
Details
| Responder | Other questions or concerns | Comments |
|---|---|---|
| Wilco Fiers | No, I have no further questions or concerns. | |
| Charu Pandhi | No, I have no further questions or concerns. | |
| Kathy Eng | No, I have no further questions or concerns. | |
| Mary Jo Mueller | No, I have no further questions or concerns. | |
| Jonathan Avila | No, I have no further questions or concerns. | |
| Jey Nandakumar | 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. | 3 |
| Yes, it is ready to publish with the following changes. | 2 |
| No, it is not ready to publish and the reason is documented below. | 1 |
Details
| Responder | Readiness for publishing | Comments |
|---|---|---|
| Wilco Fiers | Yes, it is ready to publish with the following changes. | #1106 needs to be merged. |
| Charu Pandhi | Yes, it is ready to publish as-is. | |
| Kathy Eng | No, it is not ready to publish and the reason is documented below. | Failed Example 2. |
| Mary Jo Mueller | Yes, it is ready to publish with the following changes. | Merge the pull request and update the implementation table with the results posted for the moved test case. |
| Jonathan Avila | Yes, it is ready to publish as-is. | |
| Jey Nandakumar | 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
- Romain Deltour
- Alastair Campbell
- Detlev Fischer
- Chris Loiselle
- Rachael Bradley Montgomery
- Charles Adams
- Daniel Montalvo
- Helen Burge
- Todd Libby
- Thomas Brunet
- Catherine Droege
- Suji Sreerama
- Shane Dittmar
- Nayan Padrai
- 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