Skip to content

    Accessibility Statement

    We want this site to work for everyone who needs what we do, including people using screen readers, keyboard-only navigation, magnification, or speech input.

    Last reviewed August 3, 2026

    Conformance target

    We target WCAG 2.1 Level AA. We describe the site as partially conformant, which means it meets the standard in the areas we have tested and we know of specific gaps, listed below. We use that wording deliberately rather than claiming full conformance we have not established.

    Accessibility is checked automatically on every change, not audited once and forgotten. Our build pipeline runs the axe-core rule set against one page per template, at both desktop and mobile widths, and refuses to ship a change that introduces a serious or critical violation. Keyboard behavior that automated tools cannot judge, such as whether a modal dialog actually traps focus, is asserted separately in a real browser.

    What works today

    • Every page template is scanned for accessibility violations before it can ship, at desktop and mobile widths, with reduced motion applied. Nothing that axe-core classes as a serious or critical failure of WCAG 2.1 A or AA is present.
    • A skip link is the first focus stop on every page, and following it moves focus to the main content region rather than only scrolling to it.
    • Dialogs that declare themselves modal move focus into the dialog, keep Tab and Shift+Tab inside it, close on Escape, and return focus to the control that opened them.
    • Body text on the shipped dark theme clears the AA contrast minimum of 4.5:1: secondary text measures 7.46:1 on the page background and 7.0:1 on cards, and primary accent text measures 8.99:1.
    • Links inside blocks of text are underlined, so they do not rely on color alone to be recognisable as links.
    • Every focusable control has a visible focus indicator.
    • Form controls have programmatically associated labels, so a screen reader announces the same name that is shown on screen.
    • Images that convey meaning have text alternatives; decorative images are hidden from assistive technology rather than given filler text.
    • Animation and scroll effects respect the operating system's reduce-motion setting, and the reduced-motion rendering is the one the automated scan checks.
    • Content reflows to a single column at 320 CSS pixels wide without horizontal scrolling, and remains usable at 200% zoom.

    Known limitations

    These are the gaps we are aware of. We would rather name them than let you discover them.

    Automated coverage is per template, not per page

    The site generates 195 distinct paths across 16 languages. The automated scan covers one representative page for each page template rather than all of them, on the basis that pages sharing a template share the code that would produce a violation. A defect confined to one page's content could go undetected.

    Automated testing does not equal conformance

    Automated rules catch a meaningful share of accessibility failures but not all of them. Judgments a tool cannot make (whether alternative text is actually useful, whether a heading structure matches the content's meaning, whether an error message tells you how to fix the problem) have been reviewed by hand, not measured. We have not commissioned an independent audit or user testing with assistive technology users.

    Translated content has not been reviewed by native speakers

    Fifteen non-English translations are machine-assisted. Reading order, abbreviation expansion, and screen-reader pronunciation have not been verified by a native speaker in each language. This statement, and our privacy, terms, and cookie policies, are published in English only.

    The framework overlap matrix is dense

    The interactive matrix on the framework mapping page presents a large data grid. It is keyboard operable and each cell carries a text label, but navigating it with a screen reader is slower than reading the same information as a list. If that is a barrier for you, contact us and we will send the mapping in a format that works for you.

    Third-party embeds

    Where a page loads content from another service, we do not control that service's accessibility.

    Tell us about a barrier

    If something on this site blocks you, we want to hear about it, and we will tell you what we can do and by when. Include the page address and what you were trying to do; if you can, mention the assistive technology and browser you were using, because it helps us reproduce the problem.

    We aim to acknowledge within two business days. If the fix will take longer than that, we will give you the information another way in the meantime.

    How this statement is maintained

    This statement is reviewed whenever a new page template ships or the automated gate changes. It describes the site as built, not as we hope to build it. Top Floor Security, LLC is responsible for its content.