Accessibility Statement

Our commitment

Scillint is built for every student navigating the college process, including students who use assistive technology — screen readers, keyboard-only navigation, switch devices, and browser zoom or high-contrast display settings. We're working to make the platform usable by everyone, and we treat accessibility as an ongoing engineering practice, not a one-time checklist.

Our target

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. We audit and remediate against this standard incrementally across the app; we are not yet claiming full conformance (see Known limitations below).

What's implemented

As of this statement's last-updated date, the following are in place across the student, parent, and practice surfaces:

DoneColor contrast

Text and interactive elements use color tokens re-tuned to meet WCAG AA contrast ratios (4.5:1 for normal text, 3:1 for large text and UI components) in both light and dark mode.

DoneTouch and click targets

Interactive controls — buttons, nav items, form fields, chips — meet a 44×44px minimum tap-target floor on touch surfaces.

DoneKeyboard navigation

• Every interactive element reachable by mouse (nav items, dashboard cards, answer choices, toggle chips, accordion headers, modal close buttons) is also reachable by Tab and activatable with Enter or Space.
• Modals and drawers (the help drawer, onboarding cards, ad hoc dialogs) trap focus while open, move focus to the dialog on open, and return focus to the triggering control on close.
• Esc closes open modals and drawers.
• Visible focus outlines are preserved (never suppressed with outline:none alone) and use :focus-visible so mouse users don't see a ring on click while keyboard users always do.

DoneScreen readers

• Icon-only buttons carry aria-label text describing the action, not the icon.
• Toggle-style controls (tab switchers, tag chips, section filters) expose their state via aria-pressed, aria-expanded, or aria-checked as appropriate.
• Toast/status notifications use role="status" with aria-live="polite", so confirmations and errors are announced without interrupting whatever the screen reader is currently reading.
• Countdown timers (practice and mock-exam clocks) are marked role="timer". We intentionally use aria-live="off" on these rather than "polite" — a live region that updates every second would talk over everything else on the page. The timer is still reachable and readable on demand.
• The student, parent, and practice app shells expose a role="main" content region and a labeled sidebar navigation landmark, so screen reader users can jump straight past repeated navigation.
• All informative images carry descriptive alt text; purely decorative icons are hidden from assistive tech.

DoneForms

Form fields across sign-up, sign-in, and profile forms use programmatic <label for> associations (or aria-label where a visible label doesn't fit the layout), so a screen reader announces what each field expects before the student fills it in.

DoneReduced motion

We honor the operating-system prefers-reduced-motion setting: if you've asked your device to minimize motion, Scillint's transitions and animations are disabled site-wide rather than just slowed down.

Known limitations

We're honest about what isn't finished yet:

• Data visualizations. The score-trajectory chart now carries an accessible name summarizing the trend it draws (per-section start and latest scores with dates), so screen reader users get the same information as the visual. A few smaller SVG-based charts don't yet have the same treatment; the numeric values they visualize are shown as plain text elsewhere on the same page, and bringing them up to the same standard is on our list.
• Full assistive-technology testing. This pass was a code-level audit (semantic markup, ARIA attributes, keyboard operability, contrast tokens). We have not yet completed a full manual pass with NVDA, JAWS, or VoiceOver across every surface — that's a planned next step, not something we're claiming today.
• Third-party embeds. Our cookie-consent banner and payment checkout are provided by outside vendors (Termly, Stripe). We choose accessible vendors where we can, but we don't control their code directly.
• Older or lower-traffic surfaces. We prioritized the highest-traffic student and parent surfaces (dashboard, practice, essays, planner, sign-up/sign-in) in this pass. Some less-visited admin-only tooling has not yet been audited to the same depth — that tooling is used by our own staff, not students or parents, but we intend to bring it up to the same standard.

Feedback and contact

If you encounter an accessibility barrier anywhere on Scillint, we want to hear about it. Tell us the page, what assistive technology or browser you were using, and what happened — that's usually enough for us to reproduce and fix it.

Email admin@scillint.com and we'll get back to you.

Last updated: July 14, 2026.