Accessibility Statement

ArrayHash designs ArraySubs marketing and trust pages to be usable with keyboard navigation, visible focus, readable contrast, semantic structure, reduced-motion preferences and optional accessibility tools.

WCAG 2.2 AA target
Accessibility tools widget
Keyboard shortcut Alt+A

Report an accessibility issue

Standard: WCAG 2.2 AA target
Tools: 9 profiles and 26 controls
Effective date: April 10, 2026
Last reviewed: June 25, 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 site also provides an optional accessibility tools widget that lets visitors adjust presentation and reading aids for their own session. The target standard is WCAG 2.2 Level AA.

The widget is an accommodation aid, not a replacement for accessible source markup, keyboard support, assistive-technology testing or issue remediation. ArrayHash does not claim that the toolbar alone makes the website conformant.

Implemented practices

Keyboard

Header links, mobile menu, buttons, forms, accordions, tabs, custom controls and the accessibility tools panel 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 tools available

The floating Accessibility Tools button is available across the site and can also be opened with Alt+A.

The toolbar stores visitor preferences in local storage when persistence is enabled, respects reduced-motion preferences on a fresh visit and exposes all available profiles and tools. It can be reset at any time from the panel.

Accessibility tools available
Group	Available controls
Profiles	Seizure Safe, Vision Impaired, Light Sensitivity, Color Blind, Dyslexia, ADHD Friendly, Cognitive Disability, Keyboard/Motor, and Blind/Screen Reader.
Content	Legible fonts, highlight titles, font size, text magnifier, highlight links, line height, letter spacing, text alignment, dictionary, and simplify selected text.
Color	Dark contrast, light contrast, high contrast, monochrome, invert colors, and color-blind filtering.
Visibility	Reading lens, big cursor, reading mask, reading guide, read aloud, virtual keyboard, focus highlight, page structure navigator, hide images, and reduce animations.

Accessibility checklist

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.
Tools	The accessibility toolbar is keyboard operable, persistent, resettable and available on every page.

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.
The accessibility tools improve presentation and reading comfort, but they do not repair every possible content or third-party interface barrier.
If an issue is found, ArrayHash prioritizes fixes based on severity, affected workflow and available workaround.

Third-party flows

Payment and licensing providers 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.

Report accessibility issue

More trust resources

Related policies

Each page covers one part of how ArrayHash handles privacy, payments, licenses, refunds, and accessibility.

Contact

Need accessibility help?

Email ArrayHash. We route rights requests, refund questions, and accessibility reports to the right place.

Email ArrayHashContact page