Motion, photosensitivity and study interfaces

You open the clinical study app after your shift. The background slides in parallax, the welcome screen pulses, a rotating banner changes every two seconds and the start button "jumps" until you tap it. Within minutes your head feels heavy, your stomach reacts and your attention drifts away from the clues. It is not a lack of discipline. It is too much visual stimulation for a vestibular and visual system that was already tired. This text is about reducing motion, photosensitivity and the design of study interfaces: what animations, flashes and motion contrast do to people studying Medicine; what platforms should offer; and what you can adjust in the operating system and the browser. The post about digital accessibility in medical software covers the broad WCAG map and common failures. Here the focus is narrow: motion, flash and the reduce motion preference in games and clinical reasoning apps.

Nothing in this text claims that NEXO is effective. We describe visual safety principles, public criteria and features checked in the accessibility statement. If you or someone close to you has a seizure or intense discomfort linked to light or motion, seek the help you need. This article does not replace clinical assessment.

Key points

• Non-essential motion (parallax, autoplay, bounce) can cause nausea, dizziness, migraine and distraction; the problem is physiological, not "fussiness".
• Photosensitivity and striped patterns call for clear limits on flash frequency and area; the WCAG criterion of three flashes per second is the safety floor, not a ceiling on creativity.
• prefers-reduced-motion is a contract: the OS or the browser reports the preference; the app must respect it and offer local control when that makes sense.
• Clinical teaching designers should start from a quiet interface, optional animation and multimodal feedback without flash.
• In NEXO, the public accessibility statement includes respect for the reduce motion preference in the app; with no claim of learning outcome. Usage limits, when relevant, are in /economia.

Motion, attention and the body in the study session

Studying clinical reasoning already uses up working memory: reading clues, forming hypotheses, comparing with the differential and calibrating confidence. Cognitive load in health education calls for reducing what does not teach and preserving attention for what matters (van Merriënboer and Sweller, 2010; Mayer, 2010). Decorative animation competes for that budget. A carousel that changes on its own, a background that moves at a different speed from the text (parallax) or a "congratulations" confetti that fills the whole screen do not teach the differential. They pile up extraneous load.

There are two sides to the problem. The first is cognitive: continuous motion draws the eye and gets in the way of reading and memory retrieval. The second is sensorimotor: some people respond with dizziness, nausea, headache or disorientation when the visual scene suggests motion that the body did not confirm. The WCAG guidelines address both sides. The criterion to pause, stop or hide moving content that starts on its own and lasts more than five seconds exists for those who need to silence the screen. The criterion on animation from interactions (level AAA) asks that motion animation triggered by the user can be turned off, unless it is essential to the information (W3C, Understanding 2.3.3).

In a diagnosis game, the pedagogical unit is the clue and the hypothesis, not the effect. Fictional cases with a real clinical presentation, with up to six clues, call for a legible and stable screen. The post about differential diagnosis with clues and the one about case-based learning frame the practice. Here the warning is about the interface: if the clue "enters" with an aggressive slide on every tap, or if the code map shakes when you scroll, the design works against reasoning.

Compare two sessions. In the first, every action triggers a half-second transition, the score animates numbers and a background video loops silently. In the second, the screen changes state without shifting the background, proximity feedback uses color, icon and written name, and any optional movement starts paused. The second session is not "less modern". It is more respectful of those who study under fatigue, migraine or vestibular sensitivity. It engages with metacognition in medicine: you observe your own discomfort and adjust the environment before blaming "lack of focus".

In terms of cognitive load, non-essential animation works as noise in the same band as the clinical clue. You spend cycles deciding whether the moving element is information or decoration. In a short session with up to six clues, every lost cycle matters. That is why the quiet state is not minimalist aesthetics for fashion's sake: it is alignment with the load theory in health education cited above.

Vestibular and visual motion sensitivity

The vestibular system integrates information from the labyrinth, vision and proprioception to maintain balance and orientation. When vision suggests strong movement and the head is still, the sensory conflict can produce symptoms similar to motion sickness. In vestibular migraine, there is evidence of greater visual dependence and postural instability in the face of motion stimuli in the visual field (PMID 29930534). Prolonged exposure to visual motion in a wide field raised vestibular thresholds in patients with vestibular migraine compared with controls and other clinical groups (PMID 30759189).

Susceptibility to motion sickness appears associated with migraine and vestibular disorders in experimental protocols and in patient-centered measures (PMID 25118205). In a comparison between vestibular migraine, migraine without vertigo and controls, worse balance and greater motion sensitivity were observed in the vestibular group (PMID 32178946). In a student cohort, sickness sensitivity and vestibular migraine criteria overlapped with a frequency worthy of clinical attention (PMID 32501936). None of this diagnoses the reader through the screen. It serves as a reminder: parallax, scroll zoom and backgrounds that "breathe" are not neutral.

The WCAG documentation describes vestibular reactions to animation (dizziness, nausea, headache) and recommends avoiding unnecessary animation, offering control to turn off non-essential movement and respecting the system preference (Understanding 2.3.3). In study interfaces, the most common triggers are:

• Parallax and layers that move at different speeds as you scroll.
• Long transitions between clues or between result screens.
• Elements that float, vibrate or "breathe" in a loop.
• Automatic zoom or pan on clinical images without user control.
• Confetti, particles and full-screen achievement animations.

Those who design clinical material also need to think about those watching a recorded class or webinar with fast cuts and flashing bumpers. The same principle applies: movement in the service of understanding (for example, an arrow pointing to a finding) differs from movement in the service of marketing. The first can be short, local and pausable. The second can almost always go.

There is a frequent misunderstanding: "if I don't have epilepsy, flash and movement are not my problem". Distraction, migraine and visual sickness are already enough to degrade the quality of retrieval in a case session. The student who abandons the app after three nights of nausea does not show up in the "engagement" metric. They show up as silence. Designing for motion sensitivity is therefore also designing for adherence to the habit of clinical practice.

Photosensitivity and the three-flash limit

Photosensitivity, in the clinical sense used here, refers to an abnormal response to light stimuli or patterns, which in some people can trigger a seizure. It is not the same as "not liking a bright screen". The expert consensus of the Epilepsy Foundation of America described parameters of potentially dangerous flashing: relevant luminance, frequency from about three hertz and sufficient angular area in the visual field; transition to saturated red also counts as a risk; striped patterns with an excessive number of light-dark pairs require restriction (Harding et al., 2005). The associated review by the same group summarizes the clinical and epidemiological basis (Fisher et al., 2005). The model and rules for patterns in media were refined by Wilkins, Emmett and Harding (PMID 16060930). The most recent update from the Epilepsy Foundation reviews visually sensitive seizures, risk factors and prevention (PMID 35132632). A discussion of image safety in photosensitive epilepsy reinforces the role of production guidelines (PMID 18930180).

On the web, criterion WCAG 2.3.1 (level A) requires that the page contain nothing that flashes more than three times in any one-second period, or that the flash stay below the general and red thresholds (Understanding 2.3.1). This does not "guarantee zero risk" for all highly susceptible people. It is the technical floor that industry and accessibility have adopted. In teaching apps, the practical risk appears in:

• Indicators that flash to "draw attention" (critical error, timer, streak).
• GIFs or Lottie with rapid contrast alternation.
• Full-screen transitions between light and dark in quick succession.
• Fine striped patterns in backgrounds or animated graphics.
• Clinical videos with cuts and room flashes without a safety review.

Clinical tone without alarmism: most students will not have a seizure because of a poorly designed app. A minority has real risk, and the cost of avoiding aggressive flashing is low. If someone has a seizure, prolonged confusion or acute neurological symptoms in front of a light stimulus, seek the necessary help. Do not force "just one more try" with the screen flashing.

Differentiate this post from the general guide to digital accessibility in medical software: that one covers text contrast, keyboard, accessible names and the WCAG map. Here the subject is flashing and motion. The post on visual assistive technology covers readers and magnifiers; reduced motion also helps those who magnify the screen, because automatic pan and zoom are tiring.

prefers-reduced-motion: a contract between OS, browser and app

Modern operating systems let the user ask for less animation (Reduce Motion on iOS and equivalents on other systems). Browsers expose this preference to the page via the CSS media query prefers-reduced-motion: reduce. The contract is simple to state and easy to break in practice:

• The user declares the preference once in the OS (or in the browser).
• The site or app checks the preference.
• Non-essential animations disappear or become an instant state change.
• Motion essential to the information, if it exists, stays as short and local as possible, or gains explicit play/pause control.

Accessible engineering guides describe the same flow: remove or substantially reduce animation, transition, parallax and scroll effects when the preference is active; offer pause for content that moves on its own (web.dev, Animation and motion). Respecting the preference does not replace a control inside the product: not everyone knows the OS setting, and sometimes the person wants to reduce motion only in that app.

Common mistakes in teaching products:

• Detecting the preference and still keeping parallax "because it is the brand".
• Reducing only hover CSS and leaving Lottie and animated canvas untouched.
• Treating Reduce Motion as a "no full accessibility" mode, when it is actually the safe default mode.
• Animating error feedback with a saturated red flash in a loop.

For those who write cases and do curation, the parallel is direct: the clinical content can be excellent and the visual shell can still exclude. The Creators flow and the eye of the Curator take care of case quality; motion design takes care of who can stay in the session. Tools such as Researcher and Closer come into the study after the case; they also benefit from screens without autoplay.

Teaching platforms and local adjustments

Two sides of the same interface: those who publish the resource and those who study with it. Without the first, the second only mitigates. Without the second, the first takes a while to notice flaws. Responsible design takes on both fronts at the same time.

What teaching platforms should offer

A practical list for anyone designing or choosing an app, LMS or diagnosis game:

• Quiet default state: no autoplay of video, banner or particle.
• Respect for prefers-reduced-motion in CSS, in animation libraries and in canvas.
• Explicit control in the product: "reduce motion" or "disable animations", persistent in the account.
• Multimodal feedback without flashing: color + icon + text (the proximity theme in NEXO is an example of the principle, described at /accessibility).
• Clinical images and videos with a review for flashing and striped patterns before publishing.
• Short or absent screen transitions; state change by swapping content, not by camera movement.
• Scrolling that moves only the essential content; no coupled parallax.
• Testing with users who report migraine, visual nausea or photosensitive epilepsy, when possible, in addition to a WCAG checklist.

The ethics of educational games already calls for avoiding design that harms the learner; the post on ethics in educational game design sets out the ground. Here the harm can be physical: nausea and, in extreme cases, a seizure. Gamification in medical education can use points and feedback without requiring full-screen confetti (evidence on gamification; constancy, precision and speed).

For those who publish fictional cases with a real clinical presentation: prefer static figures to GIFs; if the animation teaches (for example, the flow of a signal), offer manual play and an equivalent static version. Up to six clues in sequence already structure the cognitive rhythm; the interface does not need to "sell" each clue with an effect. In product reviews, ask for evidence that Reduce Motion was tested end to end: splash, onboarding, case, feedback, ranking and achievement screens. The gap is usually in the final confetti, not on the login screen.

Anyone who embeds a lesson video or simulation needs a flash review pipeline similar to the one used in broadcasting (Harding/Wilkins consensus and ITU recommendations). It is not enough to say "the video editor did not warn us". A quick cut between a bright and a dark room, or a title that blinks, reintroduces risk on a platform that had already met the criterion on its native screens. Treat embedded media as part of the product, not as an innocent attachment.

What the student can adjust in the OS and the browser

While the platform does not change, you still have local options. None of them replaces clinical care if the symptoms are intense.

• Turn on the system option to reduce motion (Reduce Motion or equivalent) and restart the app to make sure the preference is read.
• In the browser, use accessibility settings or features that force a reduction of animation; test whether the site respects the media query.
• Turn off video autoplay in the browser preferences.
• Reduce brightness; avoid studying in total darkness with the screen at maximum (visual comfort, with no therapeutic promise).
• Prefer a mode that keeps contrast legible without pulsing between themes automatically.
• Pause or close tabs with carousels and livestreams with aggressive effects before the case session.
• If a specific resource triggers discomfort, document it (which screen, which action) and report it to the product; concrete feedback speeds up the fix.

Assistive technology and magnification change the geometry of the screen: horizontal pan and high zoom make parallax even worse. The guide to visual assistive technology goes deeper into readers and magnifiers. Metacognition helps: if after ten minutes of a "pretty" app you only feel nausea, the problem may be the motion, not the clinical content. Adjust the environment, take a break and return with a quieter interface. On breaks and study rhythm, the blog also discusses diagnostic pause in reasoning and burnout when the discomfort becomes a pattern.

A short five-minute protocol before the session: (1) Reduce Motion on; (2) brightness at a comfortable level; (3) noisy tabs closed; (4) a plan B if nausea appears (stop, hydrate, switch to a static device). This is not a superstitious ritual. It is interface hygiene, in the same spirit as choosing a desk and light to read a dense article. If the discomfort is recurrent with only one product, treat it as accessibility data to report, not as a personal failure to "tolerate the animation".

Table: visual triggers and design responses

Use the table when reviewing an app, an LMS or your own study habit. The contrasts are technical, not moral.

Trigger	Main risk	Design response	What the student can do now
Parallax and layers at different speeds	Visuovestibular conflict, nausea	Remove; scroll only the content	Turn on reduce motion; avoid pages with the effect
Autoplay of banner, GIF or video	Distraction; possible flash	Stopped by default; manual play	Block autoplay in the browser
Flash or blinking >3 times/s over a large area	Risk of seizure in susceptible people	Comply with WCAG 2.3.1; review media	Leave the screen; seek help if a seizure occurs
Confetti and particles on the full screen	Overload and nausea	Static multimodal feedback	Turn off animations in the app if there is a toggle
Automatic zoom/pan on a clinical image	Visual vertigo	User control; reset shortcut	Use manual zoom; prefer a static figure
Long transition between clues	Extraneous load, cognitive delay	Instant switch or <150 ms without displacement	Prefer apps that respect Reduce Motion

After the table, ask: does my most-used study resource survive with Reduce Motion on? If the interface "breaks" without animation, the animation was carrying meaning that should be in text, an icon or structure.

How NEXO fits in

NEXO is a daily diagnosis game with fictional cases with a real clinical presentation and up to six progressive clues. The /accessibility page states, among other features, that the app's animations respect the system preference to reduce motion (Reduce Motion). The same statement describes independence from color in the proximity feedback (color with a text label) and the absence of autoplay media on the site. No sentence here claims that this improves retention, approval or clinical performance. It is a description of a feature you can check.

Those getting to know the platform can read what NEXO is. Usage limits, when relevant, are in /economy. Ecosystem tools (Researcher, Closer, Curator, Creators) appear as the product describes them. The angle of this post is safety and visual comfort during the session. On the same topic, see cognitive accessibility, multimodal feedback, post-diagnosis explanation with assistive technologies and case flow with a screen reader.

Suggested use without any claim of outcome: turn on Reduce Motion on the device before playing; notice whether any screen still animates in a way that is uncomfortable and report it; use the proximity feedback through the combination of color, icon and text, not only through the brightness of the color; if the discomfort persists, pause the session and seek the necessary help when symptoms are intense.

Frequently asked questions

What is the difference between this text and the one on digital accessibility in medical software?

That one is the broad map (WCAG, frequent failures, what to check in a health system). This one goes deeper into motion, flash, photosensitivity and prefers-reduced-motion in clinical study interfaces.

Does reducing motion take the "fun" out of the diagnosis game?

The pedagogical core is hypothesis, clue and feedback. Decorative animation is not the game. A quiet state can keep clarity and still respect those with migraine or visual nausea.

Are three flashes per second an absolute clinical limit?

It is the WCAG criterion aligned with consensus on safe production. Highly susceptible people can react below that threshold. That is why prudent design avoids large-area flash and saturated red in sequence, even when it "passes" the minimum test.

Do only people with epilepsy need to care?

No. Vestibular disorders, migraine, visual nausea and motion distraction affect larger groups. The benefit of a quiet interface is collective; the extreme risk of a crisis is what makes the topic non-negotiable.

Does NEXO promise zero animation?

No. The public statement affirms respect for the preference to reduce motion in the app and the absence of autoplay media on the site. This is not a claim of efficacy nor a list of limitations.

What if I have strong symptoms in front of the screen?

Stop the stimulus, go to a stable environment and seek the help you need. This text is educational, not emergency guidance.

Final checklist

• Reduce Motion (or equivalent) active in the OS when there is sensitivity.
• Autoplay off in the browser and in study apps.
• No essential feature depends on parallax or confetti.
• Correct/incorrect feedback readable without flashing.
• Clinical images and videos reviewed for flash and stripes.
• In-app animation control, if the platform offers it.
• Session interrupted if nausea, aura or visual discomfort appears.
• Descriptive report to the product when a trigger can be identified.
• Cross-reading with digital accessibility and visual assistive technology.
• Zero reading of an interface feature as proof of learning efficacy.

Play the case of the day on NEXO. Prefer a session with reduced motion: the clue and the hypothesis matter more than the effect on the screen.

References

1. Harding G, et al. Photic- and pattern-induced seizures: expert consensus of the Epilepsy Foundation of America Working Group. Epilepsia. 2005. PMID 16146438.
2. Fisher RS, et al. Photic- and pattern-induced seizures: a review for the Epilepsy Foundation of America Working Group. Epilepsia. 2005. PMID 16146439.
3. Wilkins A, Emmett J, Harding G. Characterizing the patterned images that precipitate seizures and optimizing guidelines to prevent them. Epilepsia. 2005. PMID 16060930.
4. Fisher RS, et al. Visually sensitive seizures: An updated review by the Epilepsy Foundation. Epilepsia. 2022. PMID 35132632.
5. Harding G, Harding P. Photosensitive epilepsy and image safety. Appl Ergon. 2010. PMID 18930180.
6. Murdin L, et al. Motion sickness in migraine and vestibular disorders. J Neurol Neurosurg Psychiatry. 2015. PMID 25118205.
7. Choi JH, et al. Postural Instability Induced by Visual Motion Stimuli in Patients With Vestibular Migraine. Front Neurol. 2018. PMID 29930534.
8. Bednarczuk NF, et al. Abnormal visuo-vestibular interactions in vestibular migraine: a cross sectional study. Brain. 2019. PMID 30759189.
9. Abouzari M, et al. The Relationship Between Vestibular Migraine and Motion Sickness Susceptibility. Otol Neurotol. 2020. PMID 32501936.
10. Çeliker A, et al. Imbalance, motion sensitivity, anxiety and handicap in vestibular migraine and migraine only patients. Auris Nasus Larynx. 2020. PMID 32178946.
11. van Merriënboer JJG, Sweller J. Cognitive load theory in health professional education: design principles and strategies. Med Educ. 2010. PMID 20078759.
12. Mayer RE. Applying the science of learning to medical education. Med Educ. 2010. PMID 20604850.
13. W3C. Understanding SC 2.3.1: Three Flashes or Below Threshold (WCAG 2.2). w3.org.
14. W3C. Understanding SC 2.3.3: Animation from Interactions (WCAG 2.2). w3.org.
15. W3C. Understanding SC 2.2.2: Pause, Stop, Hide (WCAG 2.2). w3.org.
16. web.dev. Animation and motion (Learn Accessibility). web.dev.
17. ITU-R BT.1702. Guidance for the reduction of photosensitive epileptic seizures caused by television. itu.int.
18. NEXO. Accessibility Statement. nexo.wiki.br/accessibility.