Home › Accessibility
Accessibility commitment
Resilience means no one gets left behind, including on the website.
Our standard
Built to WCAG 2.1 AA
Stoa builds every page to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, and verifies it with automated tooling (axe-core) plus keyboard and screen-reader passes. This concept was built to that bar:
- Semantic landmarks (
header,nav,main,footer) and oneh1per page. - A visible skip link, visible focus states, and a keyboard-operable mobile menu.
- Descriptive
alttext on photography and descriptive link text throughout. - Color pairs checked for AA contrast; interactive targets at least 24 pixels.
- Impact numbers rendered as static text, readable before any JavaScript runs.
What we found on the current site
The audit behind the before/after
While reviewing riseresilience.org we noted accessibility issues worth fixing. They are real findings, shown here to demonstrate the technical approach, not to criticize.
- Impact counters animate from zero, so pre-JavaScript the page reads
$0+ million awardedand0+ jobsWCAG 1.3.1 and a credibility problem. Fix: server-render the real values, enhance with JS. - Hero and innovator headshots are missing
alttext WCAG 1.1.1. Fix: descriptive alternatives on every image. - Non-descriptive links such as “Learn More” and “How We Help Cities” WCAG 2.4.4. Fix: link text that states its destination.
- Heading hierarchy needs an H1→H2→H3 audit WCAG 1.3.1.
- Blue text over photographic heroes needs a contrast pass WCAG 1.4.3. Fix: tested overlays and color pairs.
See the before/after in action →
Found a barrier? On the live RISE site, accessibility feedback would route to the RISE team via riseresilience.org. In a Stoa engagement, accessibility is part of the support retainer, not an afterthought; every release is re-checked.