Content: Create a page that outlines processes and checks to make GC Design System accessible

[adorayi]

📇 User story

As a user of the Design System, I want to know:

• what makes the GC Design System accessible so that I feel confident when using it.
• when an accessibility issue does exist, so I can address, mitigate, or know when it will be fixed.
• that the team is committed to making GC Design System more accessible and addressing a11y issues I or others may raise.

✅ Definition of Done / Outcomes

• Content contains info on accessibility in GC Design system to provide some assurance to users
• Content relates to known user needs and insights from developer onboarding research
• Content is available on the website in EN and FR, that users can access, and provides detailed information on accessibility of the GC Design System as a whole

📜 Acceptance criteria

Add here the list of assumed steps that will be needed to complete the task

• Familiarize self with GCDS content guide
• Define the audience and main purpose of page
• Mock up using basic page template in this Figma file
• Address relevant user feedback on accessibility from developer onboarding
• Scope out work for future iteration
• Policy review
• Design review
• Developer review
• PM review
• Send to translation
• Bilingual review
• Coordination/hand off for publishing

📝 More info

We can share this with ITAO (IT Accessibility Office for GC)
Related research

. 🚫 Out of scope
Specific accessibility information for each component, pattern, or template.

[adorayi]

@SmartMouthWords @MatildePerrusclet @brockhigg10 for your review, here is the draft doc:
https://docs.google.com/document/d/1ryk1kwrq1YTrwFeJeKg7j812cMBDhehWum68Rp6Wm-o/edit?usp=sharing

[SmartMouthWords]

We could consider aligning with GC Notify's accessibility statement and disclosing "known issues" like they do. W3C recommends disclosing known limitations in their guide on A11Y statements.

[ClementineHahn]

current prototype here https://pr-427.djtlis5vpn8jd.amplifyapp.com/en/accessibility/

[Charcharbinkz]

@adorayi - after a sync with @ClementineHahn and @SmartMouthWords, I'm able to pick this up this week. Is this the latest draft? https://pr-427.djtlis5vpn8jd.amplifyapp.com/en/accessibility/

Curious what reviews it's already been through/what is still needed.

[SmartMouthWords]

@Charcharbinkz This is the working draft: https://docs.google.com/document/d/1ryk1kwrq1YTrwFeJeKg7j812cMBDhehWum68Rp6Wm-o/edit?tab=t.0#heading=h.7ghz0za2sh8u

Work is needed to link content to research insights and user outcomes, look at aligning with A11Y statements for Forms and Notify (e.g. will design system users want to be able to report accessibility issues on this page?), and revise content to meet writing standards for the website.

[SmartMouthWords]

@ClementineHahn @adorayi @daine Added points for grooming. Anything missing?

[Charcharbinkz]

After chat with Amy, will work on analysis of current state of statement, understand who users are and their specific expectations. From there, will scope if this becomes a larger task.

[Charcharbinkz]

Submitted a request question to Adrianne re: audience: https://airtable.com/appu8Sa68JKCOMAMs/pagQS7nFWI3iZkvSC/form

[Charcharbinkz]

After chat with Abdul, will work more iteratively. Focus of this draft will be:

• content review
• incorporating applicable dev onboarding insights
• incorporating applicable team feedback from current draft.

Future work will be captured in ticket #1348

[Charcharbinkz]

@SmartMouthWords - Could I get a gut-check on the mock-up? https://www.figma.com/design/nfpEteHyEJ9dhJ2YvuvLeo/Documentation-site%2FComponent-Pages?node-id=15642-23025&t=Zk2S0TwMgtfFTS3b-4

Two options: One mockup uses just headers and text components, the other adds details components to help with progressive disclosure.

I've removed sections from the original to shorten a bit. The red text is information I've added. Is it accurate?