Accessibility

The aim

StackScan aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, on getstackscan.com and in the iPhone and Android apps. It does not meet every part of that, and this page says where it falls short.

On the website

• Skip to content is the first stop for the keyboard.
• Links and buttons can be reached with the keyboard and show a clear outline when they have focus.
• Pause motion, in the corner of the page, stops the moving scenes, and this browser remembers it.
• When your device asks for reduced motion, the scenes stand still from the start.

In the app

• Buttons that show only an icon have a name a screen reader reads, such as Close.
• Sheets take the keyboard focus as they open, keep Tab inside them, and hand the focus back when they close.
• When your phone or browser asks for reduced motion, the app’s animations stop.
• Screen readers read a card’s name instead of its picture, and describe your own photo of a card when you open it.

Known limits

• Scanning is visual: you aim the camera at the card. Add a card manually, the magnifier on your stack, adds a card by name or a graded slab by its certificate number, without the camera.
• The 3D binders and display cases in Vendor mode’s Inventory are pictures.
• Card pictures come from the card databases and carry no description beyond the card’s name.

Tell us

If something in StackScan is hard to use with your setup, email the address below. Say what you were doing, on which device, and with which assistive technology, if any. We read every message.