The Live Wire

Two frosted-glass collaborators examine a monitor with a magnifying lens and stylus beside an open toolkit of cards, on plum marble with gold threads.
Editorial illustration of collaborators examining an interface together. Accessibility guidance can support investigation, but does not replace participation or testing with disabled people.

A new toolkit brings accessibility questions into AI-assisted design

Precious “Preciosa” Myers-Brown · Published

Share this essay

The Accessibility Considerations Toolkit is a starting point for investigation, not a substitute for disabled people’s expertise.

AI can help teams build interfaces faster. That speed is less useful if it repeats barriers faster, too.

In a November 11 announcement, Aaron Gustafson says his team is open-sourcing the Accessibility Considerations Toolkit, or ACT. It brings together guidance about assistive technology, access strategies and the circumstances in which people use an interface.

The resource can be read as Markdown, with generated YAML available for agents and evaluation pipelines. Examples include checking whether a form remains usable with browser zoom, screen magnification or a high-contrast theme.

Gustafson is explicit about the boundaries: ACT does not replace co-design or testing with people with disabilities, and it does not establish standards compliance. Human reviewers still need to assess evidence. Finding no issues is not proof that a product is accessible.

His announcement invites feedback, particularly from disabled people and accessibility practitioners, and links to the toolkit.

Tech Equity

The useful change is asking access questions while a design can still change, not after someone has been excluded. A team can start with one task a person needs to complete, test it under that person’s actual conditions and record what happened.

A checklist is not the person. Used well, guidance helps a team notice where it needs to listen, observe and repair. It should make participation more meaningful, not provide a reason to skip it.

Source: Aaron Gustafson, Build faster without leaving accessibility behind, November 11, 2026.

Share this essay

← All briefs