Accessibility Statement
What this document is
This page says how accessible Eigenslate is, what we know does not work yet for people who use assistive technology or a keyboard alone, and how to tell us when something gets in your way. It is written to be honest rather than reassuring: Eigenslate is a mathematics and graphing application, and some of what it does has no good equivalent for a screen reader today. Where that is the case, this page says so.
1. What this statement covers
This statement covers the parts of Eigenslate you can use: the website at eigenslate.com, including the documentation pages; the notebook; and the standalone graphing calculator. It covers them as they are deployed today.
It does not cover pages that belong to other companies and open in their own windows: the Stripe checkout and billing portal, and Google sign-in. Each has its own accessibility statement. Internal tools we use to run the service are not public and are not covered.
2. Conformance status
The standard we measure against is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.
Eigenslate is partially conformant with WCAG 2.2 Level AA. Partially conformant means that some parts of the content do not fully conform. § 4 lists what does not conform and what we intend to do about it.
This is a self-assessment. It rests on a review of the source code carried out on September 14, 2026 and a keyboard walk-through of 87 features of the website, the notebook and the graphing calculator carried out on September 16, 2026 and repeated after each round of fixes. Eigenslate has not been tested by an external auditor, has not been tested with a screen reader by someone who relies on one, and has not been run through automated accessibility tooling. We would rather say that than imply otherwise.
3. What works
- Structure. Every page has a correct language, a title, landmarks and a skip link to the main content. Every form field on the website has a real label and the right autocomplete value, and status messages on the website are announced automatically.
- Keyboard access to the interface. Menus, dialogs, tabs, the sidebar, the file explorer, the document outline and the panel splitters in the notebook can be reached and operated from the keyboard. Dialogs announce themselves, take focus, hold it while open, close on Escape and return focus to the control that opened them. The account menus are real menus: the arrow keys move through them, Escape closes them and focus returns to the button. Focus is visible on every control except the math field, where the box around it shows focus instead.
- Keyboard access inside a document. Arrow keys move between boxes and in and out of them on both axes, including out of a matrix or a cases block. Sliders respond to the arrow keys. The Quick Open palette can be driven entirely from the keyboard and announces itself as a combobox, so a screen reader hears which result is highlighted. A new document or graph, and the Find bar when it closes, leave focus in the document rather than on the page body.
- Typing mathematics. The math editor speaks its content as you move through an expression, so a screen reader user can hear what they are typing.
- Shortcuts. Every keyboard shortcut in the app uses a modifier key, and every one can be changed in the App Settings Shortcuts panel.
- Motion and themes. Every animated clip on the homepage has its own pause and play control, a caption track describing what it shows, and none starts on its own when your system asks for reduced motion. The app offers five colour themes, light and dark, and in every one of them body text, secondary text, button labels, focus rings and the borders of text fields meet the WCAG contrast minimums; a test computes the ratios from the theme file so they cannot slip. Buttons keep a quiet border on purpose: their label and fill are what identify them.
- Names and targets. Glyph-only buttons such as tab close, sidebar toggles, the graph page's save and menu controls and the document toolbar's insertion tiles carry accessible names that say what they do, and every control in the app has a target of at least 24 by 24 pixels.
- Forms. On the website, an error about a specific field marks that field invalid and links it to the message, and a confirmation revealed in place, such as cancelling a subscription, takes focus and is announced.
4. Known limitations
Each item names the part of Eigenslate it affects and what we intend to do. Where we have no fix planned, the item says that too.
4.1 Rendered mathematics has no screen-reader equivalent
The mathematics in a document is drawn as vector graphics with no alternative text, so a screen reader is silent wherever the mathematics is. This affects displayed equations, inline mathematics in text, and the results the calculator shows. Typing an expression is different: the math editor speaks as you move through it, though the field itself does not carry a name. Adding spoken descriptions to rendered mathematics would be a change to the rendering pipeline itself, and it is not on our plan today.
4.2 Graphs are visual only
The 2D and 3D plots are drawn on a canvas with no text description, no data table and no keyboard controls. You cannot pan, zoom, rotate or read a value off a plot without a pointing device, and a screen reader is told nothing about what is plotted. Reset view is the only view control that works from the keyboard. The standalone graphing calculator is affected in full.
We do not plan to add a text or audio description of what is plotted. A plot of an arbitrary expression has no faithful text equivalent that we know how to produce, and we would rather say that than promise one. Keyboard panning, zooming and rotating on the canvas are not planned either. What every plot does have is the mathematics behind it: each plotted curve is an expression in the expression list, which you can read, edit and have the math editor speak.
4.3 Reordering by drag has no keyboard equivalent in the graphing calculator
Boxes in the notebook and expression rows in the graphing calculator are reordered by dragging. In the notebook the commands Move Box Up and Move Box Down exist, but ship with no key assigned; you can give them one in the App Settings Shortcuts panel. In the standalone graphing calculator there is no keyboard route to reorder rows at all. We intend to bind both to a default key and to add the route to the graphing calculator.
4.4 A few colour pairings still fall short
The main text, secondary text, buttons, focus rings and form-control borders now meet the contrast minimums in every theme. What remains:
- Two short labels in the app are drawn in the accent colour: the "Press shortcut" prompt in the Shortcuts panel and the "overridden" marker in App Defaults. On the Latte theme that is mint on white and hard to read. Next on our list.
- Secondary grey text placed on a raised surface, such as a hover row, does not reach 4.5:1 in some themes, and on the light themes the red text inside an error box measures just under it.
- The inbox rows on the website are bounded only by the decorative border.
4.5 The notebook does not reflow at high zoom
The notebook is a fixed two-column layout. Below roughly 640 pixels of width, or at 400 percent zoom, it does not restack into one column, so content needs horizontal scrolling.
4.6 Exported PDFs are not tagged
A PDF exported from a document carries no language, title, structure or reading order, and its mathematics and graphs are embedded as pictures rather than text. The document itself stays readable in the notebook, where its text is real text and its mathematics can be read in the math editor.
5. Tell us what gets in your way
If you cannot use part of Eigenslate, or you find something this page does not mention, email support@eigenslate.com with "Accessibility" in the subject line. Tell us which page or feature, what you were trying to do, and which browser and assistive technology you were using. We will reply, and we will tell you what we can change and when. If there is something you need from Eigenslate that you cannot get because of a gap above, say so and we will find another way to give it to you.
What we do with your message is described in the Privacy Policy.
6. Technical information
Eigenslate is built with HTML, CSS, JavaScript and WAI-ARIA. Mathematics is rendered to SVG. Graphs are rendered with WebGL on a canvas element. The website, the notebook and the graphing calculator are tested in current versions of Chromium-based browsers, Firefox and Safari; the keyboard walk-through above was carried out in Chromium.
7. How this statement is maintained
This statement was prepared on September 20, 2026 from the review and the keyboard walk-through described in § 2. We update it when a gap above is fixed, when a new feature ships that changes what is covered, and at least once a year. The date at the top of the page is the date of the last update.