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. The site is also tested against the WAI-ARIA authoring practices for interactive components.
Each commit runs through an automated lint pass that includes the eslint-plugin-jsx-a11y ruleset, catching missing alt text, invalid ARIA, keyboard traps, and color-contrast regressions before they ship.
§ 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. - Color contrast on body text exceeds 4.5:1 against the page background. Headlines and supporting text exceed 7:1 (AAA).
- 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— if it's on, all motion is disabled. - Bilingual content in Yorùbá is wrapped with
lang="yo"so screen readers switch pronunciation rules correctly. - Touch targets on mobile interactive elements 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.
We are honest about what isn't finished. The site has not yet been audited by a third-party accessibility consultant. A manual screen-reader pass on every route is on our backlog. Photos taken on-site by the engineer use generic alt text; we'll improve specificity as the build progresses.
The interactive floor plan supports keyboard navigation, but on very small mobile devices the room labels remain compact even with horizontal scroll. A list-mode alternative is planned.
§ 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. We aim to acknowledge every report within five working days.
Statement last reviewed · May 2026