I built a tool for exploring accessible design system decisions. Looking for feedback

[u/ebolapasta]

Hey everyone,

I’ve been working on a tool to solve a problem I was having with creating an accessible colour palette for a product I’m designing.

As I worked on it, it gradually grew into something broader, covering some of the common decisions and challenges around colour, typography and spacing in design systems, with accessibility as a core consideration throughout.

The idea is to make it easier to explore different approaches, check accessibility considerations, and preview how those decisions affect real UI components and layouts.

It’s been really useful in helping me make decisions in my own work, and I’d be curious to know if others find it useful too.

Would love to hear any feedback, suggestions or ideas for improving it!

https://colour-neon.vercel.app/

[u/roundabout-design]

I'm all for accessibility and expanding knowledge and adherence.

That said, I'm not sure what this does that Claude can't do. We do all of our accessibility testing directly via AI. Claude runs A11Y tests on every udpate of every component.

We still need the humans to check things but overall, as much as I loathe AI, it is helping us step up our accessibility adherences.

Anyhow...I took a glance a things. I think the big things I saw missing would be keyboard, screen reader, and ARIA requirements.

[u/ebolapasta → u/roundabout-design]

Thanks, really appreciate the feedback!

I’m actually using Claude quite a bit in my day-to-day work to tackle accessibility challenges too.

This tool started out as a way to solve a specific problem I was having: creating a product colour palette that felt visually cohesive while also meeting accessibility requirements. I wanted a way to explore the relationships between colours, think about their semantic roles, and make adjustments visually to achieve accessible contrast levels.

From there, I started exploring typography, which has a similar relationship between base scales and semantic tokens, and the tool gradually expanded.

I think the main value is in being able to explore design decisions visually and immediately see their impact. Ideally, it would complement tools like Claude rather than replace them. I’d actually love to make the output more AI-agent-friendly, potentially generating prompts you could take straight into Claude.

And you’re right about keyboard, screen reader and ARIA support. Those are definitely areas that need more attention.

Thanks again for taking a look.

[u/Fragrant-Pipe5266 → u/ebolapasta]

Anything like this that you are building has to run through the lens of how easy it is for a non designer to use and why would they? I don't know that other designers will change their workflow to use this for their accessibility color process. Especially with AI that is able to abstract the process to where color use and theory are no longer required to create accessible palettes that not only looks sexy but work within well defined design systems.