Accessibility Statement

Last updated: September 2, 2026

We treat the accessibility of this site as part of the service, not an add-on to it. This page sets out the standard meduxa.ai is built to, what is actually accessible on it, the limitations we still know about, and how to report a problem so we can fix it.

1. The standard this site is built to

The site follows Israeli Standard IS 5568, "Web content accessibility guidelines", at conformance level AA. That standard adopts the W3C's WCAG 2.0 guidelines. This statement is written in the spirit of Israel's Equal Rights for Persons with Disabilities Regulations (Service Accessibility Adjustments), 5773-2013.

This is a marketing site only: it has no sign-up, no user accounts and no payment flow. The product itself is in pilot and is not served from this site; when it opens to the public, this statement will be re-examined against it.

2. What is accessible

These have been checked and work:

• Full keyboard operation. Everything that can be clicked can also be reached with Tab and activated with Enter or Space — including the four answers in the demo card, the reply chips and send control, the expand-explanation button, and the nine "science of learning" cards.
• A visible focus indicator on every interactive element, so it is always clear where the keyboard is.
• A skip-to-content link at the top of every page, revealed on the first Tab press, which jumps past the navigation.
• Semantic structure. Landmark regions (nav, main, footer), a hierarchical heading order, and either a text alternative or a decorative marking on every piece of graphics.
• Colour contrast. Every text colour on the site has been computed against the background behind it and meets at least 4.5:1 for normal-size text.
• Reduced-motion preference honoured. For visitors whose operating system requests prefers-reduced-motion, the background video at the top of the page is not shown at all and animations stop.
• The background video is completely silent, carries no information, and is marked decorative so screen readers skip it. Nothing on the site starts playing sound on its own.
• Right-to-left Hebrew is genuine — the Hebrew page is authored RTL from the start, not a mirrored Latin layout.
• Responsive layout and zoom. The page stays readable and operable at up to 200% text zoom and on narrow phone screens, without horizontal scrolling.
• Labelled forms. The email field and the consent checkbox both have associated labels, and success or failure is reported in text rather than by colour alone.
• No pop-ups, no banners covering the content, and no time limit on any action.

3. How it was checked

The most recent check was carried out on September 2, 2026 by the development team. It covered a full keyboard pass over every page, a computed contrast check of every text colour against its background, and a review of the semantic structure and landmark regions.

The site has not yet been audited by a certified accessibility professional, so this statement describes a self-assessment rather than external certification. We intend to complete such an audit, and this page will be updated to reflect what it finds.

4. Limitations we know about

These are the gaps we are aware of. They are listed so you know what to expect, not as an excuse — each is on the fix list:

• English terms inside Hebrew text are not marked with their language. On the Hebrew page, terms such as KDIGO or AKI sit inside Hebrew sentences without a separate language marking, so a screen reader may pronounce them with Hebrew phonetics. This is a deviation from the level AA "language of parts" requirement.
• The "science of learning" cards open on hover as well as on click or keypress. The content is reachable either way, but that combination may behave unpredictably in some browser and screen-reader pairings.
• AI tutor replies are generated live, so their sentence length and reading level are not reviewed in advance. They are capped in length, but they are not edited before being shown.
• The reference links at the end of the science section lead to external academic sites. Their accessibility is outside our control and rests with whoever operates them.

5. Accessibility arrangements for the service

The service is delivered entirely online. We have no office or branch that receives the public, so there are no physical accessibility arrangements to declare. Every enquiry is received and handled by email.

6. Reporting an accessibility problem

If you have run into a page, control or piece of content you could not use, please tell us — even if it seems small. A report like that is the fastest way we have of learning that something is broken.

Write to: privacy@meduxa.ai

To help us reproduce the problem, it is useful to have the page address, a short description of what did not work, and — if you know them — the browser, operating system and assistive technology you were using. We will get back to you as quickly as we can, and no later than 30 days from receiving your message.

7. Updates to this statement

This statement is re-examined on any substantive change to the site, and at least once a year. The date it was last updated appears at the top of the page.

→ Back to home · Privacy Policy · Terms of Use