Accessibility Statement for capti.io
Last updated
March 2, 2026
WCAG Version
WCAG 2.1 AWCAG 2.1 AAWCAG 2.1 AAAWCAG 2.2 AWCAG 2.2 AAAdditional Best Practices (recommended)
Compliance Status
Partially Compliant
Coverage
100% of Applicable WCAG Success Criteria Evaluated (Automated and Manual)
Evaluation includes automated testing and user-validated checks. Automated results reflect static page testing performed by AccessibilityChecker, while interactive and manual criteria require user testing and confirmation.
Our Commitment
Capti, Inc. is committed to ensuring digital accessibility for people with disabilities. We aim to continually improve the user experience for everyone and apply the relevant accessibility standards in our design and development processes.
Standards Applied
We aim to conform to:
-
WCAG 2.2 Level AA
-
EN 301 549 v3.2.1 (European standard)
-
Section 508 of the Rehabilitation Act (United States)
-
Title II and III of the Americans with Disabilities Act (ADA)
Scope of This Statement
This statement applies to all digital content, services, and files served under the domain:
This includes all webpages, subpages, web applications, downloadable documents, and other content hosted at or under this domain.
As of the last scan on 13 Apr 2026, a total of 17 unique pages are being continuously monitored by the AccessibilityChecker.org testing platform. This number is automatically updated with each new scan as new URLs are discovered or removed.
Testing & Evaluation
Last scan date
March 2, 2026
Automated test scope
AccessibilityChecker.org covers approximately 58% of WCAG 2.2 AA criteria through automation. The remaining items require human judgment and are addressed through the manual testing module.
Manual modules completion
In Progress
17 out of 22 modules completed
Accessibility is evaluated through a combination of automated and manual processes provided by the AccessibilityChecker.org testing platform:
- Weekly automated scans identify all critical, machine-detectable issues across pages using WCAG logic
- A defined set of 22 manual checks is conducted internally by our team based on guided instructions from the platform
- Ongoing issue tracking automatically detects regressions and recognizes resolved items between scans
Together, these two layers of testing — automated + manual — are designed to fully cover all WCAG 2.2 Level AA success criteria.
Known Issues (as of last scan on 13 Apr 2026)
These issues are being addressed and are prioritized for the next sprint.
| WCAG Criterion | Issue Description | Source |
|---|---|---|
| 1.1.1 Non-text Content (A), 1.4.5 Images of Text (AA), 1.3.3 Sensory Characteristics (A) | Image Text Alternatives and Avoiding Images of Text | Manual |
| 2.1.1 Keyboard (A), 2.4.7 Focus Visible (AA), 2.4.11 Focus Not Obscured (Minimum) (AA), 2.1.2 No Keyboard Trap (A), 2.4.3 Focus Order (A), 1.4.11 Non-text Contrast (AA), 2.4.13 Focus Appearance (AAA), 2.4.12 Focus Not Obscured (Enhanced) (AAA) | Keyboard Focus Management, Order, and Visibility | Manual |
| 2.1.1 Keyboard (A), 2.4.7 Focus Visible (AA), 1.4.13 Content on Hover or Focus (AA), 3.2.3 Consistent Navigation (AA), 2.4.1 Bypass Blocks (A), 2.1.3 Keyboard (No Exception) (AAA) | Keyboard Navigation and Full Access | Manual |
| 2.1.1 Keyboard (A), "4.1.2 Name, Role, Value (A)", 1.3.1 Info and Relationships (A), 2.4.11 Focus Not Obscured (Minimum) (AA), 3.2.1 On Focus (A) | Navigation Menu Focus Management & Interactive Element Clarity | Manual |
| 3.1.1 Language of Page (A), 3.1.2 Language of Parts (AA) | Page Language and Language of Parts | Manual |
Resolved Since Last Scan (as of last scan on 13 Apr 2026)
These issues are being addressed and are prioritized for the next sprint.
| WCAG Criterion | Issue Description | Pages Affected |
|---|---|---|
| Best Practice | Ensures interactive controls are not nested as they are not always announced by screen readers or can cause focus problems for assistive technologies | 15 |
| Best Practice | Ensures all page content is contained by landmarks | 3 |
| Best Practice | Ensures the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds | 2 |
| Best Practice | Ensures the order of headings is semantically correct | 7 |
| Best Practice | Ensure ARIA Roles Are Correctly Applied | 3 |
| Best Practice | Ensure that the page, or at least one of its frames contains a level-one heading | 1 |
Accessible Alternatives
If you are experiencing difficulty with any part of the website, you may request accessible formats or alternative access through the contact details below.
Feedback & Contact
We welcome your feedback on the accessibility of capti.io
Technical Compatibility
Our website undergoes comprehensive accessibility evaluations to ensure compatibility across various devices and assistive technologies:
-
Automated Testing:
Conducted weekly using the AccessibilityChecker.org testing platform, covering both mobile and desktop interfaces to identify machine-detectable issues. -
Manual Testing:
A set of 17 essential manual tests is performed to assess aspects that require human judgment, using popular browsers (Chrome, Firefox, Safari) on both desktop and mobile devices. -
Interactive Element Testing (User-Performed):
Interactive components (such as forms, menus, dialogs, and dynamic content) are evaluated through user testing using the AccessibilityChecker browser extension. -
Assistive Technology Compatibility:
Tested with major screen readers (e.g., NVDA, JAWS, VoiceOver) and across popular browsers (Chrome, Firefox, Safari) on both desktop and mobile devices.
Related Policies
Disclaimer:
AccessibilityChecker provides automated testing results and supports manual and interactive testing; however, completion of all manual and interactive tests remains the sole responsibility of the customer. The customer is also fully responsible for implementing any recommended corrections or remediation actions.
This tool is not all inclusive, and does not constitute legal advice, a legal guarantee, or certification of compliance with any accessibility laws, regulations, or standards. Accessibility requirements may change over time, and compliance depends on ongoing maintenance and review. The customer is solely responsible for ensuring the contemplated domain is reviewed periodically and remains compliant with applicable accessibility requirements.