Accessibility Statement

Last updated: June 5, 2026

Restock is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards.

What we've done

Our platform was built with the following accessibility features from the start:

• Semantic HTML — pages use proper heading hierarchies, landmarks (header/nav/main/footer), and ARIA roles only when native HTML can't carry the meaning.
• Keyboard navigation — every interactive element is reachable and operable from the keyboard. Skip-to-content links are available on every page.
• Focus indicators — visible focus outlines on every focusable element (2px brand color), never removed without replacement.
• Modal dialogs trap focus, can be dismissed with Escape, and return focus to the trigger element on close.
• Screen reader support — meaningful alt text on images, descriptive labels on icon-only buttons, ARIA labels on charts and maps, screen-reader-only lists alongside visual data.
• Color contrast — text meets 4.5:1 contrast against background; large text and UI components meet 3:1. We don't use color alone to convey information.
• Forms — every input has an associated label, required fields are marked, validation errors are announced and tied to the field.
• Touch targets — interactive elements meet a 44×44 px minimum on coarse-pointer devices, 32 px on precision pointers.
• Reduced motion — animations honor prefers-reduced-motion at the OS level. Set "Reduce motion" in your OS settings and we'll respect it.
• Responsive layouts — content reflows at 320 px width without horizontal scrolling, supports zoom up to 200% without loss of content.

Specific patterns to know

Route map

Our AI-optimized route map is presented visually, but every plotted stop is also exposed in a screen-reader-only ordered list below the visual. Screen reader users get the full route as text in optimized order.

Contracts & Invoices

Contract documents and generated invoices render as semantic HTML (not images) so they're readable by every assistive technology. Print/Save PDF opens a clean window that retains the same semantics.

Data tables

Tables use <th scope="col"> headers and the surrounding context (caption or aria-label) explains what's tabulated.

Tab interfaces

Tabbed views (e.g. contract preview vs metrics) follow the ARIA Authoring Practices Guide tab pattern: arrow keys cycle tabs, Home/End jump to first/last, and the active tab is announced as "selected."

What still needs work

We're being upfront — these areas are on our roadmap:

• Some legacy chart visualizations (territory map, heat map) need richer text alternatives.
• A small number of older settings pages predate our current modal focus-trap standard.
• Onboarding wizard transitions could be smoother for screen reader users.

If you depend on assistive technology and run into a barrier, please tell us — we will prioritize the fix.

Compatibility

Restock is designed to be compatible with:

• The latest two major versions of Chrome, Firefox, Safari, and Edge on desktop and mobile
• NVDA and JAWS on Windows; VoiceOver on macOS and iOS; TalkBack on Android
• Voice Control on macOS and iOS; Dragon NaturallySpeaking on Windows
• Switch Control and similar single-switch input methods

Technical specifications

Accessibility relies on the following technologies working with your browser and any assistive technologies you use:

• HTML5
• WAI-ARIA 1.2 (when native HTML semantics aren't sufficient)
• CSS3 (used for layout and visual styling only — content is in the HTML)
• JavaScript (used progressively — core navigation and content work without it)

Standards we reference

• Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — W3C standard
• Americans with Disabilities Act (ADA) Title III — places of public accommodation
• Section 508 of the Rehabilitation Act — federal procurement
• EN 301 549 / European Accessibility Act (EAA) — EU equivalent

Assessment approach

We assess our platform against WCAG 2.1 AA through:

• Self-evaluation using axe DevTools, Lighthouse Accessibility, and manual keyboard / screen reader testing
• Code review of every shipped change for accessibility regressions
• Annual third-party audits (planned starting Q4 2026)

Formal complaints

If our response doesn't address your concern, you may file a formal complaint with the U.S. Department of Justice (ADA) or with the accessibility regulator in your country. In the US, complaints may be filed at ada.gov/file-a-complaint.