How We Improved Accessibility Across 10+ Backstage Plugins and How...
summary
Audit across 10+ Backstage plugins uses Lighthouse to find 106 accessibility issues, of which about 76% resolved so far; fixes include color-contrast updates and improved HTML structure for screen readers. Automated scans run in CI via Lighthouse + CI checks to prevent regressions, and a GitHub Actions package (CHX) lets external repos adopt the same workflow. Practical next steps include running Lighthouse locally, adding keyboard testing, and annotating designs with a Figma accessibility kit.
AI-written summary · about
related talks
22mPrioritising Accessibility to Web Development
50mShift Left on Accessibility: Beyond the Audit
29mBuilding Accessibility Testing into Your Workflow
21mPrevent, Catch and Fix Accessibility Issues
56mContinuous Accessibility: Adding Lighthouse to Your CI/CD Pipeline
44mTesting Web Accessibility
21mBuilding an Accessibility Culture
22mAccessibility: The Sprint Filler Way