Your spec is probably incomplete

1 minute read

The spec is everything, right?

If you define what you're building and how it should work. If you outline the requirements, features, functionality and expected behavior of your feature. If you do all this properly, the work should follow.

If it meets spec, you ship it. Simple.

Except accessibility rarely makes it into the spec at all.

We write a requirement like "user can submit a form" not "user can submit a form via keyboard, screen reader, voice control and switch device." We only spec the happy path for able-bodied users and call it done.

So when developers hand that spec to an AI agent, what are we expecting? The AI will build exactly what we asked for. A form that works for some people. It won't question whether the spec is complete. It won't ask who we've forgotten.

Maybe the real issue isn't whether AI can build accessible features. Maybe it's that we're so used to incomplete specs, we don't even notice what's missing anymore.

Here's my question though.

If you set the spec correctly, truly correctly, with accessibility baked in, would that be a good enough prompt for an AI to build it?

Sent on

Did you enjoy this bite-sized message?

I send out short emails like this every day to help you gain a fresh perspective on accessibility and understand it without the jargon, so you can build more robust products that everyone can use, including people with disabilities.

You can unsubscribe in one click and I will never share your email address.