Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determining work needed from DAC Audit May 2023 #3592

Closed
12 tasks done
Tracked by #3329
CharlotteDowns opened this issue May 9, 2023 · 4 comments
Closed
12 tasks done
Tracked by #3329

Determining work needed from DAC Audit May 2023 #3592

CharlotteDowns opened this issue May 9, 2023 · 4 comments
Assignees
Labels
accessibility WCAG 2.2 All items related to WCAG 2.2 update activities

Comments

@CharlotteDowns
Copy link
Contributor

CharlotteDowns commented May 9, 2023

What

We've requested an external accessibility audit with the Digital Accessibility Centre (DAC) that is due to take place on the 9th May 2023. The audit is scheduled to take 3.5 days in total.

Why

This WCAG 2.2 audit supports our efforts to #3040.

As we approach the publishing date for WCAG 2.2, we want to ensure our existing govuk-frontend elements are meeting all WCAG 2.1 AA criteria. The only way to pass WCAG 2.2 AA is to also meet all criteria in WCAG 2.1 AA (with one exception, where a criterion is being removed).
We're doing other work to assess where updates are needed to align elements with the 9 new WCAG 2.2 criteria, but we likely don't have capacity to run an internal audit across all of the existing 78 WCAG criteria.

Who needs to work on this

@CharlotteDowns, @davidc-gds

Who needs to review this

@stevenjmesser

Done when

  • Collect and type up notes from DAC visit
  • Capture any updates to audit example based upon notes from visit
  • Reach out to DAC to check on progress
  • Received audit result from DAC
  • Create new audit tags (audit may 2023) in both the Design System and Frontend repos
  • Add fails as distinct issues on the Frontend repo and Design system repo, applying tag
  • Add usability issues as distinct issues on the Frontend repo and Design system repo, applying tag
  • Determine whether we can publish the audit paper publicly (chat with Kelly and Steve)
  • Add comments to respective component/pattern GitHub issues
  • Contact teams who have fails with results of audit
  • (moved to a new issue) Consider and make any updates to the Design System accessibility statement
  • Add bonus Design System issue to repo

Links to tagged issues

@CharlotteDowns CharlotteDowns added accessibility WCAG 2.2 All items related to WCAG 2.2 update activities labels May 9, 2023
@CharlotteDowns CharlotteDowns self-assigned this May 9, 2023
@CharlotteDowns CharlotteDowns moved this from Backlog 🗄 to Sprint Backlog 🏃🏼‍♀️ in GOV.UK Design System cycle board May 9, 2023
@CharlotteDowns CharlotteDowns changed the title Determining work needed from submission of DAC Audit May 2023 Determining work needed from DAC Audit May 2023 May 9, 2023
@CharlotteDowns CharlotteDowns moved this from Sprint Backlog 🏃🏼‍♀️ to In progress 📝 in GOV.UK Design System cycle board May 9, 2023
@CharlotteDowns
Copy link
Contributor Author

CharlotteDowns commented May 15, 2023

Some highlights from DAC visit mentioned in show and tell.

@CharlotteDowns
Copy link
Contributor Author

@CharlotteDowns
Copy link
Contributor Author

@CharlotteDowns CharlotteDowns moved this from In progress 📝 to Done 🏁 in GOV.UK Design System cycle board Jun 14, 2023
@dav-idc dav-idc closed this as completed Jun 16, 2023
@dav-idc
Copy link

dav-idc commented Jun 16, 2023

This work is now complete, and is followed by a new issue:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility WCAG 2.2 All items related to WCAG 2.2 update activities
Projects
Development

No branches or pull requests

2 participants