"Web-Stack" developer with a focus on accessibility design and development patterns, data visualization and DevOps automation.
Fell in love with Node, JS, SPA's and the JAMStack. Bye LAMP.
Yes, we are subject to them, but even for areas where we could "get away" without being accessible, we treat accessibility as a first-class requirement.
We automate where possible, so build tooling to do a lot of checks that can be done and then do manual testing for the rest.
Where possible we try and provide tooling to the other teams that builds in accessibility for free. For example, our design system is made with accessibility in mind.
"Web-Stack" developer with a focus on accessibility design and development patterns, data visualization and DevOps automation.
Fell in love with Node, JS, SPA's and the JAMStack. Bye LAMP.
To dive a bit deeper, when automating are you manually running code tests using automated checking tools (Wave,Tenon, etc...) and/or with unit testing as part of CI/CD?
Have any tips on helping to "toolchain" the process for DevOps?
How does your team handle accessibility development and testing within projects? Is your charity subject to WCAG guidelines?
Great question!
Yes, we are subject to them, but even for areas where we could "get away" without being accessible, we treat accessibility as a first-class requirement.
We automate where possible, so build tooling to do a lot of checks that can be done and then do manual testing for the rest.
Where possible we try and provide tooling to the other teams that builds in accessibility for free. For example, our design system is made with accessibility in mind.
That's great to hear that its first class!
To dive a bit deeper, when automating are you manually running code tests using automated checking tools (Wave,Tenon, etc...) and/or with unit testing as part of CI/CD?
Have any tips on helping to "toolchain" the process for DevOps?
Both and it kind of varies by the project (something we're hoping to standardise).
Generally, we do: