Accessibility Statement

1. Our commitment

We are committed to providing a website that is accessible to the widest possible audience, regardless of technology or ability, consistent with the accessibility expectations of the Americans with Disabilities Act (ADA). We treat accessibility as part of engineering quality, not an afterthought: accessibility checks run automatically on every change to this site, and changes that introduce serious or critical accessibility issues are blocked from shipping.

2. Conformance status — WCAG 2.2 Level AA

This website is assessed against the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. On 21 July 2026 the site passed a formal automated accessibility acceptance audit: axe-core scans covering the WCAG 2.0, 2.1, and 2.2 Level A and Level AA rule sets found zero serious or critical violations on all 12 pages of this website, on both desktop and 320 px mobile viewports. The same checks now run as acceptance gates in our continuous-integration pipeline, so every subsequent change to the site is re-verified against the same bar before it ships.

Automated testing cannot evaluate every WCAG success criterion — some criteria can only be judged by a human using assistive technology. Until the manual evaluation described in section 4 has been completed, we therefore describe this website as partially conformant with WCAG 2.2 Level AA: the parts that have been evaluated conform, and some aspects have not yet been fully evaluated. We do not claim full conformance before that manual audit is done, and we will update this statement with its actual findings.

3. How this site was tested and what we do

The 2026-07-21 audit was performed with the axe-core accessibility engine driven by automated browser tests against every page of this site. The audit and the permanent CI gate cover:

• Automated axe-core scans of all 12 pages against the WCAG 2.0, 2.1, and 2.2 Level A and AA rule sets, on desktop (1280 px) and mobile (320 px) viewports, with zero serious or critical violations required to pass.
• Target size (WCAG 2.5.8): interactive controls are explicitly checked for the minimum 24×24 px target size, including at the 320 px mobile viewport.
• Keyboard access: a "skip to main content" link is the first tab stop on every page and shows a visible focus indicator when reached by keyboard (WCAG 2.4.1 Bypass Blocks, 2.4.7 Focus Visible).
• Motion preferences: when the operating system asks for reduced motion (prefers-reduced-motion), decorative animation on the site is stopped (WCAG 2.3.3 Animation from Interactions).
• Forms and status messages: the contact and demo-request forms are additionally scanned in their live error state, and form errors and page navigations are announced to assistive technology (WCAG 4.1.3 Status Messages).
• Reflow: pages are checked for the absence of horizontal scrolling at a 320 px viewport width (WCAG 1.4.10 Reflow).
• The site is built with semantic HTML — landmarks, headings, labeled regions, and descriptive link text — and tables and scrollable regions carry the appropriate roles and labels.

4. Known limitations

We disclose the boundaries of our testing honestly:

• The 2026-07-21 audit was automated and script-driven. A manual audit with screen readers and other assistive technologies (for example NVDA, JAWS, VoiceOver, or TalkBack operated by a human), together with human keyboard testing, has not yet been performed; it is planned for completion by 30 September 2026, after which sections 2 and 4 will be updated with its actual findings. Issues that only human assistive-technology testing can reveal may therefore still exist.
• Automated tooling evaluates only a subset of the WCAG success criteria. Findings that axe-core classifies as moderate or minor are reported to the team but do not block releases; the blocking bar is zero serious or critical violations.
• This statement covers the 12 pages of this marketing website (nextbasket.com). It does not cover the NEXT BASKET platform application or third-party websites and services linked from this site.

5. Feedback — tell us what is not working

If you experience any difficulty accessing any part of this website, or need content in an alternative format, please contact us. We take accessibility feedback seriously and will make reasonable efforts to address problems promptly.

Email

accessibility@nextbasket.com — a monitored alias. Until the alias is confirmed live it is routed to office@nextbasket.com, so your message always reaches a monitored inbox; you may also write to office@nextbasket.com directly.

Response time

We aim to acknowledge accessibility feedback within 5 business days and to provide a substantive response or a progress update within 20 business days. Where fixing an issue depends on a third party, we will keep you informed of progress rather than promise a resolution by a fixed date.

6. Enforcement and escalation

Accessibility feedback is handled through the channel in section 5, and we encourage you to contact us first so we can fix the problem at the source. If you have contacted us about an accessibility barrier and are not satisfied with our response, you may be able to escalate your complaint to the competent authority in your jurisdiction.

Because the appropriate body depends on where you are, we do not list a single enforcement authority here as universally applicable. Depending on your location, this may be the competent equality, disability, consumer-protection, or data-protection authority. As we formally launch in specific markets, we will add the relevant jurisdiction-specific references to this section.

7. Assessment and review

Assessment approach

Formal automated acceptance audit: axe-core (WCAG 2.0/2.1/2.2 A+AA) driven by automated browser tests on all 12 pages, desktop + 320px mobile, plus scripted keyboard, reduced-motion, form-error-state, status-message, and reflow checks. The same suites run in CI as blocking acceptance gates on every change.

Last audit

2026-07-21 — automated acceptance audit passed with zero serious or critical violations. Continuously re-verified by CI thereafter.

Next planned step

A manual assistive-technology audit (human keyboard testing and screen readers) is planned for completion by 30 September 2026. Once done, sections 2 and 4 are updated with its actual result; until then this statement describes the site as partially conformant with WCAG 2.2 Level AA.