Open mgifford opened 2 years ago
Hello @pjhill and @JoeTice The ticket came in through the Platform website footer. Let me know if you have any questions or need assistance. Thanks, Jill
Slack conversation reference: https://dsva.slack.com/archives/CJRQ85PQB/p1666035245292579
Hi @pjhill! Let us know if we can assist in any way. cc @vbellissimo
@taylojill -- I agree with the sentiment of the feedback offered by Mike. Platform is currently of the disposition that a manual review of accessibility compliance is prudent. The accessibility guidance that we offer generally includes a prescription for manual verification of accessibility standards. The document intended to guide a team through the process of preparing to release their products to production is here and it includes a manual review for accessibility compliance with WCAG standards.
I think a discussion of manual verification intermingled with detailed discussion of specific automated tooling would scatter the information further in a series of documents that are already a bit scattered. If anything I think it would be a good idea to collect information about accessibility testing into fewer more focused documents.
@pjhill Hi Peter, we just wanted to confirm:
Let us know. Thank you! :)
cc @taylojill
I've been going through and reviewing some of our backlog tickets that haven't been touched in a while - this one has sat idle since October 2022.
@pjhill - I saw you were listed as an assignee here. Summarizing the last updates/comments on this, it appeared that a possible course of action, (as of last October), was to add a couple of lines of text around the importance of manual testing on the page Mike specified, as well as possibly linking this resource, https://accessibilityinsights.io/.
If you agree with that possible next step, would you be the right person/ have any bandwidth to help update the documentation on this? If not, our team can work to identify someone else who can help on this if it is still needed.
As an additional note that acknowledges your observation about scattered content, our team is hoping to do a refresh of the Platform Website IA next year, which might lead to a more logical, and better grouping of our docs, and different subject areas like accessibility, QA, etc. We do recognize that currently, some of this information is spread out in a way that isn't ideal.
FYI @JoeTice - tagging you for visibility, as I saw you were listed as an assignee here as well.
Description
I like the work here Keyboard testing helper functions but think it would benefit from having a line about the limits of automated testing. Yes, having hover functionality built into the tests will help considerably. However it is still important to have humans look at the results to see it makes sense. Even just ensuring that the flow is a consistent left-right top-bottom is useful. Pointing to https://accessibilityinsights.io/ might be helpful here. It is the best tool I know of to help document exceptions.
Relevant URLs