Cognivo

Accessibility

Built to be played by everyone.

Cognivo aims to be usable by as many people as possible, including those who rely on assistive technology. This statement describes where things stand today and how to flag a barrier.

What's built in

  • Semantic HTML and ARIA labels so screen readers can describe the interface.
  • Full keyboard navigation for menus and links, with visible focus styles.
  • Voice support: in chess you can speak your moves, and every lesson has a Listen button that reads the content aloud.
  • Responsive layouts that work from small phones to large desktops.
  • Color choices chosen for readable contrast, and no flashing or strobing content.

How to play each part of the site with the keyboard, a screen reader or voice is in the .

The standard I aim for

I'm working toward the WCAG 2.1 Level AA guidelines as a target. Cognivo isn't formally certified against them, and some areas don't fully meet that bar yet — I treat it as a direction, not a finished checkbox.

Known limitations

  • The interactive game boards rely on pointer/drag interactions that can be awkward with some assistive technology; keyboard and voice paths are still being improved.
  • Voice features depend on your browser's built-in speech support, so they aren't available everywhere.
  • This is an independent, solo-built project, so fixes ship as I get to them — your reports help me prioritize.

Found a barrier?

If something is hard or impossible to use, please tell me and I'll work to fix it. Email support@cognivo.digital with the page and what went wrong, and I'll follow up.