Accessibility at Husly

Husly exists so that anyone can put a website online. The same goes for visitors: husly.app and the sites built with Husly must work for people who use a keyboard, a screen reader or zoom, and for people who cannot tell colours apart. This page says honestly where we are today.

Our standard

We follow WCAG 2.2 level AA. It includes WCAG 2.1 level AA, the level that US ADA guidance and the European Accessibility Act (through the EN 301 549 standard) point to.

Where we are today

The public pages of husly.app conform to WCAG 2.2 level AA.

This covers the public pages of husly.app: the homepage, pricing, designs, widgets, email, the developer API page, the blog, the FAQ, about, contact, the legal pages, this page and the sign-up steps. It does not cover the Husly editor and admin, the account centre after you sign in, or the sites that people build with Husly.

The pages rely on HTML, CSS, JavaScript and WAI-ARIA.

We checked the site on 17 and 18 October 2026: an automated test (axe-core) of every type of public page in light and dark mode, a keyboard-only pass, the pages at 320 px wide and with wider text spacing, the size of buttons and links, a check that the focus is never hidden, a review of the form, menu and image code, and a pass with a screen reader (VoiceOver in Safari). An automated test finds only part of the problems, so we also checked by hand.

The "WCAG 2.2 AA" mark in the footer leads to this page. This is our own assessment, based on the checks above: no official body certifies WCAG conformance.

What already works

• Every page tells the browser its language, so a screen reader uses the right pronunciation.
• Pages have separate header, navigation, main and footer regions, and one main heading.
• Images on husly.app have a text alternative or are marked as decoration.
• Links and buttons show a focus outline when you move with the keyboard. The Escape key closes menus.
• The carousel has a pause button, and it stops while the mouse or the keyboard focus is on it.
• Many animations stop when "Reduce motion" is on in your device settings.
• On a page where something moves, a "Pause animations" button in the footer stops all the motion. With a keyboard, it is the second Tab stop. The site remembers your choice.

What we still improve

• Moving parts. Not every animation follows the "Reduce motion" setting on your device yet. That is a level AAA rule, which goes beyond level AA. Until then, the "Pause animations" button in the footer stops all the motion on any page.

If you find a problem, please tell us (see below). We will fix it and update this page.

Sites built with Husly

Husly gives every site an accessible base:

• Every image, and every file in the media library, has an alt text field. The AI can write alt text for many images at once.
• The Audit tab in the editor warns you when a page has no main heading or more than one, when an image has no alt text, when a link goes nowhere and when text is not translated.
• Every language version gets the correct language tag.

The final result also depends on you. You write the alt text, clear link text, the heading order and the captions for your videos. If you choose your own colours, check that the text is easy to read on its background. If you leave the alt text empty, the site treats the image as decoration.

Further reading

• W3C Web Accessibility Initiative - the standards and how to use them.
• WCAG 2.2 quick reference - every requirement with examples.
• The A11Y Project checklist.
• ADA.gov guidance on web accessibility (United States).
• The European Accessibility Act (European Commission).

Tell us

If something does not work, write to [email protected] or use our contact form. Tell us the page address, what you tried to do, and which device or assistive technology you use (for example, a screen reader and a browser). If the form itself is the barrier, just send an email.