DesignOps Sprint Review - Amazon Web Services · The Accessible Design Wiki will be the “source...
Transcript of DesignOps Sprint Review - Amazon Web Services · The Accessible Design Wiki will be the “source...
DesignOpsCWDS
place image here
DesignOps Sprint ReviewSprint 8.4 August 9 - August 23
Research
● Accessibility Update
● CANS 1.0 User Feedback
Design
● Re-establishing Design System Momentum
Sprint Activity
DesignOps Sprint Review 2
Research
Accessibility: What’s been done so far?
DesignOps Sprint Review
Create accessibility
strategy
June 18
Accessibility testing
brainstorm/ alignment
between Dev, QA and Design
July 10
Met with DOR
July 30
Dev/QA/Prod team meeting
pre code complete planning
Aug 1
Inventory of current
accessibility stories
July 16
Sprint Review accessibility
update
Aug 9
Set up #Accessibility Slack channel
Aug 3
Accessible Design Wiki as source of
truth
Aug 6
Scope current state
of accessibility testing, tools
and processes in
place
July 31
Create draft assessment/ test
script
Make phase 1 and phase 2
recommendations
Aug 17
Draft accessibility
policy
Aug 13
CODE COMPLETE CARES 1.0
place image hereTesting, Remediation, Education & Outreach
● Recommendations have been made for post-MVP testing tools
● The Accessible Design Wiki will be the “source of truth” for Accessibility requirements for CARES
● A Slack channel #Accessibility has been created to share education and outreach as well as provide a direct communication channel between stakeholders and DesignOps
5DesignOps Sprint Review
Accessible Design
place image here
For Devs & QA
● Narrow the toolset, OS and browsers + focus on manual testing
Engage Comms & Policy
● Start doing more share outs
Evangelize Manual Testing
● Track and follow up previous recommendations
● Track project accessibility maturity
Plan for future phases
6DesignOps Sprint Review
Phase 2post code complete
place image hereIn-progress
● Collecting feedback to inform future design changes and feature prioritization
● Sessions scheduled from Aug 20-31● 19 participants from 5 participating counties● Small, medium, and large counties represented● Analysis from Sept 3-7● Findings will be documented and shared shortly
thereafter
7DesignOps Sprint Review
CANS 1.0 User Feedback (WIP)
Design System
place image here
What’s Next? (from last time)
● ??? → county admin portal
wat?
Reestablish Momentum in Design System
● DesignOps technical resources● Taking Stock● Priorities Changed?● Milestones for a GA release?
○ Form Elements○ DataGrid○ MultiContext Card
● When?*
Library Status Tracking
Changelog
---------
* (components): fix build:watch
* (components): fix ScrollTop/Anchors
* (components): consistent HOCs
* (guide): fix netlify redirects
* (guide): add content
* Close half-open work from before
$ lerna ls
@cwds/components v0.2.0-alpha.13
v0.2.0-alpha.14
@cwds/core v0.1.0
@cwds/validation v0.0.1
design.cwds.io v0.1.0 (private)
rails_app v0.1.0 (private)
Other Activities (WiP)
● Migration to ca-cwds/design-system
● Issue Backlog● Deploy Previews● a11y test plan● Build & DX improvements
place image here
What’s Next?
● SaaS integrations with ca-cwds/design-system
● Components○ Form Elements○ MultiContext Card
● Sourcing Additional Technical Resources (e.g.; JS & QA)
Questions?