compliascan.com
Summary
Evaluation Methods
Automated testing with axe-core across the full site, supplemented by manual code inspection and interaction review (media inventory, keyboard behavior, timing, pointer input, navigation consistency, and form/checkout flows) performed 2026-08-22.
Conformance Terms
The following terms are used in this report to indicate the conformance level of the product to each listed criterion:
- Supports
- The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports
- Some functionality of the product does not meet the criterion.
- Does Not Support
- The majority of product functionality does not meet the criterion.
- Not Applicable
- The criterion is not relevant to the product.
- Not Evaluated
- The product has not been evaluated against the criterion. CompliaScan uses this conformance level when automated scanning cannot reliably assess a criterion (for example, captions on video, consistency across pages, or subjective focus-order review). Manual review is recommended to determine final conformance. ITI reserves this term for Level AAA criteria; this report also applies it to criteria not yet assessed so that unverified criteria are never reported as supported.
Table A: WCAG 2.2 Level A
| Criteria | Name | Conformance Level | Remarks |
|---|---|---|---|
| 1.1.1 | Non-text content must have text alternatives | Supports | No violations detected by automated testing. |
| 1.2.1 | Provide alternatives for prerecorded audio/video-only media | Not Applicable | Not applicable — the product contains no prerecorded audio-only or video-only media. Verified by manual code inspection and interaction review on 2026-08-22: a full-source search found no <video>, <audio>, or media-platform embeds in the UI, and headless-browser inspection of the homepage, /pricing, /features, /scan, and this report page found 0 audio, video, or media iframe elements. |
| 1.2.2 | Captions for prerecorded audio content in synchronized media | Not Applicable | Not applicable — the product contains no prerecorded synchronized media that would require captions. Verified by manual code inspection and interaction review on 2026-08-22: full-source search and headless-browser inspection of the homepage, /pricing, /features, /scan, and this report page found no video or embedded media players. |
| 1.2.3 | Audio description or media alternative for prerecorded video | Not Applicable | Not applicable — the product contains no prerecorded synchronized media that would require audio description or a media alternative. Verified by manual code inspection and interaction review on 2026-08-22: full-source search and headless-browser inspection of the homepage, /pricing, /features, /scan, and this report page found no video or embedded media players. |
| 1.3.1 | Info and relationships conveyed through presentation are programmatically determinable | Supports | No violations detected by automated testing. |
| 1.3.2 | Content order is meaningful when linearized | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 1.3.3 | Instructions do not rely solely on sensory characteristics | Supports | Verified by manual code inspection and interaction review on 2026-08-22: instructions in the UI reference controls by their visible text labels (e.g. form labels and named buttons), and a content review of the homepage, /pricing, /features, /scan, and this report page found no instructions that rely solely on shape, color, size, visual location, orientation, or sound. |
| 1.4.1 | Color is not used as the only visual means of conveying information | Not Evaluated | Automated rules check only part of this criterion (whether links inside text blocks can be told apart without color), so a passing result is not evidence of conformance. Manual review is required. |
| 1.4.2 | Audio control mechanism is provided for auto-playing audio | Not Applicable | Not applicable — no audio plays on any page, automatically or otherwise. Verified by manual code inspection and interaction review on 2026-08-22: full-source search and headless-browser inspection of the homepage, /pricing, /features, /scan, and this report page found 0 <audio> elements and 0 autoplay attributes. |
| 2.1.1 | All functionality is operable through a keyboard interface | Not Evaluated | Automated rules check only part of this criterion (whether frames and scrollable regions can be reached by keyboard and whether server-side image maps are used), so a passing result is not evidence of conformance. Manual review is required. |
| 2.1.2 | No keyboard trap exists for keyboard-only users | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 2.1.4 | Character key shortcuts can be remapped or disabled | Supports | Verified by manual code inspection and interaction review on 2026-08-22: every keyboard listener in the UI was inspected — the only keys handled are Escape (dismissing dialogs and the mobile menu) and Tab (dialog focus management). No single-character key shortcuts are implemented, and rendered pages contain 0 accesskey attributes. |
| 2.2.1 | Time limits are adjustable, extendable, or removable | Supports | Verified by manual code inspection and interaction review on 2026-08-22: no time limits are set on user activity — no session-expiry countdowns on public pages, no <meta http-equiv="refresh"> (0 on rendered pages), and no auto-advancing content. The only timed UI behaviors are non-essential status confirmations (e.g. a "Copied" button state reverting after 2 seconds) that do not limit any user action. |
| 2.2.2 | Moving, blinking, or scrolling content can be paused, stopped, or hidden | Not Evaluated | Automated rules check only part of this criterion (whether blink or marquee elements are used), so a passing result is not evidence of conformance. Manual review is required. |
| 2.3.1 | Content does not flash more than three times per second | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 2.4.1 | A mechanism is available to bypass repeated blocks of content | Supports | Verified by manual code inspection and interaction review on 2026-08-22: a "Skip to main content" link is rendered by the shared site header on every page and its activation was tested in a real browser — focus and scroll move to the <main id="main"> landmark. Pages also expose main and nav landmarks for assistive-technology navigation. |
| 2.4.2 | Web pages have descriptive titles | Supports | No violations detected by automated testing. |
| 2.4.3 | Focus order preserves meaning and operability | Supports | Verified by manual code inspection and interaction review on 2026-08-22: sequential keyboard navigation was exercised in a real browser and follows the visual layout (cookie-consent dialog, then announcement bar, then skip link, then header navigation, then page content). No positive tabindex values exist in the UI (0 found on rendered pages), and the mobile navigation menu locks background scrolling while open and closes on Escape. |
| 2.4.4 | Link purpose can be determined from the link text or its context | Supports | No violations detected by automated testing. |
| 2.5.1 | All functionality using multipoint gestures can be operated with a single pointer | Supports | Verified by manual code inspection and interaction review on 2026-08-22: the UI implements no multipoint or path-based gestures — a full-source search found no swipe, drag, or touch-path handlers. All functionality is operable with single-pointer activation (clicks/taps on links and buttons). |
| 2.5.2 | Pointer-triggered functions can be cancelled | Supports | Verified by manual code inspection and interaction review on 2026-08-22: interactive controls are native links and buttons activated on the up-event (click). The single down-event listener in the UI dismisses an open detail popup when clicking outside it — a non-destructive dismissal that is immediately reversible by reopening, with equivalent close controls (close button, Escape) also available. |
| 2.5.3 | Visible labels contain the accessible name text | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 2.5.4 | Functionality triggered by motion can be disabled and has UI alternatives | Not Applicable | Not applicable — no functionality is operated by device motion or user motion. Verified by manual code inspection and interaction review on 2026-08-22: a full-source search found no devicemotion or deviceorientation listeners and no motion-triggered features. |
| 3.1.1 | Default human language of each web page can be programmatically determined | Supports | No violations detected by automated testing. |
| 3.2.1 | Receiving focus does not initiate a change of context | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 3.2.2 | Changing a UI component does not automatically change context | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 3.2.6 | Help mechanisms occur in the same relative order across pages | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 3.3.1 | Input errors are automatically detected and described in text | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 3.3.2 | Labels or instructions are provided for user input | Not Evaluated | Automated rules check only part of this criterion (whether a form field has more than one label), so a passing result is not evidence of conformance. Manual review is required. |
| 3.3.7 | Information previously entered is auto-populated or available to select | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 4.1.2 | Name, role, and value are programmatically determinable for all UI components | Supports | No violations detected by automated testing. |
Table B: WCAG 2.2 Level AA
| Criteria | Name | Conformance Level | Remarks |
|---|---|---|---|
| 1.2.4 | Captions for live audio content in synchronized media | Not Applicable | Not applicable — the product offers no live audio or live synchronized media (no streams, webinars, or live embeds). Verified by manual code inspection and interaction review on 2026-08-22: full-source search and headless-browser inspection of the homepage, /pricing, /features, /scan, and this report page found no live media elements. |
| 1.2.5 | Audio description for prerecorded video content | Not Applicable | Not applicable — the product contains no prerecorded synchronized media that would require audio description. Verified by manual code inspection and interaction review on 2026-08-22: full-source search and headless-browser inspection of the homepage, /pricing, /features, /scan, and this report page found no video or embedded media players. |
| 1.3.4 | Content does not restrict its view to a single display orientation | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 1.3.5 | Purpose of input fields can be programmatically determined | Not Evaluated | Automated rules check only part of this criterion (whether autocomplete values that are present are valid), so a passing result is not evidence of conformance. Manual review is required. |
| 1.4.3 | Text and images of text have a contrast ratio of at least 4.5:1 | Supports | No violations detected by automated testing. |
| 1.4.4 | Text can be resized up to 200% without loss of content or function | Not Evaluated | Automated rules check only part of this criterion (whether the viewport blocks zooming and whether some text is very small), so a passing result is not evidence of conformance. Manual review is required. |
| 1.4.5 | Images of text are not used when text can achieve the same visual effect | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 1.4.10 | Content reflows without horizontal scrolling at 320px width | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 1.4.11 | Non-text UI components and graphical objects meet 3:1 contrast ratio | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 1.4.12 | Text spacing can be overridden without loss of content or function | Not Evaluated | Automated rules check only part of this criterion (whether inline style attributes lock letter, word or line spacing with !important), so a passing result is not evidence of conformance. Manual review is required. |
| 1.4.13 | Content triggered by hover or focus is dismissible, hoverable, and persistent | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 2.4.5 | More than one way is available to locate a web page in a set | Supports | Verified by manual code inspection and interaction review on 2026-08-22: pages are reachable through more than one mechanism — a persistent header navigation menu and a footer site directory (29 links) are rendered on every page, and index pages (/tools, /guides, /blog) link to their content sets. |
| 2.4.6 | Headings and labels describe topic or purpose | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 2.4.7 | Keyboard focus indicator is visible | Not Evaluated | Automated rules check only part of this criterion (whether a sample of interactive elements changes style when focused), so a passing result is not evidence of conformance. Manual review is required. |
| 2.4.11 | Focus is not entirely hidden by author-created content | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 2.5.7 | Functionality requiring dragging can be achieved with a single pointer | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 2.5.8 | Targets meet a minimum size of 24x24 CSS pixels | Supports | No violations detected by automated testing. |
| 3.1.2 | Language of each passage or phrase can be programmatically determined | Not Evaluated | Automated rules check only part of this criterion (whether lang attributes that are present have valid values), so a passing result is not evidence of conformance. Manual review is required. |
| 3.2.3 | Navigation mechanisms repeated on multiple pages appear in the same relative order | Supports | Verified by manual code inspection and interaction review on 2026-08-22: a single shared Header and Footer component is rendered by the root layout on every page, and headless-browser inspection of the homepage, /pricing, /features, /scan, and this report page confirmed the navigation links appear in identical order on each. |
| 3.2.4 | Components with the same functionality are identified consistently across pages | Supports | Verified by manual code inspection and interaction review on 2026-08-22: components with the same function are the same shared React components across all pages (header navigation, footer directory, theme toggle, sign-in control, scan form), so their identification — labels and icons — is consistent site-wide; confirmed across 5 rendered pages. |
| 3.3.3 | Suggested corrections are provided when input errors are detected | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 3.3.4 | Submissions with legal or financial consequences are reversible or confirmable | Supports | Verified by manual code inspection and interaction review on 2026-08-22: the only financial transactions are subscription purchases completed via Stripe-hosted Checkout, which presents the full order for review and correction before submission, and subscriptions are reversible (cancellable) through the Stripe billing portal. Destructive data actions (deleting a site and its scan history, cancelling a running scan) each require an explicit confirmation dialog before executing. |
| 3.3.8 | Accessible authentication does not require cognitive function tests | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
| 4.1.3 | Status messages can be programmatically determined without receiving focus | Not Evaluated | No automated rule in this scan tests this criterion, so manual review is recommended. |
Revised Section 508 Report
Conformance for Chapter 3 (Functional Performance Criteria) and Chapter 5 (Software) derives from the WCAG success criteria tables above — the Revised 508 Standards (36 CFR Part 1194, Appendices A and C) incorporate WCAG Level A and AA by reference for web content and software. Chapter 4 (Hardware) is not applicable to this web-only product. Chapter 6 (Support Documentation and Services) is addressed by the product's published documentation and support channels.
EN 301 549 Report
Clause 9 (Web): see the WCAG conformance tables above. Clauses 11 (Software) and 12 (Documentation and Support Services) are addressed through the product's web-delivered interface and published support documentation. Hardware- and telephony-related clauses (5-8, 13) are not applicable to this web-only product.
Legal Disclaimer
This VPAT (Voluntary Product Accessibility Template) is provided for informational purposes and reflects the conformance status at the time of evaluation. Conformance levels are based on automated testing with axe-core and may not cover all accessibility requirements. Manual testing by qualified accessibility experts is recommended for a comprehensive assessment. This document follows the VPAT 2.5 format published by the Information Technology Industry Council (ITI). “Voluntary Product Accessibility Template” and “VPAT” are registered service marks of ITI.