A customer reaches your website on a phone, ready to book an appointment. The text is pale against a bright background, the menu cannot be used with a keyboard, and the form labels disappear as soon as typing begins. Another visitor opens a product video but cannot follow it without sound. A third enlarges the page and finds that the checkout button has moved off-screen.
None of these people arrived looking for an accessibility test. They arrived to buy, compare, apply, learn or contact your team. The barriers appeared between their intention and your business outcome.
That is why website accessibility in Kenya belongs in the same conversation as mobile design, customer experience, lead generation and brand trust. It is not a decorative extra for large organisations. It is the practical work of making digital information and actions usable by people with different visual, hearing, physical, speech and cognitive needs, across different devices and browsing conditions.
For Kenyan businesses, the issue also has a clear public-interest and legal context. Section 26 of the Persons with Disabilities Act, 2025 says public and private institutions should provide information intended for the general public, including through the internet, in accessible formats and technologies. Organisations should obtain legal advice on their specific obligations, but the direction is unmistakable: accessible digital communication deserves operational attention.
What an accessible website should enable
An accessible website gives people more than permission to view a page. It helps them understand the content, move through the interface, complete tasks and recover from mistakes. A visitor should be able to identify headings, follow links, operate controls, submit a form and receive useful feedback without relying on one particular sense, device or input method.
The internationally recognised reference point is the Web Content Accessibility Guidelines 2.2, published by the World Wide Web Consortium. WCAG organises accessibility around four principles. Content should be:
- Perceivable: people can receive the information in a form they can use, such as text alternatives for meaningful images and captions for video.
- Operable: controls work with a keyboard and other input methods, focus is visible, and interactions do not demand unnecessarily precise movement.
- Understandable: language, navigation, instructions and error messages are clear and reasonably predictable.
- Robust: the underlying code communicates names, roles and states in ways that browsers and assistive technologies can interpret.
WCAG has three conformance levels: A, AA and AAA. Many organisations use Level AA as a practical target because it covers a substantial range of common barriers without assuming that every page can satisfy every specialised AAA criterion. A target is useful, but a badge or automated score should never replace testing the real journeys customers need to complete.
Begin with the journeys that matter commercially
A site-wide accessibility programme can feel overwhelming when a website contains hundreds of pages, old PDFs, third-party widgets and multiple forms. Start by mapping the journeys that carry the most risk or value.
For a clinic, the priority may be finding a service, reading preparation instructions and requesting an appointment. A school may focus on admissions information, fee documents and enquiry forms. An ecommerce business needs accessible product discovery, cart controls, payment steps and order updates. A professional firm may prioritise service pages, case studies, contact details and proposal requests.
List each journey from arrival to completion. Then identify the pages, controls, downloads and messages involved. This gives your team a sequence to test instead of a vague instruction to “make the website accessibleâ€.
A useful first pass covers:
- the homepage and main navigation;
- the most visited service or product pages;
- contact, enquiry, booking and checkout forms;
- account login and password recovery;
- important PDFs, menus, fee schedules and application documents;
- campaign landing pages receiving paid traffic;
- confirmation, error and follow-up messages.
This commercial approach does not excuse barriers elsewhere. It creates an accountable order of work while the wider site is improved.
Check that every task works without a mouse
Keyboard testing is one of the fastest ways to expose serious interaction problems. Unplug the mouse or leave the trackpad alone, reload the page and use the Tab key to move forward, Shift and Tab to move back, Enter to activate a link, and Space where appropriate for buttons and controls.
You should always be able to see where focus has moved. A visible focus indicator may be an outline, underline or colour treatment with enough contrast to stand out. It should not disappear behind sticky headers, cookie banners or chat widgets.
Test menus, accordions, sliders, modal windows, form controls, date pickers and video players. If a user can open a dialog but cannot close it, or focus escapes into the page behind it, the interaction is not ready. If a custom element only reacts to a mouse click, ask whether a standard HTML control could do the job more reliably.
Do not remove browser focus outlines because a designer dislikes their appearance. Style them to fit the brand while preserving a clear indication of position.
Make text readable in ordinary Kenyan browsing conditions
Readability is affected by more than font choice. Visitors may be using a small screen outdoors, an older phone, a dim display or a browser zoom setting. Strong colour contrast, sensible line length and flexible text sizing help in all of these situations.
Check body text, navigation labels, form instructions, prices, captions and text placed over images. Placeholder text and disabled controls are often especially weak. A colour palette can look refined on a designer’s monitor and become unreadable in sunlight.
Avoid fixing text inside images when normal HTML text would work. Image-based text does not resize, translate or adapt as well, and it may not be available to assistive technology. Campaign posters can still be used, but the same information should appear as real page text nearby.
Zoom the page to 200%. Content should reflow without forcing horizontal scrolling for ordinary reading, and controls should remain available. This test also reveals rigid layouts, clipped headings and buttons that overlap. It complements the responsive principles discussed in our article on mobile-first web design.
Use headings and landmarks to create a clear structure
A sighted visitor often scans a page visually before deciding where to read. Screen-reader users can also navigate by headings and landmarks when the structure is coded properly. The page should have one clear primary heading, followed by H2 and H3 headings in a logical hierarchy.
Do not choose a heading level merely because it has the desired font size. Styling belongs in CSS; heading levels communicate the document outline. A large bold paragraph is not a substitute for a real heading.
Use meaningful page regions such as header, navigation, main content and footer. Add a “skip to main content†link so keyboard users can bypass repeated navigation. Keep the navigation order consistent across the site, and use descriptive page titles that distinguish one browser tab from another.
Link text should also make sense out of context. “View our ecommerce website features†is more useful than five links that all say “click hereâ€. Avoid using a raw URL as the visible label unless the URL itself is information the reader needs.
Write useful alternative text for images
Alternative text should communicate the purpose of a meaningful image, not mechanically describe every pixel. The right wording depends on context.
A photograph showing a completed office fit-out may need a short description of the result. A chart needs the key insight and the underlying data in an accessible format. A button represented by a search icon needs an accessible name that identifies the action. A decorative flourish that adds no information should usually have an empty alt attribute so it can be ignored.
Avoid stuffing keywords into alt text. “Best website accessibility Kenya digital agency web design Nairobi†is not helpful to a person who cannot see the image. Write the concise description you would give a colleague over the phone.
Review existing media-library entries because duplicated or irrelevant alt text often spreads when an image is reused. Make accessible content part of the publishing checklist rather than a one-off clean-up.
Give video, audio and motion an accessible alternative
Videos with speech need accurate captions. Captions should identify important speakers and meaningful sounds, not merely display an unedited automated transcript. Audio-only information needs a transcript. When important visual information is not explained in the soundtrack, consider an audio description or a text alternative.
Do not make sound play automatically. Give users an obvious way to pause, stop or mute media. Carousels, animated banners and moving counters also need controls when movement continues or distracts from the task.
Respect the reduced-motion preference supported by modern operating systems and browsers. A subtle transition may be comfortable for one user and disorienting for another. Critical information should never be communicated only through animation.
Build forms that explain themselves
Forms are where accessibility problems become lost leads. Every field needs a persistent label. Placeholder text can provide an example, but it should not be the only label because it disappears during entry and often has low contrast.
Tell users which fields are required before they submit. Group related options with appropriate labels. Make instructions specific: “Enter a Kenyan mobile number beginning 07 or 01†is more useful than “Invalid inputâ€. Do not identify errors with colour alone; add text and programmatic information that assistive technology can announce.
After a failed submission, move focus to an error summary or clearly identify the affected fields. Preserve information the user entered wherever possible. Re-entering an entire application because one field failed is frustrating for everyone and can be a serious barrier for people with motor or cognitive disabilities.
Authentication deserves special attention. Do not block password managers or pasting into password fields. If a verification step relies on a puzzle, image or precise movement, provide an accessible alternative. WCAG 2.2 added guidance around accessible authentication and redundant entry because these obstacles regularly prevent completion.
Design controls for touch, not perfect precision
Small icons placed close together are difficult for people with limited dexterity and for anyone using a phone while moving. Provide a generous clickable area around menu icons, close buttons, pagination, form checkboxes and quantity controls.
Do not make dragging the only way to complete an action. A slider should also offer buttons or direct input. Swipe gestures should have visible controls. WCAG 2.2 includes minimum target-size and dragging-movement criteria that are particularly relevant to mobile interfaces.
Keep essential buttons away from overlays and browser edges, and test both portrait and landscape orientations. Real-device testing often reveals problems that a desktop responsive preview misses.
Treat PDFs and third-party tools as part of the experience
A website may be well structured while its most important information is trapped in an inaccessible PDF. Scanned images of menus, forms, reports and fee schedules need searchable text, a logical reading order, headings, meaningful links and properly tagged tables. When practical, provide the information as an HTML page as well.
Third-party booking engines, payment gateways, chat widgets, maps and form plugins also affect the customer journey. Ask vendors about keyboard operation, screen-reader testing, focus management, error handling and their WCAG conformance approach. Include accessibility in procurement requirements before a tool becomes expensive to replace.
If a supplier cannot fix a barrier immediately, document the issue, provide an alternative route and communicate how customers can complete the task. A telephone number can be useful, but it is not a universal substitute for an accessible online service.
Combine automated checks with human testing
Automated tools are valuable for finding missing labels, contrast failures, duplicate IDs and common code errors. They are not capable of deciding whether every alt description is useful, whether a page order makes sense, or whether a customer can complete a task comfortably.
Use at least four layers of review:
- Automated scanning across representative page templates.
- Keyboard testing of every critical journey.
- Screen-reader spot checks on navigation, headings, forms and dynamic messages.
- Testing with people with disabilities whenever the scale and importance of the service justify it.
The W3C’s Easy Checks resource offers a useful starting point for preliminary review. Treat the results as evidence for prioritisation, not a conformance certificate.
Keep a defect register with the affected page, barrier, user impact, WCAG reference, owner, due date and verification status. Re-test after fixes because a change in one component can create a problem elsewhere.
Use a 30-60-90 day improvement plan
In the first 30 days, fix barriers that prevent core tasks. Restore visible keyboard focus, label critical forms, correct unreadable contrast, add captions to essential videos, remove keyboard traps and provide accessible versions of high-priority documents.
During days 31 to 60, improve shared components and templates. Navigation, headers, footers, buttons, form patterns, modal windows and content cards affect many pages at once. Updating a design system produces more reliable gains than repairing the same defect page by page.
During days 61 to 90, strengthen governance. Add accessibility checks to design reviews, content publishing, development acceptance criteria, vendor procurement and staff training. Publish an accessibility statement that explains your commitment, known limitations and a clear way to report a problem.
Assign named owners. Accessibility declines when everyone supports it in principle but no one is responsible for the next action.
Ask better questions when briefing a web partner
A credible web team should be able to explain its process in practical terms. Ask which WCAG version and level it targets, which page templates it will test, how keyboard and screen-reader checks are performed, how defects are prioritised, and what evidence will be delivered at handover.
Request accessible components, not a promise to “install an accessibility pluginâ€. Overlays and widgets cannot repair every problem in content, structure, forms, code and third-party systems. Accessibility needs to be considered during discovery, design, development, content entry and quality assurance.
Also ask how the team protects mobile performance. Accessibility and speed should support each other through clean code, responsive layouts and purposeful media. Our guide to website performance optimisation explains why a technically heavy experience can cost users and conversions.
Make fewer customers fight the interface
An accessible website will not be finished by one audit, and no single tool can guarantee that every person will have the same experience. The useful goal is continuous reduction of real barriers: let more people perceive the information, operate the controls, understand the next step and complete the task.
For a Kenyan business, that work protects more than compliance. It improves the quality of the website, makes forms easier to complete, strengthens mobile usability and shows customers that the organisation has thought beyond the ideal user on the ideal device.
If your website needs a practical accessibility and usability review, talk to Dot Digital Agency about a structured website audit and improvement plan. We can assess priority journeys, identify design and content barriers, and help your team turn the findings into a clearer, more inclusive website rather than a report that sits unread.
