Accessibility

What’s in place

• Full keyboard navigation, with no keyboard traps and visible focus states on every interactive element.
• Semantic HTML with proper landmarks (nav, main, header, footer) and a logical heading hierarchy — one H1 per page.
• Sufficient colour contrast (4.5:1 for body text, 3:1 for large text and UI) in both light and dark presentations.
• Accessible forms — labelled inputs, associated error messages, and no reliance on colour alone to signal state.
• Alternative text for meaningful images, and a text description alongside every architecture diagram — diagrams never rely on the image alone.
• prefers-reduced-motion respected — motion is minimised for anyone who requests it.
• Automated accessibility checks run in CI on changes to the site.

Known limitations

None currently identified. This list is updated as issues are found.

Feedback

If you encounter an accessibility barrier, email alausaabimbola@gmail.com and I’ll address it. Accessibility is reviewed on every change to the site and re-audited before each production release.