Accessibility Statement.

Our Commitment

RobotCare, LLC is committed to ensuring that robothealthpassport.app is accessible to as many people as possible, including people with disabilities. This commitment applies to the visual, motor, auditory, and cognitive accessibility of the Site and its content.

Accessibility is an ongoing priority, not a one-time project. As we build and revise the Site through pre-launch and into general availability, we integrate accessibility into design, development, and content decisions rather than treating it as an afterthought.

Because the humanoid robot economy is an inclusive economy by design, including operators, technicians, investors, and educators of many backgrounds, RobotCare's commitment to accessibility extends beyond compliance. We want the Site to be genuinely usable.

Conformance Target

Our target conformance standard is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the World Wide Web Consortium (W3C) in October 2023 and currently the most recent stable version of the guidelines. We design and implement with WCAG 2.2 AA success criteria in mind across the four guideline categories: Perceivable, Operable, Understandable, and Robust.

WCAG 2.2 adds nine success criteria to the WCAG 2.1 baseline, with a focus on users with cognitive or learning disabilities, users with low vision, and users on mobile and touch devices. Criteria we actively apply include 2.4.11 Focus Not Obscured (Minimum), 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum), and 3.3.8 Accessible Authentication (Minimum).

Because 2.2 is a superset of 2.1, conformance with 2.2 AA means conformance with 2.1 AA as well. This matters for alignment with regional regulations, such as the EU harmonized standard EN 301 549, that currently reference WCAG 2.1 AA. We also monitor the draft WCAG 3.0, in early working-draft status, to understand where the guidelines are headed next.

Scope of This Statement

This Accessibility Statement applies to the public-facing website at robothealthpassport.app, including all pages served under that domain as of the effective date above.

It does not apply to:

• Third-party services linked from the Site, including external OEM product pages, standards body references, research sources, content delivery networks, and analytics providers. These operate under their own accessibility policies.
• The user interface of third-party embedded components, including the GTranslate language selector and any analytics or form-embed widgets. We apply reasonable pressure on vendors to meet accessibility standards but do not control their implementation.
• Documents provided for download, such as PDFs generated by the HR IV™ sample report tool, which are noted in section 6 as a known limitation with a remediation target.
• Private, authenticated areas of the Site that do not yet exist at pre-launch, including any future CHRT™ technician sign-in or Robot Health Passport™ fleet operator dashboards. These will be covered by an updated statement at general availability.

The scope of this statement will expand as the Site expands. It will be reviewed at or before the general availability launch in Q3 2026 and updated to reflect the production platform.

Current Accessibility Practices

The following practices are implemented on pages built under our current accessibility commitment. Where a practice is universal across the Site, it is marked accordingly.

Structural and semantic

• Semantic HTML landmarks. Pages use <header>, <nav>, <main>, and <footer> landmarks with explicit roles where appropriate, allowing assistive-technology users to navigate between regions.
• Proper heading hierarchy. Each page has one <h1> and a logical <h2> / <h3> outline that reflects content structure, so screen reader users can navigate by heading.
• Skip-to-main-content link. A keyboard-focusable "Skip to main content" link is the first interactive element on each page, allowing keyboard and screen-reader users to bypass repetitive navigation.
• Language declared. The document language is declared at the page root so assistive technology can pronounce content correctly.

Visual and perceptual

• Color contrast meeting or exceeding AA ratios. Body text, interactive elements, and meaningful icons meet the WCAG 2.2 AA minimum contrast of 4.5:1 for normal text and 3:1 for large text. Primary body text uses near-black ink on cream for ratios above 15:1.
• Color is not the only cue. Links are underlined, not just colored. Status indicators pair color with icons, text, or position. Charts label series with text, not color alone.
• Responsive typography. Text sizes use relative units and remain readable at common zoom levels (up to 200%) and when user font sizes are increased.
• Alternative text. Images that convey information include alt text. Decorative images and characters are marked aria-hidden or use empty alt attributes so screen readers skip them.

Keyboard and interaction

• Keyboard-navigable interfaces. All interactive elements (links, buttons, form fields, sliders, tabs) can be reached and operated with a keyboard.
• Visible focus indicators. Keyboard focus is indicated by a high-contrast gold outline with offset, so the current focus target is always obvious.
• Form labels and instructions. Form fields have associated labels. Where a field has specific format or constraint requirements, the requirements are provided next to the field, not inside the field as placeholder-only text.

Technical Specifications and Compatibility

The Site is built using standards-based HTML, CSS, and JavaScript. Accessibility relies on the interaction between the Site, your web browser, and any assistive technologies you use.

We aim to support recent versions (current release and one prior major version) of:

• Browsers: Chrome, Safari, Firefox, Microsoft Edge, on Windows, macOS, iOS, and Android.
• Screen readers: NVDA, JAWS, VoiceOver (macOS and iOS), and TalkBack (Android).
• Input methods: Keyboard only, mouse, touch, voice control (Dragon, Voice Control, Voice Access), and switch access.

Some interactive features, including our HR IV™ Calculator and Chart.js visualizations, rely on JavaScript. We strive to ensure that the primary information conveyed by these features is also available in text form below the interactive element. If you experience difficulty with an interactive feature, please contact us as described in section 8.

Known Limitations

We are committed to transparency about areas where the Site does not yet fully meet our WCAG 2.2 AA target. The following limitations are known and on a remediation schedule.

• Legacy link contrast on older pages. Earlier RHP pages use a lighter cadet tone for hyperlinks that falls just below the WCAG AA 4.5:1 threshold on cream backgrounds. Remediation is underway; legal pages (Privacy, Terms, Accessibility) already use the higher-contrast cadet-deep value.
• Third-party widgets. The GTranslate language selector is implemented by a third-party provider whose widget accessibility sits outside our direct control. We are evaluating alternatives.
• Downloadable PDF reports. PDFs generated by the HR IV™ sample report tool (via client-side jsPDF) are not yet tagged for full screen-reader accessibility. At general availability, production HR IV™ Reports will ship as tagged PDFs meeting PDF/UA where feasible, or as accessible HTML alternatives.
• Complex visualizations. The architecture diagram on the Architecture page and the five-year cumulative chart on the Calculator page provide visual information. Text alternatives accompany each, but we are working to improve the richness and precision of those alternatives.
• Video and audio. The current Site does not publish substantive video or audio content. If and when it does, we will apply captions, transcripts, and audio descriptions as required.

If you encounter a barrier not listed above, please let us know using the feedback channel in section 8.

How We Assess Conformance

We apply the following methods to assess and improve accessibility of the Site:

• Self-assessment. Pages are reviewed by the team against the WCAG 2.2 AA success criteria at publication and again on material revisions.
• Automated testing. Accessibility linting tools are used during development to flag issues such as missing alt text, incorrect heading order, insufficient color contrast, and missing form labels. Automated tools catch roughly 30-40% of accessibility issues; the rest require human review.
• Keyboard and screen-reader testing. Key pages are tested using keyboard-only navigation and with a screen reader (VoiceOver or NVDA) to verify that functional and informational content is reachable and understandable.
• User feedback. Reports from Site users through the feedback channel described in section 8 inform our priority list for remediation.
• External review. At or before general availability in Q3 2026, we intend to engage a third-party accessibility auditor to conduct a formal WCAG 2.2 AA conformance audit across the production platform.

Feedback and Barrier Reporting

If you encounter an accessibility barrier on the Site, or if information on the Site is not available to you in a format you can use, please contact us. We want to hear from you.

How to report a barrier

Email ken@robotcare.app with "Accessibility" in the subject line. To help us respond quickly, please include:

• The URL of the page where you encountered the barrier;
• A description of the barrier (for example: "the focus indicator disappears on this button", "the screen reader does not announce this field's label", "text and background don't meet contrast");
• The browser, operating system, and assistive technology you are using, if applicable;
• Your preferred way for us to follow up with you.

Our response commitment

We aim to acknowledge accessibility reports within five (5) business days. Where a barrier can be fixed promptly, we will fix it and let you know. Where a barrier cannot be fixed immediately, we will explain what we can do, including providing the information you need in an alternative format at no cost.

Alternative formats

If any information on the Site is not accessible to you and cannot be made accessible immediately, we will work with you to provide the information in an alternative format that meets your needs. This service is provided at no cost and without requiring a formal request process.

Applicable Laws

Our accessibility commitment aligns with the following laws and regulations where they apply to our activities:

• Americans with Disabilities Act (ADA), United States. Title III of the ADA has been interpreted by US courts to apply to the websites of places of public accommodation. While RobotCare is pre-revenue, we design the Site to support ADA Title III accessibility expectations.
• Section 504 of the Rehabilitation Act, United States. Applies to programs and activities receiving federal financial assistance and to federal agencies. Not currently applicable to RobotCare directly but informs our standard.
• Section 508 of the Rehabilitation Act, United States. Sets accessibility standards for US federal agencies. Not applicable to RobotCare directly but informs our standard. The 2017 Revised Section 508 Standards incorporate WCAG 2.0 Level AA by reference for web content, and the US Access Board has signaled future updates toward more current WCAG versions.
• European Accessibility Act (EAA), European Union. Effective June 28, 2025. Establishes accessibility requirements for certain products and services sold to EU consumers, including websites providing e-commerce and banking services. We track our obligations under EAA as the Site evolves from pre-launch marketing into a public registry and report-delivery service.
• Unruh Civil Rights Act and California Disabled Persons Act. Apply to California business practices and have been applied to inaccessible websites.
• Ontario Accessibility for Ontarians with Disabilities Act (AODA), European Union Web Accessibility Directive, and similar regional regulations. The EU harmonized standard EN 301 549, referenced by both the Web Accessibility Directive and the European Accessibility Act, currently includes WCAG 2.1 Level AA. Our target of WCAG 2.2 AA is a superset of 2.1 AA, so conformance with 2.2 AA meets or exceeds the baseline referenced by most current regional regulations.

This list is not exhaustive, and changes in applicable law over time will be incorporated in future updates of this statement.

Formal Complaints

If you have reported an accessibility barrier through the feedback channel in section 8 and are not satisfied with our response, you may have the right to pursue a formal complaint under applicable law. Options include:

• In the United States: Filing an ADA complaint with the US Department of Justice Civil Rights Division (ada.gov), or filing a complaint with the US Access Board (access-board.gov) for issues covered by Section 508.
• In the European Union: Filing a complaint with the national enforcement authority designated under the European Accessibility Act or the Web Accessibility Directive in your member state. The European Commission maintains a public list of national monitoring, reporting, and enforcement bodies for each EU member state.
• In other jurisdictions: Contacting the human rights, equality, or disability rights authority with jurisdiction over digital services in your region.

We hope we never reach this stage. The fastest path to a fix is usually a direct email to us describing the problem.

Contact Us

For any accessibility concern, barrier report, or request for information in an alternative format, please use the contact below.

This statement was prepared with reference to the W3C guidance on creating and maintaining accessibility statements, including the W3C Web Accessibility Initiative's model statement. We expect to review and update this statement at least annually, and at or before general availability of the Robot Health Passport™ registry in Q3 2026.