Accessibility Statement
Last updated: February 11, 2026
Particular Ltd. is committed to making RegSecure® accessible to all users, including people with disabilities. We are working to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, the Americans with Disabilities Act (ADA), and the European Accessibility Act (EAA) / EN 301 549.
1. Accessibility Standard
We aim to meet WCAG 2.1 Level AA, which satisfies the requirements of both the ADA (United States) and the European Accessibility Act (EAA) / EN 301 549 (European Union).
2. Current Accessibility Features
| Feature | Status | Details |
|---|---|---|
| Semantic HTML | Supported | Proper heading hierarchy, landmarks, and HTML5 semantic elements throughout. |
| Keyboard navigation | Supported | All interactive elements (buttons, inputs, modals) are accessible via keyboard. |
| Color contrast | Supported | Text and interactive elements meet WCAG AA contrast ratios (4.5:1 for normal text, 3:1 for large text). |
| Focus indicators | Supported | Visible focus rings on all interactive elements. |
| Responsive design | Supported | The application adapts to different screen sizes and zoom levels up to 200%. |
| Text alternatives | Supported | Images and icons include alt text or aria-labels. |
| Form labels | Supported | All form inputs have associated labels. |
| Screen reader compatibility | Supported | ARIA labels, roles, and live regions throughout. Session events (connection, recording, screen share) are announced via aria-live regions. All modals have proper dialog roles and focus trapping. |
| Focus management | Supported | Focus is trapped within modal dialogs and restored on close. Skip navigation link provided. Escape key closes all modals. |
| Reduced motion | Supported | Respects the prefers-reduced-motion system setting. All animations and transitions are disabled when this preference is set. |
| Skip navigation | Supported | Skip-to-content links on all pages allow keyboard users to bypass navigation. |
| High contrast mode | Supported | Supports Windows High Contrast Mode and forced-colors media query. |
3. Technical Implementation
The following accessibility features have been implemented across the RegSecure application and website:
- 26+ ARIA labels throughout the application for screen reader compatibility
- ARIA live regions for dynamic announcements (connection status, recording state, screen sharing)
- Focus trapping in all modal dialogs with Escape key to close
- Semantic HTML5 elements (main, header, nav, footer, section) with appropriate roles
- Proper heading hierarchy (h1 → h2 → h3) on all pages
- Form input labels with explicit for/id associations or aria-label attributes
- Table accessibility with scope attributes on headers and proper table structure
- Decorative SVG icons marked with aria-hidden="true"
- Focus-visible indicators using the :focus-visible pseudo-class for keyboard-only focus styles
- Video participant labels positioned above video frames to avoid obscuring content
4. Known Limitations
While we strive for full accessibility, the following limitations currently exist:
- Video session interface: While the video calling interface includes full ARIA labeling, screen reader announcements for key events, and keyboard controls, the real-time nature of video communication presents inherent challenges for non-visual use.
- Document signing: The PDF viewer and signature canvas may have limited accessibility for users who rely solely on keyboard or screen readers. We are exploring alternative signing methods.
- Live captions: Video sessions do not currently include automatic captioning. Browser-based speech recognition (Web Speech API) is being evaluated, but is not yet supported across all browsers.
5. Assistive Technologies
RegSecure has been tested with the following assistive technologies:
- VoiceOver (macOS/iOS)
- NVDA (Windows)
- Browser zoom (up to 200%)
- Keyboard-only navigation
6. Feedback and Contact
We welcome feedback on the accessibility of RegSecure. If you encounter any accessibility barriers or have suggestions for improvement, please contact us:
Email: contact@regsecure.com
We aim to respond to accessibility feedback within 5 business days and to resolve reported issues as soon as possible.
7. Enforcement and Complaints
If you are not satisfied with our response to your accessibility concern, you may file a complaint with the relevant authority in your jurisdiction, such as the U.S. Department of Justice (ADA complaints) or your national enforcement body under the European Accessibility Act.
8. Ongoing Efforts
We are committed to continuously improving the accessibility of RegSecure. Our ongoing efforts include:
- Regular accessibility audits of new features
- Incorporating accessibility into our development process
- Incorporating accessibility testing into our QA process
- Monitoring WCAG updates and adapting accordingly