Skip to main content

Accessibility

Accessibility Statement

APN is built for keyboard users, screen-reader users, low-vision readers, and players with cognitive or motor differences. Accessibility is part of shipping, not a polish step at the end.

Last reviewed May 19, 2026Target: WCAG 2.2 AA. Self-audit, ongoing.

1#Our commitment

All Patch Notes wants every player to be able to read patch notes, follow their games, and find what changed. That means keyboard support, screen-reader support, readable contrast, and respecting motion preferences as part of the build, not as cleanup.

2#Standards we follow

APN targets Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. The 2.2 release adds criteria around focus appearance and target sizing that matter for content with a lot of small interactive tiles.

3#Conformance status

APN is partially conformant with WCAG 2.2 Level AA. Some areas listed in section 5 do not yet meet every success criterion. The pre-launch audit is in progress; partial conformance will be re-evaluated before public launch.

4#How we test

APN runs through these checks on every release:

  • Keyboard-only navigation through header, sidebar, feed, modals, search, and forms.
  • Screen readers: NVDA with Firefox, JAWS with Chrome, VoiceOver on macOS and iOS, TalkBack on Android.
  • 200% browser zoom, 400% text-only zoom, reduced motion, and forced-colors modes.
  • Color contrast at WCAG 2.2 AA (4.5:1 body, 3:1 large text and non-text indicators).
  • axe-core and Lighthouse, plus manual checks for issues automation will miss.

APN has not commissioned a third-party audit yet. Self-evaluation is the honest label until a firm signs off.

5#Known limitations

Currently being tracked pre-launch:

  • Some embedded third-party videos lack accurate captions. APN links to source pages where captions exist (WCAG 1.2.2 Captions).
  • Image-heavy game tile rails can exceed the 1.5x max line-height adjustment at some zoom levels (WCAG 1.4.12 Text Spacing).

Hit something not on this list? Report it. Accessibility blockers do not wait for the next release cycle.

6#Features built in

  • Single tab order across pages with visible focus rings on every interactive element.
  • Skip-to-content link on every page (visible on focus).
  • Semantic landmarks: header, nav, main, complementary, contentinfo.
  • ARIA on dialogs, listboxes, the search combobox, and follow / save toggles.
  • Reduced-motion variants for non-essential animation (respects prefers-reduced-motion).
  • Real labels, real error messages, aria-live updates for async states.
  • Descriptive alt text for meaningful images; decorative images marked aria-hidden.

7#Supported assistive tech

  • Latest two versions of Chrome, Edge, Firefox, Safari.
  • Latest two versions of NVDA, JAWS, VoiceOver.
  • Mobile Safari + VoiceOver on iOS 17+, Chrome + TalkBack on Android 13+.
  • Switch control, voice control (Dragon, Voice Access), high-contrast OS modes.

8#How to report a problem

Email contact@allpatchnotes.com with subject "Accessibility". Include the URL, your assistive tech and version, and a one-line description of what happened. Accessibility reports get triaged ahead of other issues.

9#Preparation of this statement

  • First published: May 19, 2026
  • Last reviewed: May 19, 2026
  • Next review: within 12 months of the last review, or whenever a major release changes assistive-tech support
  • Prepared by: All Patch Notes team (self-evaluation, no third-party audit at this time)