Statement
Accessibility at Omotunde Memorial.
The hospital we are building must be usable by everyone — and so must the website that announces it. This page describes the standards we hold ourselves to and how to tell us when we fall short.
§ I · Our standard
We target WCAG 2.1 AA.
Every page of omotundehospital.org is designed and built to meet the Web Content Accessibility Guidelines version 2.1, Level AA — the standard most public-sector and healthcare bodies use as their baseline. Interactive components use standard ARIA roles and states.
Every change to the site's code is checked automatically with the eslint-plugin-jsx-a11y rules, which catch problems such as missing alternative text and invalid ARIA. Each page is also scanned with pa11y, which tests the rendered page for colour contrast and other WCAG 2.1 AA issues.
§ II · What we've built in
Specific provisions on every page.
- A skip-to-content link appears at the top of every page for keyboard users, jumping past the header straight to the main content.
- Every image carries descriptive alternative text. Decorative SVGs are marked
aria-hiddenso screen readers don't announce them. - Colour contrast meets WCAG AA throughout: text is at least 4.5:1 against its background, and the main body text exceeds 7:1.
- Keyboard navigation reaches every interactive element. Focus indicators are visible. Buttons can be activated with Enter or Space.
- Auto-rotating hero can be paused. The site also respects the operating-system setting
prefers-reduced-motion: when it's on, animations and auto-playing content are switched off. - Bilingual content in Yorùbá is wrapped with
lang="yo"so screen readers switch pronunciation rules correctly. - Touch targets for the main mobile controls, including the menu button and the walkthrough markers, are at least 44 × 44 pixels.
- Semantic landmarks — every page has a single primary
<main>, plus proper header, nav, and footer regions.
§ III · Known limitations
Where we're still improving.
The site has not yet been audited by an independent accessibility consultant, and a full manual screen-reader review of every page is still to be done. Some image descriptions are brief, and will become more specific as the build log grows.
The interactive floor plan can be used with a keyboard and scrolls sideways on phones so its labels stay readable. It is still a visual tool, though, and a text version of the room list would serve screen-reader users better.
§ IV · Tell us
Found something we missed?
Email the management board. Describe the page, the device or assistive technology you were using, and what wasn't working. Every report is read.
Statement last reviewed · October 2026