We use cookies to improve the site and measure our ads. Manage your cookie preferences.

Skip to main content

Accessibility

modelworks.ai is built and tested to WCAG 2.2 AA.

Here is what that covers, how we check it, and how to tell us when something is hard to use.

Contents

  1. The standard we work to
  2. What the site does
  3. How we test it
  4. Known limitations
  5. Report a problem
  6. Questions we get asked

The standard we work to

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA across every page of modelworks.ai. WCAG is the accessibility standard published by the W3C, the body that sets web standards.

What the site does

  • Keyboard: every page opens with a skip link to the main content, every link, button, and field has a visible focus outline, and menus, dialogs, and dropdowns open and close with the keyboard.
  • Contrast: text meets the AA ratio of 4.5:1 against its background, and large headings meet 3:1. Icon-only buttons carry text alternatives for screen readers.
  • Motion: decorative background animation — including the particle fields and shimmer effects — stops entirely when your device is set to reduce motion. Loading states stay visible as a static icon.
  • Forms: every field is labelled, sign-up, login, and password recovery fields announce their errors to screen readers, and required fields are marked.
  • Images: meaningful images carry text alternatives, and decorative ones are hidden from screen readers.
  • Zoom: pages reflow to narrow widths, so text can be enlarged without sideways scrolling.

How we test it

Every shared component on the site was audited against WCAG 2.2 AA in November 2026, combining automated checks with manual passes: a keyboard only pass through every flow, a screen reader pass through the auth, publishing, and purchasing flows, and manual contrast checks of the theme palette. We re-audit whenever we ship changes that touch navigation, forms, or motion.

This page, like the rest of the site, is a living commitment — if any page falls short of what is described here, tell us and we will fix it.

Known limitations

  • Sign-in with other providers: signing in with a linked account (such as X) opens the provider's own page, whose accessibility is set by that provider. If it gives you trouble, you can always sign up with email at modelworks.ai/signup.
  • Documentation: our documentation lives at a separate address, docs.modelworks.ai, and is maintained in its own repository. Plainly: this statement describes modelworks.ai, not the docs site.
  • Member content: circuit names, descriptions, and other member-uploaded content are written by our users. If a piece of content is inaccessible or otherwise problematic, contact us and we will take it up with the author or take it down.

Report a problem

Use the Contact Us link in the footer of any page. Include the page address and what went wrong. If you need anything on the site in another format, such as plain text, ask and we will provide it.

We treat accessibility reports as bugs. Something hard to use is our problem, not yours.

Questions we get asked

Does modelworks.ai meet WCAG 2.2 AA?

That is the standard we build and test to. Every shared component was audited against WCAG 2.2 AA in November 2026, and we re-audit when components change. If you find a page that falls short, contact us and we will fix it.

How do I report an accessibility problem?

Use the Contact Us link in the footer with the page address and what went wrong. We can also send any content from the site in another format.