What we found on rbcra.com
Before designing this prototype, Stoa audited the live CRA homepage. These are real findings from the published markup, captured June 2, 2026, with the WCAG criterion each touches and how this prototype answers it.
Seven findings, seven fixes
| # | WCAG | Finding on rbcra.com | Answered here |
|---|---|---|---|
| 1 | 2.4.1 Bypass Blocks (A) | No skip link anywhere in the markup. Keyboard users tab through the whole navigation on every page. | A visible-on-focus skip link is the first element on every page of this prototype. Press Tab right now to see it. |
| 2 | 1.3.1 Info & Relationships (A) | Two h1 elements on the homepage, breaking the document outline for screen readers. |
Exactly one h1 per page, with a logical heading tree below it. |
| 3 | 1.1.1 Non-text Content (A) | Of 34 images, 2 had no alt attribute and 30 had empty alt="", including content images. 17 were base64 placeholder GIFs that never resolve. |
Every meaningful image here carries real alternative text; decorative SVG art is marked hidden. No placeholder images. |
| 4 | 3.3.2 / 4.1.2 Labels (A) | The search form had two inputs and only one label: at least one unlabeled control. | Every input on this prototype has a programmatic label, including both search boxes on the homepage. |
| 5 | 4.1.2 Name, Role, Value (A) | Only one aria-label on the entire page; custom widgets likely lack accessible names. |
Navigation, filter groups, and live regions are all named; interactive demos announce their state. |
| 6 | Best practice | No accessibility statement on the CRA site, though the city's own site publishes one. | This prototype ships with a standing accessibility commitment and a barrier-report path. |
| 7 | Performance | 53 jQuery references, render-blocking Google Fonts loaded from third-party servers, and 17 placeholder GIFs slow first paint and leak visitor data to Google. | Zero runtime dependencies, zero third-party requests. Fonts are self-hosted; scripts are a few kilobytes of vanilla JavaScript. |
Method. Findings come from the homepage HTML as served on June 2, 2026. They are markup-level observations, not a full manual audit; a production engagement would include screen reader passes, keyboard walkthroughs, and page-by-page axe-core checks like the ones this prototype is held to.
Why it matters for this RFP
The CRA's website redesign calls for ADA-compliant, mobile-first design. Compliance is easiest when it is structural: built into the templates, checked by machines on every change, and owned by a vendor who treats it as the floor rather than the finish line.
This prototype is the proof: the same agency content, the CRA's own photography and brand colors, rebuilt to WCAG 2.1 AA with working search and zero third-party requests.