Continuous Accessibility: Strategies for Success at Scale

Melanie Sumner

Helios Design System

Notist profile

Continuous Accessibility: Website

The Vision

Start Where You Are

Strategic Implementation

Outcomes and Action Steps

Continuous Integration

Continuous Deployment

Continuous Accessibility

Definition

Expectations

HashiCorp&amp;#039;s Accessibility Statement

Expectations

Some Examples

Flexibility in Use

Simple and Intuitive Use

Perceptible Information

Tolerance for Error

Figma Plugins

Naming Things is Hard

Design Support: Summary

Principles of Continuous Software Engineering

Principles of Continuous Software Engineering

Principles of Continuous Software Engineering

Principles of Continuous Software Engineering

Principles of Continuous Software Engineering

Purposeful Planning: Three Parts

Plan: Existing code

Strategy: Existing Code

Strategy: Existing Code

User Reported Issues

Audit Reported Issues

Automation Identified Issues

Why not all of them?

Plan: Future Code

Principle Three

Dynamic Code Analysis

Static Code Analysis

Anytime Code Analysis

It made me feel sad

TODO states

Code Analysis Strategy

Plan: Metrics

Metrics must be...

Actionable Outcomes

Goodhart&amp;#039;s Law

Metric: Potential Violation Count

How do we establish this count?

Start with a list

Why not just use WCAG?

A11y Automation Tracker

A11y Automation Tracker details

A11y Automation Tracker  possibilities

Automation Count(s)

Metric: Valid Bug Count

Bug Severity

Bug Frequency

Bug Fixes

Metrics to Inform: Potential A11y Health

More potential a11y health ideas

Imagine an accessibility health dashboard

Schedule Metric Review

Inform Future Work

Outcomes

Action Steps

A11y Automation website has a list of tools

Contribute to efforts that already exist

How to fund accessibility work

You do not require permission to create accessible code