Accessibility statement

ArcVelvet is committed to making the platform usable by everyone, including people with disabilities. We work to meet Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards across the surfaces we ship, and we treat accessibility as a quality bar on par with security and performance.

What we currently do

• Semantic HTML and ARIA roles on interactive components.
• Keyboard navigation across primary surfaces — including dialogs, share modals, and the deletion confirmation flow.
• Visible focus indicators on interactive elements.
• Color contrast targeting WCAG AA on body text and primary controls.
• aria-label + aria-modal on dialogs, aria-live on toasts and status messages.
• Escape-to-close on every modal that opens during normal use.
• Reduced-motion respect on ambient visual surfaces where animations are decorative.

Known gaps

We are a small team and we ship in iterations. We know about the following gaps and treat them as backlog items rather than acceptable permanent state:

• Focus traps are not implemented on every modal — Escape-to-close is the consistent escape path, but a screen-reader user navigating with Tab may exit modals into the underlying surface.
• Some interactive elements on dense surfaces (the discovery rail share button, certain action chips on signal cards) are smaller than the WCAG-recommended 44×44 pixel touch target. We are working through these in order of frequency-of-use.
• Some images embedded in user-generated content lack alt text. We require alt text on platform-authored imagery; user-authored imagery is on a separate uplift track.
• The ambient-canvas surfaces (cosmic-luxe backdrops, particles) carry decorative meaning only and are aria-hidden; we are auditing whether any of them carry navigational meaning that requires alternative presentation.

If something doesn't work for you

If you encounter an accessibility barrier on the platform — anything from a missing label to a flow you can't complete — please email arcvelvet@arcvelvet.com with "Accessibility" in the subject line. Tell us which page, which element, what browser and assistive technology you were using, and what you expected to happen. We will respond as quickly as we can and prioritize the fix.

We treat accessibility feedback the same as security feedback: it is a material contribution to the platform's quality, and we are grateful for it.