We've already tried accessibility tools and were disappointed. Why would Includdy be different?

You probably got a list of 500 errors and nobody knew what to do with them. Includdy doesn't stop at the list. Your developer gets a ticket with the fix tailored to his stack. Your designer sees contrast and hierarchy issues. Your tester knows what to verify manually. Tickets export to Jira, GitLab, GitHub, Trello, or Linear. Work is distributed, not piled into a spreadsheet.

I see new AI accessibility tools coming out every week. What sets you apart?

You ask ChatGPT to fix an accessibility issue. It suggests an ARIA attribute that doesn't exist. You apply it, you re-scan, the problem is still there. You've wasted 20 minutes. Includdy generates corrections from a knowledge base built with active participation from a certified RGAA auditor and W3C member, with 10 years of field experience. You get a fix, you apply it, it passes.

Concretely, how does it work day-to-day?

You enter your page URL and launch the scan. The tool identifies RGAA and WCAG non-conformities and ranks them by impact. For each non-conformity: you generate an AI correction tailored to your stack, or a ticket assigned to the right role. You export tickets to Jira, GitLab, GitHub, Trello, or Linear. The team fixes, you re-scan to validate. Complete cycle: scan, plan, fix.

What's the difference between automated scan and guided scan?

The automated scan analyzes the page code and detects technical non-conformities: contrasts, missing alt text, HTML structure, ARIA attributes. The guided scan covers what automation can't check: keyboard navigation, content consistency, form comprehension. The tool guides you step-by-step through these manual checks. Both are needed to cover all RGAA criteria.

Why a subscription? Can't I just buy it once?

Your site evolves. Each new page or modified component can introduce non-conformities. RGAA and WCAG standards are updated regularly. The subscription includes unlimited scans and updates to detection criteria as standards evolve.

Will the tool become outdated when RGAA standards change?

When new versions of RGAA or WCAG are published, we update the detection criteria. Your subscription covers these updates.

How long does it take to make my site compliant?

It depends on your site's initial state and your team size. With Includdy, diagnosis time is nearly zero: from the first scan you know what to fix, who should fix it, and how. What's left is fix time.

Will adding Includdy complicate our workflow?

Includdy fits into your existing workflow. Correction tickets export to Jira, GitLab, GitHub, Trello, or Linear. Your developers open a ticket and find: the problem explained, the fix suggestion tailored to their stack, the reference to the RGAA criterion.

We use Jira. Do I have to re-enter problems manually?

No. Includdy generates tickets automatically: title, problem description, RGAA criterion involved, correction suggestion, assigned role. You export and import into Jira. Export also works to GitLab, GitHub, Trello, and Linear.

Our site runs on React / Vue / Angular. Does it work?

Yes. Includdy analyzes the HTML rendered in the browser, regardless of framework. Correction suggestions are tailored to your tech stack.

Our site is on WordPress / Shopify / Webflow. Can we use Includdy?

Yes. Includdy detects non-conformities regardless of CMS. Some issues are fixed in the CMS interface (contrasts, alt text, labels). Others require modifying template code. The tool specifies what to modify.

We use AI tools like Cursor, Lovable, or Bolt. Are they compatible?

Yes. Includdy provides correction suggestions compliant with RGAA and WCAG. You copy the correction ticket, feed it to your AI tool, it applies the change to your code. You re-scan the page to verify.

Do we need to install anything on our servers?

No. Includdy works via a web platform and a Chrome browser extension. The extension lets you scan pages locally (dev environment) and pages requiring authentication. Nothing to install on your servers.

Can fixing accessibility break other things on the site?

After each fix, you re-scan the page. The tool compares before and after. If new problems appear, you see them before production deployment.

Guided remediation

Fix every error with AI assistance

Smart suggestions, annotated examples, and guided checklists to fix non-compliance without prior expertise

Compatible with your technologies

Guided Remediation

Know exactly where to start

Junior or tech lead, no need to google best practices or tinker with ten prompts in ChatGPT. Includdy offers three approaches adapted to your way of working.

3tailored
approaches

Choose what works for you: quick fix, learning by example, or step-by-step guide

AI Suggestion AI

Correction generated instantly from our best practices. Apply and move on.

Annotated Examples

Bad code vs good code, with detailed explanations. Understand the logic and avoid pitfalls.

Checklist Guided

Step-by-step action plan to work independently without forgetting anything.

Clear Explanations

Understand every issue, without technical jargon

When you're starting out in accessibility, it's easy to feel lost. In Includdy, every detected issue comes with a simple explanation.

Explanations in plain language

No more deciphering WCAG specifications or searching across 5 sites. We explain it to you like a colleague would, in simple words.

Real cases to understand the impact

Real-world situations where this issue blocks or excludes a user. To raise awareness with your team and your clients.

Who is affected?

Real use cases, user impact

Business impact

Direct link to your business

Who fixes it and how

Role involved and steps to follow

Official standards

RGAA and WCAG references one click away