Danish K.

Danish K.

UI UX Designer

Forums

Designers — would love your honest feedback on A11y before launch tomorrow

Tomorrow we go live on Product Hunt and before the noise kicks in, I wanted to reach out to designers directly.

A11y started as a personal tool. I kept hitting the same wall, contrast checkers that flag problems but offer zero help fixing them. So I built something that suggests accessible colour alternatives instead of just reporting failures. It works as a Figma plugin and a web app, and everything runs locally so nothing leaves your machine.

But I'd genuinely love to know from designers who deal with accessibility day to day:

  • Does the "suggest fixes not just failures" approach actually solve a real problem for you?

  • Is there a feature you wish every contrast tool had but none of them do?

  • Would you use this in your current workflow, and if not, what's missing?

What's the most frustrating part of checking contrast in your design workflow?

Most contrast tools just tell you "fail" and leave you to figure out the rest. You're left manually tweaking hex values, guessing which shade works, and checking again from scratch.

That was the exact frustration that led me to build A11y Smart Color Contrast Checker. Instead of just flagging failures, it suggests accessible alternatives that keep your brand colours intact. No guesswork, no leaving Figma.

But I'm curious about your experience. Where does contrast checking actually slow you down?

Danish K.

16h ago

A11y – Smart Color Contrast Checker - The contrast checker that suggests fixes, not just failures

Most contrast checkers tell you what's broken. A11y fixes it. Web app: Paste any colour and instantly see if it passes WCAG 2.1 and 2.2 standards. Get AI-generated accessible alternatives that keep your brand palette intact. Figma plugin: Select any element inside your design and catch contrast issues in real time, without leaving Figma. Free to use. Open source. Everything runs locally, no data leaves your machine.