Accessibility

Site accessibility checks and how to report an access problem.

This project aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. It aims to work with screen readers, keyboards, zoom, forced colors, reduced motion, and other access tools.

Automated checks help find barriers. They do not prove that every person can use the site. Real experiences and reports remain necessary.

Automated checks

The build examines every page with axe-core in a real browser. Additional browser tests examine:

  • Keyboard access to available lessons.
  • Visible focus on controls and links.
  • A skip link that moves to the main content.
  • Search focus returning to the search button.
  • Page reflow at a 320-pixel viewport.
  • Horizontal keyboard scrolling inside the periodic table.
  • Visible tile status with forced colors.
  • Reduced motion when that preference is active.

The build also examines headings, table captions, local link destinations, and page language. It makes sure that every tile’s status matches the task map. Examine external sources separately. A successful response does not prove that a source gives evidence for the surrounding claim.

Using the periodic table

Tiles with a solid border and the words Read lesson are links. Every task on the map has a lesson. A planned task will have a dashed border and show Planned. Its tile will be plain text, not a disabled control.

The table is wider than a phone screen. Touch users can swipe sideways. Keyboard users can focus the table and use the left and right arrow keys. Each group prints its stage and group name, so color is never the only way to understand the organization.

Checks that still need people

Manual tests with current NVDA, JAWS, VoiceOver, keyboard-only navigation, and browser zoom remain pending. Automated success does not change that status. Before accessibility approval, reviewers must examine the site with the assistive technology that its intended readers use. Manual tests should include:

  • Heading and landmark announcements.
  • Table reading order.
  • Link and button names.
  • Browser zoom at 200% and 400%.
  • Keyboard operation without a pointer.
  • High-contrast and forced-colors settings.
  • Reading effort for readers with cognitive disabilities.

Report a barrier

Open an accessibility issue to report a problem. Include the page address. Describe the action you tried and what happened. Name the browser or assistive technology you used. Do not include private information.