Update accessibility statement after Frontend V5 release

[dav-idc]

What

Remove items from the accessibility statement once V5 goes out. Or possibly, add a section on recently fixed pieces?

These issues will be resolved by V5:

• Accessibility issue: duplicate links on example for summary cards #2680
• Summary card actions must specify which card they are for govuk-frontend#3673
• Summary list row actions within summary cards must specify which summary card they're part of govuk-frontend#3674

These issues will not be resolved, and should be left on the statement:

• Accordion - Elements must only use allowed ARIA attributes govuk-frontend#2472
• Details component does not work well with Dragon and VoiceOver govuk-frontend#3693
• Upload file component doesn't respond to 'click choose file' due to Dragon / browser bugs govuk-frontend#3686

Resources:

• Accessibility statement page
• Previous accessibility statement update Google Doc
• Previous PR for updating the accessibility statement

Why

Once V5 is published, some of the issues we list in our accessibility statement should be resolved. For cleanliness and transparency, we should update the statement and remove those items.

Who needs to work on this

David (accessibility), content designer

Who needs to review this

Product manager? Delivery manager?

Done when

• Statement update is drafted
• Statement update is reviewed by team
• Statement update is published
• Related GitHub issues are closed

[stevenjmesser]

Steve to check with Frontend squad when they think v5 will be ready.

[claireashworth]

Latest accessibility statement draft underway

[claireashworth]

Amendments checked with Charlotte and draft shared with team.

[romaricpascal]

@claireashworth Lost track of what's merged and not, did this one go in the big v5 content merge or will it go on its own now we've released. Feel free to close and set to Done if the former 😊

[claireashworth]

this isn't merged yet. I've only linked the draft doc into the issue. I think there was something outstanding to do, but would have to check

…

On Fri, 8 Dec 2023 at 17:05, Romaric Pascal ***@***.***> wrote: @claireashworth <https://github.com/claireashworth> Lost track of what's merged and not, did this one go in the big v5 content merge or will it go on its own now we've released. Feel free to close and set to Done if the former 😊 — Reply to this email directly, view it on GitHub <#3129 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMXUGHG5JE75GBCABK4FU7LYINCGBAVCNFSM6AAAAAA4L6HAKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBXGUZTIOJVG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Claire Ashworth (she/her) Technical Writer 07793206027

[stevenjmesser]

I've suggested one change as we were saying that that the Design System website was partially compliant but that nothing on the website was non-compliant, which doesn't make sense.

Have also suggested some (bad) wording for including mention of compliance against WCAG 2.2, but Claire helpfully pointed out we might have to stick to the template language.

Have finished my review and shall pass this back to Claire for writing the WCAG 2.2 lines, and move it back to In Progress.

[claireashworth]

The statement is redrafted in line with the latest accessibility template and ready for another review.

[stevenjmesser]

Reviewed. Moving back to in progress so that accessibility.md can be updated in main...wcag-22-content-updates.

[claireashworth]

Accessibility statement amended in PR 'WCAG 2.2 guidance updates #3090'
@calvin-lau-sig7 @CharlotteDowns for info/to review
This is the active issue for the accessibility statement. I've also commented on #3332, but this might be a duplicate issue.

[stevenjmesser]

It's published.