Create and publish documentation for DAC Audit 2023

[CharlotteDowns]

What

This ticket completes work related to the DAC audit 2023 and how we share results of the audit more publicly.

Why

This WCAG 2.2 audit supports our efforts to https://github.com/alphagov/govuk-frontend/issues/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

• [x] Check the usability results against our teams collective understanding
• [x] Consider writing a blog post, look to see if an accessibility audit is a new topic
• [x] Determine work needed to publish DAC audit reports on the Design System website (we can publish but waiting on other epics to determine where)
• [x] Receive approval from DAC to share publicly
• [x] Decide what items to add to the accessibility statement
• [x] Determine where remaining guidance changes are monitored (at the moment they have been monitored here as a comment but will think about how that can be improved)

  
  ### Tasks

• [ ] https://github.com/alphagov/govuk-design-system/pull/2995
• [ ] https://github.com/alphagov/govuk-design-system/pull/2996

[CharlotteDowns]

Blog posts that relate to an accessibility audit:

• Bringing accessibility audits in-house
• How we made GOV.UK more accessible

[CharlotteDowns]

Components and patterns that need a guidance change

WCAG criteria

• [x] Step-by-step navigation, #2794 and usability criteria #3687
• [x] Password (show/hide), #2795
• [x] Tabs, #2797
• [x] Links, #2796

  Usability criteria

• [x] Error message, Error summary, #2801
• [x] Pagination, #3682
• [x] Character count, #3689

Components and patterns that need a comment added to our accessibility statement

• [x] Summary list, WCAG criteria #3673 and #3674
• [x] Details, #3693
• [x] File upload, #3685 and #3686

[CharlotteDowns]

Accessibility statement changes

Drafted in July 2023 accessibility statement update google document.

Committed to the GOV.UK Design System website in this pull request.

[CharlotteDowns]

We've also added some component specific usability information to the file upload component

[CharlotteDowns]

Messaged DAC today (Tuesday 17 October 2023) to find out if we could get an alternate version of the report in a more accessible format.

_Side note: We carparked 'How we might talk about our audits' in our Design Sprint in Summer 2023 to revisit at a later date when we have a place on the website where it can live_

[CharlotteDowns]

We have now received DAC Accessibility Report WCAG 2.2 GOV.UK Design System 17-05-2023 in a read-only.docx format.