MilEats Accessibility Statement

Version: v1.0 · Effective date: May 24, 2026 · Last updated: April 21, 2026 · Next review: within 90 days post-launch (after third-party audit)

MilEats is committed to making its digital services usable by everyone, including people with disabilities. This statement describes how we work toward that goal, where we currently stand against the international standard, and how to reach us if you encounter a barrier.

1. Our commitment

MilEats believes that the people who serve and support our military communities deserve a delivery service that works for everyone. We design, build, and maintain our products with accessibility as a default consideration, not an afterthought.

We work toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, the international standard for digital accessibility published by the World Wide Web Consortium (W3C). We treat accessibility as an ongoing program, not a one-time project.

2. Scope of this statement

This statement covers the following MilEats products and services:

When a new property launches, this statement will be updated within 5 business days to include the property and its current conformance status.

This statement does not cover:

• Third-party services accessed through our products (such as Stripe payment forms or Auth0 login pages). Those services are governed by their own accessibility commitments.
• Content created by users (customer reviews, restaurant menus uploaded by partners). We provide accessible structures for that content but cannot guarantee its accessibility.
• Pages or features in beta, preview, or limited release. Those will be brought into scope as they reach general availability.

3. Conformance status

Self-assessed conformance: Partially Conforms with WCAG 2.2 Level AA.

"Partially Conforms" means most content meets the standard, but some parts of the content do not yet fully conform. This is the W3C-defined term for our current state.

Why "Partially Conforms"

We have built mileatsdelivery.com to WCAG 2.2 AA where reasonably achievable. We have not yet completed a third-party accessibility audit. Until that audit is complete, we cannot claim "Fully Conforms," and we are honest about that.

Third-party audit, scheduled

We have committed to completing a third-party accessibility audit of mileatsdelivery.com within 90 days of launch (May 24, 2026). The audit will be conducted by a qualified, independent accessibility evaluator. The audit will produce a written report identifying any Level A or AA conformance issues. We will:

• Update this statement within 30 days of receiving the audit report to reflect the verified conformance status (Fully Conforms, Partially Conforms with specific remaining issues, or Does Not Conform).
• Address Level A and AA issues per the remediation timeline in §7 below.
• Publish a redacted summary of the audit's findings on request.

Mobile apps

Each mobile app (Customer, Rider, Partner) will receive a separate self-assessment when it launches and a third-party audit within 90 days of its public launch.

4. Standards and assessment approach

Standard

We measure ourselves against WCAG 2.2 Level AA, published by the W3C Web Accessibility Initiative. WCAG 2.2 includes the four foundational principles:

• Perceivable. Information and user interface components must be presentable in ways users can perceive.
• Operable. Components and navigation must be operable by everyone.
• Understandable. Information and operation of the interface must be understandable.
• Robust. Content must be robust enough to be interpreted reliably by user agents, including assistive technologies.

Assessment methods

We assess accessibility using a combination of:

• Automated testing. axe DevTools, Lighthouse, and Pa11y run as part of our build and deployment pipeline. Automated tests catch about 30 to 40 percent of common WCAG issues.
• Manual code review. Our engineering and design teams review pull requests for accessibility-affecting changes (semantic HTML, ARIA usage, keyboard handling, color contrast).
• Manual functional testing. We test new features with keyboard-only navigation and with screen readers (VoiceOver on macOS and iOS, TalkBack on Android, NVDA on Windows).
• Third-party audit. Scheduled within 90 days of launch (see §3).
• User feedback. Reports from users (see §6) inform ongoing work.

5. Compatibility

We design our products to work with the following user agents and assistive technologies:

Browsers (web)

• The current and immediately previous major versions of Chrome, Safari, Edge, and Firefox.
• iOS Safari and Android Chrome on the current and immediately previous major OS versions.

Assistive technologies

• Screen readers: VoiceOver (macOS, iOS), TalkBack (Android), NVDA and JAWS (Windows).
• Magnification: native OS magnifiers, ZoomText.
• Voice control: Voice Control (macOS, iOS), Voice Access (Android), Dragon NaturallySpeaking (Windows).
• Keyboard-only navigation: standard keyboard, switch devices via OS-level switch control.

If you use a different assistive technology and find a barrier, please tell us (see §6). We will document compatibility with additional tools over time.

Technical specifications

Our web products use:

• HTML5 (semantic).
• CSS3 (responsive, scalable units).
• JavaScript (progressive enhancement where feasible).
• WAI-ARIA where native semantics are insufficient.

Our mobile apps use:

• iOS: Swift and React Native via Expo, with VoiceOver and Dynamic Type support.
• Android: Kotlin and React Native via Expo, with TalkBack and font-scale support.

6. Feedback

We welcome feedback on the accessibility of our products. If you encounter a barrier, please tell us. Your feedback helps us improve.

How to reach us

When you contact us, please include:

• The product or page where you encountered the barrier (URL, app screen, or feature name).
• The assistive technology or browser you were using.
• A description of what you were trying to do and what happened.
• Your contact information so we can follow up (optional, but helpful).

Response commitments

We do not require you to be a MilEats user, customer, rider, or partner to submit accessibility feedback. Anyone can report.

If our response is not satisfactory

If you are not satisfied with our response, you may:

• Reply to our acknowledgement and explain what you need.
• Email legal@mileatsdelivery.com to escalate.
• Contact a federal or state authority. The U.S. Department of Justice handles ADA Title III complaints (ada.gov). Many states also have civil-rights or human-rights agencies that handle accessibility complaints for state-jurisdiction matters.

7. Remediation timelines

When we receive a credible report of an accessibility barrier (or identify one ourselves), we triage by severity and commit to the following timelines:

If we cannot meet a target for a specific issue (for example, a fix requires a third-party vendor to update their SDK), we will notify the reporter with the new estimated timeline and the reason for the delay.

8. Known limitations

We list known accessibility limitations here so users can plan around them and so we can hold ourselves accountable to fix them.

mileatsdelivery.com (as of v1.0 publication)

Anticipated areas of focus based on the platform's current implementation:

• Map interactions for screen-reader users. Live order tracking via interactive maps is challenging to make fully accessible. We will provide text-based alternatives for delivery status updates.
• Live order-status updates. ARIA live regions are used for important updates; we will validate that they are not over-announcing or under-announcing.
• Third-party embedded content. Stripe Elements (payment) and Auth0 (login) are embedded into our checkout and login flows. We rely on those vendors' accessibility and provide direct contact channels with them for users who hit a barrier.

This list will be updated to reflect actual findings within 30 days of the third-party audit.

Mobile apps

To be populated when each app launches.

9. Standards and law

We aim to meet or exceed the requirements of:

• WCAG 2.2 Level AA, the international standard.
• Americans with Disabilities Act (ADA) Title III, which applies to public accommodations in the United States. WCAG 2.1 / 2.2 AA is the de facto standard for ADA Title III compliance for digital products under U.S. Department of Justice guidance.
• California Unruh Civil Rights Act and similar state-level civil rights laws.
• EN 301 549 (the European harmonized accessibility standard) where it applies.

We do not currently contract with the U.S. federal government; if we do in the future, we will conform to Section 508 as required.

10. Date this statement was prepared

This statement was prepared for publication on May 24, 2026, by MilEats. It will be reviewed:

• Within 30 days of the third-party audit completion.
• When any new property is added to scope (mobile apps).
• At least annually thereafter.
• Whenever a material change to a covered product creates new accessibility considerations.

The current version is v1.0. Prior versions, when they exist, will be archived at mileatsdelivery.com/legal/accessibility/archive/v{n}.

11. Contact

Accessibility feedback Email: accessibility@mileatsdelivery.com Postal: MilEats LLC, 254 Chapman Rd, Ste 208 #23094, Newark, DE 19702, United States

Legal escalation Email: legal@mileatsdelivery.com

Privacy-related accessibility (DSR) Email: privacy@mileatsdelivery.com · Webform: mileatsdelivery.com/legal/dsr

Change log