Accessibility Statement

---

1. Our Commitment

Wildwood Works believes that access to software should not depend on how a person sees, hears, moves, or processes information. We treat accessibility defects the same way we treat any other defect: they are logged, prioritised, and fixed. Accessibility is an ongoing effort rather than a finished state, and this statement is written to be honest about where we are today.

2. Scope of This Statement

This statement applies to:

• The Wildwood public website at wildwoodworks.io, including the marketing, pricing, legal, and documentation pages
• WildwoodAdmin, the authenticated administration portal at admin.wildwoodworks.io
• The user-facing UI components Wildwood publishes for customers to embed in their own applications (React, React Native, Blazor, Razor, and Swift)

It does not cover applications built by customers on top of the Platform. Each customer is responsible for the accessibility of the application they ship — see Section 8.

3. Conformance Status

Our target conformance standard is the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium. WCAG 2.1 Level AA is the benchmark generally referenced for compliance with the Americans with Disabilities Act ("ADA") and is the standard incorporated by Section 508 of the Rehabilitation Act.

The Wildwood API Platform is currently partially conformant with WCAG 2.1 Level AA. "Partially conformant" means that most of the standard is met, but some content or interactions do not yet fully conform. The gaps we are aware of are listed in Section 7. We do not claim full conformance, and we do not claim certification by any third party.

4. Measures We Take

To keep accessibility part of how the Platform is built, Wildwood Works:

• Treats WCAG 2.1 Level AA as the acceptance bar for new user-facing screens and components
• Builds on semantic HTML and standard, keyboard-operable controls rather than custom widgets wherever a native element will do the job
• Reviews colour contrast when themes and palettes change
• Includes accessibility in design and code review for user-facing changes
• Accepts accessibility reports through the same channels as any other defect, and tracks them to resolution

5. Accessibility Features

Features currently available across the Platform's own interfaces include:

• Keyboard operation — navigation, forms, dialogs, and menus are reachable and operable with a keyboard alone
• Semantic structure — headings, landmarks, lists, and labelled form controls so assistive technology can convey page structure
• Text alternatives — meaningful images carry alternative text, and decorative imagery is hidden from assistive technology
• Light and dark themes — selectable themes, including higher-contrast options, with contrast targets applied to text and interactive elements
• Resizable text and responsive layout — content reflows and remains usable when zoomed or viewed on small screens, without loss of function
• Visible focus — focus indicators on interactive elements
• Error identification — form errors are described in text, not by colour alone

6. Compatibility & Technical Specifications

The Platform is designed to work with current versions of major browsers — Chrome, Edge, Firefox, and Safari — on desktop and mobile, used together with the assistive technology available on those platforms, including screen readers, screen magnification, speech input, and operating-system accessibility settings.

Accessibility of the Platform relies on the following technologies:

• HTML
• CSS
• JavaScript
• WAI-ARIA, where a native HTML element cannot express the required role or state

Interactive areas of the administration portal are rendered server-side and kept in sync over a persistent connection, so JavaScript and an uninterrupted network connection are required for those screens to function. Where JavaScript is unavailable, informational and legal pages such as this one remain readable. Customer applications built with Wildwood components may additionally use WebAssembly or native mobile runtimes, depending on how the customer has built them.

7. Known Limitations

We are aware of the following gaps. They are recorded here rather than omitted, and each is on our remediation list:

• Data-dense administration screens — some analytics tables and charts in WildwoodAdmin do not yet expose a fully equivalent text alternative for the information conveyed visually
• Third-party embedded content — payment forms rendered by our payment provider, and CAPTCHA challenges rendered by their providers, are controlled by those third parties and may not meet our conformance target
• Documentation code samples — syntax-highlighted code blocks may present contrast or verbosity issues with some screen readers
• Customer-supplied content — text, images, and files uploaded by customers are outside our control; we cannot guarantee alternative text for content we did not author
• Older screenshots in documentation — some documentation screenshots predate our current alternative-text guidance

If you encounter a barrier that is not listed here, please tell us — see Section 10. Reports from users are the most reliable source of information we have.

8. Accessibility of Wildwood Components in Your Apps

Wildwood publishes prebuilt UI components (authentication, AI chat, messaging, payments, tiers, notifications, consent, and others) that customers embed in their own applications. We build these components against the same WCAG 2.1 Level AA target, with keyboard operability, labelled controls, and assistive-technology-friendly markup.

However, the accessibility of a delivered application depends on choices made by the customer who ships it — theme colours and contrast, surrounding page structure, heading order, custom CSS overrides, and any content supplied at runtime. Customers remain responsible for the accessibility of their own applications, including their obligations under the ADA and any other law that applies to them. Using Wildwood components does not, on its own, make an application conformant.

9. How We Assess Accessibility

Wildwood Works evaluates the accessibility of the Platform through:

• Self-evaluation — internal review of user-facing changes against WCAG 2.1 Level AA
• Manual testing — keyboard-only operation and screen-reader spot checks of primary flows such as sign-in, registration, and core administration tasks
• Browser tooling — accessibility inspection using the tools built into modern browsers. We are working towards automated accessibility checks running as part of our build; that coverage is not yet in place, and automated tools would in any case catch only a portion of accessibility issues
• User feedback — reports received through the channels below

The Platform has not been assessed by an independent third-party auditor. If that changes, we will say so here.

10. Feedback & Reporting a Barrier

We welcome reports of accessibility problems. If any part of the Platform prevents you from completing a task, please contact us and include:

• The page address or the screen where the problem occurred
• A description of the problem and what you were trying to do
• The browser, operating system, and any assistive technology you were using

You can reach us by email at [email protected] or through our contact page. Please put "Accessibility" in the subject line so the report is routed correctly.

We aim to acknowledge accessibility reports within 5 business days and to respond with either a fix or a remediation plan, including a target timeframe, within 30 days. Where a barrier prevents you from completing an essential task, tell us — we will work with you to provide the information or complete the task through an alternative channel while the underlying issue is fixed.

11. Formal Complaints & Legal Context

If you are not satisfied with our response to an accessibility report, you may escalate it to [email protected], and we will review the matter.

This statement is provided in the spirit of the Americans with Disabilities Act and Sections 504 and 508 of the Rehabilitation Act, and is modelled on the W3C's guidance for accessibility statements. It is a description of our practices and commitments; it is not a warranty of conformance, a legal certification, or an admission of liability, and it does not modify the Terms and Conditions.

12. Changes to This Statement

We review this statement at least annually and whenever we make significant changes to the Platform's user interface. The "Last Reviewed" date at the top of this page reflects the most recent review.

13. Contact Us

For accessibility questions, reports, or requests for an alternative format, contact us at:

• Accessibility & Support: [email protected]
• Escalation: [email protected]
• Contact form: wildwoodworks.io/contact
• Website: wildwoodworks.io