Skip to content
Agora

Accessibility

Agora’s target is WCAG 2.1 AA.

This page says what has actually been checked against that target, when, with what, and what has not.

What was checked

On September 19, 2026, the checks a university’s accessibility reviewers ask for first were run on a production build of the demo campus, in one browser (Chromium, as Microsoft Edge) driven by a script, at 1280 by 900, 640 by 450 and 320 pixels wide: 26 screens, keyboard only through signup, login, the feed, a post with an image and its alt text, a delete dialog, messages and settings; the focus outline at or above 3:1; text at 200%; zoom at 200%; style sheets disabled; and contrast measured on the painted page, 45 of 45 checks in four palette and scheme combinations.

No screen reader has been run yet, and there is no conformance report.

The accessibility tree was read on every screen, which is a proxy and not a pass. Firefox, Safari, iOS VoiceOver and Android TalkBack have not been tried.

Known gaps

What the check found, and its state in the build this page describes.

Fixed since that check

  • the composer’s hidden file input as a Tab stop
  • no skip link
  • avatar-only and cover-only links with no accessible name
  • the email-timing radio group without arrow keys
  • duplicate ids in a conversation
  • a conversation unusable at 200% text and the composer under the phone bar at 640 by 450
  • the alt-text field’s thin focus cue
  • the organization About page’s two h1s
  • the feed has no live region, so a submitted post is not announced
  • a post’s permalink is named only by its relative time

Still open

  • Firefox, Safari, iOS VoiceOver and Android TalkBack untested