Company
Accessibility
StudyGrid should be usable with a keyboard, a screen reader, and a phone. This page says what is in place and how to tell us when it is not.
What we aim for
Lessons use a single main heading, real lists and tables, and a skip link to the main content. Code samples sit in text you can copy. The header stays available on small screens through a menu button. Form controls on this site, including the contact page, have visible labels.
Known limits
- Some in-browser editors are split panes with a large textarea. They are harder on a phone than a lesson page, and they are harder with a screen reader than a static example.
- Syntax colours in examples are extra. The code is still plain text.
- Compiler and plot output can be dense. If a plot does not describe itself, the printed numbers above it are the source of truth.
How we test
Pages are built as HTML first, then styled. We check contrast on the main chrome (teal on white, white on the dark header) and we check that the layout still reads when the viewport is phone-width. We do not claim a full WCAG audit of every chapter.
Tell us
If a page traps focus, hides text, or cannot be read with assistive technology, emailinfo.studygrid@gmail.comwith the URL and what you were trying to do. That is the fastest way to get a fix into the next pass.
Last updated 19 August 2026.