Forms
Name, email, date: labels in the HTML, errors next to the field. A form that only shakes is not acceptance.
Accessibility at Eqlo and in the sites it produces
Accessibility here is whether a stranger can open the menu, read the H1, and send the form without a pointer. Eqlo starts from real HTML, one H1 per page, and labelled fields when the brief names them. You still owe the words, the contrast, and the images you publish. A score on an empty shell is not the test.
- 1H1 per page
- WCAG 2.2AA target on these templates
- 24 hPhone preview link
- hello@eqlo.appReport a fault
Our commitments on the product
Our commitments on the product start with this marketing site. One H1 per page. Skip to content. The header menus work with a keyboard and as a drawer. Locale switching lands on the counterpart page, not on the homepage. FAQ blocks are native details, not a fake button that forgets focus.
We target WCAG 2.2 AA on these templates. If a control fails, write through contact with the URL and the key you pressed. We date the fix on the changelog.
We do not print a VPAT on this page. Public-sector buyers who need one can ask. We will answer with what is true that week.
What the generator applies to your pages
What the generator applies to your pages is pre-rendered HTML, labelled fields when the brief names them, alt text in the language of the page, and headings that follow the outline you typed. Images become WebP, with sizes. A booking flow that cannot be finished with a keyboard is a bug, not a style.
iOS and Android packages inherit VoiceOver and TalkBack only if we use the ordinary components. Custom paint that ignores the system will fail review and will fail a user. If a screen is a web view of an inaccessible page, fix the page first.
Images
Decorative shots can be empty alt. A price, a name, or a street in an image needs words next to it. Do not hide the offer in a PNG.
Motion
The home demo respects reduced motion when the browser asks. A generated page should not loop a hero video as the only H1.
What stays your job
What stays your job is the copy, the contrast, and the pictures. A red hero on a red button is still your token choice. Fifty unnamed photos will not grow alt text we can defend.
We do not promise a full audit of every project. Test the live URL with a keyboard, with zoom, and with a reader if you have one. Generation can be wrong. Read the screens before a stranger pays.
A redesign of an inaccessible legacy site only fixes the failures you write down. We will not magically invent alt for a folder you never named.
Report a problem
Report a problem through the contact form: the URL, the browser, and whether you used a keyboard, a reader, or zoom. A screenshot helps. A password does not.
Write to hello@eqlo.app if the form does not open. We date a public fix on the changelog when the fix is public.
Related pages
Access is a document problem first. The SEO page is the crawler half of the same idea.
Frequently asked questions
Do you guarantee AA on every generated page?
We guarantee real HTML and labelled controls on the paths we ship. Your tokens, your copy, and your images can still fail. Test the live URL.
Can I import an inaccessible legacy site and have it fixed?
The redesign page is the product loop. Access is part of that loop only if you write the failures you already know. We will not invent alt for fifty unnamed photos.
What about PDFs a project exports?
We do not sell a PDF engine on this site. If a project exports a file, check it. Do not assume a tagged document.
Build the page. Then try it with the keyboard.
Five free projects, no card. If a path fails, write and we will date the fix.