Back to The developer console

Text version of the video: A tour of the developer console

About this video

A narrated screen recording, about 6 minutes long. It tours the developer console, shows how to install the toolkit's browser extension, builds an adapter by describing a need, and tries the toolkit on Redbird, a practice online store. Two people speak: a presenter from the team, who records the screen, and a narrator, who reads the cards we added between the parts. The narration below is transcribed from the video and lightly tidied. Descriptions of what is on screen are in square brackets, with the time in the video where each part starts.

The video was recorded on a test copy of the console, so the addresses on screen start with "localhost". The console itself is at a11y-toolkit.web.app. The presenter's access token is blurred wherever it appears.

Part 1: Introduction (0:00)

[On screen: a title card, "A tour of the developer console".]

Narrator: This video is a quick tour of the developer console, where you can build adapters and try them out in your browser. You'll see the main parts of the console, how to install the browser extension, how to build an adapter just by describing what someone needs, and how to try it out on a practice website that we built for this workshop.

Part 2: Signing in (0:22)

[On screen: the console, titled "Accessibility Toolkit, developer workspace". A menu on the left lists Profiles, Memory, Adapters, Apps, Listings, and Account and tokens. Below it is a sign-in box with a username, a password and a Sign in button.]

Presenter: Welcome to the brief overview of the AI for Accessibility toolkit. To get started, log in with the username and password provided to you by the organizers, and click Sign in.

Part 3: Profiles (0:36)

[A card reads: "Profiles. Choose a test person, so you can see how your adapters work for them." Then the Profiles page: a profile library lists nine ready-made profiles, such as "Profile 1 (limited arm mobility)", "Profile 2 (autism)" and "Profile 3 (blindness)", each with a Load profile button and a link to the W3C story it draws on. To the right, a profile editor shows the active profile's settings.]

Presenter: On the right, there are some built-in ability profiles that you can inspect. You can click Load profile to load a certain profile, which will be synced to all the instances that use the accessibility toolkit.

[A red circle marks the Load profile button for Profile 1. The presenter clicks it, and the editor shows the profile's settings, such as "supportAreas: motor" and its free-text description, "Support keyboard operation and easy navigation."]

Presenter: And then you can inspect all the values within that profile.

Part 4: Memory (1:02)

[A card reads: "Memory. What the toolkit learns about the test person as they use it." Then the Memory page, headed "What your toolkit learned". It remembers one thing: "User prefers plain-language definitions for technical terms and difficult words."]

Presenter: On the second page, Memory, which will show a list, as you use the toolkit, of what it's learned about you.

Part 5: Adapters (1:14)

[A card reads: "Adapters. Small tools that change a website or app to suit someone. You build them here." Then the Adapters page. A box headed "Run adapters in your browser" says the extension is not found in this browser, and lists the steps to set it up.]

Presenter: And the third page is Adapters. Adapters are tools that are designed to change the behavior of certain things. For example, change the behavior of your application, or change the behavior of a web app. To do so, there are two ways of building adapters.

Part 6: Installing the browser extension (1:38)

[A card: "Installing the browser extension".]

Narrator: Next, we'll install the browser extension. It's what runs your adapters on real websites in Chrome. Before you start, you'll need a copy of the toolkit's code on your computer, and the link is on the page underneath this video.

Presenter: The first one is to set up a Chrome extension, which is recommended for this workshop. Click on the extensions button on the top right of your Chrome, and then click Manage extensions.

[A red circle marks the extensions button at the top right of the browser, shaped like a puzzle piece. A menu of extensions opens, and a red circle marks Manage Extensions at its foot. Chrome's Extensions page opens.]

Presenter: Make sure Developer mode is on, on the top right, and then click Load unpacked on the top left.

[A red circle marks the Developer mode switch, which is on, and then the Load unpacked button. A window opens to choose a folder.]

Presenter: Navigate to the AI for Accessibility toolkit, and select the extension folder.

[The view slowly zooms in on the window. It shows the folders in the toolkit's code. A red circle marks the folder called "extension", at the top level of the toolkit, and then the Select button. The window closes, and the view zooms back out. A new card has appeared on the Extensions page, "AI for Accessibility: adapter runtime", marked with a red circle.]

Presenter: Now that it is loaded, we can turn this page off.

Part 7: One more step (2:34)

[A still of the Extensions page, darkened, with the Details button on the new extension's card circled in red. Below it, a card: "One more step".]

Narrator: There's one more step that you may need to take in order to make sure your extension is working. On the new extension, click Details and turn on Allow user scripts, because your adapters won't run without it.

Part 8: Connecting the extension to the console (2:48)

[Back in the console, on the Adapters page. A red circle marks the extension's icon in Chrome's toolbar, a small coloured star. The presenter clicks it, and a side panel called "Adapter runtime" opens on the right, with three tabs: Profile, Builder and Settings. A red circle marks its button, "Connect with this console".]

Presenter: And we can turn on the adapter and connect with the console.

[The presenter clicks the button. On the Adapters page, a red circle marks the new status: "Connected in this browser".]

Part 9: Building an adapter (3:00)

[A card reads: "Building an adapter. Describe what's hard, and the extension's Builder makes an adapter for it."]

Presenter: Now we can switch to Builder to describe your needs, and then build an adapter.

[The view slowly zooms in on the side panel's Builder tab. A red circle marks the request typed into it: "I find it difficult to understand the technical terms." Below it, the Builder asked three questions, each answered with its recommended choice: show plain definitions on hover, on this website, to help with reading. The Builder replies that it has added clear, plain-language definitions to the technical terms on the page, and that you can point to an underlined term, or reach it with the keyboard, to read its definition. A box says "Plain definitions for technical terms" is ready.]

Presenter: Once the adapter is built, you can click Add to my account to have it appear in your account.

[A red circle marks the Add to my account button, and the presenter clicks it. The view slowly zooms back out. The presenter opens the Toolkit tab of the Adapters list, which shows 11 adapters, such as Announce changes, Bigger targets and Calm page.]

Presenter: There are also existing built-in adapters in the toolkit, which you can see in the Toolkit tab. Another way of creating an adapter is through a coding agent. You can see detailed instructions by clicking the New adapter button.

[A red circle marks the New adapter button. A window opens, "Build an adapter with a coding agent", and the video holds on it while the view slowly zooms in and out. It has four steps: copy two lines into a file named .env at the top of the toolkit's code (the line with the token is blurred); open the code in your coding agent, such as Claude Code or opencode; say what to fix, naming the website and the barrier; and see it work, by opening the page in Chrome with the extension connected.]

Part 10: Apps, and Redbird (3:49)

[A card reads: "Apps, and Redbird. Connect something you built, like a website, so it uses your profiles and adapters. Redbird is a practice online store." Then the Apps page, with a box to open the Redbird demo, already connected, and a sample of code for connecting your own web app.]

Presenter: Next, I will introduce the concept of apps. Apps are basically anything that you can build that would plug into the AI for Accessibility toolkit to understand and support diverse abilities. We built a shopping website as an example. So just click Open Redbird. It will show this shopping website.

[Redbird opens: an online store with sections such as "Charge up for less" and "Cozy home picks". On its left is the toolkit's panel, with tabs for Profiles, Adapter Library, Build your adapter and Audit. It shows the active profile, Profile 1, and the adapters it has turned on, such as big-targets, focus-locator and skip-links. The presenter opens the list of profiles, then the Adapter Library, then Build your adapter, which has a box headed "What should change on this page?".]

Presenter: What you can see is, you can also choose the ability profiles from the developer toolkit. You can see the adapter libraries, and you can build your own adapter. You can also audit the page by running an audit, finding all the accessibility issues, and fix the page with proposed adapters.

[The view slowly zooms in on the panel. A red circle marks Run the audit. The audit finds 100 problems, such as 18 photos with no description and 24 places where text has too little contrast. A red circle marks Fix this page. After the fix, the counts drop: 0 photos with no description, and 35 problems left.]

Presenter: And you can see which elements are fixed.

[The presenter opens the list of images that were missing a description, and points to each one. Each is outlined on the page. The view slowly zooms back out. Back in the console, the Apps page now lists the Redbird demo, with its seven adapters, such as Real arrival dates, Swatch names and Calm urgency.]

Presenter: Going back, you can also see that the adapters that are provided by the app are also available within the Apps menu.

Part 11: Listings (5:09)

[A card reads: "Listings. Share what you built, so other people can find it and use it." Then the Listings page, which shows what apps have shared, such as seven adapters from an app for smart glasses, each with an Install button.]

Presenter: When you're finished developing, you can host your app or adapters on the Listings page to share with other people that might be interested in using your adapters or apps. That's an overview of the AI for Accessibility toolkit. Please let us know if you have any questions. Thank you.

Part 12: Try it yourself (5:34)

[A closing card: "Try it yourself: a11y-toolkit.web.app".]

Narrator: To try it yourself, open the developer console at a11y-toolkit.web.app and sign in with your team's username and password. On the day of the event, you'll find those on the same page as the API key. The links to the console and the browser extension are on the page underneath this video as well.