Skip to main content
Try it

Accessibility commitment

Accessibility Statement

Established on 26 May 2026 — last review: 26 May 2026

Amir KELLOUSIDHOUM, publisher of the Scope service, is committed to making the Scope website and application accessible to people with disabilities, in line with the WCAG 2.1 international standard.

This statement applies to getscope.dev and the Scope web application. It was prepared on 26 May 2026 against the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA published by the W3C.

1. Scope of this statement

This statement covers the public marketing pages of getscope.dev (landing, Trust Center, demo page, pricing, comparison, methodology, tools) and the authenticated Scope web application used to capture project context, run the AI scoping pipeline, and generate scoping deliverables (PDF, DOCX, PPTX).

Out of scope: third-party widgets embedded inside the product (Stripe payment elements, Supabase magic-link UI), externally hosted pages linked from the footer, and PDF / DOCX / PPTX files generated by the export pipeline — those carry their own semantic accessibility attributes (language, headings) but are not audited under this statement.

2. Conformance status

The Scope service is partially conformant with WCAG 2.1 Level AA. "Partially conformant" means that some parts of the content do not fully conform to the accessibility standard; the known gaps are listed in section 6 below.

Level AAA is not targeted: it goes beyond the obligations that apply to the Scope service and would require design trade-offs that are not justified for a professional B2B AI copilot.

Scope's target audience includes enterprises subject to the EU Web Accessibility Directive (Directive (EU) 2016/2102) and the European Accessibility Act (Directive (EU) 2019/882). Meeting WCAG 2.1 Level AA is therefore part of our product quality bar, not a one-off compliance exercise.

3. Assessment approach

The assessment carried out on 26 May 2026 combined the following methods:

  • Automated testing with axe-core (https://github.com/dequelabs/axe-core), running the WCAG 2.0 A/AA and WCAG 2.1 A/AA rulesets. The suite is wired into our Playwright end-to-end tests and re-runs on every code change via continuous integration. Any new critical or serious violation fails the build before merge.
  • Manual DOM inspection of the key user flows (extract → clarify → scope → estimate → export), of the design-system primitives (buttons, forms, modals, side panels) and of both public and authenticated layouts.
  • Keyboard-only navigation review: Tab / Shift+Tab order, visible focus indicator, focus trapping inside modal dialogs (WAI-ARIA "Modal Dialog" pattern), Escape-to-close.
  • Contrast-ratio verification on every design-system token, in both light and dark mode.

Transparency note: automated tools cover roughly 30–50 % of WCAG success criteria. The remainder requires manual review, and we plan to commission an external audit before a significant change in customer tier.

4. Pages covered by the automated audit

The automated audit runs against the following routes, chosen as representative of both the public and the authenticated experience:

  • Landing page (/)
  • Trust Center (/trust)
  • Demo page (/demo)
  • Comparison page (/comparison)
  • Project list (/projets) — authenticated
  • Project creation (/projets/nouveau) — authenticated

The internal pipeline screens (extract, clarify, scope, estimate, export) are covered by complementary manual audits. Wiring them into the automated suite is on our backlog and requires richer project fixtures.

5. Supported accessibility features

Navigation and structure

  • "Skip to main content" link at the top of every page, visible on keyboard focus.
  • Page landmarks (main, nav, header, footer) on both public and authenticated layouts.
  • Dynamic lang attribute on the html element, aligned with the user's locale (English or French).
  • Sequential heading hierarchy (h1 → h2 → h3) on the main screens.

Keyboard interactions

  • Visible focus on every interactive element through the --shadow-focus design token (3 px, AA-conformant contrast ratio).
  • Focus trapping inside modal dialogs and side panels — Escape closes, Tab / Shift+Tab cycle through.
  • Touch targets of at least 44 × 44 px on mobile (WCAG 2.5.5 "Target Size").

Content and perception

  • Contrast ratios meeting Level AA (4.5:1 for normal text, 3:1 for large text) in both light and dark mode.
  • Mandatory aria-label on every icon-only button, enforced at the TypeScript compile step.
  • Honouring the prefers-reduced-motion media query across every animation and transition (motion-reduce utility applied throughout).
  • Clear distinction between "running on the machine" and "awaiting user input" states — no permanent spinner that would mislead a screen-reader user.

Forms

  • Labels associated with every field (via htmlFor or aria-labelledby).
  • Plain-language error messages, no stack traces or technical jargon surfaced to the user.

6. Known limitations

The following items are not yet fully conformant and are tracked explicitly:

  • Automated testing to be extended to the internal pipeline screens that require an existing project (extract, clarify, scope, estimate). Covered by manual audit in the meantime.
  • Complex cards and tables on the Trust Center and the comparison page: header semantics and screen-reader navigation are operational but can gain in finesse (sort announcements, extended labels).
  • Document editor (TipTap): third-party component whose accessibility depends on the upstream library. A dedicated review is planned.
  • Supabase authentication page (magic link): third-party iframe, partially outside our control.
  • Formal external accessibility audit by a certified agency: not yet carried out, planned ahead of a significant change in customer tier.

7. Compatibility with browsers and assistive technologies

The Scope service is designed to be compatible with the following combinations:

  • Browsers: Chrome 124+, Safari 17.4+, Firefox 125+
  • Targeted assistive technologies: VoiceOver (macOS / iOS), NVDA (Windows)
  • Viewports: 320 × 568 (mobile) through 2560 × 1440 (desktop)

8. Technical specifications

Accessibility of Scope relies on the following technologies working with the combination of web browser and any assistive technologies or plugins installed on your computer:

  • HTML5, CSS (Tailwind CSS 4), JavaScript (React 19, Next.js 15.1)
  • WAI-ARIA for custom interactive components
  • Key third-party libraries: @axe-core/playwright (automated tests), lucide-react (icons), next-intl (i18n), tiptap (document editor)

These technologies are relied upon for conformance with the accessibility standards used.

9. Feedback and contact

We welcome your feedback on the accessibility of Scope. If you encounter accessibility barriers — content or functionality you cannot access — please let us know. We can also provide the relevant information in an alternative format on request.

  • Accessibility contact: accessibility@getscope.dev
  • Target response time: 5 business days.

If you are based in the European Union and your feedback is not addressed satisfactorily, you can also escalate the matter to the relevant national enforcement body designated under the Web Accessibility Directive or the European Accessibility Act for your member state.

10. Date of statement and evolution

This statement was prepared on 26 May 2026 and last reviewed on 26 May 2026. It is reviewed on every major change to the Scope service, and at minimum annually. Automated audit results from continuous integration are monitored continuously; any blocking regression fails the integration pipeline and is fixed before deployment.

Accessibility Statement · Scope