Accessibility Toolkit DEVELOPER WORKSPACE
PROFILE MANAGER
Text size

DEVELOP & TEST

Profiles

Explore different needs. Shape how your toolkit responds.

Profile library

9

Nine starting points adapted from W3C WAI user stories. Settings are illustrative mappings for development; individual needs vary.

PROFILE EDITOR

Current profile

Draft

Loading a library profile updates the connected toolkit immediately. Editor changes are drafts until you apply them.

Profile fields 0

Where it goes in the profile, such as fields.largeTargets. The toolkit keeps it; an adapter can read it by name.
Edit full JSON
Presets are saved in your account when you are signed in, otherwise in this browser.

NEW ADAPTER

Build an adapter with a coding agent

A coding agent such as Claude Code or opencode writes the adapter, publishes it to this toolkit and runs it in your browser. The toolkit skill in the repository shows it how.

  1. Copy these two lines into .env

    Make a file named .env at the top of the toolkit repository and paste the lines into it. Git ignores .env, so your token stays out of commits.

    
            
  2. Open the repository in your coding agent

    Start claude or opencode in the toolkit repository folder. The skill is already in .claude/skills, and the agent picks it up on its own.

  3. Say what to fix

    Name the website and the barrier. For example:

    Make an adapter that underlines each link on https://example.com, for people who find links hard to tell apart from other text. Publish it to my toolkit so it runs in my browser.
  4. See it work

    Open the page in Chrome with the adapter runtime extension connected. The adapter appears on this page under Yours, with how it ran.