Accessibility Statement
Last updated: November 9, 2026
We want everyone to be able to use AriesAi, whether they use a mouse, a keyboard, a screen reader, zoom or other assistive technology.
Our target
AriesAi aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. This covers AriesAi's own pages, the dashboard and the editor.
Where we stand
AriesAi partly meets WCAG 2.2 AA. We check contrast and keyboard use as we build: text is designed for a contrast of at least 4.5:1, controls show a visible focus ring, dialogs keep keyboard focus inside them and hand it back when they close, and every page can be zoomed.
Known limitations
- Visual editing in the preview (clicking an element to change its text, image or icon) needs a mouse or a touch screen. You can ask for the same changes in the chat instead.
- Comment pins on the preview are placed with a mouse or a touch screen. You can describe the change in the chat instead.
- Websites and apps built with AriesAi are the responsibility of the person who creates them. The AI is asked to build accessible sites, but we can't guarantee that every generated site meets WCAG, so please check yours before you publish it.
Report a barrier
If something in AriesAi is hard or impossible for you to use, write to info@ariesai.dev. Tell us which page it was, what you were trying to do and, if you like, which browser and assistive technology you use. We read every message and will get back to you.
About this statement
This statement is based on our own testing. We review it whenever AriesAi changes in a way that affects accessibility.