W3C

Site Navigation

Nearby

Results of Questionnaire ACT TF - Rule Review: Scrollable element is keyboard accessible

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-09-23 to 2020-10-08.

6 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 accessibility requirements
  6. Remaining open issues
  7. Other questions or concerns
  8. Rule is up-to-date
  9. Readiness for publishing

1. Instructions

Review the rule Scrollable element is keyboard accessible. 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
Levon Spradlin
Kathy Eng
Mary Jo Mueller
Charu Pandhi
Trevor Bostic

2. Consistency with ACT Rules Format

Does the rule follow the ACT Rules Format 1.0?

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

Details

Responder Consistency with ACT Rules FormatComments
Wilco Fiers Yes
Levon Spradlin Yes
Kathy Eng Yes
Mary Jo Mueller Yes
Charu Pandhi Yes
Trevor Bostic Yes

3. Rule assumptions

Are the assumptions acceptable?

Summary

ChoiceAll responders
Results
Yes 3
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
Wilco Fiers Yes
Levon Spradlin Yes
Kathy Eng I don't know. My questions are documented below. Please clarify "other way"s that scroll can be controlled, if not by keyboard, to meet 2.1.1 Keyboard?

From: Scrollable elements that do not need to be keyboard accessible, perhaps because their content is purely decorative or because *scroll can be controlled some other way*, may fail this rule but still satisfy success criterion 2.1.1 Keyboard.
Mary Jo Mueller I don't know. My questions are documented below. How does one get around the requirement for keyboard access as stated in the 2nd sentence?
Charu Pandhi No. I have opened an issue in GitHub or have documented my comments below. >>scroll can be controlled some other ways<< does this mean overflow? i think this can be clrafied more a bit
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.

Details

Responder Implementation dataComments
Wilco Fiers Yes
Levon Spradlin Yes
Kathy Eng Yes
Mary Jo Mueller Yes
Charu Pandhi Yes
Trevor Bostic Yes Not sure if this should be included in the rule (possibly as an accessibility support item), but Firefox seems to automatically add any elements with overflow: scroll to the tab order. So failed example 1 actually kind of passes on Firefox. If you explicitly set tabindex="-1" then this is no longer the case. I am unsure if this is intended or a FF bug.

5. Consistent with accessibility requirements

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. 1

Details

Responder Consistent with accessibility requirementsComments
Wilco Fiers Yes
Levon Spradlin Yes
Kathy Eng Yes
Mary Jo Mueller I don't know. My questions or comments are documented below. Yes...other than the statement about allowing scroll to be controlled some other way. e.g. Touch is "some other way", but I would say that still doesn't take away the requirement for allowing keyboard access.
Charu Pandhi 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.
No, there are no open issues. 6

Details

Responder Remaining open issuesComments
Wilco Fiers No, there are no open issues.
Levon Spradlin No, there are no open issues.
Kathy Eng No, there are no open issues.
Mary Jo Mueller No, there are no open issues.
Charu Pandhi No, there are no open issues.
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. 2
No, I have no further questions or concerns. 4

Details

Responder Other questions or concernsComments
Wilco Fiers No, I have no further questions or concerns.
Levon Spradlin 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.
Charu Pandhi Yes, I have questions or concerns, described below. Can we assume being in sequential focus navigation also mean keyboard operable? what if the control does not have keyboard even handlers?
Trevor Bostic Yes, I have questions or concerns, described below. Is there any further value from having a horizontal-scroll passed example? Or changing one of the passed examples to be horizontal instead of both being vertical?

8. Rule is up-to-date

Is the rule up to date? If so, the accessibility support should still be relevant, it should follow the recommended writing style, and use up to date links.

Summary

ChoiceAll responders
Results
Yes, all information is up-to-date. 6
No, it needs the following changes.
I don't know, but I have the following concerns.

Details

Responder Rule is up-to-dateComments
Wilco Fiers Yes, all information is up-to-date.
Levon Spradlin Yes, all information is up-to-date.
Kathy Eng Yes, all information is up-to-date.
Mary Jo Mueller Yes, all information is up-to-date.
Charu Pandhi Yes, all information is up-to-date.
Trevor Bostic Yes, all information is up-to-date.

9. 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. 5
No, it is not ready to publish and the reason is documented below.

Details

Responder Readiness for publishingComments
Wilco Fiers Yes, it is ready to publish with the following changes. I proposed this minor change of moving the note to the background: https://github.com/act-rules/act-rules.github.io/pull/1453
Levon Spradlin Yes, it is ready to publish as-is.
Kathy Eng Yes, it is ready to publish with the following changes. Please see my #3 response.
Mary Jo Mueller Yes, it is ready to publish with the following changes. See my and other's comments. I think we're real close on this one though.
Charu Pandhi Yes, it is ready to publish with the following changes. See my concern in #3 and #7
Trevor Bostic Yes, it is ready to publish with the following changes. See earlier comments.

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. Detlev Fischer
  6. Chris Loiselle
  7. Jonathan Avila
  8. Rachael Bradley Montgomery
  9. Charles Adams
  10. Daniel Montalvo
  11. Helen Burge
  12. Todd Libby
  13. Thomas Brunet
  14. Catherine Droege
  15. Suji Sreerama
  16. Shane Dittmar
  17. Nayan Padrai
  18. 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 w3c/wbs-design or by mail to sysreq.