Policies

Accessibility

We want everyone to be able to use madelabs.io and our client portal. We design and build to WCAG 2.2 Level AA, and if something on the site gets in your way, tell us and we will fix it or get you the information another way.

Last updated:

What standard do we work to?

The Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the W3C.

That is our target for this site and our client portal. We haven't had the site independently audited, so we don't claim full conformance. The limitations we know about are listed below.

What do we do to meet it?

We check color contrast against AA, write pages so they work without JavaScript, and structure every page so assistive technology can read it.

  • Every text and background color pair on the public site is checked to the AA contrast ratio, including our accent color, which has a darker variant for links and small text.
  • Every public page's content is in the HTML the server sends, so it reads the same with JavaScript off, in reader modes and in screen readers.
  • Each page has one main heading and a logical heading order, and declares its language.
  • Form errors are written out in words and tied to the field they belong to, so a screen reader announces them with the field.
  • Animation is kept to a minimum, and the animations we add stop when your device asks for reduced motion.
  • Wide tables on this site scroll sideways on a phone, and can be scrolled from the keyboard.

What are the known limitations?

Older downloadable case-study PDFs, some parts of the client portal, and pages run by other companies.

  • Older PDFs. The downloadable case-study PDFs predate this target and may not be tagged for screen readers. Every case study is also published as a web page, and we will send the content in another format on request.
  • The client portal. Parts of the portal were built before this target and have not yet been reviewed against it.
  • Third-party pages. The Google sign-in screen and the other websites we link to are run by other companies, and their accessibility is outside our control.
  • Automated testing. We are adding automated accessibility checks to our release process; until then, checks are manual.

How do you report a barrier?

Use our contact page or call (888) 369-1330, and tell us the page, what you were trying to do and what got in the way.

If you use assistive technology, telling us which one and which browser helps us reproduce the problem. We will reply, tell you what we plan to do, and, where a fix will take time, get you the information or service you need in another way in the meantime.