Wag3s
Accessibility

Accessibility Statement

Our WCAG 2.1 AA and RGAA 4.1 conformance level for wag3s.io — what works, what doesn't yet, and how to reach us if something blocks you.

Statement published March 2026

CONFORMANCE STATUS

Our current level of conformance with WCAG 2.1 AA and RGAA 4.1

1. CONFORMANCE STATUS

wag3s.io, published by Wag3s VER, is partially conformant with WCAG 2.1 Level AA and the French RGAA 4.1. Partial conformance means some parts of the site don't yet meet the standards. The known gaps are listed below.

Applicable standards:

  • WCAG 2.1 Level AA (Web Content Accessibility Guidelines)
  • RGAA 4.1 (Référentiel Général d'Amélioration de l'Accessibilité)

This statement was established in March 2026 and will be updated as we fix things.

KNOWN NON-CONFORMANCES

Accessibility issues we've found and haven't fixed yet

2. KNOWN NON-CONFORMANCES

These are the issues we know about:

Background animations

Most pages have animated star and constellation effects in the background. We don't yet respect the prefers-reduced-motion setting, so users who have enabled that system preference will still see the animations. We're working on a fix.

Relevant WCAG criteria: 2.2.2 Pause, Stop, Hide (AA) — 2.3.3 Animation from Interactions (AAA)

Button labels on wallet connect

The "Connect wallet" button and some related controls don't have a reliable accessible name that screen readers can announce. A user relying on a screen reader may hear nothing, or hear the button's icon name instead of its purpose.

Relevant WCAG criteria: 4.1.2 Name, Role, Value (AA) — RGAA criterion 11.9

Keyboard access in Web3 modals

The wallet connection modal (AppKit) is rendered client-side by a third-party library. Focus management inside the modal is incomplete: focus doesn't move into the modal when it opens, and keyboard navigation through the options is unreliable.

Relevant WCAG criteria: 2.1.1 Keyboard (A) — 4.1.3 Status Messages (AA)

This isn't a complete list. We plan a full audit to catch anything else we've missed.

TECHNOLOGIES USED

The technical stack powering wag3s.io and its compatibility with assistive technologies

3. TECHNOLOGIES USED

wag3s.io is built with:

  • Nuxt 4 — Vue.js framework with server-side rendering (SSR)
  • Nuxt UI 4 — component library built on Tailwind CSS and Headless UI
  • Tailwind CSS — utility-first CSS framework
  • Semantic HTML5 — structured markup using nav, main, section, header, and footer elements

Nuxt UI is built on Headless UI, which handles focus management and ARIA attributes for interactive components. That's our baseline, not a guarantee — as the issues above show, it doesn't cover everything.

TESTING ENVIRONMENTS

Browsers and assistive technologies used during accessibility checks

4. TESTING ENVIRONMENTS

We tested in the following environments:

Browsers: Chrome (latest), Firefox (latest), Safari (macOS)

Assistive technologies: VoiceOver (macOS / iOS), NVDA (Windows)

Audit tools: Lighthouse Accessibility, axe DevTools

CONTACT & FEEDBACK

Report an accessibility barrier or request assistance

5. CONTACT

If something on the site blocks you from reading content or using a feature, email us. If you need content in a different format, ask and we'll sort it out.

Email: hello@wag3s.com

Response time: Within 48 business hours

6. ENFORCEMENT

If you're not happy with our response, you can contact the relevant national authority. In France, that's the Défenseur des droits:

  • Online at www.defenseurdesdroits.fr
  • By phone: 09 69 39 00 00 (Monday to Friday, 8 am – 8 pm)
  • By post (free, no stamp required): Le Défenseur des droits, Libre réponse 71120, 75342 Paris CEDEX 07