Win with Metrics: How to Track and Show the Value of Your Program
summary
Shows concrete metrics and methods: use Microsoft Clarity, Hotjar and Google Analytics for session and keyboard-click data; log average issues per component, time-to-remediate, and ticket action time to prove impact; baseline audits then embed an accessibility engineer to prevent ~80% of issues and aim for measurable drops in issues and a target 20% faster time to market; expect ROI claims up to 99x, conservative cost-per-issue estimates around $2,480, and measurable wins like captions driving +4.2% unique visitors and +89% inbound links.
AI-written summary · about
chapters (20)
- 0:00Tracking accessibility value
- 1:11Metrics and KPIs explained
- 3:09Accessibility program metrics
- 6:46Inventorying data sources
- 8:31Rich data for accessibility impact
- 10:16Metrics versus statistics
- 12:02Reports for leadership
- 14:53Key metrics by initiative
- 21:41Storytelling with data
- 23:06Budget and conformance metrics
- 27:47Usability statistics for KPIs
- 33:21Resistance to accessibility
- 36:11Business value of accessibility
- 39:03Prevention initiative metrics
- 40:48Training impact measurement
- 43:37Vendor monitoring costs
- 45:24Automation business value
- 47:08Engineering ROI calculation
- 49:16Building a data ecosystem
- 51:04Q&A on metrics
related talks
48mBuilding Your Program Through Metrics and Storytelling
20mBaby Steps for Metrics
20mReal metrics for front-end performance
49mMeasuring and Benchmarking Accessibility
20mHow to Communicate Metrics to Build Engagement
40mThe Importance of Using Analytics and Feedback for your Documentation
34mProving and improving the value of your docs
46mEngineering Intelligence via Engineering Metrics