Our commitment

Aliso LLC dba Deviation Check aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across this Site (deviationcheck.com) and the authenticated review Service. WCAG 2.1 Level AA is published by the World Wide Web Consortium (W3C) and is the conformance target most commonly cited in United States federal and state procurement, in Section 508 refresh references, and in commercial accessibility expectations; meeting it does not guarantee that every interaction works for every assistive technology, but it sets a concrete, testable baseline that we hold ourselves to.

This is a continuing commitment, not a one-time audit. Our pages are typographic and form-driven; we have deliberately kept the Site free of decorative imagery, autoplaying media, and motion that would otherwise create barriers. As we add interactive surfaces (the upload flow, the report viewer, account screens), each new surface is held to the same conformance target before it ships.

Measures we take

The list below is what we actually do today, not aspirations.

  • Semantic HyperText Markup Language (HTML). Every page uses real landmarks (header, nav, main, footer), real headings, real lists, real buttons, and real form controls. We do not stand up div-based controls when a native element exists. Screen readers, voice-control tools, and keyboard users all benefit from the same underlying structure.
  • One H1 per page, sensible heading order. Each page has exactly one h1 wired to the page banner. Section headings descend in logical order so that jumping headings in a screen reader gives a coherent outline of the page.
  • Skip link to main content. The first focusable element on every page is a Skip to content link that jumps past the site header and navigation directly to the page's main landmark. The link is visually hidden until focused; when focused it appears with clear contrast.
  • Keyboard navigability. Every interactive element on the Site can be reached and operated with a keyboard alone, in document order. Focus styles are deliberate, high-contrast outlines that meet WCAG 2.1 Success Criterion 2.4.7. The Contact form, the Upload form, and every link in the navigation work without a pointing device.
  • Sufficient contrast. Body text and interactive elements meet or exceed WCAG 2.1 Level AA contrast minimums (4.5:1 for normal text, 3:1 for large text and meaningful non-text content). The Site ships in a single light color scheme with a documented palette; we do not rely on color alone to convey meaning.
  • Form labels, hints, and errors. Every form field has a visible label element programmatically associated with its input. Helper text uses real prose under the field. Validation errors surface in an error summary plus inline per-field messages, both linked to the relevant input via Accessible Rich Internet Applications (ARIA) attributes so that screen readers announce them.
  • Alternative text for non-text content. The Site currently uses no decorative or content imagery on home, contact, security, privacy, terms, or accessibility pages, so there is little non-text content to caption; the logo and a small handful of icon glyphs are marked decorative (aria-hidden="true") where they carry no information, and any image we add in the future will carry meaningful alt text or be explicitly decorative.
  • Respect for user motion preferences. We do not autoplay video, animate full-page transitions, or introduce parallax. The Site honors the operating-system prefers-reduced-motion setting for the small handful of micro-interactions it does ship.
  • Predictable focus and language. The document lang attribute is set to en on every page. Focus order matches reading order. Links describe their destination; we avoid bare "click here" patterns.
  • Plain-language acronym expansion. Construction and infrastructure acronyms are spelled out on first use on each page (for example "Construction Specifications Institute (CSI)," "Project Manager (PM)," "Large Language Model (LLM)"). Spelling acronyms out helps screen-reader users and readers new to the domain.

Known limitations

No known significant issues. If you encounter a barrier on any page of the Site or in the review Service, please tell us via the contact form. We treat accessibility regressions as bugs and fix them on the same triage track as functional regressions.

We monitor for two categories of risk specific to a content-light, form-driven Site like this one.

  • Third-party widgets. The Contact form loads Cloudflare Turnstile for bot protection. Turnstile is operated by a third party; if its embedded widget exhibits an accessibility regression we will surface it here and pursue the vendor for a fix. As of the last reviewed date below we are not aware of an outstanding Turnstile accessibility issue affecting our Contact flow.
  • Generated reports. The deviation reports we generate are returned as HTML, Markdown, and JSON. The HTML report uses the same semantic structure as the Site (real headings, real lists, real tables with th scope), so screen readers can navigate it. If a specific report exhibits a structural barrier, the contact form is the right route and we will treat it as a content bug.

Reporting an issue

The fastest route is the contact form with subject "accessibility". Include the URL of the page (or report), the assistive technology and browser combination you are using, and a short description of what you tried to do and what blocked you. Screenshots or a short screen recording help, but are not required.

Our commitment back:

  • Acknowledgment within 1 business day. We confirm receipt and tell you who is looking at it.
  • Substantive response within 5 business days. We describe what we found, whether it reproduces, and what we plan to do about it.
  • Fix on the same triage track as functional bugs. Accessibility regressions are not parked in a separate queue.

We do not require a formal complaint, a legal demand, or proof of harm to act on an accessibility report. A short note through the form is enough.

How we review

We review this Site against the WCAG 2.1 Level AA criteria at least annually, after significant feature work that touches the user interface, and whenever a reported issue prompts a broader sweep. Reviews combine automated checks (axe-core class tooling for low-hanging structural and contrast issues), keyboard-only walk-throughs of the home, contact, upload, and report-viewer surfaces, and screen-reader smoke tests with at least one screen reader on each of Windows and macOS.

Reviews are conducted by Aliso LLC personnel. The Site is small enough that no third-party accessibility audit firm has been engaged to date; if a customer's procurement process requires a third-party Voluntary Product Accessibility Template (VPAT) or an independent audit, tell us through the form and we will scope it.

This page is a public commitment. We update it as the Site and Service evolve; the date below shows when it was last reviewed.

Last reviewed: May 10, 2026. Review cadence: at least annually plus after material UI changes.