Optimizing Web Accessibility for Public Sector Portals
Building for the public sector means building for everyone. When I was tasked with developing the official portal for the Somali National Women Organization (SNWO), accessibility wasn’t just a “nice-to-have”—it was a fundamental requirement.
Digital inclusion ensures that people with disabilities—visual, auditory, motor, or cognitive—can navigate, understand, and interact with the web. Here is how we achieved WCAG 2.1 compliance.
Semantic HTML: The Foundation
Using correct HTML tags is the first and most impactful step. Screen readers rely on the document object model (DOM) to interpret content.
- Use
<nav>,<main>, and<footer>landmarks. - Ensure heading levels (
h1throughh6) follow a logical hierarchy. - Use
<button>for actions and<a>for navigation links.
Color Contrast and Visual Hierarchy
We adhered to a strict contrast ratio of at least 4.5:1 for normal text. This is crucial for users with low vision. Additionally, we ensured that color was not the only method used to convey information (e.g., adding text labels to error fields, not just red borders).
Keyboard Navigation
A mouse is not the only way to browse the web. We rigorously tested the site using only a keyboard to ensure focus states were visible and logical tab order was preserved.
/* Example of high-visibility focus state */
button:focus-visible {
outline: 3px solid #ea580c;
outline-offset: 2px;
}
By prioritizing accessibility, we didn’t just meet a standard; we expanded the reach of the organization’s critical resources to the widest possible audience.
Heidar Abdi Ahmed
Full Stack Engineer and AI enthusiast passionate about bridging the gap between complex machine learning models and intuitive user experiences. Based in Mogadishu.