Accessibility Compliance
ArrayHash designs ArraySubs marketing and trust pages to be usable with keyboard navigation, visible focus, readable contrast, semantic structure and reduced-motion preferences.
- WCAG 2.2 AA target
- Keyboard and focus-visible controls
- Reduced-motion support
- Standard
- WCAG 2.2 AA target
- Applies to
- ArrayHash website
- Effective date
- April 10, 2026
- Last reviewed
- June 2, 2026
Accessibility commitment
ArrayHash aims to make ArraySubs web pages usable by as many people as possible.
The ArrayHash website is built with semantic landmarks, one main content region, clear headings, visible focus indicators, keyboard-operated navigation and controls, readable contrast and reduced-motion support. The target standard is WCAG 2.2 Level AA.
Implemented practices
Keyboard
Header links, mobile menu, buttons, forms, accordions, tabs and custom controls are designed for keyboard operation.
Focus
Focus-visible styles are intentionally visible and must not be removed from interactive elements.
Structure
Pages use semantic landmarks, ordered headings, labelled navigation, meaningful link text and accessible tables.
Accessibility checklist
| Area | Commitment |
|---|---|
| Landmarks | Pages use header, main, footer and labelled navigation landmarks. |
| Headings | Each page has one h1 and follows an ordered heading structure. |
| Keyboard | Navigation and controls are operable without a mouse. |
| Focus | Interactive elements expose visible focus states. |
| Color | Text and controls are designed for readable contrast across site surfaces. |
| Motion | Motion respects reduced-motion preferences. |
| Forms | Fields use labels, descriptions and announced error states where applicable. |
| Tables | Policy tables use captions, column headers and semantic table markup. |
Known limitations and ongoing work
ArrayHash actively reviews accessibility as pages, forms and components change. If a third-party checkout, licensing or embedded provider interface is used, that provider's accessibility behavior may affect the final experience inside that flow.
- We test pages at desktop and mobile widths when shipping new route or layout changes.
- We avoid hidden focus, unlabeled controls, inaccessible custom widgets and motion that blocks content.
- If an issue is found, ArrayHash prioritizes fixes based on severity, affected workflow and available workaround.
Third-party flows
Stripe and Freemius may provide checkout, payment, licensing or account screens. ArrayHash selects established providers and links to their own policies where relevant, but those third-party interfaces are controlled by the provider.
Report an accessibility barrier
If you have trouble using any ArrayHash or ArraySubs page, email [email protected]. Include the page URL, browser, device, assistive technology if relevant, and what blocked you. Do not include passwords, full card details or private customer exports.
Email accessibility issueRelated policies
Each page covers one part of how ArrayHash handles privacy, payments, licenses, refunds, and accessibility.
Privacy Policy
What the ArrayHash website collects, why it is used, and how to exercise privacy rights.
Read policyData Safety
How website data, payment data, and merchant WordPress data are separated.
Read policyRefund Policy
The 60-day ArraySubs Pro refund guarantee and how refund requests are handled.
Read policyNeed accessibility help?
Email ArrayHash. We route rights requests, refund questions, and accessibility reports to the right place.