Accessibility

Our interface approach

• Use semantic HTML and a logical heading structure.
• Support keyboard navigation and visible focus states.
• Provide a skip link for users who do not want to traverse navigation repeatedly.
• Use readable contrast, responsive layouts and scalable text.
• Respect reduced-motion preferences where the interface uses motion.
• Avoid making JavaScript the only way to access core public content.
• Design for smaller screens and variable connection quality rather than treating desktop broadband as the only context.

Content accessibility

Editors should add meaningful alternative text to informative images, avoid using images as the only carrier of essential text, use descriptive link wording, label tables clearly and structure long pages so headings remain understandable out of context.

Documents and third-party content

PDFs, third-party embeds, advertisements, external tools or legacy material may not meet the same accessibility standard as the MaishaThabiti interface. Where a barrier is identified, we should assess a practical fix, a more accessible alternative or a clearer explanation of the limitation.

Performance is part of access

Accessibility also includes the practical ability to load and use the site. The public interface should avoid unnecessary dependencies and should remain useful on modest devices and connections where reasonably possible.

Report a barrier

If part of MaishaThabiti is difficult to use because of an accessibility barrier, use the verified channel on the Contact Us page and identify the page, device or browser involved and the task you were trying to complete. Specific reports are especially useful for diagnosing and fixing the problem.

Last updated: 6 September 2026.