Frequently asked questions

Scan your site's main pages with Includdy. The tool ranks non-conformities by impact and generates tickets assigned to the right role on your team. You distribute the work without having to understand the standard yourself.

Your developers receive tickets with correction suggestions tailored to your stack. They fix, you re-scan to verify. Before the official audit, you can request a dry-run audit: a certified expert reviews your work and tells you what's left to fix.

An official audit by an external auditor is still mandatory for the public sector. Includdy doesn't replace it.

Includdy prepares your team beforehand. You scan your pages, you receive corrections explained in plain language, you fix them before the auditor arrives. The scenario to avoid: failing the audit, fixing in a rush, paying for a second audit.

The interface is educational. When the tool detects a non-conformity, it explains what's wrong, who is impacted (blind user, low-vision user, motor disability), and which RGAA criterion is involved. The correction suggestion is tailored to the tech stack you use.

You learn by fixing your real projects.

Includdy automates detection and correction ticket generation. The repetitive part (contrasts, alt text, HTML structure, ARIA attributes) is handled automatically. You spend your time on what the tool can't do: UX, business trade-offs, strategic guidance.

Tickets export to Jira, GitLab, GitHub, Trello, or Linear.

No. Accessibility requires human judgment. No tool does everything alone. Keyboard navigation, relevance of alt text, content consistency: these must be verified manually.

Includdy detects non-conformities and generates correction suggestions. Your team applies the fixes in the code. The tool eliminates research time, not fix time.

Yes. The difference: without a tool, you spend hours figuring out what's wrong and how to fix it. With Includdy, you have correction tickets from the first scan. The diagnosis disappears, the fixing remains.

Includdy is a SaaS tool. It makes your team self-sufficient; it doesn't replace a service provider.

If you're looking for complete support, contact us. We work with partner audit firms.

Includdy analyzes up to 200 pages per project. But you don't need to scan every product page: you scan your templates (product page, category, cart, checkout). If the template is compliant, the pages generated from that template are too.

For specific volumes or configurations, contact us.

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.

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.

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.

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.

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.

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

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.

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.

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.

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

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.

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.

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.

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

The tool is designed for teams discovering accessibility. Each non-conformity is explained in plain language: what's the problem, who is impacted, why it's non-conformant per RGAA. Correction suggestions are tailored to each person's role. A developer doesn't get the same ticket as a designer.

For an official RGAA audit: an external auditor is necessary (mandatory for public sector, recommended for private). Includdy doesn't replace this audit.

Includdy prepares you. You fix non-conformities beforehand. When the auditor arrives, most of the work is done.

Yes. Our founder is a certified RGAA auditor and W3C member with 10 years of accessibility experience. We conduct official RGAA and WCAG audits and work with partner auditors. Contact us.

A dry-run audit is a check before the official audit. A certified expert reviews your work and tells you if anything's left to fix. It's a safety net.

The official audit is the regulatory audit, conducted by an independent auditor. It determines your compliance with the law.

No. Includdy handles automatic detection and ticket generation. Your consultant focuses on strategic advice and cases automation can't solve.

Email support, response within 1-2 business days. Priority support on the Team plan. Training sessions and dry-run audits with experts on request.

No. Some RGAA criteria require human judgment. No tool covers everything alone. Includdy detects automatic non-conformities and guides you on manual checks. To maximize your audit chances: combine automated scan, guided scan, and dry-run audit with expert.

If you took a dry-run audit with an expert before the official audit and you fail, we refund the dry-run audit fees.

Without a dry-run: follow the complete method (automated scan, guided scan, fixes). It covers all RGAA criteria.

Digital accessibility is a legal obligation since the EAA (June 2025). Penalties go up to €50,000 fines and exclusion from public procurement.

With Includdy, accessibility is verified during development, component by component. It's not a separate project that blocks sprints; it's a check built into the existing process.

Every component developed without verification will need rework later. Checking a page during development takes minutes. Reworking 50 pages afterward takes weeks.