# Teach Your AI Agent to Build Products Everyone Can Use - Jemima Abu, CAIS

Jemima Abu, CAIS

[Talk page](https://ai.engineer/talks/YV1x6gCdgQA-teach-your-ai-agent-build-products-everyone) · [Video](https://www.youtube.com/watch?v=YV1x6gCdgQA)

## Teach Your AI Agent to Build Products Everyone Can Use

Jemima Abu gave a coding agent the same Figma design twice. The run with an accessibility skill took five minutes. A simple accordion shows what belongs in that skill and why the choice matters to someone using a keyboard.

### How far can you get with your eyes closed?

[0:12](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=12s)

Close your eyes, unlock your phone, open the notes app and type `hello world`. Jemima Abu, a product engineer and certified accessibility professional, gave the room that exercise, then scaled it back. Forget the note. Could people enter their lock password with their eyes closed? She gave them 30 seconds.

With the screen out of view, it was hard to tell what a gesture had done. Even gathering answers exposed a similar problem. Abu couldn't see people nodding, so she asked them to answer aloud. Muscle memory could help someone swipe up and tap familiar key positions. What would happen on a phone they'd never used? A first-time user would need a way to discover where those keys were.

Accessibility means building products that people can use regardless of disability. The phone exercise isolates one assumption about sight. An interface can just as easily depend on a movement someone can't make, a sound they can't hear or an interaction they find difficult to understand. A feature can be present on the device and still be out of reach.

### One Figma design, two agent runs

[2:05](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=125s)

Abu cites a figure of 96% of the top one million websites having accessibility issues. When she asks developers why accessibility gets put off, she hears that a manager won't sign off on extra time, a client hasn't asked for it, or the company has other priorities. Those answers treat accessibility as time added to a build. Abu wanted to see what would happen if an agent received the guidance before it started.

How much work did the agent do on the same Figma design under each condition? On the first run, Abu asked it to implement the design and left the approach up to the agent. That took 15 minutes. On the second, she supplied a skill she'd written specifically for accessibility. That run took 5 minutes, used fewer tokens and cost 58% less.

Abu catches herself before turning that result into a general savings claim. This was a one-off comparison in an uncontrolled environment. The figures describe the work of generating the implementation. How well people could use each result is a separate question. Her reason for giving an agent a skill is more specific: it can settle implementation choices the agent would otherwise have to make for itself.

![Both runs used the same prompt and model. With the accessibility skill, duration fell from 15.6 to 5.2 minutes, turns from 84 to 32, total tokens from 4,595,916 to 1,429,426 and estimated cost from $14.20 to $5.97, a 58% cost reduction.](https://ai.engineer/api/talk-essay-media/285b569779fdeb6e4b2ed4df961c428ac4e0be90726b67a032de2433e7cd2820)

With the same model and prompt, the two runs differed in time, turns and the accessibility of the result.

### Why an agent reaches for custom JavaScript

[4:11](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=251s)

Abu compares a coding agent to a toddler on a first errand. In the Japanese show *Old Enough*, a parent sending a child to the supermarket might have walked the route with them, drawn a map or supplied a shopping list. The child knows where to go and what to bring back. A Figma design gives an agent a destination, too. It still leaves room for the agent to reproduce what it sees with a pile of `div` elements.

Consider where the agent's examples come from. A developer tries a feature on a laptop, clicks through it successfully and ships. Someone navigating with a screen reader or using a keyboard alone may encounter a problem the developer's test never exercised. Models learn from human-written code, including code shipped after just such a test. An agent can reproduce the omission, and a developer using the same test can approve it again. Abu cites 16% of the world's population as having some form of disability.

Take an accordion, where activating a heading reveals or hides content. A custom implementation can use JavaScript to manage that interaction. For a simple disclosure, HTML already provides the `details` element. The browser handles opening and closing it, which leaves less code to generate and less behavior for the developer to get right. Abu expects an agent to favor the more common custom implementation. A skill can tell it when to choose the native element.

Leaving accessibility until the end reminds Abu of someone serving a plain muffin with blueberries shoved on top. Adding labels to a finished site has much the same limitation. A label can tell someone what a control is called. If the control still responds only to a click, a keyboard user who knows its name still can't operate it.

![A person hammers at a workbench displaying code that makes a div act as a button. Beside the bench, a finished wheel labeled <button /> illustrates the native HTML element.](https://ai.engineer/api/talk-essay-media/89932ed53dcbaf0e9c212f33ce70337042da2ed52eaffd8035a962b9f2ce252f)

Reimplementing a button in a div adds keyboard and semantic work that comes with a native button.

### The customer who switched banks

[8:03](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=483s)

At a conference, Abu heard from someone who moved from Bank A to Bank B because they couldn't use Bank A's app. Bank A could have had better features and still lost that customer. Being able to use the service settled the choice before a feature comparison mattered.

That departure is easy for a business to misread. A team looks at its customers and concludes that nobody uses assistive technology. People who tried the app, couldn't navigate it and left are missing from the very group the team is looking at. Abu compares it to a shopkeeper wondering why nobody comes into a store that has no door. Inaccessible websites also carry legal risk. She points to US lawsuits under the Americans with Disabilities Act.

### Four changes to how the agent builds

[9:47](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=587s)

1. **Define the product's accessibility requirements.** A web app and a mobile app can call for different standards and different ways of meeting them. Whoever specifies the work, whether a developer or a product manager, needs to identify the requirements that apply and include them when asking the agent to build.

2. **Audit the code the agent will copy.** A new roommate who finds dishes piled in the sink learns something about the house rules. Existing components send an agent much the same signal about what the team accepts. Look for accessibility faults in that codebase. An agent can also do a separate pass to find and fix problems in the examples it would otherwise follow.

3. **Fix shared components in a design system.** A simple reusable library is enough. Suppose 150 pages use the same component. Fix its implementation in the library and all 150 pages get the correction. Independently generated copies would each need attention.

4. **Make the guidelines part of every run.** Three hours before a deadline is a poor time to rely on someone remembering the keyboard requirement. A standing instruction gives the agent that requirement while it chooses and builds each control, including on the rushed job.

![Downward arrows link three steps in order. Define your accessibility requirements, audit your existing codebase, then implement a design system.](https://ai.engineer/api/talk-essay-media/1e71f494f1883921dd649f05173ca741aabd96883e0b252190939bbe9d7f290a)

Three steps put accessibility into the agent’s workflow before implementation.

### What goes in a lightweight accessibility skill?

[12:03](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=723s)

What should the agent do differently the next time it builds a web control? Abu's lightweight skill gives it an implementation preference and a condition the result has to meet.

- **Choose elements for their meaning.** Start with semantic HTML. For a section that expands and collapses, `details` tells the browser what interaction to provide.
- **Require keyboard operation.** Every interactive element must work with the keyboard alone. For the accordion, someone using a keyboard must be able to reach the control, open the content and close it again.

A complementary modern web guidance skill points the agent toward browser features it might overlook. It can suggest `details` for an accordion or bring `popover` to the agent's attention when it needs to show content over a page. The accessibility instruction tells the agent how a person must be able to use the control. The browser guidance helps it find an implementation. [Abu's examples at 12:29](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=749s)

These prompts reflect Abu's work on the web and need adapting for other platforms. Even on the web, following them can address familiar barriers while leaving others in place. Whether someone can complete a task with the finished product remains the measure of success.

### A keyboard handler and a corner widget

[13:27](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=807s)

Asked about her biggest frustration with accessibility, Abu starts with a developer giving a `div` the job of a button and leaving out keyboard handling. Someone with a mouse can activate the control, so the developer may never encounter the failure. The person trying to use the keyboard encounters it every time.

Then she remembers the accessibility overlay, often a small stick-person icon in the corner of a page. It brings her back to the blueberries on top of the muffin. A team can install a conspicuous accessibility widget while leaving that same control unusable. The repair belongs in the control, where the person pressing a key needs something to happen.

## Key takeaways

- On one Figma build, the run with an accessibility skill took 5 minutes against 15 minutes without it and cost 58% less. The uncontrolled comparison leaves the savings on other builds an open question.
- Pair an implementation preference with an observable requirement. For a simple accordion, choose the native `details` element and require that someone can open and close it using only a keyboard.
- The code around an agent supplies examples of what a team accepts. Audit those examples, repair shared components and carry the product's accessibility requirements into every run.

## Slides

### The Cost of Accessibility in AI

[0:12](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=12s) [“The Cost of Accessibility in AI” is subtitled “a.k.a stop wasting tokens on building products that people can’t use.” The bottom credit reads “Jemima Abu · AIE NYC.”](https://assets.ai.engineer/sites/aiecode2025/sha256/b551bd433fb28472e89052291f78cc5a343d374134b00c03ae8985cf53493c17.webp)

The Cost of Accessibility in AI
a.k.a stop wasting tokens on building products that people can't use
Jemima Abu • AIE NYC

### Accessibility

[1:34](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=94s) [The definition beneath “Accessibility” reads “Able to be used, regardless of disability.”](https://assets.ai.engineer/sites/aiecode2025/sha256/41bf6a0d6e9f50b2e6bd9826ff9879d8bc99b57f456c90b556f0977dac426e19.webp)

Accessibility
Able to be used, regardless of disability

### Accessibility issues among the top one million websites

[2:05](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=125s) [Under “Observation,” the slide states that approximately 96% of the top one million websites have accessibility issues.](https://assets.ai.engineer/sites/aiecode2025/sha256/fb5a8ff0f8ec2f070ea4423ca3a39c85627aa77c5ad7e6ce90c6d89ceb0d064a.webp)

~96% of the top 1 million
websites online have
accessibility issues.
Jemima Abu • The Cost of Accessibility • October 2026

### Why aren’t websites built to be accessible?

[2:25](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=145s) [The slide asks “Why aren’t websites built to be accessible?” At lower right, a cartoon person at a laptop holds their head and says “It takes too long.”](https://assets.ai.engineer/sites/aiecode2025/sha256/b4f38f93a35a0bbdcb95af353e333fc2d5125bcaa21ca86222631e8c6e6d0387.webp)

QUESTION
Why aren’t websites built to be accessible?
It takes too long.

### AI runs with and without an accessibility skill

[3:11](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=191s) [Both runs used the same prompt and model. With the accessibility skill, duration fell from 15.6 to 5.2 minutes, turns from 84 to 32, total tokens from 4,595,916 to 1,429,426 and estimated cost from $14.20 to $5.97, a 58% cost reduction.](https://assets.ai.engineer/sites/aiecode2025/sha256/285b569779fdeb6e4b2ed4df961c428ac4e0be90726b67a032de2433e7cd2820.webp)

DATA
Same prompt, same model | No accessibility skill | With accessibility skill
Duration: 15.6m | 5.2m (−67%)
Turns: 84 | 32 (−62%)
Total token usage: 4,595,916 | 1,429,426 (−69%)
Rough cost: $14.20 | $5.97 (−58%)
Token usage = input + cache-create + cache-read + generated, summed across every turn.

### Building an accessible website was cheaper and faster in this…

[3:28](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=208s) [The headline says it is cheaper and faster for AI agents to build accessible websites. An asterisk points to the qualification “in this one experiment.”](https://assets.ai.engineer/sites/aiecode2025/sha256/b16f893d23e531475f9b1c0daa633abe8452c2af55a2b4e7f69feadeb75262d4.webp)

CONCLUSION
It’s cheaper and faster for AI agents to build accessible websites*
*in this one experiment

### Jemima Abu’s introduction

[3:57](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=237s) [A portrait appears above the text “Jemima Abu” and “Product Engineer, CAIS.” A yellow speech bubble reads “Let’s make the web accessible!” A line of professional qualifications appears beneath her role.](https://assets.ai.engineer/sites/aiecode2025/sha256/6c0d06e9dd2d2f5e444d18befdc04c8a4c8784dee1a096412f81b867919d9188.webp)

Let's make the
web accessible!
Jemima Abu
Product Engineer, CAIS
Google Developer Expert • Microsoft MVP • CPACC

### “I’m 3 years old”

[4:10](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=250s) [A smiling cartoon robot labeled “Chat, Claude, Copilot…” raises its hands and says “I’m 3 years old.” A book, globe, map and code window surround it.](https://assets.ai.engineer/sites/aiecode2025/sha256/110e4f401a65c1bb17dbca67f362e2941d8d451f5e35898cb727e3f0829be6b5.webp)

I’m 3 years old
Chat, Claude, Copilot…

### Old Enough! and a toddler’s first errand

[4:23](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=263s) [Two children carry shopping bags with balloons beside them. The still bears the title “Old Enough!” The caption describes a Japanese documentary series about toddlers being sent on their first errand.](https://assets.ai.engineer/sites/aiecode2025/sha256/49086ea6029667bb52a11f35cf70bc2c4c0bb42cc6bdee7f68f55aba4cde3357.webp)

Old Enough!
A Japanese documentary series about toddlers being sent on their first errand
Jemima Abu • The Cost of Accessibility • October 2026

### A child's first errand

[4:34](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=274s) [A red arrow follows the main road from home to the supermarket. A pinned shopping list names milk, bread, eggs and apples.](https://assets.ai.engineer/sites/aiecode2025/sha256/f22f32d4ea5a7045adc594e770a2ffdd225aed1d5fa36b217d4ebdf8bf7265e3.webp)

A child's first errand
SUPERMARKET
HOME
start
walk this way
main road
you made it!
shopping list
• milk
• bread
• eggs
• apples
Jemima Abu • The Cost of Accessibility • October 2026

### A coding agent's prompt

[4:53](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=293s) [An arrow marked “follow the accessibility prompts” leads from a codebase to a web page, past trees labeled <div>. The checklist calls for semantic HTML, keyboard support, visible focus, labeled inputs and cues that work without color alone.](https://assets.ai.engineer/sites/aiecode2025/sha256/8c729db5c34febdf29d1e291350a6a4da487ca30904f788ce21c190ca29b6963.webp)

A coding agent's prompt
<div>
<div>
WEB PAGE
<div>
start
CODEBASE
follow the accessibility prompts
the build path
you made it!
a11y checklist
• semantic HTML
• keyboard works
• visible focus
• label inputs
• no colour-only cues
Jemima Abu • The Cost of Accessibility • October 2026

### The Cost of Inaccessible Code

[5:10](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=310s) [The words “The Cost of Inaccessible Code” appear in large black type at the center of a white slide.](https://assets.ai.engineer/sites/aiecode2025/sha256/48468e98f19b12ba5cdfbe152480451fd226207af0f168284fe0e6f3600de683.webp)

The Cost of Inaccessible Code

### Human bias becomes AI bias

[5:19](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=319s) [A five-step loop shows developers publishing inaccessible code, AI training on public code and learning inaccessible patterns as normal, then developers using AI to generate code. The resulting inaccessible output feeds back into publication.](https://assets.ai.engineer/sites/aiecode2025/sha256/5b2ea9fed38b031a1fb672314a687090f85e5a7e98e1ff7f71ad8cb8978e33ff.webp)

The Cost of Inaccessible Code
01 Developers publish inaccessible code
02 AI trains on publicly available code
03 AI learns inaccessible patterns as “normal”
04 Developers use AI to generate code
05 AI produces inaccessible output
Human bias becomes AI bias

### Building custom components takes a lot longer than using semantic…

[6:20](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=380s) [A person hammers at a workbench displaying code that makes a div act as a button. Beside the bench, a finished wheel labeled <button /> illustrates the native HTML element.](https://assets.ai.engineer/sites/aiecode2025/sha256/89932ed53dcbaf0e9c212f33ce70337042da2ed52eaffd8035a962b9f2ce252f.webp)

The Cost of Inaccessible Code
custom-button.html
role="button"
tabindex="0"
Submit order
<button />
Building custom components takes a lot longer than using semantic elements

### It’s much harder to bake in accessibility in a fully built site

[7:26](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=446s) [Two photos show blueberry muffins on a cooling rack and crumb-topped muffins in a pan scattered with blueberries. The caption likens adding accessibility to a finished site to trying to bake in an ingredient afterward.](https://assets.ai.engineer/sites/aiecode2025/sha256/5736d4bb87d9d936568b91417b82339e974481387f2a0523232d75e95fd78757.webp)

The Cost of Inaccessible Code
It's much harder to bake in accessibility in a fully built site
Jemima Abu • The Cost of Accessibility • October 2026

### The Cost of Inaccessible Code — Losing Customers

[8:01](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=481s) [A wheelchair user moves away from a shop with steps toward a shop with a ramp. The caption says users with disabilities move to businesses that cater to them.](https://assets.ai.engineer/sites/aiecode2025/sha256/68740a5de898b95d0cbe13ae284eecd3d116bcd49946835df1b47c7210c7a435.webp)

The Cost of Inaccessible Code
Users with disabilities move to businesses that cater to them
Jemima Abu • The Cost of Accessibility • October 2026

### The Cost of Inaccessible Code — Legal Repercussions

[9:17](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=557s) [A cartoon character appears beside the words “WE GOT SUED.” The caption says inaccessible websites have legal repercussions.](https://assets.ai.engineer/sites/aiecode2025/sha256/24e5ad5742a763c69888c303a52e2f4db1fb8e7fa16e6a12ce3e89203ffb46e5.webp)

The Cost of Inaccessible Code
WE GOT SUED
There are legal repercussions to inaccessible websites
Jemima Abu • The Cost of Accessibility • October 2026

### Prompting for accessibility

[9:48](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=588s) [Large black text centered on white reads “Prompting for accessibility.”](https://assets.ai.engineer/sites/aiecode2025/sha256/f058eb7acc992cae7952ece9262500a936fa9bab86276a4e0c52b18b8dd79719.webp)

Prompting for accessibility

### How to get your agent to write accessible code

[11:10](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=670s) [Downward arrows link three steps in order. Define your accessibility requirements, audit your existing codebase, then implement a design system.](https://assets.ai.engineer/sites/aiecode2025/sha256/1e71f494f1883921dd649f05173ca741aabd96883e0b252190939bbe9d7f290a.webp)

How to get your agent to write accessible code
Define your accessibility requirements
Audit your existing codebase
Implement a design system
Jemima Abu • The Cost of Accessibility • October 2026

## Full transcript

[0:01](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=1s) [music]

[0:12](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=12s) Now, I'm going to ask you to do an

[0:13](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=13s) exercise for me. This is not going to be

[0:15](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=15s) an interactive session. This is just the

[0:16](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=16s) one thing I want you to do for me. I

[0:18](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=18s) want you to take out your mobile phone

[0:20](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=20s) or your device or whatever laptop you

[0:23](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=23s) use. And then I'm not hearing people

[0:26](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=26s) taking out their mobile. I can't see

[0:27](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=27s) you. So, I need to actually hear if

[0:30](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=30s) you're taking out your mobile phone. And

[0:31](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=31s) what I want you to do is close your

[0:33](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=33s) eyes. And with your eyes closed, I want

[0:36](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=36s) you to unlock your phone and go to the

[0:38](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=38s) notes app and write in hello world. That

[0:41](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=41s) is what I want you to do for me. Okay.

[0:43](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=43s) Oh, is that too much? Okay. You know

[0:44](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=44s) what?

[0:46](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=46s) You know what? Just unlock your phone

[0:47](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=47s) with your eyes closed. Write in your

[0:50](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=50s) lock password. Let's try that. Okay. And

[0:53](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=53s) while people trickle in, we'll see if

[0:55](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=55s) that works. I'm going to give you a 30

[0:57](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=57s) seconds to do that.

[1:03](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=63s) No. Right. Exactly. Now, what happened

[1:05](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=65s) while you were trying to do that? You

[1:07](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=67s) had no idea what you were doing on your

[1:08](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=68s) screen, did you?

[1:11](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=71s) You guys, if you're nodding, once again,

[1:12](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=72s) I cannot see. So, I'm going to need some

[1:14](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=74s) auditory help. So, you had no idea what

[1:15](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=75s) you were doing on your screen. Yes or

[1:16](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=76s) no?

[1:17](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=77s) Oh, we have some yeses. Okay. For people

[1:19](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=79s) that had the yeses, was it more like

[1:21](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=81s) muscle memory? So, you're able to swipe

[1:22](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=82s) up and you remember where your keys are

[1:24](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=84s) and you're able to eat it. Exactly. Now

[1:25](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=85s) imagine if this was your first time

[1:27](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=87s) using that phone and you had no idea

[1:29](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=89s) where any of those keys were. Would you

[1:31](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=91s) have been able to carry out the same

[1:32](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=92s) action? No. Exactly. And that is what

[1:35](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=95s) accessibility is. Accessibility is the

[1:37](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=97s) practice of building products that

[1:39](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=99s) people can use regardless of disability.

[1:42](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=102s) Because while you may be lucky enough to

[1:44](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=104s) be cited, there are people that for them

[1:46](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=106s) having their eyes shut is a permanent

[1:47](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=107s) state. If we are building products that

[1:49](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=109s) those people cannot use or if you're

[1:51](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=111s) building products for people that have

[1:52](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=112s) motor disabilities, cognitive

[1:53](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=113s) disabilities, auditory disabilities and

[1:56](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=116s) they cannot use that product that makes

[1:58](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=118s) it what? A useless product and we don't

[2:00](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=120s) want to build that. So let's talk about

[2:02](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=122s) how we're going to build more useful

[2:03](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=123s) products. But before we get into that,

[2:05](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=125s) let's look at some stats. So 96% of the

[2:07](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=127s) top 1 million websites online have

[2:09](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=129s) accessibility issues. What this

[2:10](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=130s) basically means is that for 96% of

[2:13](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=133s) websites, [clears throat] they cannot be

[2:14](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=134s) fully used by people with disabilities.

[2:17](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=137s) Now, why is that? I go around and I talk

[2:19](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=139s) about accessibility from time to time.

[2:20](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=140s) So, I have the opportunity to talk to a

[2:21](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=141s) lot of developers. And when I ask them,

[2:23](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=143s) why don't we spend more time making

[2:25](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=145s) things accessible? I usually hear it

[2:27](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=147s) takes too long. So, it's like, oh, my

[2:28](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=148s) manager is not going to sign up for me

[2:30](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=150s) spending time to make things accessible

[2:31](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=151s) or the client just doesn't care about

[2:33](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=153s) accessibility or even it's not a

[2:34](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=154s) priority of my company to make things

[2:36](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=156s) accessible. But, I had a hypothesis that

[2:38](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=158s) it actually takes more time and it costs

[2:41](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=161s) more money to build products that are

[2:43](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=163s) inaccessible. So because I am a woman in

[2:46](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=166s) STEM, I had to carry out a little

[2:47](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=167s) experiment. So in um I basically

[2:50](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=170s) prompted my agent to implement this

[2:52](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=172s) design from Figma. The first time was

[2:54](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=174s) without any accessibility guidance. So I

[2:56](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=176s) just let it do whatever it wanted to do.

[2:57](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=177s) And the second time I gave it a skill

[2:59](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=179s) that I had written specifically for

[3:00](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=180s) accessibility. And what I noticed that

[3:02](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=182s) was not only was it faster when it was

[3:05](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=185s) using the accessibility skill, but there

[3:06](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=186s) was also a 58% reduction in cost because

[3:10](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=190s) it was using the accessibility skill.

[3:11](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=191s) Let's take a look at some data. So

[3:13](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=193s) without the accessibility skill, it took

[3:14](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=194s) it 15 minutes to run the prompt. With

[3:16](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=196s) the accessibility skill, it was just 5

[3:18](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=198s) minutes. That's a lot of tokens as you

[3:20](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=200s) can see. And that's a little less tokens

[3:22](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=202s) as you can see over there. And all in

[3:23](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=203s) all, it costs less. So what does this

[3:26](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=206s) tell us? That it is cheaper and faster

[3:28](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=208s) for AI agents to build accessible

[3:30](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=210s) agents. Actually, it doesn't tell us

[3:32](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=212s) that because this was a one-off

[3:33](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=213s) experiment in not a constrained

[3:34](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=214s) environment. So it's not empirical data

[3:36](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=216s) that says it's cheaper and faster. But

[3:37](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=217s) the point is, when you provide skills to

[3:40](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=220s) agents that tell them do this thing this

[3:42](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=222s) specific way, it's going to be faster

[3:44](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=224s) and it's going to save you a lot more

[3:45](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=225s) money in the long run.

[3:48](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=228s) Hi, I'm Jamaima. I'm a product engineer

[3:51](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=231s) at Case. I'm also a Google developer

[3:53](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=233s) expert, a Microsoft MVP, and a certified

[3:55](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=235s) professional in accessibility core

[3:56](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=236s) competencies. I like to go around

[3:58](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=238s) talking about how to make the web

[3:59](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=239s) accessible. Basically, I'm a very

[4:01](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=241s) dangerous combination of a middle child

[4:03](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=243s) and a formerly gifted child. So I'm

[4:04](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=244s) constantly seeking validation and I

[4:06](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=246s) crave attention as well. So that brings

[4:08](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=248s) us here. So let's get back to the talk.

[4:11](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=251s) This is your AI agent. Every popular

[4:15](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=255s) model they're using right now, Chat,

[4:16](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=256s) GPT, Claude, Copilot, they were all

[4:17](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=257s) built three years ago. And of course,

[4:19](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=259s) they're all very smart. The mobile

[4:20](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=260s) models are building very quickly, but at

[4:22](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=262s) the same time, they're just a baby.

[4:24](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=264s) There's a Japanese show that I really

[4:26](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=266s) love called Old Enough. It's basically

[4:28](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=268s) about children being sent on their first

[4:30](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=270s) errand. So it can be like a 2-year-old

[4:31](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=271s) girl, and they ask her to go to the

[4:33](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=273s) supermarket. And one thing I really like

[4:34](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=274s) about the show is that whenever the

[4:36](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=276s) parent sends that child on the errand,

[4:38](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=278s) they always give them very specific

[4:39](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=279s) guidelines. So it's like maybe the child

[4:41](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=281s) has gone to the supermarket with her

[4:42](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=282s) mother multiple times or they'll have a

[4:44](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=284s) helpful little map that says this is how

[4:46](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=286s) to get to the supermarket. Don't go into

[4:48](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=288s) the trees. Don't get lost and this is

[4:49](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=289s) the shopping list that you need. This is

[4:51](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=291s) the exact same one thing you want to

[4:53](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=293s) have in mind when you are prompting your

[4:54](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=294s) agent. You want to make sure that your

[4:56](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=296s) agent is not getting lost in where you

[4:58](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=298s) don't want it to go. So if you're

[4:59](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=299s) building products, you don't want your

[5:01](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=301s) agent to get lost generating things with

[5:03](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=303s) a lot of divs, for example. You want it

[5:05](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=305s) to follow the prompts that you're giving

[5:06](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=306s) it, and you want to make sure that the

[5:08](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=308s) finished result is exactly what you're

[5:10](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=310s) looking for.

[5:12](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=312s) So let's talk a little bit about the

[5:13](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=313s) cost of inaccessible code. So what

[5:15](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=315s) exactly do we lose when we let our

[5:17](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=317s) agents generate code that people can't

[5:19](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=319s) use? Firstly, human bias becomes AI

[5:23](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=323s) bias. One thing that we can see from the

[5:25](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=325s) stats that 96% of the websites in the

[5:27](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=327s) world have some sort of accessibility

[5:28](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=328s) issue or the other is that as humans as

[5:31](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=331s) developers we just don't care that much

[5:32](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=332s) about accessibility and the fact is

[5:34](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=334s) people tend to have a very it works for

[5:37](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=337s) me mindset you know so if I build

[5:39](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=339s) something and I test it on my laptop and

[5:40](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=340s) I'm like it works for me that's great

[5:41](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=341s) I'm going to ship it I'm not going to

[5:43](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=343s) think oh what about somebody that's

[5:44](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=344s) using a screen reader what about

[5:45](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=345s) somebody that's using a mouse instead of

[5:47](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=347s) a key is using a keyboard instead of a

[5:49](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=349s) mouse these things don't necessarily

[5:51](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=351s) occur to us because we have not been

[5:52](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=352s) taught that these things should occur to

[5:53](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=353s) us. And now the problem is much with our

[5:55](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=355s) AI baby, we're teaching it the exact

[5:57](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=357s) same things. AI looks at code that

[5:59](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=359s) humans have generated and it says,

[6:00](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=360s) "Okay, this is what good code looks like

[6:02](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=362s) or this is what code should look like."

[6:03](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=363s) And in turn, AI keeps generating code

[6:05](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=365s) that isn't accessible. Humans keep

[6:07](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=367s) producing more of that code. And we end

[6:09](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=369s) up in this very dangerous loop where if

[6:11](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=371s) we get to the stage where AI is writing

[6:13](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=373s) most of the code for us, we're

[6:15](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=375s) effectively shutting out 16% of the

[6:17](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=377s) world's population who has some form of

[6:19](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=379s) disability or the other.

[6:21](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=381s) Secondly, AI likes to write a lot of

[6:24](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=384s) code. I don't know if anybody has

[6:25](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=385s) noticed that, but if you tell it to

[6:27](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=387s) write something and it can do it in five

[6:29](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=389s) lines, it would rather do it in 500

[6:31](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=391s) lines cuz, you know, the more tokens you

[6:33](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=393s) use, the more money they make. So,

[6:35](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=395s) that's something to keep in mind. So,

[6:36](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=396s) when you are prompting your agent, you

[6:37](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=397s) want to make sure that you're telling it

[6:39](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=399s) to default to the best way of writing

[6:40](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=400s) things. When it comes to building

[6:42](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=402s) products for the web or building

[6:44](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=404s) products in general, there is a popular

[6:46](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=406s) way to do it, but it's not always the

[6:47](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=407s) right way to do it. So for example,

[6:49](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=409s) let's take an accordion component. If I

[6:52](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=412s) was developing an accordion component

[6:53](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=413s) with JavaScript, I could write a custom

[6:55](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=415s) code that uses a lot of JavaScript to

[6:57](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=417s) develop the accordion component. Or I

[6:59](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=419s) could use the HTML details element,

[7:01](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=421s) which is the exact same thing for an

[7:03](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=423s) accordion component and it's way less

[7:04](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=424s) code. It's accessible by default and

[7:06](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=426s) it's browser tested because it was built

[7:08](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=428s) by the people that built browsers. So

[7:10](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=430s) because the details element is not as

[7:13](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=433s) popular as a custom JavaScript

[7:14](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=434s) implementation, AI is going to write a

[7:16](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=436s) custom JavaScript implementation. You as

[7:18](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=438s) a developer, it's your job to tell AI,

[7:20](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=440s) don't go for what's popular, go for what

[7:22](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=442s) is best. And that is why part of your

[7:24](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=444s) skill should also be looking out for

[7:26](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=446s) this. And then when it comes to

[7:28](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=448s) accessibility, it's a lot harder to bake

[7:30](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=450s) in accessibility on a fully built site.

[7:32](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=452s) So on the left hand of the screen, we

[7:34](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=454s) have a blueberry muffin, which is what

[7:36](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=456s) you would expect a blueberry to look

[7:37](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=457s) like. On the right hand of the screen,

[7:39](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=459s) we have imagine somebody handed you a

[7:41](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=461s) plain muffin and they had shoved a bunch

[7:43](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=463s) of blueberries on top and you're like,

[7:44](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=464s) "Here you go, a blueberry muffin." You

[7:46](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=466s) would be like, "Get that trash away from

[7:47](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=467s) me. What is wrong with you?" That is

[7:49](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=469s) exactly what happens when somebody

[7:51](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=471s) builds a complete website and then makes

[7:53](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=473s) it accessible at the end. You cannot

[7:55](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=475s) shove a bunch of area labels into a

[7:57](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=477s) product and call it an accessible

[7:58](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=478s) website. Much like a blueberry muffin,

[8:00](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=480s) you need to bake it in from the start.

[8:03](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=483s) Thirdly, people lose customers when you

[8:06](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=486s) don't make things accessible. So, one

[8:07](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=487s) thing I've noticed from going to a lot

[8:08](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=488s) of um conferences and speaking on

[8:10](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=490s) accessibility is that people that have

[8:11](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=491s) disabilities, they just go to use

[8:14](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=494s) products that work from them. So, for

[8:15](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=495s) example, someone um at a conference I

[8:17](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=497s) was at recently, somebody was talking

[8:18](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=498s) about a banking app they were using. I

[8:20](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=500s) can't remember which one it was and I

[8:22](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=502s) don't want to bismerch the poor bank's

[8:23](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=503s) name if I got it wrong. So, bank A and

[8:25](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=505s) they were basically saying how bank A

[8:27](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=507s) wasn't accessible. So, they ended up

[8:29](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=509s) moving over to bank B just because they

[8:31](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=511s) could not use the product of bank A. So,

[8:32](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=512s) it does not mean that bank A did not

[8:34](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=514s) have better features. It was not a

[8:35](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=515s) better bank as a whole, but it just

[8:37](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=517s) meant the user was not able to use their

[8:39](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=519s) product. So, they went somewhere that

[8:41](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=521s) could cater to their product. So, when

[8:42](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=522s) you build things to be accessible, you

[8:44](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=524s) allow people that can use those products

[8:46](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=526s) use it. And one thing that I always

[8:47](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=527s) hear, which is so funny to me, is that a

[8:49](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=529s) business will be like, "Oh, but none of

[8:50](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=530s) our users rely on assistive

[8:52](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=532s) technologies." My dude, none of your

[8:53](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=533s) users rely on assistive technologies cuz

[8:55](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=535s) they cannot use your product. When they

[8:57](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=537s) get there and they cannot navigate the

[8:58](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=538s) product, they leave the site. Ergo, you

[9:00](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=540s) have no users. It's like imagine a

[9:02](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=542s) business that didn't have a door. I was

[9:04](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=544s) like, "Oh, nobody comes into our store."

[9:05](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=545s) Yeah. Why do you think that is? They

[9:07](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=547s) can't get in the building.

[9:10](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=550s) Oh my god, it's crazy. So, yes, make

[9:12](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=552s) sure your things are accessible and stop

[9:14](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=554s) assuming that your users don't use

[9:15](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=555s) assistive technologies cuz you wouldn't

[9:16](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=556s) know. They're not there in the first

[9:18](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=558s) place. And then finally, there are legal

[9:21](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=561s) repercussions to not building your

[9:23](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=563s) website to be accessible. In the US

[9:25](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=565s) specifically, they have the Americans

[9:26](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=566s) with Disability Act that states that any

[9:28](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=568s) public facing website must be

[9:30](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=570s) accessible. And one thing I have learned

[9:31](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=571s) about Americans is that y'all love to

[9:33](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=573s) sue because there are so many lawsuits

[9:36](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=576s) related to inaccessible websites. So

[9:39](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=579s) make sure you're reading your websites

[9:40](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=580s) to be accessible or you can use this

[9:42](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=582s) really fun sticker from Microsoft Teams.

[9:44](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=584s) So weigh your options. All right, that

[9:47](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=587s) being said, the fact is we've gotten to

[9:50](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=590s) a stage where we're not really writing

[9:52](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=592s) our own code anymore, right? The agent

[9:53](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=593s) is doing most of it for us. So how do we

[9:55](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=595s) ensure that we're getting our agent to

[9:56](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=596s) write code that is accessible? Firstly,

[10:00](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=600s) you want to define your accessibility

[10:02](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=602s) requirements. Every company or every

[10:04](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=604s) organization has different requirements

[10:06](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=606s) depending on what field you are in. So,

[10:08](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=608s) somebody building a web app is going to

[10:09](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=609s) have different accessibility

[10:10](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=610s) requirements than somebody building a

[10:12](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=612s) mobile app. So, it's up to you as a

[10:13](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=613s) developer or as the PM or as whoever,

[10:15](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=615s) even if you're vibe coding, you should

[10:17](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=617s) know what the accessibility standards

[10:19](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=619s) are for that app and make sure you're

[10:21](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=621s) keeping that in mind when you're

[10:22](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=622s) prompting your agent. Secondly, you want

[10:25](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=625s) to audit your existing codebase. If you

[10:28](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=628s) introduce,

[10:30](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=630s) have you ever noticed that like if you

[10:31](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=631s) bring somebody into a room that's messy,

[10:33](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=633s) let's say you have a roommate, like a

[10:34](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=634s) roommate's moving in, and then when they

[10:35](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=635s) move in, they notice a bunch of dishes

[10:36](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=636s) in the sink, that roommates will never

[10:38](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=638s) do dishes because I'm going to be like,

[10:39](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=639s) "When I moved in, there were dishes in

[10:40](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=640s) the sink. Why would I start doing them

[10:42](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=642s) now?" Or maybe you all have had better

[10:43](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=643s) roommates than me. But anyway, if you're

[10:46](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=646s) introducing your agent into a codebase

[10:48](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=648s) that has bad code or has poorly written

[10:50](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=650s) code, that agent is going to take that

[10:52](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=652s) kind of code as the standard. It's going

[10:53](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=653s) to be like, "Why should I do this when

[10:55](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=655s) you didn't?" So, make sure you're

[10:56](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=656s) auditing your existing codebase to look

[10:58](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=658s) out for any accessibility faults in the

[11:00](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=660s) first place. And it's also really easy

[11:01](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=661s) to do this now because you can tell your

[11:03](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=663s) agent to do it as well. You can set up

[11:05](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=665s) an agent that carries out audits on your

[11:07](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=667s) codebase to look for any accessibility

[11:09](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=669s) issues and then fixes them. Thirdly, you

[11:12](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=672s) want to implement a design system or

[11:14](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=674s) some sort of reusable system so that if

[11:15](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=675s) you're fixing issues in one place, they

[11:17](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=677s) are going to be fixed across multiple

[11:19](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=679s) places. So this is just a good standard

[11:20](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=680s) practice in web development or if you're

[11:22](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=682s) working in any kind of app development

[11:24](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=684s) as well, just having a simple library

[11:25](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=685s) where you can refer to one component and

[11:27](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=687s) be like, "Oh, this thing has an issue,

[11:29](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=689s) but if I fix it here, it fixes it across

[11:31](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=691s) 150 pages." That's a really good

[11:32](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=692s) practice to have. And then finally, once

[11:35](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=695s) that is done, you want to make it

[11:37](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=697s) mandatory for your agents to follow

[11:39](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=699s) these guidelines. So every single time

[11:40](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=700s) your agent runs, tell it, make sure that

[11:42](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=702s) you are building these things in a way

[11:43](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=703s) that people can use them and not just in

[11:45](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=705s) the way that I think they should be used

[11:47](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=707s) because it's easy to forget about

[11:49](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=709s) accessibility when you have 3 hours to

[11:51](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=711s) the deadline and you told your manager

[11:53](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=713s) you'd finished it last week and then you

[11:54](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=714s) open the dog and you're like, "Oh [&nbsp;__&nbsp;]

[11:55](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=715s) I need that permissions for that." You

[11:56](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=716s) know, it's easy to forget about these

[11:58](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=718s) things. So if your agent has it in mind,

[12:00](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=720s) it's more likely for it to actually get

[12:02](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=722s) done.

[12:03](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=723s) This is a lightweight version of an

[12:04](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=724s) accessibility skill that you can use. So

[12:07](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=727s) this I will just give a disclaimer. A

[12:08](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=728s) lot of my prompts are geared towards web

[12:10](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=730s) development because that is what I do.

[12:12](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=732s) But like I said, depending on what field

[12:13](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=733s) you're working on, you can um adapt your

[12:15](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=735s) own prompts as needed. This is the

[12:16](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=736s) lightweight version of what I use. It's

[12:18](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=738s) basically telling your agent, make sure

[12:19](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=739s) you're using semantic HTML, only

[12:21](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=741s) reaching for area. Every interactive

[12:23](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=743s) element must work by keyboard alone.

[12:24](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=744s) These are basically just best practices

[12:25](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=745s) or standard practices for web

[12:27](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=747s) accessibility. Another skill that I

[12:29](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=749s) really like is the modern web guidance

[12:31](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=751s) skill. This is by Chrome or Google. I

[12:34](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=754s) don't know why they have different

[12:34](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=754s) names, those people. And basically it is

[12:37](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=757s) a skill that tells your agent the newest

[12:40](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=760s) features to reach for. So kind of the

[12:42](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=762s) example I gave with the accordion. This

[12:43](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=763s) skill just tells your agent, oh if you

[12:45](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=765s) want to build an accordion, you can use

[12:46](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=766s) details. If you want to build a model,

[12:48](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=768s) you can use popover things like that. So

[12:50](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=770s) it's a really good skill.

[12:52](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=772s) And then at the end of the day, I do

[12:54](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=774s) have to give a disclaimer which is that

[12:56](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=776s) just by implementing all these prompts

[12:57](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=777s) and using all these things, it does not

[12:59](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=779s) mean that your website is going or

[13:00](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=780s) whatever product you're building is

[13:01](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=781s) going to be 100% accessible. But it does

[13:04](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=784s) mean that it can help because at the end

[13:06](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=786s) of the day, you want to make sure that

[13:07](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=787s) you are keeping these things in mind

[13:09](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=789s) because the web is for everyone. So,

[13:11](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=791s) everyone should be able to use it. With

[13:13](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=793s) whatever products you're building, make

[13:14](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=794s) sure you're building accessibly so

[13:16](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=796s) everybody can use it. Thank you.

[13:21](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=801s) [applause]

[13:27](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=807s) Not going to lie, you I can't see. So,

[13:29](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=809s) if [laughter] you have any questions,

[13:30](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=810s) you can be like, "Hey, I have a

[13:31](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=811s) question." I'll be like, "Yes, please go

[13:33](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=813s) ahead."

[13:39](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=819s) Can I what?

[13:40](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=820s) Your biggest frustration in

[13:41](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=821s) accessibility.

[13:42](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=822s) Is that with people making things

[13:44](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=824s) accessible or when I'm trying to make

[13:45](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=825s) things accessible?

[13:46](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=826s) What you've seen people

[13:48](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=828s) Yeah. I think one thing is with people

[13:49](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=829s) making things accessible, they tend to

[13:51](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=831s) go one of either way, which is that they

[13:53](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=833s) either don't care at all and then they

[13:55](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=835s) do things like making a div or butting

[13:57](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=837s) or not putting like keyboard handlers

[13:59](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=839s) for certain things. and their excuses

[14:01](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=841s) what I said about how they're like oh

[14:02](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=842s) none of our users use assistive

[14:03](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=843s) technologies or sometimes they tend to

[14:05](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=845s) go overboard and then actually no I just

[14:08](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=848s) remembered I hate those accessibility

[14:09](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=849s) overlays I don't know if you've ever

[14:10](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=850s) gone on a website and you see like

[14:12](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=852s) something in the corner it's like it

[14:13](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=853s) usually looks like an icon of a stick

[14:15](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=855s) person and then you click it and those

[14:16](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=856s) things are terrible they're like the

[14:18](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=858s) blueberry muffing analogy you're just

[14:20](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=860s) adding blueberries to your plain muffin

[14:22](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=862s) so those two things I would say I really

[14:24](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=864s) hate so not caring enough about

[14:25](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=865s) accessibility or just throwing an

[14:27](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=867s) overlay on it and acting like that's the

[14:29](https://www.youtube.com/watch?v=YV1x6gCdgQA&t=869s) fix
