Accessibility Statement

Last Updated: October 4, 2026

1. Our Approach

Lantanios Solutions Inc. ("Lantanios") works to make the Lantanios platform usable by as many people as possible, including people who use screen readers, keyboard-only navigation, voice control, screen magnification, or other assistive technology.

We treat accessibility as part of building a feature rather than a later cleanup pass.

2. The Standard We Work Toward

We use the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as our design and review target.

We describe this as a target, not as certified conformance. The platform has not undergone a third-party accessibility audit, and we do not currently publish a VPAT or an Accessibility Conformance Report. We have no formal conformance statement to offer for a procurement process.

3. What the Platform Supports Today

These are accessibility behaviors we design for in the Lantanios application interface — the screens a Builder uses to create and run a site, and the shared components a visitor interacts with on a published store. Coverage is uneven (see Section 4), and none of them is a guarantee about any particular screen:

Keyboard operation. Interactive controls are designed to be reachable and operable from the keyboard. Option groups implement roving focus with the Arrow, Home, and End keys, so a group behaves as one stop in the tab order rather than many.
Visible focus. Focused controls carry a visible focus indicator.
Correct semantics. Choice controls expose real checkbox and radio semantics with accurate checked state, grouped controls are named groups, and a selection can be reversed from the same control that announces it — so a screen reader conveys both what a control is and what state it is in.
Touch target size. Interactive targets in newer surfaces are sized to at least 44 by 44 pixels.
Form validation. Validation messages are associated with their fields and announced rather than conveyed by color alone.
Data alternatives. Charts are designed to come with the same figures as a table, so the information does not depend on reading a graphic.
Responsive layout. Interfaces are designed for viewports down to 375 pixels wide, which supports both small screens and high zoom levels.
Light and dark presentation. The interface honors the active theme rather than forcing one appearance.
Alternative text tools. Builders can set alternative text on uploaded media and on product images, so a published store can describe its own images.

4. Known Limitations

We would rather list these than let you discover them:

No independent audit has been performed. Our accessibility review is internal, and internal review misses things that testing with assistive technology users does not.
Coverage is uneven across the product. Newer and recently revised surfaces have had explicit accessibility work; older surfaces have had less, and some have not been reviewed against WCAG 2.2 AA at all.
Some individual defects are known and tracked rather than fixed — for example, a narrow-viewport dialog heading that truncates instead of wrapping.
Content generated with the platform's AI features is a starting draft. It is not checked for accessibility, and a Builder remains responsible for reviewing it.
Third-party components embedded in the platform — most notably hosted payment and identity screens provided by our processors — are outside our control, and we make no statement about their conformance.

5. Sites Built on Lantanios

This statement covers the Lantanios platform itself. It does not cover the individual sites that Builders create using it.

Lantanios provides the building blocks — accessible components, alternative-text fields, keyboard- operable controls, and themes with defined color roles. What a visitor actually encounters on a Builder's store depends on how the Builder uses them: whether alternative text was written, whether a chosen color combination has sufficient contrast, whether headings describe the content, and what media and copy were published.

Each Builder is responsible for the accessibility of the site they publish and the content they put on it. If you encountered a barrier on a store built with Lantanios, the site owner is the one to contact; you are also welcome to tell us.

6. Reporting an Accessibility Barrier

If any part of Lantanios is difficult or impossible for you to use, please tell us at [email protected]. Put "Accessibility" in the subject line so it reaches the right place quickly.

It helps us reproduce the problem if you can include:

the page or screen where it happened, and a link if you have one;
what you were trying to do;
the assistive technology, browser, and operating system you were using; and
what happened instead of what you expected.

We do not promise a response time or a fix. If you need information that is currently only available through an inaccessible part of the platform, say so in your report.

7. Changes to This Statement

This page may change at any time. The "Last Updated" date at the top shows when it last changed.