Purpose

Accessibility = The ability to access.

Accessibility for most people means letting disabled people use your product. My core belief is that accessibility isn’t just about a blind person like me trying to use a website or a deaf person having captions on screen. Access blockers can exist in the form of language, price and location barriers. If you made your product in one language you’ve isolated access to billions of people. If your product only runs on machines that cost more than a certain price, you’ve priced out entire groups of people. If your product can only function within the laws of one country then the rest of the world is unavailable to you. The key distinction is to not let social and economic barriers make the work done for people with disabilities fall short and abstracted away — instead it is to broaden the view so that access can be looked at holistically and designed for from the ground up.

Accessibility is a product decision.

If you want things to be accessible the decision needs to happen early — at the product level. Most bad or decorative implementations of accessibility come from access being an afterthought, something bolted on at the end. The friction of adding things later gets higher the further along in the product story you go. If designing for visual access is a product decision from the start, you don’t build layouts with multiple Z axis interactions. If global availability is a product decision from the start, the choice to default to English disappears.

Accessibility makes things better for all users.

When designing with access in mind the implementation, while built for a specific group of people, benefits everyone. When access is decided early every user downstream gets the benefits of those design decisions. A basic example: if your UI is simple enough for someone with motor disabilities to use, people with full motor function will walk through it even easier.

Accessibility unlocks greater second order systems.

Good design happens within constraints, and having accessibility as a constraint enables more robust systems across all aspects of a product. The design solutions made to tackle access often get consumed by entirely different parts of the system. The vinyl record was first created to give blind users access to books in audio format. Now vinyl is the most sold form of music in 2026.

Blinding Pixels exists to show — through real work, real products, and real methodology — that these ideas are not only possible but better. Agentic coding has opened a door: people can now embed their values directly into software without needing fifteen years of background to do it. My goal here is to use that to demonstrate what design looks like when access isn’t an afterthought. Because when you design for access from the ground up, you don’t make compromises. You make better things.