Accessibility Statement

NeuroBridgeEDU exists to make European education work for every learner: particularly the neurodivergent and multilingual students for whom existing tooling is least well-fitted. That framing shapes every product decision; accessibility is not an afterthought.

We commit to:

• WCAG 2.2 AA as the standard we design toward across both the desktop application and this website.
• Continuous review: accessibility regressions are treated as bugs of the same severity as functional regressions.
• Open feedback: anyone affected by an accessibility issue can reach us directly and expect a response.

WCAG 2.2 Level AA

We design toward the Web Content Accessibility Guidelines version 2.2 at Level AA. The guidelines cover colour contrast, keyboard operability, focus visibility, alternative text, semantic structure, language identification, and consistent navigation, among other criteria.

EN 301 549

The European harmonised standard for ICT accessibility, applicable to public-sector procurement across the EU. EN 301 549 references WCAG 2.1 Level AA as its web baseline; we exceed this by targeting WCAG 2.2.

European Accessibility Act (Directive 2019/882)

The EAA enters force in June 2025 for in-scope private-sector products and services. We design against its requirements for computer hardware, operating systems, and consumer-grade software where applicable to a desktop application.

Neurodivergent-friendly patterns (beyond WCAG)

WCAG covers visual, motor, and screen-reader accessibility well but is less prescriptive about cognitive accessibility. We additionally apply the following patterns:

• Consistent, predictable layout across all screens: no surprise modal interactions or shifting controls.
• Reduced cognitive load through progressive disclosure (the "+2 More preferences" pattern, the disclosed-by-default FAQ).
• A dedicated low-stim mode in the desktop app that desaturates colour and disables ambient motion entirely.
• Lexend as the body face: designed by Bonnie Shaver-Troup specifically for reading proficiency.
• Customisable summary density (Just the highlights / Good balance / Full picture) so the output format matches the reader, not the reverse.

Website (neurobridgeedu.eu): Partially conforms to WCAG 2.2 AA, based on a self-assessment. We are working toward full conformance.

Desktop application (NeuroBridgeEDU v2): Partially conforms to WCAG 2.2 AA, based on a self-assessment. Its UI runs automated accessibility checks with vitest-axe in CI. Native OS integration (file pickers, system notifications) inherits the accessibility of the host operating system.

We track accessibility issues in the public GitHub issue tracker with the accessibility label. Currently known limitations:

• The cinematic scroll journey on the homepage uses sticky-scroll reveals that can feel disorienting for some users; reduced motion preference fully disables them, and we are also evaluating a non-cinematic alternative layout for users who want one without enabling system-wide reduced motion.
• The Tetris mini-game on the homepage is keyboard-only; on mobile viewports it shows a "click to play on a desktop" message rather than an alternate touch interface. A touch control scheme is on the roadmap for the desktop app's in-product version of the game.

The interface and in-app Help are available in all 32 supported languages, selectable in Settings; a small number of strings may still appear in English while translations are completed.

If you encounter an accessibility issue not on this list, please report it (next section): every report is triaged.

Two routes, both with the same response commitment (one working day):

1. Email contact@neurobridgeedu.eu with "Accessibility" in the subject line. Use this for sensitive issues or if you'd prefer not to discuss in public.
2. Open a GitHub issue on the OSS repository with the accessibility label. Public reports help other users see what's been raised and what's been fixed.

Please include, if you can:

• The page or screen where the issue occurs.
• The assistive technology you were using (screen reader version, browser, OS).
• What you expected to happen vs what actually happened.

None of these are required: even a one-line report ("the focus ring isn't visible on the contact form's submit button") is enough for us to investigate.

If you have raised an accessibility issue with us and are not satisfied with our response, EU residents can lodge a formal complaint with their national accessibility enforcement body. In Ireland this is the National Disability Authority (nda.ie). For other Member States, see the European Commission's list of national focal points for the EAA.