Accessibility

If you work in education or government, this is usually the first question you have to answer, and most vendors do not answer it. Here is everything we actually know, including the parts that do not look good.

Read this first. What follows is automated checks only. Machine testing catches roughly a third of real accessibility problems. It cannot tell you whether alt text is meaningful, whether a screen reader announces something sensibly, or whether an interaction can really be completed without a mouse. We have not had a human accessibility audit, we do not have a VPAT, and we have not tested with screen reader users. Do not treat this page as a conformance claim, because it is not one.
The measurement changed in v0.23.0. The script that produces these numbers was rewritten, and the set of checks it runs is not the same one behind any figure published before then. Several old results turned out to be wrong in both directions: it read colours through a stylesheet without accounting for transparency, so it invented contrast failures on three courses that never had one; it rejected valid labelling; and it counted headings in pages that build their headings after load, marking four packages as missing a main heading when each of them has one. Scores from before v0.23.0 are not comparable with these. A number that moved is at least as likely to mean we fixed the ruler as that we fixed the product — where a package genuinely improved, its row below says what it now passes, and the fixes are in the changelog rather than implied by the total.
18packages checked
17passed every check
99%of checks passed overall
0human audits, so far

What we check

Static analysis of the HTML and CSS each package ships, run against 18 of the 18 packages that have a live demo. Nothing here is measured in a running browser, which is a real limit: it is why the list below is short and why the caveats under it matter.

Why the totals differ between packages. A check that cannot apply is left out of a package’s total rather than counted as a pass — a page with no form fields is not credited for labelling them. A check is also left out when the answer cannot be read from the files: several packages build their whole interface in JavaScript, and for those we can see the code but not the page it produces. That is why one package is scored out of five and another out of eight. A missing check is not a passed check.

Two limits worth naming. Contrast is only sampled where a rule sets a text colour and a background together, and it is not sampled at all on translucent panels, because what sits behind them is not knowable from a stylesheet. And the 4.5:1 threshold we apply is the one for normal text; we do not model the looser 3:1 allowance for large text, so a heading can be reported as failing when it would in fact pass.

What fails most often

Across all 18 packages we checked. This is our fix list, in priority order.

Exactly one main heading1 of 18 packages

The most common remaining failure is exactly one main heading, on 1 of 18 packages. Keyboard focus styling used to head this list on most of the catalog; it was fixed in v0.23.0 and every package now defines a visible focus ring.

Every package, worst first

Nothing is hidden or sorted to flatter. If a package you need is low on this list, ask us before you buy.

PackageAutomated checksWhat failed
Inbox Rush7/8Exactly one main heading
Auto Course Trailer5/5nothing
Block Course (Rise-style)5/5nothing
Brewing Methods5/5nothing
Crossword7/7nothing
Decision Tree5/5nothing
Espresso Foundations6/6nothing
Illustrated Slide Course3/3nothing
Microlearning module6/6nothing
Paginated Reader6/6nothing
Scrollytelling lesson4/4nothing
Self-Talk reflection3/3nothing
Semantic-Zoom Canvas3/3nothing
Slide Player5/5nothing
The Institute Framework (SL2)7/7nothing
The Science Lab5/5nothing
Transitions library7/7nothing
Widgets library5/5nothing

If you need more than this

A buyer with a legal obligation needs more than automated checks, and we would rather say so than sell you something that fails a review. Write to hello@actyra.com and tell us which packages matter to you. We will tell you honestly what has and has not been tested, and what it would take to get a package to the standard you need.