Accessibility
We want Picasso IA to work for everyone, including people who use assistive technology like screen readers, switch devices, or keyboard navigation. This page explains what we do today, the standards we follow, and how to tell us when something gets in your way.
We treat accessibility as part of the product, not an afterthought. It is not finished, and we keep improving it as we ship new features.
What we do
| Area | What we do |
|---|---|
| Keyboard | Core flows work without a mouse |
| Screen readers | Labels and alt text on controls and generated media |
| Contrast | Text and buttons aim for readable contrast in dark and light themes |
| Motion | Animations stay subtle and avoid flashing |
| Languages | Full interface in six languages |
Standards we follow
We work toward WCAG 2.1 AA. We review new features against it before they ship and go back to fix older parts of the app when we find gaps. We are not there on every screen yet, and we are honest about that.
Found a problem?
If something is hard to use or blocks you, please tell us. Email the page where it happened and the device or assistive tool you were using, and we will look into it. We treat access bugs as a priority. Write to us at team@picassoia.com.
Tips if you use assistive tech
- Core flows work with the keyboard alone, using Tab and Enter
- Generated images and media carry alt text and labels
- Browser zoom works without breaking the layout
- Switch the full interface to your language from the menu
What we are improving
We are honest about the gaps. Right now we are adding clearer focus states, more screen reader labels in the editor, and captions on video output. If something blocks you, tell us and we will move it up the list.
Your feedback makes the product better for everyone. If you hit a wall or have an idea, send it our way and we will read it.