PROXIA STUDIO

Accessibility

Accessibility statement

Proxia Studio (proxia.studio)

Compliance status

Proxia Studio is in partial compliance with the French General Reference for Improving Accessibility (RGAA), version 4.1, due to the non-conformities and exemptions listed below.

This statement applies to the website proxia.studio

Test results

The RGAA 4.1 compliance audit carried out in May 2026 covered all page templates on the site.

  • •Number of applicable RGAA 4.1 criteria: 106
  • •Overall compliance rate: not yet measured (the priority fixes from June 2026 have been applied; a full tooled audit to establish an official rate is planned for Q4 2026).

Two rounds of fixes were applied in June 2026: priority RGAA fixes (visible focus, form labels, buttons without an accessible name, aria-live for dynamic content), followed by secondary fixes (focus trapping on all public modals, tooltips, external links with a screen reader warning, dynamic messages using role="alert"). A third pass in July 2026 addressed the remainder of the accessibility findings from the react-doctor audit: labels and tooltips on interactive controls, label/field association, keyboard handling on interactive elements, and a declared language on every page. A fourth pass in late July 2026 added modal semantics (focus trap, role="dialog") to the supervisor eligibility dialogs, an aria-expanded state on expandable session rows, and support for the prefers-reduced-motion system setting on looping animations. A full tooled audit is planned for the second half of 2026.

Non-accessible content

Non-conformities

  • •Some interactive elements may show insufficient contrast in dark mode (RGAA criterion 3.2), to be documented during the full audit planned for late 2026.
  • •Some data tables in the admin dashboard lack explicit headers (criterion 5.7); these tables are not accessible to the public, and a fix is planned for 2027.

Exemptions for disproportionate burden

  • •Exported project files (PRPROJ, XML, DRP) downloadable from the platform are proprietary formats whose internal structure falls outside the accessibility scope of the website.
  • •AI-generated timeline previews are complex visual representations for which a complete text alternative is not technically feasible at this stage.

Preparation of this statement

This statement was drawn up on 23 May 2026. It was prepared by the in-house Proxia Studio team.

Technologies used

  • HTML5
  • CSS3
  • JavaScript
  • React
  • Next.js

User agents and assistive technologies tested

  • •NVDA + Firefox (Windows)
  • •VoiceOver + Safari (macOS / iOS)
  • •Keyboard-only navigation (Chrome, Firefox)

Feedback and contact

If you encounter an accessibility barrier that prevents you from accessing content or a feature on the site, you can contact us to obtain an accessible alternative or another way to access the content.

We are committed to responding within 5 business days.

Right of appeal

If you notice an accessibility issue that prevents you from accessing content or a feature on the site, and you report it to us but do not receive a prompt response, you have the right to submit a complaint or a request to the Défenseur des droits (France's independent rights ombudsman).

  • •Défenseur des droits: defenseurdesdroits.fr (opens in a new tab)
  • •Contact the regional delegate of the Défenseur des droits in your area
  • •Send postal mail (free of charge, no stamp required) to: Le Défenseur des droits, Libre réponse 71120, 75342 Paris CEDEX 07

Multi-year accessibility action plan

Proxia Studio is committed to progressively improving the accessibility of its platform according to the following schedule:

  1. 2025-2026

    In progress
    • ✓ Initial RGAA 4.1 audit of all page templates
    • ✓ Fixed critical non-conformities: page language, focus visibility, label/field associations, buttons without an accessible name
    • ✓ Added aria-live to the AVA chat for dynamic content
    • ✓ Created the accessibility statement and software guide pages
    • ✓ Added the required navigation links to the footer
    • ✓ Focus trap on all public modals with role="dialog" and aria-modal
    • ✓ Added aria-label to icon buttons lacking an accessible name
    • ✓ Screen reader warning on all links that open in a new tab
    • ✓ role="alert" on dynamic error and success messages
    • ✓ Labels and tooltips (aria-label + title) on all interactive controls without an accessible name (439 occurrences, 59 files)
    • ✓ Label/field association via htmlFor on forms, and removal of placeholders used as the sole label
    • ✓ Keyboard handling (Enter/Space, arrow keys for progress bars) on interactive elements without native semantics (66 occurrences, 25 files)
    • ✓ Declared language on the global error page (global-error)
    • ✓ Focus trap and role="dialog" on supervisor eligibility dialogs
    • ✓ aria-expanded on expandable session rows
    • ✓ Support for prefers-reduced-motion on looping animations (streaming cursor, AVA waves, score ring)

  2. 2026

    Planned
    • Full RGAA 4.1 audit with a certified third-party tool
    • Fix insufficient contrast in dark mode (criterion 3.2)
    • Testing with users with disabilities
    • Publication of the official compliance rate

  3. 2027

    Goal
    • Achieve full RGAA 4.1 compliance
    • Full compliance with the European Accessibility Act (EAA) directive 2019/882
    • Establish a continuous accessibility testing process integrated into the development cycle