Everyone should be able to use this. Tell us if you cannot.

The standard

WCAG 2.2 at level AA governs both surfaces. It is applied when a page is written rather than retrofitted afterwards, and the same rules hold on the marketing site and inside the product, because the person doing the work is often the same person who read the pricing page.

Accessibility here is treated as part of whether a screen is finished. A control nobody can reach with a keyboard is a broken control, in the same way a button that posts to the wrong address is a broken button.

How it is built

• Real structure. Exactly one h1 per page, heading levels chosen for the document outline rather than for the size they render at, landmarks rather than styled divs, and a skip link as the first focusable element on every page.
• Every link goes somewhere. A link on this site resolves to a page. Nothing is rendered as a link in order to hold a space.
• A control says what it is. The menus in the header open from buttons that carry their expanded state, so a person told "button, Products, collapsed" gets what they were promised when they press it. On a narrow screen the navigation is replaced by a stacked equivalent rather than hidden.
• Focus stays visible. The focus outline is drawn from a dedicated token at the root, so removing a browser default cannot quietly remove the only indication of where the keyboard is.
• Colour never carries meaning alone. Every palette value comes from one token layer, enforced by a build gate that rejects a hardcoded one. Status is written as a word next to the hue, and the section navigation on documents like this one marks the current section with an assistive-technology attribute rather than only a darker colour.
• Motion is optional and never load-bearing. There are two animations on the whole site. Under an operating-system preference for reduced motion the script that arms them does not run, which leaves both in their final state: nothing moves and nothing is hidden. Content is never revealed by script, so a page whose JavaScript fails still shows everything.
• Reading measure is relative. Line lengths are capped in em rather than pixels, so a passage keeps its measure when the text around it is scaled up.

Report a barrier

Write to support@attergo.com. It reaches the people who build the site rather than a queue, and you will get a reply from a person.

Three things make a report immediately actionable, and none of them is required: the address of the page, what you were trying to do when it stopped, and the browser and assistive technology you were using. If a barrier is standing between you and something you need from us, say so, and we will get you that information another way while the fix is made.

Scope

This statement covers the public site at attergo.com and the signed-in application at https://app.attergo.com. Both are built to the same standard by the same people.

If you are evaluating Attergo for an organisation with a procurement requirement in this area, write to sales@attergo.com and you will get our position on it in writing.