CodeCogs®FxEditor
User guideQuickstartDeploymentAPIDesignFxTeX
APIExamplesAccessibility
FxTeXServer
DeploymentAPILaTeXRender
DeploymentAPIPlugins
CK Editor v5Tiny MCE v6BloggerAngularDeveloper GuideLicensing
How licensing worksfxTeX Accessibility
Every equation the editor produces is MathML, and every equation carries generated spoken text alongside it. This page is the bench we test that on: each row below renders one equation and shows, beside it, the exact wording a screen reader should be speaking.
It is deliberately a live page rather than a report. The markup is generated by the same converter the editor ships, in your browser, right now — so what you hear here is what your users will hear.
How it works
The editor does not simply attach an alt string to a picture. There is a pipeline, and each stage is a thing that can be tested:
LaTeX→expression tree→MathML →spoken mathematics
The MathML is what a browser draws and what a screen reader with native maths support reads. The spoken text is the fallback, and on macOS it is not a fallback at all — it is the only thing that works. Which of the four ways of attaching it you should use is the question this page exists to answer.
The four options
Below is exactly what the converter emits for \alpha + \beta under each option,
generated live so it cannot drift from what the test cases further down are actually using.
Test bench
How to reach an equation. Every equation below is focusable, so the simplest
route is Tab — it steps from one equation to the next, skipping everything else, and
your screen reader reads each one as it lands. Shift+Tab goes back.
macOS VoiceOver. Cmd+F5 turns it on and off. Then either
Tab as above, or Ctrl+Option+→ to walk every item on the page.
Ctrl+Option+A reads continuously from where you are.
NVDA and JAWS on Windows. Arrow through the page, or Tab as above. On an
equation, NVDA+Alt+M opens MathCAT's own navigation, which lets you walk
inside the expression rather than hearing it in one go.
Tab) and this line will show which one, and the exact
text a screen reader should be speaking for it.
More
fxTeX API — the options that control how speech is generated and attached.
User guide — what someone writing an equation sees and hears.
How we compare — where the other engines stand on accessibility.