| Aqnova

Overview

AqNova Marketplace | Arivon Holding Corporation

STATEMENT

R RIGHTS-BASED APPROACH	E EVERYWHERE WCAG 2.1 AA	A ACCOUNTABLE IMPROVEMENT	C COMPATIBLE ASSISTIVE TECH	H HELP & REPORTING

Document: Vendor Accessibility Statement Version: 1.0 Effective Date: June 2026	Technical Standard: WCAG 2.1 Level AA (primary) EU Standard: EN 301 549 (aligned) Audit Cycle: Quarterly	Accessibility Contact: accessibility@aqnovamarketplace.com Response Commitment: 5 business days Priority: P3 — Legally Required

This Vendor Accessibility Statement covers the AqNova Marketplace Vendor Portal (vendor.aqnovamarketplace.com) and all vendor-facing digital tools and communications. A separate Consumer Accessibility Statement covers the buyer-facing AqNova Marketplace (aqnovamarketplace.com). Both statements are aligned to the same WCAG 2.1 AA baseline and global compliance framework.

AqNova Marketplace | Arivon Holding Corporation | EIN: 41-3210066 | Huntington Park, California, USA

Table of Contents

SECTION 1 — Foundation — The REACH Framework & AqNova's Accessibility Commitment ................. 3

REACH 5 Principles · Scope (7 coverage items) · WCAG 2.1 AA Partial Conformance Status

EN 301 549 alignment · WCAG 2.2 assessment (9 new criteria; upgrade target Q4 2026) · VPAT availability

SECTION 2 — Technical Standards — WCAG 2.1 AA Implementation (All 50 Success Criteria) ............. 8

PERCEIVABLE: 20 criteria (1.1.1-1.4.13) — alt text; captions; audio descriptions; contrast; reflow; spacing

OPERABLE: 17 criteria (2.1.1-2.5.4) — keyboard; focus; no seizure triggers; skip nav; timeout; pointer

UNDERSTANDABLE: 10 criteria (3.1.1-3.3.4) — language; consistent navigation; error identification

ROBUST: 4 criteria (4.1.1-4.1.3) — parsing; name/role/value; status messages (ARIA live regions)

SECTION 3 — Accessibility Features — Vendor Portal, Mobile App & Email .................................. 22

Vendor Portal: keyboard; screen readers (NVDA; JAWS; VoiceOver; TalkBack); contrast; resize

Mobile App (iOS & Android): VoiceOver; TalkBack; Dynamic Type; Switch Access; Reduce Motion

Email: HTML + plain-text alternative; large print on request; BSL/ASL video relay (UK/US)

SECTION 4 — Global Legal Compliance — 30+ Rows Across 8 Regions ....................................... 28

North America: ADA Title III; California Unruh; Ontario AODA (EXCEEDS); Canada ACA; Québec PLANNED

EU: European Accessibility Act (Directive 2019/882 — effective June 2025); EN 301 549; Germany BFSG

UK: Equality Act 2010 §29 · Middle East: UAE; Saudi Arabia; Israel IS 5568 (EXCEEDS)

Africa: Nigeria DAPDA; South Africa PEPUDA (EXCEEDS); Kenya

Asia: India RPWD Act; Japan JIS X 8341-3; South Korea KWCAG 2.1; China GB/T 37668 (EXCEEDS)

Asia-Pacific: Australia DDA; New Zealand Human Rights Act

Latin America: Brazil LBI / ABNT NBR 17060; Mexico; Colombia NTC 5854 (EXCEEDS)

SECTION 5 — Known Non-Conformances, Remediation Plan & Improvement Roadmap .......................... 42

6 Known Non-Conformances: Analytics charts (Q3 2026); Legacy PDFs (Q4 2026); DHL widget (Q3 2026)

Android app labels (Aug 2026); Video audio descriptions (Q4 2026); Session timeout focus (Q3 2026)

Quarterly automated audits (Axe; WAVE; Lighthouse; SiteImprove) · Annual third-party audit

SECTION 6 — How to Report an Accessibility Issue — Channels & Response Commitments ................... 48

Email accessibility@aqnovamarketplace.com · Vendor Portal form · Chat · Phone callback · BSL/ASL relay

2BD acknowledgment · 5BD substantive response · 1BD interim accommodation for critical blockers

SECTION 7 — Formal Complaints, Legal Escalation & Enforcement Contacts by Jurisdiction ............... 53

Formal complaint escalation · 10BD formal written response · 14-jurisdiction enforcement authority table

APP A — Assistive Technology Compatibility Matrix (12 AT combinations) .............................. 58

APP B — Accessibility Glossary (13 terms: WCAG; EN 301 549; ADA; EAA; AODA; POUR; AT; ARIA etc.) ... 60

APP C — Version History & Approval Log .......................................................................... 62

SECTION 1 \| FOUNDATION — THE REACH FRAMEWORK & AQNOVA'S ACCESSIBILITY COMMITMENT

1.1 AqNova's Accessibility Philosophy

AqNova Marketplace is a global platform that serves vendors — the businesses that list and sell products — across more than 30 countries and territories. Our vendor community includes individuals and business operators with a wide range of abilities. A vendor who is blind; has low vision; is Deaf or Hard of Hearing; has a motor impairment; or has a cognitive disability must be able to use the AqNova Vendor Portal and all associated vendor tools just as effectively as any other vendor. Accessibility is not an optional feature at AqNova — it is a fundamental platform requirement.

AqNova's sustainable marketplace mission is grounded in the belief that commerce should be equitable. That principle extends to how we build our own technology. A platform that systematically excludes vendors or buyers with disabilities is not a sustainable marketplace — it is one that replicates, in digital form, the barriers that have historically prevented people with disabilities from full economic participation. We refuse to build such a platform.

Field	Detail
R — Rights-Based Approach	Accessibility on AqNova is not treated as a charitable accommodation extended to users with disabilities. It is a right. The right of persons with disabilities to access goods; services; and commerce on equal terms with persons without disabilities is recognized in law across every major jurisdiction where AqNova operates: the Americans with Disabilities Act (US); the European Accessibility Act (EU); the Equality Act 2010 (UK); the AODA (Canada); and equivalent legislation globally. AqNova implements accessibility as a legal compliance obligation and a human rights imperative.
E — WCAG 2.1 AA Everywhere	The Web Content Accessibility Guidelines (WCAG) 2.1 Level AA is AqNova's technical standard for all vendor-facing digital tools and content. WCAG 2.1 AA is referenced in EN 301 549 (the EU/UK harmonized standard for digital accessibility); is the standard required by ADA compliance guidance; is the standard mandated by the Canadian AODA; and is the international technical benchmark adopted by accessibility laws in Australia; India; Brazil; Japan; South Korea; and most other major economies. One global standard; consistently applied.
A — Accountable Improvement	AqNova publishes this Vendor Accessibility Statement publicly and updates it with every material platform change. We commit to quarterly automated accessibility audits; annual third-party manual audits by accessibility specialists; a published roadmap for resolving known non-conformances; and transparent reporting on accessibility progress. A commitment to accessibility that cannot be verified is not a real commitment.
C — Compatible with Assistive Technology	The AqNova Vendor Portal and all vendor-facing digital tools are designed to work with the assistive technologies our vendor community uses: screen readers (NVDA; JAWS; VoiceOver; TalkBack; Narrator); screen magnification software (ZoomText; macOS Zoom; Windows Magnifier); voice recognition software (Dragon NaturallySpeaking; Windows Speech Recognition; iOS Voice Control); switch access devices; and refreshable Braille displays. Where compatibility issues exist: we treat them as bugs; not as acceptable limitations.
H — Help and Reporting	Vendors who encounter accessibility barriers on the AqNova Vendor Portal — whether or not the barrier is a known non-conformance — can report it and receive a substantive response within 5 business days. AqNova provides multiple reporting channels to ensure that the act of reporting an accessibility problem is itself accessible. Accessibility reports are prioritized in our development backlog; not deprioritized. We also provide human-assisted alternatives for any vendor who is unable to access a specific function due to an accessibility barrier.

1.2 Scope of This Statement

Scope Item	Description	Coverage Level
Vendor Portal (vendor.aqnovamarketplace.com)	The primary web application used by all vendors to manage listings; orders; payouts; analytics; compliance; and account settings.	Primary scope — full WCAG 2.1 AA target
AqNova Vendor Mobile App (iOS & Android)	The AqNova Vendor app for mobile management of orders; dispatch notifications; and performance monitoring.	Primary scope — WCAG 2.1 AA mobile criteria (including APCA for iOS; WCAG 2.1 mobile Success Criteria)
Vendor API Documentation (docs.aqnovamarketplace.com)	Technical documentation for vendors integrating directly with AqNova's API.	Primary scope — documentation accessibility (WCAG 2.1 AA for web documents)
Vendor Email Communications	All transactional emails (order notifications; payout confirmations; compliance alerts; policy updates) sent to vendors from AqNova systems.	Primary scope — accessible HTML email format; plain-text alternative provided
Vendor PDF Documents (e.g., Payout Statements; Policy Documents)	PDF documents generated by the Vendor Portal or provided via the Vendor Support Center.	Primary scope — PDF/UA (ISO 14289) target; tagged PDF with reading order; alt text; language identification
AqNova Vendor Support Center (support.aqnovamarketplace.com)	Self-service knowledge base and support ticket submission for vendors.	Primary scope — WCAG 2.1 AA target
Third-Party Embedded Tools (e.g., payment processor checkout widgets; carrier tracking widgets)	Tools embedded in the Vendor Portal that are controlled by third parties (not AqNova).	Partial scope — AqNova requires contractual accessibility commitments from all third-party vendors; actively tests third-party integrations; escalates failures to third-party providers

1.3 Conformance Status

Field	Detail
Conformance Level	WCAG 2.1 Level AA — Partial Conformance (as of June 2026). AqNova targets full conformance with all 50 WCAG 2.1 AA success criteria. Known non-conformances are documented in Section 6 with planned fix timelines.
Standard Reference	Web Content Accessibility Guidelines (WCAG) 2.1, published June 5, 2018 by the World Wide Web Consortium (W3C). Also: WCAG 2.2 (published October 5, 2023) — AqNova has assessed all 9 new/modified WCAG 2.2 success criteria; adoption target: Q4 2026.
EN 301 549 Alignment	AqNova's Vendor Portal is being developed in alignment with EN 301 549 v3.2.1 (2021-03), the European harmonized standard for Information and Communication Technology (ICT) accessibility. EN 301 549 references WCAG 2.1 for web-based content and adds additional requirements for non-web ICT. AqNova evaluates all new features against both WCAG 2.1 and EN 301 549 requirements.
Last Accessibility Audit	Internal automated audit: May 2026 (tools: Axe DevTools; WAVE; Google Lighthouse). Manual review: May 2026. Next planned third-party audit: September 2026.
VPAT Status	Voluntary Product Accessibility Template (VPAT®) v2.5 covering WCAG 2.1 Level AA: available on request from accessibility@aqnovamarketplace.com.

SECTION 2 \| TECHNICAL STANDARDS — WCAG 2.1 AA IMPLEMENTATION ON THE VENDOR PORTAL

2.1 WCAG 2.1 AA — The Four Principles (POUR)

WCAG 2.1 is organized around four principles: Perceivable; Operable; Understandable; and Robust (POUR). Every success criterion in WCAG 2.1 belongs to one of these four principles. The table below lists each WCAG 2.1 AA success criterion; its level (A or AA); and how AqNova implements it in the Vendor Portal.

This table covers all 50 WCAG 2.1 AA success criteria (38 from WCAG 2.0 AA + 12 new in WCAG 2.1). Success criteria marked with an asterisk (*) in the feature column are areas where AqNova has identified known non-conformances — see Section 6 for fix timelines.

PERCEIVABLE — Information and User Interface Components Must Be Presentable to Users

SC	Name	Level	AqNova Vendor Portal Implementation
1.1.1	Non-text Content	A	All product images; icons; buttons; and infographics in the Vendor Portal include descriptive alternative text (alt text). Decorative images are marked with empty alt attributes (alt=""). Charts in the Analytics Dashboard include both alt text and a text-based data table alternative accessible to screen readers.
1.2.1	Audio-only and Video-only (Prerecorded)	A	AqNova Vendor Portal tutorial videos include synchronized captions. Audio-only onboarding content (if any) includes a full text transcript. All prerecorded vendor training webinar recordings are captioned within 5 business days of recording.
1.2.2	Captions (Prerecorded)	A	Closed captions are provided for all prerecorded video content in the Vendor Portal and Vendor Support Center. Captions follow SMPTE-TT standard and are accurate (not auto-generated without review).
1.2.3	Audio Description or Media Alternative (Prerecorded)	A	Prerecorded video content that includes visual information not available in the audio track provides either audio description or a full text alternative. Vendor onboarding video tutorials include audio description of visual-only steps.
1.2.4	Captions (Live)	AA	Live webinars and video events hosted for vendors (e.g., product launch briefings; compliance training sessions) include real-time captioning via trained captioner or CART (Communication Access Realtime Translation) service.
1.2.5	Audio Description (Prerecorded)	AA	All prerecorded instructional videos in the Vendor Portal provide audio description of visual information not included in the main audio track (e.g., screen actions; chart annotations).
1.3.1	Info and Relationships	A	The Vendor Portal uses semantic HTML5 throughout: headings; lists; tables; forms; and landmarks (header; nav; main; footer; aside) are properly coded. Form fields are programmatically associated with their labels via <for> / <id> pairing or aria-labelledby. Data tables use <th> with scope attributes. ARIA roles used where native HTML semantics are insufficient.
1.3.2	Meaningful Sequence	A	The visual reading order of the Vendor Portal corresponds to the DOM order. CSS-based visual repositioning does not reorder DOM structure. Screen readers present content in a logical sequence.
1.3.3	Sensory Characteristics	A	Instructions and actions in the Vendor Portal do not rely on sensory characteristics alone. Example: error messages state "The field labeled 'Product Title' is required" — not "Click the red field."
1.3.4	Orientation	AA (WCAG 2.1)	The Vendor Portal does not restrict content display to a single screen orientation (portrait or landscape). Vendors can rotate their device without loss of functionality.
1.3.5	Identify Input Purpose	AA (WCAG 2.1)	All input fields in the Vendor Portal that collect personal information (name; email; phone; address; payment details) include autocomplete attributes that identify the input purpose, enabling browsers and assistive technology to autofill accurately.
1.4.1	Use of Color	A	Color is not the only means of conveying information in the Vendor Portal. Error states: indicated by both red color AND an error icon AND descriptive text. Charts: use patterns/textures in addition to color. Status indicators: include text labels.
1.4.2	Audio Control	A	No audio plays automatically in the Vendor Portal. If audio is incorporated into any vendor-facing notification or tutorial: a mechanism to pause; stop; or control volume is provided.
1.4.3	Contrast (Minimum)	AA	Text and images of text in the Vendor Portal meet a minimum contrast ratio of 4.5:1 against the background for normal text (under 18pt; or under 14pt bold); and 3:1 for large text (18pt+; or 14pt+ bold). AqNova's brand green (#7D9A37) on white: tested and meets 4.5:1 for large text.
1.4.4	Resize Text	AA	Text in the Vendor Portal can be resized up to 200% using browser zoom without loss of content or functionality. No fixed pixel heights that prevent text expansion.
1.4.5	Images of Text	AA	The Vendor Portal uses CSS-styled text rather than images of text for all functional interface elements. Logos and branding (which may use images of text): provide text alternatives.
1.4.10	Reflow	AA (WCAG 2.1)	The Vendor Portal content reflows to a single column at 320 CSS pixels wide (equivalent to 400% zoom on a 1280px viewport) without requiring horizontal scrolling. Responsive design: all Vendor Portal views are tested at 320px wide.
1.4.11	Non-text Contrast	AA (WCAG 2.1)	UI components (form borders; button outlines; focus indicators; checkboxes; radio buttons) and informational graphics (chart lines; icons with meaning) have a contrast ratio of at least 3:1 against adjacent colors.
1.4.12	Text Spacing	AA (WCAG 2.1)	Content in the Vendor Portal does not lose readability or functionality when users override spacing: line height 1.5× font size; paragraph spacing 2× font size; letter spacing 0.12× font size; word spacing 0.16× font size.
1.4.13	Content on Hover or Focus	AA (WCAG 2.1)	Tooltips and other content that appears on hover or keyboard focus in the Vendor Portal: can be dismissed (Escape key); can be hovered over without disappearing; persists until hover/focus is removed or the user dismisses it.

OPERABLE — User Interface Components and Navigation Must Be Operable

SC	Name	Level	AqNova Vendor Portal Implementation
2.1.1	Keyboard	A	All functionality of the Vendor Portal is accessible via keyboard only. Tab order is logical. All interactive elements (buttons; links; form fields; dropdowns; modals; date pickers; drag-and-drop alternatives) are keyboard operable. No keyboard traps.
2.1.2	No Keyboard Trap	A	Keyboard focus is never trapped in any component of the Vendor Portal. Modal dialogs: pressing Escape closes the modal and returns focus to the trigger element.
2.1.4	Character Key Shortcuts	A (WCAG 2.1)	Single-character keyboard shortcuts (if implemented) in the Vendor Portal: can be turned off; remapped; or are active only when a component has focus.
2.2.1	Timing Adjustable	A	The Vendor Portal session timeout warning is shown 5 minutes before session expiration. Vendors can extend the session by clicking "Stay Logged In." Time limits (if any) are adjustable to at least 10× the default. Exception: the 30-minute session limit itself is extended on user request with no maximum limit for active sessions.
2.2.2	Pause; Stop; Hide	A	No moving; blinking; or scrolling content in the Vendor Portal runs for more than 5 seconds without a mechanism to pause; stop; or hide it. Loading spinners: are not persistent animations exceeding this threshold.
2.3.1	Three Flashes or Below Threshold	A	No content in the Vendor Portal flashes more than 3 times per second. AqNova checks all animation and transition content against PEAT (Photosensitive Epilepsy Analysis Tool) thresholds before deployment.
2.4.1	Bypass Blocks	A	A "Skip to main content" link is the first focusable element on every Vendor Portal page. This allows keyboard users and screen reader users to bypass repeated navigation and jump directly to the page's primary content.
2.4.2	Page Titled	A	Every page in the Vendor Portal has a descriptive, unique <title> element in the format "Page Name — Vendor Portal \| AqNova Marketplace".
2.4.3	Focus Order	A	Keyboard focus moves through the Vendor Portal in an order that preserves meaning and operability. Focus order follows the visual reading order and logical task sequence.
2.4.4	Link Purpose (In Context)	A	All links in the Vendor Portal have descriptive text that identifies their purpose. No "Click here" or "Read more" links without context. When link destination is a file download: file type and size are included in the link text.
2.4.5	Multiple Ways	AA	The Vendor Portal provides multiple ways to locate content: navigation menu; search function; breadcrumbs; and a site map (sitemap.aqnovamarketplace.com). Vendor Portal help content is findable via both navigation and search.
2.4.6	Headings and Labels	AA	All pages in the Vendor Portal use a logical heading hierarchy (H1→H2→H3). Form fields have visible, descriptive labels that remain visible (not placeholder text that disappears on focus).
2.4.7	Focus Visible	AA	A visible focus indicator is present on every keyboard-focusable element in the Vendor Portal. Focus indicator: minimum 3:1 contrast ratio between focused and unfocused states. Default browser focus styles are not suppressed without replacement.
2.5.1	Pointer Gestures	A (WCAG 2.1)	All multi-pointer gestures (pinch-to-zoom; two-finger swipe) in the Vendor Mobile App have single-pointer alternatives (buttons; sliders with + / - controls).
2.5.2	Pointer Cancellation	A (WCAG 2.1)	Activation of UI components in the Vendor Portal occurs on the up-event (mouse button release; touchend). Accidental presses can be cancelled by moving the pointer off the component before release.
2.5.3	Label in Name	A (WCAG 2.1)	The accessible name of all UI components in the Vendor Portal includes the visual text label. Voice recognition software users can activate components by speaking the visible text.
2.5.4	Motion Actuation	A (WCAG 2.1)	No functionality in the Vendor Mobile App requires physical device motion (shaking; tilting) as the only input method. Motion-triggered functions have button alternatives; and motion can be disabled.

UNDERSTANDABLE — Information and User Interface Must Be Understandable

SC	Name	Level	AqNova Vendor Portal Implementation
3.1.1	Language of Page	A	The HTML lang attribute is set to the correct language on every Vendor Portal page. Multi-language Vendor Portal: currently English (lang="en"); French; Spanish; Portuguese; Arabic; and Japanese language versions planned for 2026 Q3-Q4.
3.1.2	Language of Parts	AA	Phrases in languages other than the page language are marked with the correct lang attribute. Example: product names in Japanese on an English-language page include lang="ja".
3.2.1	On Focus	A	No context changes occur in the Vendor Portal when a component receives focus. Navigation menus expand on activation (Enter or Space) — not on focus alone.
3.2.2	On Input	A	No automatic context changes occur when vendors enter data in Vendor Portal forms — except where the vendor has been advised in advance (e.g., a "live search" filter that updates results as the user types — announced via ARIA live region).
3.2.3	Consistent Navigation	AA	Navigation menus appear in the same order on every page of the Vendor Portal. Navigation is not reordered between pages.
3.2.4	Consistent Identification	AA	UI components that have the same functionality across the Vendor Portal are consistently identified. Example: the "Save" button always has the same label; icon; and ARIA role on all forms.
3.3.1	Error Identification	A	All form validation errors in the Vendor Portal are described to the user in text: identifying the specific field in error; describing what is wrong; and providing guidance on correction. Error messages are programmatically associated with their fields via aria-describedby.
3.3.2	Labels or Instructions	A	All Vendor Portal forms include visible labels for every input field. Required fields are indicated with both an asterisk (*) and the word "Required" in the field label. Format requirements (e.g., date formats; phone number formats) are stated before the field.
3.3.3	Error Suggestion	AA	Where a Vendor Portal input error is identified and the suggestion is known and does not jeopardize security: the error message includes a suggested correction (e.g., "Your HS code must be 6 digits. You entered 5 digits.").
3.3.4	Error Prevention (Legal; Financial; Data)	AA	Vendor Portal actions that are legal; financial; or delete data (submitting a payout request; deleting a product listing; accepting a policy update) include: a review step; a confirmation mechanism; and (where applicable) the ability to reverse the action or correct data before final submission.

ROBUST — Content Must Be Interpretable By Current and Future User Agents

SC	Name	Level	AqNova Vendor Portal Implementation
4.1.1	Parsing	A	Vendor Portal HTML is validated against W3C specifications. No duplicate IDs; all start and end tags properly nested; all required attributes present. Automated parsing validation is part of the CI/CD pipeline — broken HTML does not reach production.
4.1.2	Name; Role; Value	A	All UI components (buttons; links; form inputs; custom controls; modal dialogs; accordions; tabs; tooltips) have: an accessible name (text alternative); an appropriate role (via native HTML semantics or ARIA roles); and correct state/property values (aria-expanded; aria-checked; aria-selected; aria-required; etc.) communicated to assistive technologies.
4.1.3	Status Messages	AA (WCAG 2.1)	Status messages in the Vendor Portal (form submission success; payout processed; new order received; error notifications) are programmatically determined via ARIA live regions (aria-live="polite" for non-urgent; aria-live="assertive" for urgent errors) so screen reader users are informed without losing keyboard focus.

SECTION 3 \| ACCESSIBILITY FEATURES — VENDOR PORTAL, MOBILE APP & COMMUNICATIONS

3.1 Vendor Portal Accessibility Features

Field	Detail
Keyboard Navigation	Full keyboard access: Tab; Shift+Tab; Enter; Space; Arrow keys; Escape. Skip navigation link as first focusable element. Logical tab order throughout all workflows (listing creation; order management; payout settings; compliance documents). All dropdown menus and modals: keyboard operable.
Screen Reader Compatibility	Tested with: NVDA + Firefox (Windows — most common free screen reader); JAWS + Chrome (Windows — most common enterprise screen reader); VoiceOver + Safari (macOS and iOS); TalkBack + Chrome (Android). All page landmarks; heading hierarchies; form labels; error messages; and status updates are correctly announced by all tested screen readers.
Color and Contrast	Minimum 4.5:1 contrast ratio for all body text and informational text. Minimum 3:1 for large text (18px+ or 14px+ bold); for UI component boundaries; and for informational graphics. AqNova brand green (#7D9A37) on white (#FFFFFF): contrast ratio 4.56:1 — meets WCAG 2.1 AA minimum for normal text. Dark text (#1A1A1A) on white: 17.5:1 — exceeds requirement significantly.
Text Resizing and Reflow	Browser zoom up to 200%: no horizontal scrolling; no loss of functionality; no text clipping. Content reflows to single column at 320px viewport width (WCAG 2.1 1.4.10 Reflow). Mobile-responsive design tested at all standard device breakpoints.
Focus Indicators	Visible focus indicator on all interactive elements. Focus indicator: 3px solid green (#7D9A37) with 3:1 minimum contrast against both the component and the adjacent page color. Default browser focus rings are not suppressed — they are enhanced for greater visibility.
Form Accessibility	All form fields have permanently visible text labels (not placeholder-only). Required field indication: asterisk (*) + "Required" text + aria-required="true". Inline validation: real-time feedback as fields are completed; errors announced via aria-describedby + aria-live. Error summary at top of page on form submission failure; focus moves to error summary.
Alternative Text	All product images; icons; illustrations; and charts have descriptive alt text. Decorative images: empty alt attribute. Dynamic content (chart updates; real-time order notifications): alt text and ARIA live region updates.
Language Support	Current: English (primary). Planned (2026 Q3-Q4): French; Spanish; Portuguese; Arabic (RTL layout); Japanese; Yoruba; Hindi. RTL language support: full CSS logical properties implementation planned for Arabic/Hebrew.
Accessible PDFs	All AqNova-generated PDF documents (payout statements; policy documents; customs invoice templates): PDF/UA (ISO 14289) compliant. Tagged PDF structure; reading order; alternate text for images; document language identification. Older PDF documents in the Support Center: being remediated on a rolling schedule.
Session Timeout Warning	Session timeout warning displayed 5 minutes before expiration in a modal dialog accessible to screen readers. Option to extend session: clearly labeled button; keyboard accessible. Timeout counter displayed in text (not only visually).

3.2 Vendor Mobile App Accessibility Features (iOS & Android)

Field	Detail
iOS (VoiceOver)	The AqNova Vendor iOS app is designed to work with VoiceOver. All interactive elements have accessibility labels and hints. Custom gestures have VoiceOver alternatives. The app is tested against Apple's HIG (Human Interface Guidelines) accessibility requirements.
Android (TalkBack)	The AqNova Vendor Android app is designed to work with TalkBack. All interactive elements have content descriptions. The app complies with Google's Material Design accessibility guidelines. Minimum touch target size: 48×48dp (exceeds 44×44px minimum).
Dynamic Text (iOS)	The iOS app supports Dynamic Type: font sizes scale with the user's iOS accessibility text size setting. Layout adapts to larger text sizes without overlap or clipping.
Switch Access	The iOS and Android apps support switch access for users who cannot use touchscreen directly. Navigation paths are logical and operable via switch scanning.
Reduce Motion	The iOS app respects the iOS "Reduce Motion" accessibility setting. The Android app respects the "Disable animations" developer option and the "Remove animations" accessibility option. Animations are suppressed or reduced when these settings are enabled.

3.3 Accessible Email Communications

Field	Detail
HTML Email Format	All AqNova vendor emails use a simple; accessible HTML email structure: plain semantic HTML (not complex table-based layout); clearly coded heading hierarchy; sufficient color contrast; linked text with descriptive anchor text; no reliance on color alone for meaning.
Plain-Text Alternative	Every HTML email from AqNova includes a plain-text alternative (multipart/alternative MIME type). Plain-text versions contain all the information in the HTML version without any formatting loss.
Email Language	Email language attribute: set to the primary language of the email in the HTML <html lang="en"> element. Multi-language emails: each language block is marked with the appropriate lang attribute.
Large Print and Accessible Alternatives	Vendors who require email communications in large print; Braille-ready format; or audio (text-to-speech accessible format): contact accessibility@aqnovamarketplace.com to arrange a preferred accessible format for all AqNova vendor communications.

SECTION 4 \| GLOBAL LEGAL COMPLIANCE — ACCESSIBILITY LAWS ACROSS 20+ JURISDICTIONS

The table below summarizes the accessibility laws applicable to AqNova's platform across all operating jurisdictions. Status: MEETS = currently meeting; EXCEEDS = exceeding requirements; PARTIAL = partially meeting; PLANNED = compliance planned (timeline stated). AqNova's WCAG 2.1 AA baseline means that compliance with laws referencing this standard is substantially addressed.

Jurisdiction	Applicable Law / Standard	Key Requirements for AqNova	AqNova Status	Enforcement Body
NORTH AMERICA
USA (Federal)	Americans with Disabilities Act (ADA) Title III (42 U.S.C. §12181 et seq.); Department of Justice Web Accessibility Guidance (March 2022); Final Rule 28 C.F.R. Part 36 (WCAG 2.1 AA for state/local entities — April 2024; private sector: DOJ guidance)	Commercial websites operated by "places of public accommodation" must be accessible to persons with disabilities. DOJ 2022 guidance: WCAG 2.1 AA is the standard the DOJ recommends. Robles v. Domino's Pizza (9th Cir. 2019): commercial websites must comply with ADA. DOJ Final Rule (March 2024): WCAG 2.1 AA mandatory for state and local government websites.	◑ PARTIAL	DOJ (Department of Justice); private right of action; class action risk
California (USA)	Unruh Civil Rights Act (Cal. Civ. Code §51); California Government Code §11546.7 (state websites); CPRA + ADA combined exposure	Unruh Act: extends ADA protections to California residents; statutory damages $4,000 per violation. California courts have consistently found inaccessible commercial websites violate Unruh. Most ADA website litigation in the US is filed in California (S.D.N.Y. is also high volume).	◑ PARTIAL	California courts; private right of action; CCPA enforcement (CPPA); AG
New York (USA)	NYCHRL (NYC Human Rights Law); NY Executive Law §296; ADA Title III (Southern District of New York — busiest ADA website docket in the US)	NYCHRL: broader protections than federal ADA; applies to websites serving NYC residents. Southern District of New York courts have accepted ADA website accessibility cases including cases against e-commerce platforms.	◑ PARTIAL	NYCCHR (NYC Commission on Human Rights); private right of action
Canada (Federal)	Accessible Canada Act 2019 (S.C. 2019, c. 10); CAN/ASC EN 301 549:2024 (adopts WCAG 2.1 AA for ICT)	ACA: requires federally regulated entities to identify; remove; and prevent barriers to accessibility. Accessibility standards reference EN 301 549 (which references WCAG 2.1 AA). AqNova: not a federally regulated entity under ACA scope — but demonstrates best practice compliance.	✓ MEETS	Accessibility Standards Canada; Canadian Human Rights Commission
Ontario (Canada)	AODA — Accessibility for Ontarians with Disabilities Act 2005; Integrated Accessibility Standards Regulation (O. Reg. 191/11); Web Content Accessibility Guidelines 2.0 Level AA (AODA mandates WCAG 2.0 — AqNova's WCAG 2.1 exceeds this)	AODA requires all organizations with 50+ employees that operate in Ontario to comply with WCAG 2.0 Level AA for their web content. AqNova's WCAG 2.1 AA implementation exceeds the AODA WCAG 2.0 Level AA requirement.	★ EXCEEDS	Accessibility Directorate of Ontario; Human Rights Tribunal of Ontario
British Columbia (Canada)	Accessible British Columbia Act 2021; Government of Canada WCAG 2.0 AA standard	BC Accessibility Act: requires organizations to establish accessibility plans; consult with persons with disabilities; report on progress. WCAG 2.0 AA is the BC government digital standard.	✓ MEETS	Accessibility Commissioner of BC
Québec (Canada)	Act Respecting Equal Access to Employment in Public Bodies (Bill 60); Charte de la Langue Française / Bill 96 (French language in digital services)	For digital commerce in Québec: French language must be available. Bill 96: significantly expanded French language requirements for businesses operating in Québec including digital services. All Vendor Portal content must be available in French for Québec users — planned for Q3 2026.	◌ MONITORING	Office Québécois de la Langue Française; CDPDJ
EUROPE
EU (27 Member States)	European Accessibility Act (EAA) — Directive 2019/882 (effective June 28 2025 for new products/services; June 28 2030 for existing services); EN 301 549 v3.2.1 (2021-03)	EAA: applies to e-commerce services providing online sales of products. Requires WCAG 2.1 AA compliance (via EN 301 549). From June 28 2025: all new e-commerce services must comply. Existing services: until June 2030. AqNova commercially launched April 2026 — EAA compliance required from launch.	◑ PARTIAL	National market surveillance authorities; European Accessibility Resource Centre (EARC)
United Kingdom	Equality Act 2010 (Section 29 — services; Section 20 — reasonable adjustments); Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 (No. 952 — public sector); BS 8878:2010 Web Accessibility Code of Practice (best practice for commercial entities)	Equality Act 2010 §29: service providers must not discriminate against persons with disabilities; §20: duty to make reasonable adjustments. WCAG 2.1 AA: the standard courts and the Equality and Human Rights Commission (EHRC) reference as the reasonable adjustment benchmark. UK public sector bodies: must comply with the 2018 Accessibility Regulations (WCAG 2.1 AA mandatory).	◑ PARTIAL	Equality and Human Rights Commission (EHRC); private right of action; UK courts
Germany	EU EAA implementation (Barrierefreiheitsstärkungsgesetz — BFSG — effective June 28 2025); BITV 2.0 (Barrierefreie-Informationstechnik-Verordnung — for German public sector); BGG (Disability Equality Law)	BFSG: Germany's national implementation of the EAA. Applies to e-commerce services. WCAG 2.1 AA via EN 301 549. German accessibility enforcement: market surveillance authority (Marktüberwachungsbehörde) per Bundesland.	◑ PARTIAL	Bundesbehörde für Barrierefreiheit der Informationstechnik (BFIT) — national coordinating body; Landesbehörden (state-level market surveillance)
France	EU EAA implementation (Loi accessibilité numérique / RGAA 4.1 — Référentiel Général d'Amélioration de l'Accessibilité); Loi République Numérique 2016	RGAA 4.1: France's web accessibility standard; closely aligned with WCAG 2.1 AA but with French-specific testing criteria. For public sector: mandatory. Private sector: RGAA recommended; EAA mandatory from June 2025 for e-commerce. French accessibility statement must follow DINUM template format.	◑ PARTIAL	DINUM (Direction Interministérielle du Numérique); Défenseur des droits
Netherlands; Belgium; Spain; Italy; Sweden; Other EU member states	National EAA implementations; WCAG 2.1 AA via EN 301 549	Each EU member state implements the EAA in national legislation. All reference WCAG 2.1 AA via EN 301 549. From June 28 2025: e-commerce services must comply in all 27 EU member states simultaneously.	◌ MONITORING	National market surveillance authorities in each member state
MIDDLE EAST
UAE	UAE Vision 2031 Digital Accessibility Framework; Dubai Electronic Security Center; WCAG 2.1 guidelines adopted by Federal e-Government Authority; UAE Law No. 29/2006 on Rights of Persons with Disabilities	UAE: WCAG 2.1 AA referenced for government and private sector digital services under the UAE's digital transformation agenda. Smart Dubai accessibility requirements apply to digital services in Dubai. No specific private sector e-commerce accessibility enforcement mechanism currently — but recommended compliance.	✓ MEETS	Federal Authority for Identity and Citizenship; Smart Dubai; Ministry of Community Development
Saudi Arabia	National Transformation Program 2020+; Vision 2030 Digital Accessibility; ZATCA e-invoicing digital standards; Saudi Disability Law (updated 2017); Ministerial Decree on Electronic Services Accessibility	Saudi Arabia: digital accessibility requirements apply to government portals and are increasingly expected of private e-commerce. SAMA financial services digital requirements include accessibility components. Vision 2030: accessibility as a pillar of digital inclusion.	✓ MEETS	Ministry of Communications and Information Technology (MCIT); SDAIA; Satr platform
Israel	Equal Rights for Persons with Disabilities Law 1998 (§19b amended 2014); Accessibility Regulations for Service (2013); IS 5568:2014 (Israeli accessibility standard; based on WCAG 2.0 AA); Amendment extending to websites 2017	IS 5568: Israeli web accessibility standard based on WCAG 2.0 AA. Amendment: websites serving Israeli customers must comply. AqNova's WCAG 2.1 AA compliance exceeds IS 5568 requirements.	★ EXCEEDS	Commission for Equal Rights of Persons with Disabilities; Israeli courts
AFRICA
Nigeria	Discrimination Against Persons with Disabilities (Prohibition) Act 2018 (DAPDA); Federal Ministry of Finance digital inclusion guidelines; NCC digital accessibility guidance	DAPDA 2018: prohibits discrimination against persons with disabilities; applies to service providers. No specific web accessibility technical standard currently mandated for private sector in Nigeria. AqNova applies WCAG 2.1 AA as best practice; aligns with DAPDA principles.	✓ MEETS	National Commission for Persons with Disabilities (NCPWD); NCC
South Africa	Constitution §9 (equality) + §28; Promotion of Equality and Prevention of Unfair Discrimination Act 4/2000 (PEPUDA); SANS 10264:2008 (web accessibility standard; based on WCAG 1.0 — updated reference to WCAG 2.1 expected)	PEPUDA: prohibits discrimination including on basis of disability. South Africa: WCAG 2.1 AA recommended. SANS 10264 is the formal SA standard (currently based on WCAG 1.0; update expected). AqNova's WCAG 2.1 AA implementation significantly exceeds SANS 10264 requirements.	★ EXCEEDS	South African Human Rights Commission (SAHRC); Equality Courts
Kenya	Persons with Disabilities Act 2003; Constitution of Kenya 2010 (Art.54 — rights of persons with disabilities); Kenya National Digital Master Plan 2022-2032	Kenya: no specific web accessibility standard mandated for private sector. Kenya National ICT Masterplan includes digital inclusion goals. AqNova applies WCAG 2.1 AA as best practice and aligns with Kenya's digital inclusion aspirations.	✓ MEETS	National Council for Persons with Disabilities (NCPWD); Kenya Human Rights Commission
ASIA
India	Rights of Persons with Disabilities Act 2016 (RPWD Act — Chapter XII §42: accessible websites); Guidelines for Indian Government Websites (GIGW) 3.0; Indian Standard IS 15139:2015 (based on WCAG 2.0); Information Technology Act 2000 §72A	RPWD Act §42: "all content available on the internet by information, public communication, and broadcasting services shall conform to the Standards". IS 15139 references WCAG 2.0. For private sector e-commerce platforms serving Indian users: RPWD Act principles apply. AqNova's WCAG 2.1 AA exceeds IS 15139.	✓ MEETS	Department of Empowerment of Persons with Disabilities (DEPwD); STQC (Standardization Testing and Quality Certification)
Japan	JIS X 8341-3:2016 (Japanese Industrial Standard for web accessibility; aligned with WCAG 2.1 AA); Basic Act for Persons with Disabilities 2011; Act for Eliminating Discrimination against Persons with Disabilities 2016	JIS X 8341-3: Japan's primary web accessibility standard; closely aligned with WCAG 2.1 AA. Public sector: mandatory. Private sector: strongly recommended by the Act for Eliminating Discrimination. AqNova's WCAG 2.1 AA compliance aligns with JIS X 8341-3.	✓ MEETS	Ministry of Internal Affairs and Communications (MIC); Japan Industrial Standards Committee
South Korea	Act on Welfare of Persons with Disabilities (§22b accessible websites); Web Content Accessibility Guidelines for Korea (KWCAG 2.1; aligned with WCAG 2.1 AA); NIA Digital Accessibility Standards	KWCAG 2.1: Korea's web accessibility standard; based on and aligned with WCAG 2.1. Public sector websites and certain private sector online services: mandatory compliance. AqNova's WCAG 2.1 AA compliance substantially aligns with KWCAG 2.1.	✓ MEETS	National Information Society Agency (NIA); Ministry of Science and ICT
China	Web Information Accessibility Assessment Standard GB/T 37668-2019; Law on the Protection of Disabled Persons 1990 (amended 2018); No. 1 Accessible Digital Standard (2023)	GB/T 37668: China's national web accessibility standard; aligned with WCAG 2.0. For government websites: mandatory. Private sector: recommended and increasingly expected under China's digital inclusion agenda. AqNova's WCAG 2.1 AA exceeds GB/T 37668 requirements.	★ EXCEEDS	China Disabled Persons' Federation (CDPF); MIIT (Ministry of Industry and Information Technology)
Singapore	Infocomm Media Development Authority (IMDA) Enabling Masterplan; PDPA accessibility data rights; Singapore Government Web Accessibility Guideline (WCAG 2.1 AA)	Singapore: WCAG 2.1 AA is the Singapore government's standard for digital accessibility. IMDA recommends private sector adoption. No mandatory private sector digital accessibility law currently — but best practice compliance expected.	✓ MEETS	IMDA (Infocomm Media Development Authority); Ministry of Social and Family Development
ASIA-PACIFIC
Australia	Disability Discrimination Act 1992 (DDA); Advisory Note on the DDA and World Wide Web Access (AHRC 2010; 2022 update); Australian Government Digital Service Standard (WCAG 2.1 AA); AS EN 301 549	DDA: all suppliers of goods and services (including websites and apps) must not discriminate against persons with disabilities. WCAG 2.1 AA: the AHRC's recommended standard as the reasonable adjustment benchmark. Australian government: AS EN 301 549 mandatory (aligns with WCAG 2.1). Private sector e-commerce: DDA duty of care; WCAG 2.1 AA is the defense-enabling standard.	◑ PARTIAL	Australian Human Rights Commission (AHRC); Federal Court; Australian Communications and Media Authority (ACMA)
New Zealand	Human Rights Act 1993 (§42 — goods and services); NZ Web Accessibility Standard 1.1 (WCAG 2.1 AA); NZ Web Usability Standard 1.3	NZ Web Accessibility Standard: mandates WCAG 2.1 AA for NZ government websites. Private sector: Human Rights Act duty to make reasonable accommodation. WCAG 2.1 AA is the benchmark.	✓ MEETS	NZ Human Rights Commission; Privacy Commissioner
LATIN AMERICA
Brazil	Lei Brasileira de Inclusão (LBI) — Lei 13.146/2015 (Estatuto da Pessoa com Deficiência); e-MAG v3.1 (Modelo de Acessibilidade em Governo Eletrônico); ABNT NBR 17060:2022 (Brazilian web accessibility standard)	LBI §63: websites must be accessible to persons with disabilities; technology must be accessible. For government websites: e-MAG compliance mandatory. Private sector e-commerce: LBI principles apply. ABNT NBR 17060 (2022) is Brazil's national web accessibility standard; aligned with WCAG 2.1 AA. Decree 5.296/2004 also applies accessibility requirements.	◑ PARTIAL	Ministry of Human Rights; National Council of Rights of Persons with Disabilities (CONADE); courts
Mexico	Ley Federal para Prevenir y Eliminar la Discriminación; Ley General para la Inclusión de las Personas con Discapacidad 2011; NMX-I-271-NYCE-2012 (Mexican ICT accessibility standard; based on WCAG)	LGIPD: comprehensive disability rights law; digital accessibility obligations for public and private sector. NMX-I-271 references WCAG standards. AqNova applies WCAG 2.1 AA as best practice.	✓ MEETS	CONAPRED (Consejo Nacional para Prevenir la Discriminación)
Colombia	Ley 1618/2013 (full exercise of rights for persons with disabilities); NTC 5854:2011 (Colombian web accessibility standard; based on WCAG 2.0); MinTIC Resolution for accessible digital services	NTC 5854: Colombia's web accessibility standard; based on WCAG 2.0. Ley 1618: digital inclusion obligation for all service providers. AqNova's WCAG 2.1 AA implementation exceeds NTC 5854.	★ EXCEEDS	Ministry of ICT (MinTIC); SISBEN
Argentina; Chile; Peru	AR: LGTS Ley 26.522; CL: Ley 20.422 (disability equality); PE: Ley 29.973 (persons with disabilities)	Regional disability equality laws apply to service providers. No specific web accessibility standard mandated for private sector e-commerce in most cases. AqNova applies WCAG 2.1 AA as best practice across all Latin American markets.	✓ MEETS	National disability agencies; consumer protection authorities in each country

SECTION 5 \| KNOWN NON-CONFORMANCES, REMEDIATION PLAN & IMPROVEMENT ROADMAP

5.1 Known Non-Conformances as of June 2026

AqNova is committed to transparency about known accessibility gaps. The following are known non-conformances with WCAG 2.1 AA as of the effective date of this statement. Each has a planned remediation date. We update this section whenever new issues are identified or remediation is completed.

#	Non-Conformance	WCAG Criterion	Current Status	Planned Remediation
1	Analytics Dashboard — Complex Charts	WCAG 1.1.1 (Non-text Content); WCAG 1.4.11 (Non-text Contrast)	Some chart types in the Advanced Analytics Dashboard do not currently provide fully accessible text alternatives or meet non-text contrast requirements. Screen reader users may not receive the full data context from chart descriptions.	Q3 2026 — Add text-based data table alternatives for all chart types; improve chart color scheme to meet 3:1 non-text contrast; add comprehensive aria-label descriptions to all SVG charts.
2	Vendor Portal — Legacy PDF Documents (pre-June 2026)	WCAG 1.1.1; PDF/UA (ISO 14289)	PDF documents published in the Vendor Support Center before June 2026 may not be fully tagged or PDF/UA compliant. Affected documents include some older policy guides and archived shipping label templates.	Q4 2026 — Remediate all pre-June 2026 PDFs in the Vendor Support Center to PDF/UA standard. New PDFs published after June 2026 are PDF/UA compliant from creation.
3	Third-Party Carrier Tracking Widget	WCAG 2.1.1 (Keyboard); WCAG 4.1.2 (Name; Role; Value)	The embedded DHL carrier tracking status widget included on the Order Management page is controlled by DHL and currently does not fully meet keyboard accessibility or ARIA requirements for screen readers.	Q3 2026 — AqNova is in active engagement with DHL to remediate the widget. Interim alternative: accessible tracking information page linked directly from the order management page provides the same tracking data without the widget.
4	Vendor Mobile App — Accessibility Labels (partial)	WCAG 4.1.2 (Name; Role; Value) — mobile equivalent	Some interactive elements in the AqNova Vendor Android app (v1.x) do not have complete accessibility labels for TalkBack. iOS VoiceOver: fully compliant. Android app: remediation in progress.	App update v1.2 — August 2026 — Full TalkBack accessibility label audit and remediation; accessibility regression testing added to Android release pipeline.
5	Video Tutorials — Audio Descriptions	WCAG 1.2.5 (Audio Description; Prerecorded)	Approximately 8 of 24 vendor onboarding tutorial videos in the Vendor Support Center do not yet have audio descriptions for visual-only content (e.g., screen annotation highlights; cursor movement descriptions).	Q4 2026 — All tutorial videos to have audio descriptions. An audio-described version or video alternative will be published alongside the original for all videos in the Support Center.
6	Session Timeout — Announcement to Screen Readers	WCAG 4.1.3 (Status Messages)	The session timeout warning modal is currently announced to screen readers but does not transfer focus to the modal automatically. Screen reader users may miss the countdown if focus is elsewhere on the page.	Q3 2026 — Implement focus management on session timeout modal: focus moves to the modal automatically; Escape key and "Stay Logged In" button both return focus to previous location.

5.2 Continuous Improvement Roadmap

Field	Detail
Q3 2026 (July-September)	(1) Remediate all known non-conformances listed in §5.1 items 1; 3; and 6. (2) Complete third-party independent accessibility audit by accredited IAAP (International Association of Accessibility Professionals) certified firm. (3) Publish updated VPAT 2.5 reflecting third-party audit findings. (4) Deploy WCAG 2.2 gap analysis results — begin implementation of 9 new/modified WCAG 2.2 success criteria (2.4.11 Focus Appearance; 2.4.12 Focus Appearance (minimum); 2.4.13 Focus Appearance (enhanced); 2.5.7 Dragging Movements; 2.5.8 Target Size (minimum); 3.2.6 Consistent Help; 3.3.7 Redundant Entry; 3.3.8 Accessible Authentication (minimum); 3.3.9 Accessible Authentication (no exception)).
Q4 2026 (October-December)	(1) Remediate non-conformances §5.1 items 2; 4; and 5. (2) Launch French-language version of Vendor Portal (for Québec compliance). (3) Begin Spanish; Portuguese; Arabic; and Japanese language versions. (4) Publish WCAG 2.2 conformance statement. (5) Complete second accessibility audit cycle. (6) Begin accessible PDF remediation of pre-June 2026 Support Center documents.
2027 Q1-Q2	(1) Full launch of Spanish; Portuguese; Arabic (RTL); Japanese language versions of Vendor Portal. (2) Target: full WCAG 2.1 AA conformance (resolve all known non-conformances). (3) Begin WCAG 2.2 AA formal conformance testing. (4) Introduce accessible video captioning and audio description for all new video content on a same-day basis. (5) Implement Accessibility User Research program — quarterly testing sessions with vendors who use assistive technology.
Ongoing	(1) Quarterly automated accessibility scanning of all Vendor Portal pages using Axe DevTools; WAVE; Lighthouse; and SiteImprove. (2) All new features undergo mandatory accessibility review before deployment. (3) Accessibility testing integrated into CI/CD pipeline — builds with accessibility regressions do not deploy to production. (4) Annual third-party accessibility audit. (5) This Vendor Accessibility Statement updated quarterly or upon material changes.

5.3 Testing Methodology

Field	Detail
Automated Testing Tools	Axe DevTools (Deque Systems) — integrated into CI/CD pipeline; scans every page build. WAVE (WebAIM) — monthly scans. Google Lighthouse — integrated into CI/CD pipeline (accessibility score target: 95+). SiteImprove — continuous monitoring with email alerts for new issues.
Manual Testing	Keyboard-only navigation: every new user flow tested by keyboard before release. Screen reader testing: NVDA + Firefox; JAWS + Chrome; VoiceOver + Safari (macOS and iOS); TalkBack + Chrome Android. Mobile app testing: iOS VoiceOver; Android TalkBack; iOS Switch Control; Android Switch Access. Manual testing performed by AqNova's accessibility team on every new feature and on the full Vendor Portal on a quarterly basis.
User Testing with Persons with Disabilities	AqNova's Accessibility User Research program (launching Q1 2027) will conduct quarterly usability testing sessions with vendors who use assistive technologies in their daily work. Participants: vendors who use screen readers; vendors with low vision; vendors with motor impairments; vendors who are Deaf or Hard of Hearing. Findings: feed directly into the development backlog.
Third-Party Independent Audit	Annual audit by an accredited accessibility specialist (IAAP Certified Professional in Accessibility Core Competencies — CPACC; or Web Accessibility Specialist — WAS). Audit methodology: manual WCAG 2.1 AA review; screen reader testing; user research review. Audit report: published on request.

SECTION 6 \| HOW TO REPORT AN ACCESSIBILITY ISSUE — MULTIPLE CHANNELS & RESPONSE COMMITMENTS

6.1 Reporting an Accessibility Issue

AqNova wants to hear from vendors who encounter accessibility barriers when using the Vendor Portal; the Vendor Mobile App; or any other vendor-facing AqNova tool or communication. Every accessibility report is treated as a bug report — not as a complaint. Accessibility issues go directly to AqNova's development team with priority status.

AqNova is committed to providing alternative means of completing any task that cannot currently be accomplished due to an accessibility barrier. If you are unable to complete a specific task in the Vendor Portal because of an accessibility issue — creating a listing; submitting a payout request; uploading a document; responding to a dispute — contact accessibility@aqnovamarketplace.com and a member of our team will complete the task on your behalf until the accessibility barrier is resolved.

Channel	Details
Email (Primary — Accessible)	accessibility@aqnovamarketplace.com — preferred for accessibility issue reports; accessibility accommodation requests; and requests for accessible format alternatives (large print; Braille-ready; audio description).
Vendor Portal — Accessibility Feedback Form	Vendor Portal → Help → Accessibility Feedback. The form itself is fully accessible (WCAG 2.1 AA). For vendors who are unable to access this form due to an accessibility barrier: use email or phone.
Vendor Support Chat	The Vendor Support Center live chat at support.aqnovamarketplace.com includes accessibility features (keyboard navigation; screen reader compatible). Chat agents are trained to receive and escalate accessibility reports.
Phone (Available on Request)	AqNova can arrange a phone call to discuss accessibility issues or provide a telephone alternative to Vendor Portal functions. Request a callback: email accessibility@aqnovamarketplace.com with subject "Callback Request — Accessibility" and your preferred calling time and phone number.
BSL / ASL Video Relay (UK and US)	For Deaf or Hard of Hearing vendors in the UK or US who use British Sign Language (BSL) or American Sign Language (ASL): AqNova can arrange a video relay interpretation service for support sessions. Request via email: accessibility@aqnovamarketplace.com Subject: "BSL/ASL Video Relay Request."

6.2 What to Include in an Accessibility Report

Field	Detail
1. Describe the barrier	What were you trying to do when you encountered the accessibility problem? (e.g., "I was trying to upload a product image" or "I was trying to read my payout statement.")
2. Which page or function	Provide the URL of the page; the name of the feature; or the name of the document where you encountered the issue.
3. What assistive technology you use (if any)	What screen reader; magnification software; voice recognition; or other assistive technology were you using? What browser; operating system; or device?
4. What happened vs. what you expected	Describe what happened and what you expected to happen. Example: "The dropdown menu opened but I could not navigate the options with my keyboard arrow keys. I expected to be able to select an option using the arrow keys."
5. Severity (optional)	Can you currently complete the task using another method? Or is the accessibility barrier completely blocking you from completing the task?

6.3 AqNova's Response Commitments

Field	Detail
Acknowledgment	AqNova acknowledges receipt of every accessibility report within 2 business days of receipt.
Substantive Response (Assessment)	AqNova provides a substantive response — confirming whether the reported issue is a known non-conformance; a newly identified issue; or a usage clarification — within 5 business days of receipt.
Interim Accommodation	Where an accessibility barrier is preventing a vendor from completing a critical business task (listing a product; managing an order; submitting a dispute response): AqNova provides a human-assisted alternative within 1 business day of the report.
Prioritization of Fixes	Critical accessibility barriers (issues preventing completion of any core vendor workflow): prioritized in the next sprint release (typically within 2-4 weeks of confirmation). Non-critical accessibility issues: scheduled in the next quarterly accessibility maintenance sprint.
Follow-Up	AqNova follows up with the reporting vendor when the accessibility issue is resolved; inviting the vendor to confirm that the resolution addresses the barrier they experienced.
Anonymous Reports	Vendors may submit accessibility reports without identifying themselves. Anonymous reports are investigated on the same basis as identified reports. Anonymous reporters do not receive follow-up communications.

SECTION 7 \| FORMAL COMPLAINTS, LEGAL ESCALATION & ENFORCEMENT CONTACTS BY JURISDICTION

7.1 If Our Response Is Not Satisfactory

If you are not satisfied with AqNova's response to your accessibility report — or if you have not received a response within the committed timelines — you have the right to escalate to AqNova's formal complaints process and to the relevant national or regional enforcement authority in your jurisdiction.

Field	Detail
AqNova Formal Accessibility Complaint	Email: accessibility@aqnovamarketplace.com with subject "Formal Accessibility Complaint — [Description]". AqNova escalates formal complaints to the CCRO (Chief Compliance & Risk Officer — Ronke Olatoye) and the Head of Product. Response commitment: 10 business days for a formal written response to a formal complaint. Formal complaints are tracked and reported in AqNova's annual accessibility transparency report.
Legal Notice	If you wish to assert legal rights in connection with AqNova's accessibility: legal@aqnovamarketplace.com. Postal: Legal Department; AqNova Marketplace / Arivon Holding Corporation; Huntington Park; California; USA.

Field

Detail

AqNova Formal Accessibility Complaint

Email: accessibility@aqnovamarketplace.com with subject "Formal Accessibility Complaint — [Description]". AqNova escalates formal complaints to the CCRO (Chief Compliance & Risk Officer — Ronke Olatoye) and the Head of Product. Response commitment: 10 business days for a formal written response to a formal complaint. Formal complaints are tracked and reported in AqNova's annual accessibility transparency report.

Legal Notice

If you wish to assert legal rights in connection with AqNova's accessibility: legal@aqnovamarketplace.com. Postal: Legal Department; AqNova Marketplace / Arivon Holding Corporation; Huntington Park; California; USA.

7.2 Enforcement Authorities by Jurisdiction

Jurisdiction	Enforcement Authority & Contact	Legal Recourse
USA (ADA)	US Department of Justice (DOJ) ADA Disability Rights Section. doj.gov/crt/disability-rights-section. Phone: 1-800-514-0301 (voice); 1-800-514-0383 (TTY). ADA.gov complaint form.	Private right of action in federal district court. DOJ may investigate and file civil action.
California (USA)	California Department of Fair Employment and Housing (now DFEH; absorbed into CRC — Civil Rights Department). calcivilrights.ca.gov. Unruh Act: private right of action in California Superior Court.	Statutory damages $4,000 per violation (Unruh Act) + attorney fees.
Canada (Federal)	Canadian Human Rights Commission (CHRC). chrc-ccdp.gc.ca. ACA complaints: Accessibility Commissioner.	Human Rights Tribunal of Canada; ACA Compliance Commissioner.
Ontario (Canada)	Accessibility Directorate of Ontario. ontario.ca/accessibility. Human Rights Tribunal: hrto.ca.	Human Rights Tribunal of Ontario; Accessibility Compliance Directorate.
UK	Equality and Human Rights Commission (EHRC). equalityhumanrights.com. Citizens Advice for free legal advice.	Employment Tribunal; County Court; High Court.
EU (all member states)	National Disability Equality Bodies (vary by member state). EAA complaints: national market surveillance authority. European Accessibility Resource Centre: accessibility-in-europe.eu.	National courts; national equality bodies; European Commission.
Australia	Australian Human Rights Commission (AHRC). humanrights.gov.au/complaints/make-complaint. Free conciliation service.	Federal Court of Australia; Federal Circuit and Family Court of Australia.
New Zealand	NZ Human Rights Commission. hrc.co.nz. Free complaint service.	Human Rights Review Tribunal.
India	National Commission for Persons with Disabilities. depwd.gov.in. State Commissioner for Disabilities.	Civil courts; STQC for technical standards.
Japan	Japan Legal Support Centre (Houterasu). Support for disability discrimination complaints under the 2016 Act.	Local government civil rights offices; mediation before formal proceedings.
Brazil	National Council of Rights of Persons with Disabilities (CONADE). mdh.gov.br/conade. Ministry of Human Rights (MDH).	Federal and state courts; Procon (consumer protection).
South Africa	South African Human Rights Commission (SAHRC). sahrc.org.za. Free complaint investigation.	Equality Court; High Court.
Nigeria	National Commission for Persons with Disabilities (NCPWD). Federal High Court.	Federal High Court; Consumer protection through FCCPC.
UAE	General Secretariat for Persons of Determination (Ministry of Community Development). mcd.gov.ae.	Consumer protection tribunal; UAE courts.

APPENDICES \| ASSISTIVE TECHNOLOGY COMPATIBILITY, GLOSSARY & VERSION HISTORY

Appendix A — Assistive Technology Compatibility Matrix

Assistive Technology	Platform	Vendor Portal Compatibility	Notes
NVDA 2024.x + Firefox (latest)	Windows	Full. Tested on every release. Headings; landmarks; forms; tables; ARIA patterns; live regions all tested.	Critical path — most common free screen reader globally
JAWS 2024 + Chrome (latest)	Windows	Full. Tested quarterly. All core Vendor Portal workflows verified.	Most common enterprise screen reader; used by many professional vendors
VoiceOver + Safari (latest)	macOS	Full. Tested quarterly. macOS specific: rotor navigation; heading navigation; form mode.	Required for Safari/macOS compliance
VoiceOver + Safari (latest)	iOS (latest)	Full. Tested on Vendor Mobile App with every iOS app release.	Critical for mobile vendors
TalkBack + Chrome (latest)	Android (latest)	Partial — known issues in Android app v1.x; see §5.1. Web app via Chrome: full.	Android app: remediation in progress (v1.2 August 2026)
Narrator + Edge	Windows	Partial. Tested quarterly. Some ARIA patterns require additional testing with Edge/Narrator combination.	Secondary priority — improving compatibility
ZoomText + any browser	Windows	Full. Content reflow and text resize (1.4.4; 1.4.10) verified with ZoomText magnification.	Used by low vision vendors
macOS Zoom + Safari	macOS/iOS	Full. No content clipping at 200% zoom; 400% reflow.	Built-in macOS/iOS feature; no compatibility issues
Dragon NaturallySpeaking 15+	Windows	Full. Label-in-Name (2.5.3) ensures voice activation of all labelled UI components.	Voice recognition compliance verified
iOS Voice Control	iOS	Full. Consistent with VoiceOver testing; voice command labels match visual labels.	iOS built-in; no compatibility issues
Refreshable Braille Displays (JAWS; NVDA compatible)	Windows	Full via JAWS/NVDA integration. ARIA and semantic HTML structure provides correct Braille output.	Used by Deaf-Blind vendors
Switch Access (iOS Switch Control; Android Switch Access)	iOS; Android	Full on iOS; partial on Android (v1.x app). Web app via keyboard: full.	Supported via keyboard equivalents

Appendix B — Accessibility Glossary

Field	Detail
WCAG (Web Content Accessibility Guidelines)	The international technical standard for web accessibility published by the W3C. WCAG 2.1 AA is the primary standard AqNova targets. Success criteria are organized into four principles (POUR): Perceivable; Operable; Understandable; Robust.
EN 301 549	The European harmonized standard for ICT (Information and Communication Technology) accessibility. Used in EU law (EAA; WAD) to define technical requirements. EN 301 549 references WCAG 2.1 for web content and adds non-web ICT requirements.
ADA (Americans with Disabilities Act)	US law prohibiting discrimination against persons with disabilities in all areas of public life. Title III applies to places of public accommodation including commercial websites.
EAA (European Accessibility Act)	EU Directive 2019/882 requiring accessibility of certain products and services (including e-commerce) in EU member states. Effective June 28 2025 for new services.
AODA (Accessibility for Ontarians with Disabilities Act)	Ontario; Canada law requiring WCAG 2.0 Level AA compliance for websites of organizations with 50+ employees. AqNova's WCAG 2.1 AA implementation exceeds AODA requirements.
Screen Reader	Software that reads digital content aloud or outputs it to a Braille display for users who are blind or have low vision. Examples: NVDA; JAWS (Windows); VoiceOver (Apple); TalkBack (Android); Narrator (Windows).
ARIA (Accessible Rich Internet Applications)	A W3C specification that defines how to make web applications accessible to persons with disabilities using roles; properties; and states that assistive technology can recognize.
POUR (Perceivable; Operable; Understandable; Robust)	The four principles of WCAG. All 78 WCAG 2.1 success criteria belong to one of these four principles.
PDF/UA (ISO 14289)	The ISO standard for universally accessible PDF documents. Tagged PDFs with PDF/UA compliance can be navigated by screen readers and assistive technologies.
VPAT (Voluntary Product Accessibility Template)	A document that describes how a digital product meets accessibility standards. Used by government and enterprise purchasers to assess accessibility conformance.
Level A / Level AA / Level AAA	The three levels of WCAG conformance. Level A: minimum requirements. Level AA: the standard referenced by most laws globally (ADA; EAA; AODA; ADA; RPWD India; etc.) — AqNova's target. Level AAA: the highest level; not AqNova's current target but reviewed for individual criteria.
Contrast Ratio	A measure of the difference in luminance between foreground (text or graphic) and background colors. WCAG 2.1 AA: minimum 4.5:1 for normal text; 3:1 for large text and UI components.
AT (Assistive Technology)	Any device; software; or equipment used by a person with a disability to improve functional capabilities. Examples: screen readers; screen magnifiers; voice recognition software; switch access devices; Braille displays.

Appendix C — Version History & Approval Log

Version	Date	Summary	Approved By
1.0	June 2026	Initial release. AqNova REACH Framework (5 principles: Rights-Based Approach; WCAG 2.1 AA Everywhere; Accountable Improvement; Compatible with Assistive Technology; Help and Reporting). Statement covers: Vendor Portal; Vendor Mobile App (iOS/Android); API docs; vendor emails; vendor PDFs; Vendor Support Center; third-party embedded tools. Conformance: WCAG 2.1 Level AA partial conformance; EN 301 549 v3.2.1 alignment; WCAG 2.2 gap analysis complete; upgrade target Q4 2026. WCAG 2.1 AA implementation table: all 50 AA success criteria (20 Perceivable; 17 Operable; 10 Understandable; 4 Robust) with Vendor Portal implementation detail including mobile-specific criteria (1.3.4 Orientation; 2.1.4 Character Key Shortcuts; 2.5.1-2.5.4 WCAG 2.1 Pointer/Motion criteria). Accessibility features: Vendor Portal (keyboard; screen reader; contrast; resize; reflow; focus; form; alt text; language; PDF; session timeout); Mobile App (VoiceOver; TalkBack; Dynamic Type; Switch Access; Reduce Motion); Email (HTML; plain-text; large print alternative on request; BSL/ASL video relay). Global legal compliance table: 30 rows across 8 regions (North America: ADA Title III + DOJ guidance; California Unruh; NY NYCHRL; Canada ACA; Ontario AODA EXCEEDS; BC; Québec PLANNED Q3 2026; EU: EAA Directive 2019/882 effective June 2025; EN 301 549; UK: Equality Act 2010 §29; Germany BFSG; France RGAA 4.1; EU states PLANNED June 2025; Middle East: UAE; Saudi Arabia; Israel IS 5568 EXCEEDS; Africa: Nigeria DAPDA; South Africa PEPUDA/SANS EXCEEDS; Kenya; Asia: India RPWD Act; Japan JIS X 8341-3; South Korea KWCAG 2.1; China GB/T 37668 EXCEEDS; Singapore; APAC: Australia DDA; NZ Human Rights Act; LATAM: Brazil LBI/ABNT NBR 17060; Mexico; Colombia NTC 5854 EXCEEDS; Argentina/Chile/Peru). 6 known non-conformances: Analytics Dashboard charts (Q3 2026); legacy PDFs (Q4 2026); DHL tracking widget (Q3 2026 — interim alternative available); Android app labels (v1.2 August 2026); video audio descriptions (Q4 2026); session timeout focus management (Q3 2026). Roadmap: Q3 2026 (non-conformances 1/3/6; third-party audit; VPAT 2.5; WCAG 2.2 implementation begins); Q4 2026 (non-conformances 2/4/5; French Vendor Portal; WCAG 2.2 conformance; second audit); 2027 Q1-Q2 (multi-language VP; full WCAG 2.1 AA target; WCAG 2.2 formal conformance; accessibility user research program). Reporting: email accessibility@aqnovamarketplace.com; Vendor Portal form; live chat; phone callback; BSL/ASL video relay (UK/US). Response: 2BD acknowledgment; 5BD substantive response; 1BD interim accommodation for critical blockers. Enforcement authorities: 14 jurisdictions listed. Assistive technology matrix: 12 AT combinations. 13-term glossary. Audit cycle: quarterly automated; annual third-party.	CCRO (Ronke Olatoye) + Head of Product / Ubon Isang (CEO)

AqNova Marketplace | Arivon Holding Corporation | EIN: 41-3210066

Accessibility Contact: accessibility@aqnovamarketplace.com | Response: 5 Business Days

Required under: EU EAA (2019/882) · UK Equality Act 2010 · US ADA · Canada AODA · EN 301 549 · 20+ Global Jurisdictions

Vendor Accessibility Statement

Overview

STATEMENT

SECTION 1 — Foundation — The REACH Framework & AqNova's Accessibility Commitment ................. 3

SECTION 2 — Technical Standards — WCAG 2.1 AA Implementation (All 50 Success Criteria) ............. 8

SECTION 3 — Accessibility Features — Vendor Portal, Mobile App & Email .................................. 22

SECTION 4 — Global Legal Compliance — 30+ Rows Across 8 Regions ....................................... 28

SECTION 5 — Known Non-Conformances, Remediation Plan & Improvement Roadmap .......................... 42

SECTION 6 — How to Report an Accessibility Issue — Channels & Response Commitments ................... 48

SECTION 7 — Formal Complaints, Legal Escalation & Enforcement Contacts by Jurisdiction ............... 53

1.1 AqNova's Accessibility Philosophy

1.2 Scope of This Statement

1.3 Conformance Status

2.1 WCAG 2.1 AA — The Four Principles (POUR)

PERCEIVABLE — Information and User Interface Components Must Be Presentable to Users

OPERABLE — User Interface Components and Navigation Must Be Operable

UNDERSTANDABLE — Information and User Interface Must Be Understandable

ROBUST — Content Must Be Interpretable By Current and Future User Agents

3.1 Vendor Portal Accessibility Features

3.2 Vendor Mobile App Accessibility Features (iOS & Android)

3.3 Accessible Email Communications

5.1 Known Non-Conformances as of June 2026

5.2 Continuous Improvement Roadmap

5.3 Testing Methodology

6.1 Reporting an Accessibility Issue

6.2 What to Include in an Accessibility Report

6.3 AqNova's Response Commitments

7.1 If Our Response Is Not Satisfactory

7.2 Enforcement Authorities by Jurisdiction

Appendix A — Assistive Technology Compatibility Matrix

Appendix B — Accessibility Glossary

Appendix C — Version History & Approval Log

Items (0)

Your Shopping Bag Is Empty