Background/Goal
Create and publish Design System Design Guidelines for Accessibility v1.
User stories
- As a front-end development team, we need to ensure that components are accessible and meet accessibility standards.
Considerations
- This is related to Design Style Guide, but we should document how the Design System is incorporating this and encoding it into the Design System
Requirements
- There is a single source of truth for Design System Accessibility on wiki (ex: are we extending this: https://design.wikimedia.org/style-guide/visual-style.html or adding elsewhere?)
The Accessibility section of the Design Guideline MUST include the following:
- Any workflows that reinforce accessibility standards
- Workflow roles and responsibilities (who is doing what, when, and why)
- Clear set of steps and/or checklist for ensuring accessibility in design
- How the Design System incorporates and/or enforces accessibility standards
- There is a single source of truth for each user story (aka artifact)
- All source of truth documents/artifacts are available via Design System Portal/Wiki
Acceptance criteria
- There is a single source of truth for each user story (aka document)
- All documentation should link back to a central Design System Portal/Wiki
- Artifacts should be:
- easy to read (limited jargon)
- clear to follow (written as steps, checklists, visual diagrams, etc.)
- Ambiguity in who does what should be mitigated
- Access to artifacts should NOT be restricted for viewing by target users (aka remove or update permissions as necessary)
Test scenarios
[N/A]
Open questions
[N/A]