Draft for review. Wendel is pre-pilot and has not yet completed a third-party accessibility audit. This statement reflects the conformance targets the company has set and the controls implemented to date. A WCAG 2.2 AA audit by an independent firm is planned prior to general availability.
Wendel, Inc.

Accessibility Statement

Effective: May 14, 2026Last revised: May 14, 2026Version: 0.1 (draft)

§1Purpose and Scope

This Accessibility Statement (this "Statement") describes the commitments of Wendel, Inc. ("Wendel") to the accessibility of the Wendel platform (the "Services") for End Users with disabilities. It applies to the public marketing site at trywendel.com, the authenticated web application served at trywendel.com/app, and the Wendel iOS application (collectively, the "Properties").

§2Conformance Standard

Wendel targets conformance with the Web Content Accessibility Guidelines version 2.2, Level AA ("WCAG 2.2 AA"), published by the World Wide Web Consortium (W3C). Where the Properties incorporate functionality that is not addressed by WCAG 2.2, Wendel applies the analogous criteria of the most recent draft of WCAG 2.x or the EN 301 549 European harmonized standard, as applicable. The iOS application additionally targets conformance with the Apple Human Interface Guidelines for Accessibility.

§3Accessibility Commitments

Wendel commits to the following:
  1. treat accessibility as a feature requirement rather than a remediation activity, applied at the design and development stages;
  2. maintain accessibility as a non-negotiable acceptance criterion for new features;
  3. provide an accessible escalation path for End Users who encounter barriers;
  4. respond to accessibility feedback within five (5) business days and provide a remediation plan or workaround within twenty (20) business days;
  5. publish an Accessibility Conformance Report (in VPAT 2.4 format) once Wendel has completed an independent accessibility audit; and
  6. not introduce new features that would degrade existing accessibility conformance.

§4Accessibility Features Implemented

The Properties presently implement the following accessibility features:
  1. semantic HTML structure throughout the application, with landmarks, headings, and lists used appropriately to support assistive-technology navigation;
  2. visible focus indicators on all interactive elements;
  3. keyboard operability for all functionality that is operable through a mouse or touch interface;
  4. color contrast ratios meeting or exceeding 4.5:1 for normal text and 3:1 for large text and non-text interactive elements;
  5. respect for the user-agent prefers-reduced-motion media query, which disables non-essential animations, transitions, and view-transition effects;
  6. responsive layouts that reflow without horizontal scrolling at viewport widths from 320 CSS pixels upward;
  7. accessible names and roles on all custom controls, surfaced through ARIA attributes where native semantics are insufficient;
  8. support for the operating-system text-size setting (Dynamic Type on iOS and the analogous browser zoom on the web);
  9. error messages that identify the field at fault and describe how to correct the error in plain language; and
  10. support for screen readers, including VoiceOver on iOS and the most recent versions of NVDA and JAWS on Windows and VoiceOver on macOS.

§5Known Issues and Limitations

Wendel maintains a public register of known accessibility issues, updated as new issues are identified or existing issues are resolved. As of the Effective Date, the known limitations are:
  1. the calendar grid does not yet expose a fully accessible alternative view for screen-reader users; a list-format alternative is planned;
  2. certain marketing-page animations do not yet honor the prefers-reduced-motion media query; remediation is in progress;
  3. the NFC tap-to-check-in flow on iOS relies on a sound and haptic indicator that, while supplementary, is not yet accompanied by an equivalent on-screen confirmation for End Users who use external switch input.

The register is reviewed at least monthly. End Users encountering an issue not listed above are encouraged to report it pursuant to Section 10.

§6Third-Party Components

The Services incorporate certain third-party components for which Wendel does not directly control accessibility conformance, including (a) the Apple Wallet pass-rendering surface; (b) third-party identity-provider sign-in flows (such as Google and Microsoft); and (c) browser-native form controls. Wendel will publish the relevant third-party conformance statements when such statements become available and will use commercially reasonable efforts to provide accessible alternatives where a third-party component is the sole source of an accessibility barrier.

§7Testing Methodology

Wendel evaluates the Properties for accessibility conformance through a combination of (a) automated scanning using axe-core, integrated into the continuous-integration pipeline; (b) manual testing with screen readers and keyboard-only navigation by Wendel personnel trained in accessibility evaluation; and (c) periodic third-party audits. Pull requests that fail automated accessibility checks are not merged absent a documented exception.

§8Generated Documents and PDFs

The Services generate certain artifacts on behalf of Schools and End Users, including the involvement-record export, Apple Wallet passes, and printable rosters. Wendel commits that all such generated artifacts will be (a) tagged with appropriate structure for assistive technology where the artifact format supports such tagging (e.g., PDF/UA-conforming PDFs); (b) accompanied by an accessible web-format alternative where the artifact format does not support adequate tagging; and (c) tested with the relevant assistive technology prior to inclusion in the production Services.

§9Section 504 / Title II / ADA Considerations

Wendel acknowledges that Schools subject to Section 504 of the Rehabilitation Act, Title II of the Americans with Disabilities Act, and the U.S. Department of Justice's 2024 Title II web-accessibility rule (28 C.F.R. Part 35) bear independent obligations to ensure that the digital services they procure are accessible. Wendel supports each School's compliance by (a) furnishing the Accessibility Conformance Report described in Section 3upon request; (b) cooperating with the School's accessibility coordinator on remediation matters; and (c) prioritizing remediation of any barrier that prevents a specific End User from accessing the educational benefits of the Services on the same basis as their peers.

§10Feedback and Remediation Requests

End Users, Schools, parents, and members of the public who encounter an accessibility barrier are encouraged to report it to accessibility@trywendel.com. Reports should include, where possible, (a) the URL or screen at issue; (b) the assistive technology in use; (c) the operating system and browser version; and (d) a description of the barrier encountered and the expected behavior. Wendel will acknowledge receipt within five (5) business days and provide a remediation plan or workaround within twenty (20) business days.

§11Periodic Review

Wendel reviews this Statement and the underlying accessibility program not less than annually, and following any material change to the Properties or to the controlling conformance standard. Updates are reflected by revision of the "Effective" and "Last revised" dates at the head of this Statement.

§12Contact

Accessibility inquiries should be directed to accessibility@trywendel.com. Where confidential or expedited communication is required (for example, in connection with an Office for Civil Rights complaint), please indicate so in the subject line.
Wendel, Inc.
Attn: Accessibility
[Mailing address to be provided to Schools upon execution of a DPA]