Accessibility at GratNis
GratNis is used by counselors, teachers, office staff, students and parents — including people who use screen readers, keyboards without a mouse, screen magnifiers and voice control. This page says what we have tested, what we have not, and what to do if something is in your way.
Last reviewed 1 August 2026.
What we aim for
We target WCAG 2.1 Level AA. That is the standard the US Department of Justice adopted for public entities under Title II of the ADA in 2024, and the one most Louisiana districts and charter networks now write into procurement.
What has actually been measured
On 1 August 2026 we ran an automated audit (axe-core, WCAG 2.0/2.1 A and AA rules) across the marketing site, the sign-in page and twelve application screens covering every panel — counselor, school management, teacher and family portal — including list, form and dashboard pages.
Result
471 failing elements at the start; zero at the end. The work included:
- Naming 16 form controls that had none — a screen reader announced them only as "combo box".
- Correcting text colours across the whole palette. Award and risk badges were at 2.5:1 where 4.5:1 is required, and those carry the most urgent information on screen.
- Removing links with no text, produced by empty table cells.
- Adding a skip link, a visible focus outline on every control, and honouring the device's reduce-motion setting.
Colour contrast is additionally checked by an automated test on every change, so a future edit that breaks it fails before release rather than after.
Adjustments you can turn on
Signed in, under Accessibility in the menu, anyone can switch on larger text, higher contrast, reduced motion, dyslexia-friendly spacing, always-underlined links and larger click targets. These save to your account and follow you to any device you sign in from.
They are adjustments on top of a platform meant to work without them — not a replacement for it. We do not use an accessibility overlay widget, and we would not recommend one: they sit on top of the problem instead of fixing it, and disabled users overwhelmingly report that they get in the way.
Known gaps
Being specific here is the point. These are real and we are not claiming otherwise.
- No formal audit by disabled users yet. Automated tools catch roughly a third of WCAG issues. They cannot tell you whether a screen reader's reading order makes sense or whether a workflow is actually completable. We have not yet paid for testing with people who use this software with assistive technology daily, and until we do, this page cannot claim conformance.
- No published VPAT / ACR. If your district needs one for procurement, contact us and we will tell you honestly where we are rather than sending a filled-in template.
- PDF and CSV exports — printed transcripts and downloads have not been assessed for accessibility. Tagged-PDF structure in particular is not implemented.
- Charts — the GPA and award charts convey their data visually. Underlying figures are available in the tables beside them and in every export, but the charts themselves are not annotated for screen readers.
Tell us about a barrier
If any part of GratNis is hard or impossible for you to use, that is a defect and we treat it as one. Email accessibility@gratnis.com with the page and what happened, and tell us what you were using — screen reader and version, keyboard only, magnifier, voice control. We aim to reply within five working days.
If you are at a school using GratNis and need something urgently to support a specific student, say so and we will prioritise it.