Accessibility Statement

Last updated: September 27, 2026

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

1. The standard, and what this statement covers

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

It covers both parts of the service: the information site meduxa.ai, and the learning app app.meduxa.ai — sign-up and sign-in, practice, mock exams, daily review, the question map, the AI tutor, and buying a subscription.

2. What is accessible

These have been checked and work.

In the learning app

• Full keyboard operation. Every button, field, drop-down and answer option can be operated with Tab, Enter and Space. The first Tab reveals a "Skip to main content" link that jumps past the navigation menu.
• A visible focus indicator on every button, field and drop-down.
• Screen-reader support. Navigation and content regions are marked, every field and drop-down has a label, and pop-up windows are marked as titled dialogs.
• Answer results are not conveyed by colour alone. After you answer a question, the screen reader announces whether you were right and which answer is correct, and each option is labelled in text as "correct answer" or "your answer — incorrect".
• No mandatory time limit. Every mock exam can also be taken in "untimed" mode.
• Five interface languages (Hebrew, English, Arabic, Russian and French), each with its correct writing direction — right-to-left or left-to-right — and the page language declared to the browser and screen reader.
• Dark and light modes, switchable at any time.
• Zoom and small screens. The interface can be zoomed and adapts to phones, and on a phone the side menu, when closed, is removed from the keyboard order entirely.

On the information site

• 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 chips and send button for the tutor, the expand-explanation button and the nine "science of learning" cards.
• A visible focus indicator on every interactive element, and a skip-to-content link at the top of every page.
• Semantic structure. Landmark regions (nav, main, footer), a hierarchical heading order, and either a text alternative or a decorative marking for every graphic.
• Colour contrast. Text and button colours meet at least 4.5:1 for normal-size text, and links inside running text are underlined rather than distinguished by colour alone.
• 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.
• Responsive layout and zoom. Pages stay readable and operable at up to 200% text zoom and on narrow phone screens, without horizontal scrolling.
• Labelled forms, with success or failure reported in text rather than by colour alone. No pop-ups cover the content, and no action has a time limit.

3. How it was checked

The most recent check was carried out on September 27, 2026 by the development team. It covered an automated scan of every site page and of the app's screens against the WCAG level A and AA rules, at desktop and phone widths; a full keyboard walk-through; and a check of what a screen reader receives while answering a question.

No audit by a certified accessibility professional has been carried out yet, and no full test by a screen-reader user has been done. This statement therefore describes a self-assessment, not external certification. We intend to commission such an audit and will update this page with its findings.

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:

• Image-based questions (renal pathology, urine sediment). The image is the question itself, so its text alternative identifies it as the question image without describing the findings — a description would give the answer away. Someone who cannot see the image will not be able to answer these questions; they are grouped in separate topics and on the "image exams" screen, and you can practise without them.
• English terms inside Hebrew text are not marked with their language. Terms such as KDIGO or AKI appear inside Hebrew sentences — on the site and in the questions themselves — without a separate language marking, so a screen reader may pronounce them with Hebrew phonetics. This departs from the AA "language of parts" requirement.
• The AI tutor's replies are generated in real time. Screen readers do not read them out automatically while they are being written; you need to navigate to them. Their sentence length and wording are not reviewed in advance; they are length-limited, but not edited before being shown.
• The "science of learning" cards on the site open both on mouse hover and on click or keyboard. The content is reachable either way, but the combination may behave unexpectedly with some browser and screen-reader pairings. The reference numbers inside the cards are visual pointers only; the sources themselves are ordinary links in the list below the cards.
• External services. The payment provider's checkout page, sign-in with Google and the academic source links lead to sites we do not control, and their accessibility is the responsibility of their operators.

5. Accessibility arrangements for the service

The service is provided 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 came across a page, screen, component or piece of content you could not use, please write to us — even if it seems minor. That is the fastest way for us to learn about a problem.

Contact: privacy@meduxa.ai

To help us reproduce the problem, please include the page address or screen name, 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 soon as possible, and no later than 30 days after receiving your message.

7. Updates to this statement

This statement is reviewed after every significant change to the site or the app, and at least once a year. The date of the last update appears at the top of the page.

→ Back to home · Privacy Policy · Terms of Use