w3c/wbs-design
or
by mail to sysreq
.
The results of this questionnaire are available to anybody.
This questionnaire was open from 2022-05-26 to 2022-06-07.
10 answers have been received.
Jump to results for question:
The ACT Task Force would like to publish the following rule:
SVG element with explicit role has non-empty accessible name
Do you agree with the proposal from the ACT Task Force to publish this rule?
Choice | All responders |
---|---|
Results | |
I approve of the rule being published | 8 |
I approve of the rule being published with adjustments (please comment) | |
I do not approve because (please comment) |
(2 responses didn't contain an answer to this question)
Responder | New rule: SVG element with explicit role has non-empty accessible name | Comments |
---|---|---|
Shawn Lawton Henry | ||
Wilco Fiers | I approve of the rule being published | |
Michael Gower | I approve of the rule being published | |
Bruce Bailey | I approve of the rule being published | |
John Foliot | I approve of the rule being published | |
Todd Libby | I approve of the rule being published | |
Mary Jo Mueller | I approve of the rule being published | |
Ben Tillyer | ||
Laura Carlson | I approve of the rule being published | |
Gregg Vanderheiden | I approve of the rule being published |
The ACT Task Force would like to publish the following rule:
Element with presentational children has no focusable content
Do you agree with the proposal from the ACT Task Force to publish this rule?
Choice | All responders |
---|---|
Results | |
I approve of the rule being published | 7 |
I approve of the rule being published with adjustments (please comment) | |
I do not approve because (please comment) |
(3 responses didn't contain an answer to this question)
Responder | New Rule: Element with presentational children has no focusable content | Comments |
---|---|---|
Shawn Lawton Henry | ||
Wilco Fiers | I approve of the rule being published | |
Michael Gower | ||
Bruce Bailey | I approve of the rule being published | |
John Foliot | I approve of the rule being published | |
Todd Libby | I approve of the rule being published | |
Mary Jo Mueller | I approve of the rule being published | I'm sure you've had conversations on this, but I'm wondering why this rule doesn't map to 2.4.3 Focus Order. If focus goes to items that have no programmatic meaning, one could argue that this affects the aspect of the requirement, "focusable components receive focus in an order that preserves meaning and operability". Though I won't hold up publication on this note. |
Ben Tillyer | ||
Laura Carlson | I approve of the rule being published | |
Gregg Vanderheiden | I approve of the rule being published |
The ACT Task Force would like to publish the following rule:
headers attribute specified on a cell refers to cells in the same table element
Do you agree with the proposal from the ACT Task Force to publish this rule?
Choice | All responders |
---|---|
Results | |
I approve of the rule being published | 5 |
I approve of the rule being published with adjustments (please comment) | 2 |
I do not approve because (please comment) |
(3 responses didn't contain an answer to this question)
Responder | New Rule: headers attribute specified on a cell refers to cells in the same table element | Comments |
---|---|---|
Shawn Lawton Henry | ||
Wilco Fiers | I approve of the rule being published | |
Michael Gower | ||
Bruce Bailey | I approve of the rule being published | |
John Foliot | I approve of the rule being published | |
Todd Libby | I approve of the rule being published | |
Mary Jo Mueller | I approve of the rule being published with adjustments (please comment) | The testcase that best matches the title of the rule isn’t covered nor discussed. - No testcase that covers headers that reference an id within another table element. - Inapplicable 3 is visible to a screen reader, so I question that this isn’t applicable. I would agree it’s not applicable if it were display:none or visibilty:hidden. |
Ben Tillyer | ||
Laura Carlson | I approve of the rule being published | |
Gregg Vanderheiden | I approve of the rule being published with adjustments (please comment) | see MJ comments |
ACT Task Force has reviewed and approved a number of small changes to existing rules. These include:
The ACT Task Force requests AG to publish updates to existing rules approved with the above changes.
Choice | All responders |
---|---|
Results | |
I approve of publishing the updates | 6 |
I approve of publishing the updates with adjustments (please comment) | |
I do not approve because (please comment) |
(4 responses didn't contain an answer to this question)
Responder | Update Approved ACT Rules | Comments |
---|---|---|
Shawn Lawton Henry | ||
Wilco Fiers | I approve of publishing the updates | |
Michael Gower | ||
Bruce Bailey | I approve of publishing the updates | |
John Foliot | I approve of publishing the updates | |
Todd Libby | I approve of publishing the updates | |
Mary Jo Mueller | Comments on "Programmatically Hidden": - This sentence is difficult to understand as written. "The HTML standard suggests rendering elements with the hidden attribute with a CSS rule that applies the value none to the CSS property display of the element." Not sure what to suggest to make it better. - Editorial: "Contrarily" should be "Contrary" | |
Ben Tillyer | ||
Laura Carlson | I approve of publishing the updates | |
Gregg Vanderheiden | I approve of publishing the updates |
Please review:
As described in ACT's Work statement, the ACT Task Force has been working on improve how we track which accessibility test tools and methodologies have implemented which ACT Rules. Something that is also part of the W3C-lead WAI-CooP project. This effort is a continuation of work previously done by the ACT-Rules Community Group.
The purpose of the implementation matrix is to give greater insight into which test tools and methodologies have adopted ACT Rules, and to what extend they have done so. The matrix only includes tools and methodologies that have made test results available to the ACT Task Force. We are in contact with various other organisations to get more test results. Our hope is that by publishing this list, we can encourage other tool and methodology vendors to start aligning their test solutions with ACT Rules, and so improve consistency of testing across the web accessibility industry.
The ACT Task Force would like AG's opinion on publishing these implementation pages. We are still working on some slight editorial and usability aspects, which may lead to minor changes before publication.
Choice | All responders |
---|---|
Results | |
I approve of publishing the matrix | 5 |
I approve of publishing the matrix with the following adjustments (please comment) | 3 |
I do not approve because (please comment) |
(2 responses didn't contain an answer to this question)
Responder | DONE: ACT Test Tools & Methodology Matrix | Comments |
---|---|---|
Shawn Lawton Henry | I approve of publishing the matrix with the following adjustments (please comment) | Some important edits and issues, and some minor suggestions for consideration: https://github.com/w3c/wcag-act-rules/pull/103 |
Wilco Fiers | I approve of publishing the matrix | |
Michael Gower | I approve of publishing the matrix with the following adjustments (please comment) | Focus handling isn't controlled very well. If I execute on an example, i think it should open in a new window by default so that I can close the example window and be at my prior point of interaction. In the current implementation, keyboard users lose their point of regard when trying to return to the example list (focus is lost from list). |
Bruce Bailey | I approve of publishing the matrix | |
John Foliot | I approve of publishing the matrix with the following adjustments (please comment) | It would be helpful to also cross link tools to their "homes" on the web (i.e. furnish URLs to the tools/resources in question) |
Todd Libby | I approve of publishing the matrix | |
Mary Jo Mueller | On the ACT Test Tools & Methodology Matrix page in the Understanding ACT Consistency section: should there be a link from the "report the outcome in a standard format" to the expected standard reporting format? | |
Ben Tillyer | I approve of publishing the matrix | |
Laura Carlson | I approve of publishing the matrix | |
Gregg Vanderheiden |
Please review the Redesigned ACT page header, which include the following changes from the current design:
The ACT Task Force has a number or proposed rules that test for requirements from WAI-ARIA that are not part of WCAG 2. Because of this, we believe the existing heading of "WCAG 2 Test Rules" needs to change. We propose returning to "ACT Rules" as the overarching name of our work, and within that grouping rules based on which standard they test for (WCAG 2, WAI-ARIA, possibly more in the future.)
The ACT Task Force requests that AG publish the updated page designs. We are still working on some slight editorial and usability aspects, which may lead to minor changes before publication.
Choice | All responders |
---|---|
Results | |
I approve of publishing the updated pages | 6 |
I approve of publishing the updated pages with the following adjustments (please comment) | 3 |
I do not approve because (please comment) |
(1 response didn't contain an answer to this question)
Responder | DONE: Separate WCAG Rules from Other ACT Rules | Comments |
---|---|---|
Shawn Lawton Henry | I approve of publishing the updated pages with the following adjustments (please comment) | Some important edits and issues, and some minor suggestions for consideration: https://github.com/w3c/wcag-act-rules/pull/103 |
Wilco Fiers | I approve of publishing the updated pages | |
Michael Gower | I approve of publishing the updated pages | I'm not sure how easy/practical it is to distinguish between rules for a technique and rules for WCAG. I understand the concept that failing a technique rule does not mean the requirement is failed. But the opposite isn't true, right? Passing a sufficient technique should in most circumstances (unless otherwise indicated) mean a pass of WCAG for that consideration, I believe? |
Bruce Bailey | I approve of publishing the updated pages with the following adjustments (please comment) | I agree that rules testing for implementation of WAI-ARIA that are not part of WCAG -- so the existing heading needs to change. Making Accessibility **Conformance** Testing Rules the parent heading is good. But there is still the unresolved contradiction of framing ACT Rules addressing WAI-ARIA as **conformance** because WAI-ARIA is not a "standard" in the same way WCAG is. I think it may be the case that ACT Rule, because they are granular, are more about validation than "conformance". ACT Rules are a valuable part of a conformance process/evaluation, but just making ACT Rules the parent heading is not the only semantic difficulty. Current: This page contains list of ACT Rules to test conformance Web Content Accessibility Guidelines (WCAG) , WAI-ARIA and other accessibility practices. ACT Rules for WCAG 2 are formally approved by the Accessibility Guidelines Working Group. Proposed: This page contains list of procedures (ACT Rules) to aid with assessing conformance to Web Content Accessibility Guidelines (WCAG), WAI-ARIA, and other accessibility best practices. ACT Rules are formally approved by the Accessibility Guidelines Working Group. |
John Foliot | I approve of publishing the updated pages | |
Todd Libby | I approve of publishing the updated pages | |
Mary Jo Mueller | I approve of publishing the updated pages with the following adjustments (please comment) | As a suggestion, deprecated rules should be listed at the bottom of the sorted list (or in a separate list). I don't know if the list of deprecated rules will grow or not but it seems odd to have them appear in the middle of the list of valid rules. |
Ben Tillyer | I approve of publishing the updated pages | |
Laura Carlson | I approve of publishing the updated pages | |
Gregg Vanderheiden |
Please review the new sections 2.6, 2.7, and 2.8: ACT Common Input Aspects.
These input aspects are used in a number of proposed ACT rules, but their definitions were never formalized. The ACT Task Force requests for AG to publish the updated ACT Common Input Aspects note, with these new sections.
Choice | All responders |
---|---|
Results | |
I approve of publishing the updated note | 5 |
I approve of publishing the updated note with the following adjustments (please comment) | 2 |
I do not approve because (please comment) |
(3 responses didn't contain an answer to this question)
Responder | DONE: Update ACT Rules Common Input Aspects | Comments |
---|---|---|
Shawn Lawton Henry | ||
Wilco Fiers | I approve of publishing the updated note | |
Michael Gower | I approve of publishing the updated note with the following adjustments (please comment) | I wonder if there is a different word/term than "input aspects" that could be used in the document title? I read this and immediately assumed it concerned input types. Since some of the 'input' aspects as actually outputs, at the least this is very open to confusion. Since this is really about atomic aspects, is that a better term? I'd request the group consider possible other terms to persue. |
Bruce Bailey | I approve of publishing the updated note | |
John Foliot | I approve of publishing the updated note with the following adjustments (please comment) | Simply as a comment/question, is it worth considering also including 'haptic output' as bullet 2.9? |
Todd Libby | I approve of publishing the updated note | |
Mary Jo Mueller | I approve of publishing the updated note | Editorial: In "Video Output" fix "RUle" to be "Rule". |
Ben Tillyer | ||
Laura Carlson | I approve of publishing the updated note | |
Gregg Vanderheiden |
The following persons have not answered the questionnaire:
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
w3c/wbs-design
or
by mail to sysreq
.