Accessibility Statement

What we aim for

The public pages of this site — the home page, the store size pages, the rule changes page and these documents — are built to meet WCAG 2.1 level AA. No third party has audited them, so read this as the standard we hold ourselves to rather than a certificate. In practice it means readable contrast, headings that describe the structure rather than the styling, links that say where they go, controls reachable and operable from the keyboard with a visible focus, and text that survives being enlarged.

Motion is treated as optional: the entrance animations on the home page are switched off for anyone whose system asks for reduced motion, and nothing in the interface depends on an animation to be understood.

Colour is never the only carrier of meaning. An error-level pre-flight problem is a message you can read, not a red dot.

What the editor requires, and why

The studio needs a window at least 1280 pixels wide, a pointing device, and Chrome or Edge 80+, Firefox 113+, or Safari 16.4+.

The width is not a preference: the canvas, the inspector and the screen list have to be visible together for the tool to make sense, and a narrower window would mean hiding the thing you are editing behind the controls that edit it.

The pointer requirement is the honest limitation. Placing a device frame, dragging a text block and adjusting a crop are direct manipulation on a canvas, and today that work is not fully operable from the keyboard or through a screen reader. The surrounding interface — the panels, the fields, the export flow, the translation grid — is ordinary form controls and behaves like them.

What we know is not there yet

The list we would want someone else to publish:

• The canvas itself has no non-pointer equivalent for positioning and resizing elements. Numeric fields cover part of it, not all of it.
• The canvas conveys layout visually. A screen reader can reach every field that decides what is drawn, but not a description of the drawing.
• The editor does not work at phone or small tablet sizes, by design rather than oversight.
• Some third-party content — the payment checkout in particular — is rendered by its provider, and we do not control its markup.

If something here blocks you

Write to support@easyappscreens.com and say what you were trying to do. We aim to answer within 3 business days, and we will either fix it, tell you honestly when it will be fixed, or do the piece of work for you so you are not stuck on our account.

Reports about this are treated as defects, not as feature requests. If you tell us a control cannot be reached from the keyboard, that is a bug and it goes in the queue as one.