Accessibility

What works, what is missing, and how to report a problem.

In the extension

  • Keyboard: every Pinner command has a shortcut, and a pin can be reached with Tab, then moved, resized, docked and hidden from the keyboard. The full list is in the guide.
  • Screen readers: every button has a label and a tooltip. Pins are named after their title.
  • Focus: keyboard focus is always visible.
  • Motion: animations are short, and they turn off when your system asks for reduced motion.
  • Light and dark: Pinner follows your system setting.

On this website

  • Pages use headings, landmarks and a Skip to content link.
  • Every screenshot has a text description.
  • Text and controls are designed to meet WCAG 2.2 AA contrast in light and dark mode.
  • Pages work with the keyboard, reflow on narrow screens and when zoomed in, and respect reduced motion.
  • The site reads without JavaScript. Scripts only run the demo, the theme switch and the phone menu.
  • The site follows your system light or dark setting. The theme button in the menu bar switches between light and dark.

Known gaps

  • A pin is a picture of part of a page. A screen reader reads its title, not what is inside the picture. For text pins, Copy text gives you the words, and for math with a TeX source, Copy LaTeX does.
  • Capture area is drawn with a pointer. Pick element works from the keyboard instead: arrow keys choose, Enter pins.
  • Markup in the viewer needs a pointer.

Tell me about a problem

If something does not work with your setup, email hello@sohamaggarwal.com. Say what you used (for example a screen reader or keyboard only) and what happened.