Stop Guessing, Start Measuring: Quantifying Accessibility

The primary focus is to improve the accessibility of Stack Overflow products by setting clear accessibility targets, measuring progress, and embedding accessibility considerations early in the development process.

Stack Overflow uses a combination of automated tools like Axecore and manual assessments from third-party auditors, community feedback, and client reports to measure accessibility scores.

The design system team leads the accessibility initiative due to their expertise, setting standards for accessibility across the organization and embedding accessibility in the design process.

APCA was adopted because it provides a more accurate assessment of color contrast, allowing Stack Overflow to maintain its signature orange color while meeting accessibility standards.

Stack Overflow uses Axecore and GitHub workflows triggered daily to run accessibility checks against important product pages, transforming results into metrics for tracking.

The accessibility dashboard provides a central hub for tracking accessibility progress, offering actionable insights for teams, and displaying score trends and identified issues.

Stack Overflow encourages early accessibility consideration by establishing accessibility champions, using a lean accessibility checklist, and providing internal training videos called 'accessibility bites.'

Key learnings include setting clear accessibility targets, securing organizational commitment, measuring and tracking progress, shifting accessibility considerations left, and continuously improving accessibility efforts.

Accessibility champions spread accessibility knowledge, meet regularly to discuss improvements, and ensure that accessibility is prioritized across teams.

Accessibility regressions are managed through service level objectives, where a drop in accessibility score triggers a priority incident, requiring resolution within a seven-day window.