Accessibility Statement

Last updated: June 2, 2026

Motive is committed to making motive-os.com usable for as many people as possible, including those who rely on assistive technologies. We treat accessibility as part of building the Site well, not as an afterthought.

Conformance target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. These guidelines explain how to make web content more accessible to people with a wide range of disabilities, including visual, auditory, motor, and cognitive needs. We are not formally certified against WCAG; this statement reflects our own ongoing assessment of the Site.

What we have done

The Site currently includes:

• A "skip to content" link so keyboard users can bypass the navigation.
• Semantic landmarks — a single main content region, a banner header, and a footer — so assistive technologies can navigate the page structure.
• A single, clear page heading and a logical heading order throughout.
• Visible keyboard focus indicators on every interactive element.
• Full support for the "reduce motion" setting: if your system requests reduced motion, background animation and scroll-triggered effects are turned off while the content stays fully usable.
• A contact form with labels tied to every field, autocomplete hints for your name and email, and clearly marked required fields.
• Decorative graphics and icons marked so screen readers skip them rather than announcing noise.
• Body text that meets AA contrast against the page background.

Known limitations

We want to be honest about where the Site does not yet fully meet our target:

• Placeholder text inside form fields uses a light gray that falls below the AA contrast threshold for normal text. Placeholder text is advisory only and is not required to convey information — every field has a visible label — but we note it here for transparency.
• The contact form relies on the browser's built-in validation for required fields and email format, rather than custom inline error messages. This works with assistive technologies but is less descriptive than a fully custom error experience.

We intend to address these as the Site evolves.

How to report a problem

If you encounter a barrier on the Site, or need information in a different format, please tell us. We take accessibility feedback seriously and will do our best to help.