Accessibility Statement

Our commitment

Arcavelo is built and maintained by a single developer, as a personal project rather than a company with a dedicated accessibility team. That doesn’t lower the bar: accessible design is treated as a normal part of building each screen, not a separate pass done at the end. This statement describes what’s actually implemented today, honestly, rather than claiming a level of conformance that hasn’t been formally verified.

What's supported

• Keyboard access. Every interactive control (navigation, forms, buttons, and custom components like dialogs and the product tour) can be reached and operated without a mouse, with a visible focus ring on whatever’s currently focused.
• Dialogs and popovers. Confirmation dialogs (like account deletion) and the guided tour trap focus while open, support closing with the Esc key, and return focus to whatever triggered them once closed.
• Labels and structure. Form fields have associated labels, custom widgets carry the appropriate ARIA roles and attributes (dialog, live regions for status updates, etc.), and pages use semantic headings rather than styled text standing in for structure.
• Color is never the only signal. Status colors (like a flagged overdue assignment or a completed goal) are always paired with text, icons, or a strikethrough, not color alone.
• Reduced motion. Animations (dialog transitions, the tour’s entrance effects, and similar polish) respect your system’s reduced-motion setting. No animation is required to understand or use any part of the app.
• Light and dark modes, plus several theme and accent options, so the app can be read comfortably in different lighting and by different color preferences.
• Responsive layout. The app is built mobile-first and is designed to stay usable, not just visually scaled, from a phone screen up to a wide desktop monitor.

Known limitations

This app hasn’t undergone a formal audit against a specific standard like WCAG 2.1, and it isn’t tested against every combination of browser and assistive technology. Some pages built earlier in the project may not yet fully reflect the patterns described above. Accessibility fixes are ongoing, alongside everything else, rather than a one-time project.

Feedback

If you run into something that doesn’t work well with a keyboard, screen reader, or other assistive technology, that’s useful to know about. Please describe what you were trying to do and what happened, and send it to support@arcavelo.app.

Changes to this statement

If this statement changes, the “Last updated” date at the top of this page will be revised to reflect that.