Accessibility

Fractions for every kind of learner

We want every kid to be able to use Slices: with a mouse, a finger, a keyboard or a screen reader, and at their own pace. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Here’s what we’ve done so far.

What we’ve built in

• Keyboard control. Every model works without a mouse or a touch screen. Parts are buttons, number-line markers are sliders, and anything you can drag also has a button or arrow-key alternative.
• Screen readers. Every picture has a text description that says what a sighted learner can see, without giving the answer away. Models announce what changed as you use them.
• Words for everything. Every slice has a complete written explanation, and a plain-text version too.
• More than color. Shaded parts also carry patterns and outlines, so meaning never depends on color alone.
• Calm motion. Animations are short and gentle, and they switch off when your device asks for reduced motion.
• Your own pace. Nothing is timed, and there are no sounds.
• Readable text. Body text uses Atkinson Hyperlegible, a typeface made for legibility, at a comfortable size with strong contrast.
• Room to tap. Buttons and the parts you tap are big enough to hit comfortably.

How we check

Our automated tests finish every model using only the keyboard, and every kind of page is scanned with an accessibility checker. Automated checks can’t catch everything, so we also test by hand with screen readers and keyboard-only navigation.

Something in the way?

If anything here is hard to use with your setup, we want to know, so we can fix it.