The developer console
The developer console is where you build adapters and try them out in your browser, without writing code. It’s one of four ways to get started, and it’s optional. It’s for people building with the toolkit: someone who only wants websites adapted to them uses one of the browser extensions instead.
Your team signs in with a username and password. On the day of your event, get your team’s sign-in on the same page as the API key, with the password the organizers give you.
A tour of the console
This video, about 6 minutes long with captions, walks through each area of the console, installs its browser extension, builds an adapter by describing what someone needs, and tries it on Redbird, a practice online store. The buttons under the video jump straight to a part. Read a text version of the video.
The video was recorded on a test copy of the console, so the addresses in it start with “localhost”. The address your team uses comes with your team’s sign-in.
What’s in the console
The console has five main areas:
- Profiles: choose a test person, so you can see how your adapters work for them. Start from one of nine ready-made profiles based on W3C user stories, and change any part of it.
- Memory: what the toolkit has learned about that person as they use it.
- Adapters: build, run and share adapters, with a new version kept each time you save. You can describe what’s hard in your own words and have an adapter built for you, or follow the steps to build one with a coding agent.
- Apps: connect something you’ve built, such as a website, so it uses your profiles and adapters. Redbird, a practice online store, is already connected, so you can try adapters on it and check it for accessibility problems.
- Listings: share what you built, so other teams can find it and use it. On the day of your event, you can try adapters other teams have shared.
Like the toolkit, the console adapts to the person using it, starting with a setting that makes its text larger.
Install its browser extension
To run adapters on real websites, you also need the console’s own browser extension, called the adapter runtime. It isn’t one of the extensions on the Demos page. It needs Google Chrome on a computer:
- Get a copy of the toolkit’s code: on GitHub, choose Code, then Download ZIP, and unzip it.
- In Chrome, go to
chrome://extensions, turn on Developer mode, choose Load unpacked, and pick the folder calledextensioninside the toolkit’s code. - On the new extension, choose Details and turn on Allow user scripts. Without it, adapters won’t run.
- Sign in to the console, open the extension from Chrome’s toolbar, and choose Connect with this console.
When you’re done, go back to Build your own project.