Accessibility Statement

1. Commitment and target

LATTY INTERACTIVE LLC is committed to making Accessibility by OpenSiteCheck usable by disabled people, including people who navigate by keyboard, zoom or reflow content, use a screen reader, use voice input, or need clear structure and language.

Our technical target is the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. That target is a development and testing benchmark, not a claim that every current page, generated report, or third-party service fully conforms.

2. What this statement covers

This statement covers the public OpenSiteCheck website, signup and login, account dashboard, online scan reports, and the legal pages on the OpenSiteCheck service.

It does not claim accessibility for:

• third-party websites submitted for scanning or their content shown as evidence;
• the payment provider or another external service linked from OpenSiteCheck;
• changes someone makes to their website based on a suggested fix; or
• downloaded files after they have been modified or redistributed by someone else.

3. Current status

The service is being prepared for public beta. Our current browser tests cover the main tasks, mobile layouts, form labels and errors, visible keyboard focus, reduced-motion settings, and automated accessibility checks on six public pages. The latest run found no automated problems on those six pages. We have not yet completed an independent WCAG audit or full screen-reader test, so we do not claim full WCAG 2.2 AA conformance.

We will update this statement with the tests completed, results, and fix dates as we finish broader keyboard, screen-reader, zoom, mobile, and assistive-technology testing.

4. Known limitations

PDF reports

Generated PDF reports are designed for reading and printing but are not currently set up for reliable screen-reader structure and navigation. Use the online report or downloadable HTML report where available. Contact us if you need the report information in another format.

Third-party page evidence

A report can reproduce inaccessible code, page titles, screenshots, or text from the site being tested. This evidence is necessary to identify the problem but may retain barriers from the source page. Screenshots have a general text alternative and may not communicate every visual detail.

Suggested code and explanations

Suggested code can be incomplete or wrong and is not automatically tested in the target website. It may use terminology or structure that needs clarification. Report a confusing explanation or inaccessible code example and we will review it.

Testing still in progress

Because full assistive-technology testing is not complete, additional barriers may exist. We prefer to state that plainly rather than make an unsupported conformance claim.

5. Measures we take

• Use semantic HTML, visible labels, heading structure, landmarks, and status or alert announcements.
• Keep interactive controls keyboard operable with visible focus indicators and practical target sizes.
• Use strong text contrast, responsive layouts, horizontal scrolling for wide code or tables, and reduced-motion fallbacks.
• Test authentication and report-email labels, errors, polling recovery, private-page metadata, and core UI paths in repeatable browser checks.
• Clearly separate automated results from WCAG conformance, legal conclusions, and testing by people.
• Review accessibility feedback as a product issue and update this statement when known barriers or testing status change.

6. Accessibility feedback and alternative formats

If a page, control, report, email, or document is difficult to use, email support@opensitecheck.com with the subject Accessibility feedback.

Please include, where you can:

• the page or report URL;
• what you were trying to do and what happened;
• your browser, device, and assistive technology; and
• the format or workaround that would help.

Do not send a password, payment credential, or sensitive target-page content. We aim to acknowledge accessibility feedback within two business days and will give a practical response or progress update as soon as we can.

If a PDF or report format is not usable, ask for the same available information in HTML, plain text, or another reasonable format. We will work with you on an alternative where the underlying report data allows it.

7. Preparation of this statement

This statement was prepared on August 17, 2026 and last reviewed on August 18, 2026 through an internal review of the current application, automated browser checks, responsive inspection, and review of known generated-report limitations. It will be reviewed after substantial interface changes, after broader assistive-technology testing, and at least annually while the service operates.

This is a voluntary product accessibility statement for a US business service. It is not a VPAT, Accessibility Conformance Report, certification, or statement issued under a specific public-sector accessibility regime.