chore(a11y): updated a11y scorecard #3980
Conversation
| <a href="https://pf-a11y_5-16-22.surge.sh/"> | ||
| Initial report (May 16th, 2022) | ||
| </a> | ||
| <p>1066 violations found</p> |
There was a problem hiding this comment.
Wondering if this should be the information for the day this new report was ran for April 23 instead. I feel like the context for each new report becomes any a11y issues found as part of that report, rather than the very first report we ever ran.
So the baseline becomes the 24 violations found in this new report, and the Critical and major accessibility violations identified in item #3 resolved (%). criteria item basically becomes "N/A" until we go through to resolve issues.
Mainly wondering because as time goes on, the initial 1066 violations become less pertinent to newer reports. Curious what @jessiehuff @nicolethoen think, though.
There was a problem hiding this comment.
Yeah, I agree with @thatblindgeye. I think the report's terminology might be confusing by calling it "Preliminary accessibility report", but I would think that each scorecard would represent a single point in time.
There was a problem hiding this comment.
Good point, that "initial" data isn't too relevant anymore. What about simply "prior" report? I think either we:
- List the last report that was done (in this case, our live website shows Nov 21, 2022)
- Or we wait to update the scorecard until after work has been done on what we find. Ex: I just found 24 violations, how many have we fixed yet?
- In this case, either it would always show "N/A" as Eric mentioned until we address & merge PRs to make the fixes (and put up another new scorecard changing from N/A to 0), or we'd wait to publish the new scorecard at all until the work is done - when do we call it done, do we have to get to 0 issues before publishing a new scorecard?
There was a problem hiding this comment.
That is also a good point. Maybe we update the "violations resolved" field whenever a new report is ran, rather than when we get to X issues remaining? If we plan to run and update this report more regularly that might be easier, say something like:
- Q1: run initial report. "Violations resolved" is N/A
- Q2: run a new report, and update the "Violations resolved" for the Q1 report
- Q3: run a new report, and update the "Violations resolved" for the Q2 report
- ...etc
That would paint the picture of how many a11y issues we're introducing/resolving between reports, but also keep us a bit accountable since we'd have a schedule of when we need to update that "violations resolved" field. Though that would mean altering that "Violations resolved" field since currently it's expecting to be filled out based on the current report.
Otherwise like you said we'd probably have to do something like run the report Q1 start, but wait to actually upload it until Q1 end with whatever number of violations that have been resolved.
There was a problem hiding this comment.
Thanks for the feedback! I've updated the wording based on this conversation to remove "preliminary" from "preliminary accessibility report", and replace "initial report" with "Q2 2024" which can be updated with each new report.
* chore(a11y): updated a11y scorecard * PR feedback - adjusted 'initial report' section with current data
* fix: bump to latest release candidates ahead of 5.2 release (#3862) * fix: bump to latest release candidates ahead of 5.2 release * bump to latest component groups prerelease * bump react to pull in bug fix * feat: release 5.3 (#3878) * feat: 5.3 release * update release highlights * fix: Bump topology to 5.2.1 (#3881) * fix: toplogy to 5.2.1 * add yarn.lock * update release highlights * Update broken link on develop.md * chore(release): Updated component groups to 5.1.0 release (#3917) * chore(release): releasing packages [ci skip] - @patternfly/ast-helpers@1.4.3 - @patternfly/documentation-framework@5.4.3 chore(component-groups): Updated component groups to 5.1.0 release chore(component-groups): Updated component groups to 5.1.0 release * Updated version.json * feat(Templates): add to org site (#3947) * feat(Templates): add to org site * update versions, fix Th * hide prev version, update screenshots * fix(docs): proper commit (#3968) * feat(docs): update screenshots (#3969) * Update link for deprecated alert (#3956) * feat(docs): fix for missing props tables (#3981) * chore(a11y): updated a11y scorecard (#3980) * chore(a11y): updated a11y scorecard * PR feedback - adjusted 'initial report' section with current data * fix(misc): fix broken about links (#3987) * add comparison table to table guidelines (#4006) * add comparison table to table guidelines * Update table.md * Update table.md * docs(tooltips): Creates separate tooltips writing guide. (#3999) * docs(tooltips): Creates separate tooltips writing guide. * Edits content. * Removes unused image. * Content edits to prep for reviews. * Adds some aria attributes. * Cross link from icons guide. * fix: Incorrectly formatted link (#4024) There was a link that was incorrectly formatted and let to a 404 page * docs: Updates PatternFly mailing list link. (#4030) * fix: update to official alpha omegas * bump docs-framework version --------- Co-authored-by: Donald Labaj <dlabaj@redhat.com> Co-authored-by: kmcfaul <45077788+kmcfaul@users.noreply.github.com> Co-authored-by: Jessie <jhuff@redhat.com> Co-authored-by: Evan <evan.wilkinson@redhat.com> Co-authored-by: Margot <51165119+mmenestr@users.noreply.github.com> Co-authored-by: Erin Donehoo <105813956+edonehoo@users.noreply.github.com> Co-authored-by: Freya Gustavsson <freya@venefilyn.se>
Closes #3744
This PR updates the a11y scorecard with a new report link from 4/23/24 and links to a new epic (#3979) with 24 new bugs.