Accessibility

I built SecuSpark because I have ADHD and could not study from a wall of text. The game loop is the accommodation, not a gimmick. That also means I owe you a straight answer about what is actually accessible today, what is not, and who to talk to when something blocks you. This page is that answer. It is written by me, not a compliance vendor, and every claim on it was checked against the code on the date above.

The target is WCAG 2.1 Level AA. SecuSpark does not fully meet it yet. The known gaps are listed below with dates so you can hold me to them.

What is built

Practice exams are never timed. There is no countdown and nothing auto-submits. The clock counts up, pausing stops it, and you can hide it entirely from the exam header or from Settings. A visible ticking clock is its own stress trigger for a lot of people, so the readout is optional and the number is only used on your results screen.

Reduced motion is honoured everywhere.Turn on your operating system's reduce-motion setting and the app drops movement animations across every screen, including the battle arena: the intro cut, damage numbers, confetti, and the experience counter. Two things still change on screen under reduced motion, and I want to be exact about them. Hit effects show their final frame instead of playing, and the level-up screen still reveals its stages on a timer. Both are on the list below.

Sound is yours to control. Mute, a volume slider, and a calm mode. Calm mode is a loudness cap at 40%, not a separate quieter sound design. Sound also mutes automatically when you switch tabs.

Keyboard. A skip-to-content link is the first thing the Tab key reaches on every page. Every focused control shows a visible ring. Scrolling panels can be reached and moved with the keyboard. The exam pause screen is a proper dialog: focus stays inside it, Escape resumes, and focus returns to the pause button.

Zoom and contrast. Pinch and browser zoom work up to 500%. The colour tokens the app is built from are checked for 4.5:1 text contrast on every build, so a palette change cannot quietly ship a regression.

No account needed for the basics. Practice exams at /exam work without signing up, so a learner who never wants the game can still do the core work.

Known gaps

• Level-up screen reveals its stages on a fixed timer even under reduced motion (about six seconds, tap to skip). Fix queued for the October 2026 release.
• Streaks have no forgiveness yet. A missed day currently ends a streak. A streak freeze for absences is next on the list, and the current reminder email wording will be corrected with it.
• Reading comfort settings (larger text, wider line and letter spacing, off-white surfaces, an optional dyslexia-style typeface) are not built yet. Planned for October 2026. When the typeface option ships it will be offered as a preference, not sold as a proven aid: the published research on OpenDyslexic found no improvement in reading rate or accuracy.
• Page landmarks. Several screens nest a second main region inside the page shell. Screen readers still work, but landmark navigation is noisier than it should be.
• Marketing pages (home, pricing, blog) carry colour-contrast failures on small secondary text. The app itself is guarded; the marketing surfaces are not yet.

What was measured

On September 4, 2026I ran axe-core's WCAG 2.0 and 2.1 A/AA rule set against 102 page states: the public pages and every signed-in screen a learner uses daily, at phone, tablet, and desktop widths, in light and dark themes. Before the pass there were 147 serious or critical findings. After it there were 0, measured on a production build of the same code. Automated checks only find part of what a real user hits, so treat that number as a floor, not a grade. There is no VPAT or Accessibility Conformance Report for SecuSpark today. If your organisation needs one, tell me the deadline and I will produce it against the real state of the product rather than a flattering one.

Accommodations, and who answers

If something in SecuSpark blocks you, email me directly at accessibility@secuspark.com. I am Pawel Sloboda, the person who writes the code, and I read every message.

You will hear back within one business day with either a fix, a workaround, or a date. Include the page, what you were trying to do, your device and browser, and any assistive technology you use. Screenshots help; a screen recording helps more.

If the game format itself is the barrier, you are not stuck. Practice exams and flashcards do not require the battle arena, energy, or any character progress, and both keep the same question bank. A programme lead or instructor can also write on a learner's behalf to arrange a per-learner accommodation such as a non-game study path, extended access, or a walkthrough for assistive technology.

Standards and scope

This statement covers the web app at https://www.secuspark.com in current versions of Chrome, Firefox, Safari, and Edge, with NVDA and VoiceOver as the reference screen readers. It does not cover third-party pages we link to. The conformance target is WCAG 2.1 AA and the automated checks use axe-core; manual keyboard and screen-reader passes are done by me before each release that touches the exam, battle, or settings screens.

See also our privacy policy and terms.