West Haven, ConnecticutFall 2026
ESUMSALUMNI ASSOCIATION

Trust

Accessibility

What works today, what we know is still hard, and how to tell us when something blocks you.

Draft for advisor review, 18 November 2026

The site is built by students, so this page is a status report rather than a badge. If something here is wrong, that is useful information. Email [email protected].

This is a pre-launch beta. We have not completed an outside accessibility audit, and automated accessibility checks are not running yet.

What we are aiming for

The site should meet WCAG 2.2 level AA, and we test against it rather than assume it. In practice that means: every page works with a keyboard alone, works with a screen reader, stays readable at 200% zoom, and never relies on colour to carry meaning.

What already works

  • Contrast. Body text is dark grey on warm off-white. Gold is used for fills and rules; when gold appears as text it is the darker shade (#8A6614), which passes against our background.
  • Text size. Body copy is 16px or larger, line length is capped near 70 characters, and nothing is set in all-caps except short labels.
  • Keyboard. Every link, button, field and dialog is reachable with Tab, has a visible focus outline, and closes with Escape.
  • Structure. One main heading per page, real heading levels, landmarks, and a skip link to the content.
  • Images. The beta does not accept member photo uploads. Any image added to the site must have alt text, and decorative images are marked as such rather than described twice.
  • Motion. Nothing autoplays, nothing flashes, and animation stops when your system asks for reduced motion.
  • Forms. Labels are visible, errors appear next to the field in text, and no form times out while you are filling it in.
  • The map. Every pin is also available as a list, so the destinations page works without seeing the map at all.
  • Language. Pages are written plainly. The site is English-only for now; no translated edition has shipped.

What we know is still hard

  • The map is the weakest part. It uses Leaflet with OpenStreetMap tiles, and while the list view carries the same information, keyboard panning is clumsy and screen-reader support for maps is limited everywhere, not just here.
  • Podcast episodes we only link to are the producer's responsibility, and we cannot promise their captions or transcripts.
  • Older newsletter issues were laid out for print. The web versions are readable, but a PDF from an earlier year may not be tagged for screen readers.
  • We have not yet tested with every screen reader and browser combination. Our testing so far is keyboard checks and the automated flow suite, not a full audit by an outside expert.
  • The site is English-only. Translated pages have not been written or reviewed yet.

If you need it in another form

Email us and tell us which page or document you cannot use and what would help. A plain text copy may be possible. An untagged PDF can often be replaced with a web page, which is usually the better fix for everyone.

Report a barrier

Email [email protected] with the page, what you were trying to do, and what happened. A screenshot helps but is not required. You do not have to explain accessibility to us or prove that it is a real problem.

This is a student-run site, so replies may take time. We prioritize barriers that block a task, signing in, reading a profile, RSVPing, subscribing, before anything cosmetic. If you are not satisfied with our answer, ask the faculty advisor, and the school's own process takes over from there.

How we check

Before each release we run a keyboard-only pass over the core screens (home, sign in, directory, settings) and the flow tests, and we check contrast and heading order by hand. Automated accessibility scanning in CI is still outstanding.

This page changes when the site does. If a claim here stops being true, that is a bug, and we would rather hear about it than keep the sentence.