Accessibility Statement
OpenMat is committed to making our platform accessible to every martial artist, regardless of disability or assistive technology. This statement describes our current conformance, known limitations, and roadmap.
Table of Contents
1 Our Commitment
Proscris LLC is committed to ensuring that OpenMat is accessible to people with disabilities. We believe that everyone who trains martial arts deserves equal access to training tools, community, and coaching — regardless of visual, motor, auditory, or cognitive ability.
Accessibility at OpenMat means:
- Every new feature is designed with accessibility in mind from the first line of code.
- We test with real screen readers and assistive technologies, not just automated tools.
- We respond to accessibility feedback within 5 business days.
- Accessibility improvements ship in every major release cycle.
- We do not charge more or restrict features for users of assistive technology.
This statement was prepared in accordance with the Web Content Accessibility Guidelines (WCAG) 2.2 and is reviewed and updated at least annually, or whenever significant platform changes are made.
2 Conformance Status
OpenMat is partially conformant with WCAG 2.2 Level AA. Partially conformant means that some parts of the content do not yet fully conform to the accessibility standard. We are actively working to address all known gaps.
Based on internal audit of April 2026. Remaining 18% consists of complex interactive components currently in active development.
| WCAG Level | Criteria Count | Passing | In Progress | Planned |
|---|---|---|---|---|
| Level A | 30 criteria | ✓ 28 pass | ⚙ 2 in progress | — |
| Level AA | 20 criteria | ✓ 15 pass | ⚙ 3 in progress | 📋 2 planned |
| Level AAA (voluntary) | 28 criteria | ✓ 8 pass | ⚙ 4 in progress | 📋 16 planned |
3 What We've Built
The following accessibility features are fully implemented and active in the current version of OpenMat:
Skip Navigation Link
A visually hidden skip-to-content link appears on focus on every page, allowing keyboard users to bypass repetitive navigation.
44px Minimum Touch Targets
Every button, link, and interactive control meets the 44×44px minimum touch target size requirement (WCAG 2.5.5).
Focus-Visible Styles
All focusable elements show a 3px solid accent-color outline on keyboard focus. Focus is never suppressed on interactive elements.
ARIA Labels Throughout
Every interactive element has a descriptive aria-label or aria-labelledby. Icon-only buttons always include screen reader text.
Semantic HTML Structure
Proper heading hierarchy (h1 → h2 → h3), landmark roles (header, main, nav, footer), and semantic list elements throughout.
ARIA Live Regions
Toast notifications, loading states, and dynamic content updates use aria-live="polite" or aria-live="assertive" for screen reader announcements.
Form Label Association
Every form input has an explicitly associated label element or aria-label. Required fields are marked with aria-required="true".
Color Contrast — Text
All body text meets minimum 4.5:1 contrast ratio. Large text and UI components meet 3:1. Tested in both light and dark themes.
Keyboard Navigation
Full Tab/Shift+Tab navigation throughout. Escape closes all modals, panels, and overlays. Arrow keys navigate appropriate widgets.
No Auto-Playing Media
No audio or video starts automatically. All timed content can be paused, stopped, or hidden by the user.
Alt Text on Images
All meaningful images have descriptive alt text. Decorative images use aria-hidden="true" or empty alt="" attributes.
Dark Mode — Both Themes
Full accessibility compliance maintained in both light and dark themes. Color contrast checked and passing in both modes.
Modal Focus Management
Focus moves into modals and dialogs when opened, and returns to the trigger element when closed. Focus is trapped within open modals.
Error Identification
Form validation errors are identified in text (not color alone), associated with the relevant input via aria-describedby, and announced to screen readers.
Language Declaration
The page language is declared as lang="en" on the root element. Language changes within the page are marked with appropriate lang attributes.
Responsive & Zoom-Safe
Content reflows correctly at 400% zoom with no horizontal scrolling required. Text resizes up to 200% without loss of content or functionality.
4 WCAG 2.2 Criteria Audit
Selected key criteria and their current status in OpenMat:
| Criterion | Level | Description | Status |
|---|---|---|---|
| 1.1.1 Non-text Content | A | Alt text for all non-decorative images | ✓ Pass |
| 1.3.1 Info and Relationships | A | Semantic HTML, ARIA roles | ✓ Pass |
| 1.3.4 Orientation | AA | Content not restricted to one screen orientation | ✓ Pass |
| 1.3.5 Identify Input Purpose | AA | Autocomplete attributes on form inputs | ✓ Pass |
| 1.4.1 Use of Color | A | Color not the only means of conveying information | ✓ Pass |
| 1.4.3 Contrast (Minimum) | AA | 4.5:1 for text, 3:1 for large text | ✓ Pass |
| 1.4.4 Resize Text | AA | Text resizable to 200% without loss of function | ✓ Pass |
| 1.4.10 Reflow | AA | Content reflows at 320px / 400% zoom | ✓ Pass |
| 1.4.11 Non-text Contrast | AA | 3:1 contrast for UI components and focus indicators | ✓ Pass |
| 1.4.12 Text Spacing | AA | No loss of content with increased text spacing | ✓ Pass |
| 1.4.13 Content on Hover or Focus | AA | Tooltips dismissible and persistent on hover | ⚙ In Progress |
| 2.1.1 Keyboard | A | All functionality operable via keyboard | ✓ Pass |
| 2.1.2 No Keyboard Trap | A | Focus never trapped without an escape mechanism | ✓ Pass |
| 2.4.3 Focus Order | A | Focus order preserves meaning and operability | ✓ Pass |
| 2.4.7 Focus Visible | AA | Keyboard focus indicator always visible | ✓ Pass |
| 2.4.11 Focus Appearance | AA | Focus indicator meets minimum size and contrast (WCAG 2.2 new) | ✓ Pass |
| 2.5.3 Label in Name | A | Visible label text contained in accessible name | ✓ Pass |
| 2.5.7 Dragging Movements | AA | Single pointer alternative for all drag functions (WCAG 2.2 new) | ⚙ In Progress |
| 2.5.8 Target Size (Minimum) | AA | 24×24px minimum; OpenMat uses 44×44px (WCAG 2.2 new) | ✓ Pass |
| 3.1.1 Language of Page | A | Default human language declared | ✓ Pass |
| 3.3.1 Error Identification | A | Input errors identified and described in text | ✓ Pass |
| 3.3.2 Labels or Instructions | A | Labels provided for all user input | ✓ Pass |
| 3.3.7 Redundant Entry | A | Previously entered info auto-populated where possible (WCAG 2.2 new) | ⚙ In Progress |
| 3.3.8 Accessible Authentication | AA | No cognitive function test required for auth (WCAG 2.2 new) | ✓ Pass |
| 4.1.2 Name, Role, Value | A | All UI components have name, role, and state | ✓ Pass |
| 4.1.3 Status Messages | AA | Status messages programmatically determined | ✓ Pass |
5 Assistive Technology Support
OpenMat has been tested with the following assistive technologies:
All navigation, forms, and dynamic content announced correctly.
Swipe navigation and double-tap activation work throughout the app.
Browse mode and forms mode both function correctly.
Virtual cursor navigation and form interaction both work as expected.
Core navigation works. Some complex widgets may need additional testing.
Browser zoom up to 400% and OS-level magnification supported without horizontal scroll.
All functionality accessible via keyboard. Tab order is logical and visible.
Most controls accessible by voice label. Complex interactive lists being improved.
Dark mode and system high contrast modes both render all content legibly.
6 Keyboard Navigation
OpenMat is fully operable by keyboard. Here are the key shortcuts and navigation patterns:
7 Known Limitations
We believe in full transparency. The following known accessibility limitations exist in the current version and are being actively addressed:
| Area | Issue | Impact | Status |
|---|---|---|---|
| Beacon Map View | The visual distance-based partner list has limited keyboard navigability for sorting and filtering interactions | Keyboard and screen reader users may have reduced access to sorting controls | ⚙ Q2 2026 |
| Reduced Motion | Page transition animations and loading animations do not fully respect prefers-reduced-motion media query | Users with vestibular disorders may experience discomfort from motion | ⚙ Q2 2026 |
| Drag-Scroll Horizontal Lists | Some horizontally scrolling carousels use mouse-drag behavior without a keyboard-equivalent for full scroll access | Keyboard users can still Tab through items but cannot scroll the container itself | ⚙ Q2 2026 |
| Timer Fullscreen Mode | The round timer fullscreen overlay does not restore focus to the trigger button on close in all browsers | Keyboard users may need to manually navigate back to their position after closing the timer | 📋 Q3 2026 |
| Community Feed Infinite Scroll | New posts loaded via infinite scroll are not always announced to screen readers | Screen reader users may not be notified when new content loads | ⚙ Q2 2026 |
| Chart & Graph Data | XP progress charts and training analytics visualizations lack full text-alternative data tables | Screen reader users cannot access the data underlying visual charts | 📋 Q3 2026 |
| Complex Data Tables | Some multi-column tables in the academy dashboard lack full row/column header associations | Screen reader users may have difficulty understanding table structure | 📋 Q3 2026 |
8 Accessibility Roadmap
Our planned accessibility improvements by quarter:
9 Technical Specification
OpenMat is built with the following technologies that support accessibility:
| Technology | Accessibility Role |
|---|---|
| HTML5 Semantic Elements | header, main, nav, footer, article, section, aside — proper landmark roles for screen reader navigation |
| WAI-ARIA 1.2 | Roles, states, and properties throughout. aria-label, aria-labelledby, aria-describedby, aria-live, aria-hidden, aria-expanded, aria-controls, aria-selected |
| CSS Custom Properties (rem units) | All sizing uses rem units. Respects browser default font size changes. No px-based font sizes that override user preferences |
| CSS :focus-visible | Focus styles shown for keyboard users, suppressed for mouse/touch users — best of both worlds without hiding focus from those who need it |
| Progressive Web App (PWA) | Service Worker enables offline use. Users with unreliable connectivity or data limitations can still access training tools fully offline |
| Responsive Design | Single codebase adapts from 320px to 4K. No separate "accessible version" — the same accessible experience for all users on all devices |
| Font Awesome 6.5 | All icons use aria-hidden="true" or have text alternatives. Never rely on icon alone to convey meaning |
| Manrope Variable Font | Wide weight range in a single font file. Designed for readability at all sizes. Supports dyslexia-friendly letter spacing via user preferences |
10 Testing Methodology
Our accessibility testing approach combines automated scanning, manual testing, and user testing:
- Automated: axe-core accessibility engine integrated into our development workflow. All pull requests run automated accessibility checks before merge.
- Manual Keyboard Testing: Every page tested with keyboard-only navigation before release. Tab order, focus visibility, and Escape behavior verified.
- Screen Reader Testing: VoiceOver (iOS and macOS) and NVDA (Windows + Firefox) tested on every major release. TalkBack tested quarterly.
- Color Contrast: All color combinations verified using the WebAIM Contrast Checker against WCAG 2.1 4.5:1 (AA) and 3:1 (large text/UI) ratios.
- Zoom Testing: All pages tested at 100%, 200%, and 400% browser zoom.
- Reduced Motion: Pages tested with prefers-reduced-motion: reduce enabled in OS settings.
- User Feedback: We incorporate feedback from users with disabilities and treat all accessibility bug reports as P1 priority issues.
11 Feedback & Contact
We actively welcome accessibility feedback. If you encounter any barrier while using OpenMat, please tell us — we treat all accessibility reports as high-priority issues.
| Accessibility Team Email | accessibility@openmat.ai |
| Subject Line | "Accessibility Feedback — [brief description]" |
| Response Time | Within 5 business days for all reports |
| Fix Commitment | Critical barriers: fixed within 1 release cycle (typically 2–4 weeks). Non-critical: scheduled in next quarterly roadmap. |
| Alternative Formats | Any content available in alternative format on request within 2 business days |
| General Support | support@openmat.ai |
When reporting an accessibility issue, it helps to include:
- The page or feature where the issue occurs.
- The assistive technology and browser you are using.
- A description of what you expected to happen and what actually happened.
- Screenshots or screen recordings if possible.
12 Formal Complaints
If you are not satisfied with our response to an accessibility concern, you have the right to escalate to an enforcement body. Here are the relevant authorities by region:
| Region | Authority | Relevant Law |
|---|---|---|
| United States | US Department of Justice Civil Rights Division ada.gov |
Americans with Disabilities Act (ADA), Section 508 |
| European Union | Your national supervisory authority for digital accessibility | EU Web Accessibility Directive (WAD) 2016/2102 |
| United Kingdom | Equality and Human Rights Commission (EHRC) equalityhumanrights.com |
Equality Act 2010, Public Sector Bodies Accessibility Regulations 2018 |
| Canada | Canadian Human Rights Commission chrc-ccdp.gc.ca |
Accessible Canada Act (ACA) |
| Australia | Australian Human Rights Commission humanrights.gov.au |
Disability Discrimination Act 1992 |
We encourage you to contact us first at accessibility@openmat.ai — we want the opportunity to resolve accessibility issues directly and quickly.
This Accessibility Statement was prepared on April 1, 2026 and is reviewed at least annually. It applies to content published at openmat.ai and the OpenMat Progressive Web App. For questions, contact accessibility@openmat.ai.
Found an accessibility barrier?
Tell us what's not working — we'll fix it fast. Every accessibility report is treated as a high-priority issue.