Skip to content

Legal

Accessibility Statement

How Kulea Hive works to make its website usable for everyone, the standard we aim to meet, known limitations, and how to report an accessibility problem or request an alternative format.

Last updated: July 2026

Legal review required

This document is a production-ready template that still requires review by Kulea Hive and its legal adviser. Items marked [PLACEHOLDER — …] must be confirmed and completed before publication.

Kulea Hive is committed to making its website usable by as many people as possible, regardless of ability, assistive technology or device. We want everyone to be able to find information, complete our forms and manage their privacy choices with confidence.

This statement explains what we have done to make the site accessible, where we know it still falls short, how we have assessed it, and how you can contact us if something does not work for you. It is an honest self-assessment: we describe the accessibility work built into the site to date, and we are candid that a formal, independent audit is still pending.

Our commitment

Kulea Hive believes that access to information and to the services we offer online should not depend on a person's disability, the device they use, or the assistive technology they rely on. We treat accessibility as an ongoing responsibility rather than a one-off task, and we aim to build it into how we design, write and maintain the site rather than adding it afterwards.

We recognise that accessibility is never fully finished. Standards evolve, content changes, and new barriers can appear. We are committed to identifying and removing barriers over time, and to responding constructively when someone tells us that part of the site does not work for them.

The standard we aim to meet

We aim to conform to the Web Content Accessibility Guidelines (WCAG) version 2.1 at Level AA, published by the World Wide Web Consortium (W3C). WCAG 2.1 AA is the standard most commonly referenced by accessibility law and policy internationally, and it is the target against which we assess our own work.

Aiming to meet a standard is not the same as having been independently certified against it. This statement records our own assessment of how far the site currently meets WCAG 2.1 AA. It has not yet been confirmed by a formal external audit — see "How we tested this website" below.

Measures we have taken

We have built a range of accessibility measures into the site. The most significant of these are:

  • Semantic HTML — pages are built with meaningful structure (headings, landmarks, lists and native controls) so that assistive technologies can interpret and navigate the content reliably.
  • Keyboard operability — interactive elements are designed to be reachable and usable with a keyboard alone, without requiring a mouse or trackpad.
  • Visible focus — a clearly visible focus indicator shows which element currently has keyboard focus, so keyboard users can see where they are on the page.
  • Reduced-motion support — where animation is used, we honour the operating-system "reduce motion" preference so that people who are sensitive to movement can avoid unnecessary animation.
  • ARIA where needed — we use WAI-ARIA roles, states and properties where native HTML alone does not convey enough information to assistive technologies, and we aim to avoid ARIA where native elements already do the job.
  • Accessible forms — our enquiry, newsletter and partnership forms use associated labels, clear instructions and error messaging intended to work with screen readers and other assistive technologies.
  • Accessible cookie and preferences dialogs — our cookie banner and Privacy Preferences dialog are built to be operable by keyboard and screen reader, so that managing consent does not itself become a barrier.
  • Colour-contrast care — we have designed text and interface colours with contrast in mind, aiming to meet the WCAG 2.1 AA contrast thresholds for text and essential interface elements.

Accessible privacy and consent controls

Managing your privacy should be as accessible as reading our content. When you first visit the site, a first-party cookie banner offers clear choices — accept all, reject non-essential, or manage preferences — and a Privacy Preferences dialog remains reachable from the footer at any time so you can change your mind later.

We have designed these controls to be operable using a keyboard and to be understandable with a screen reader, including where the dialog opens, moves focus and closes. Analytics does not run until you have granted consent, so declining or ignoring the banner does not degrade your ability to use the site.

We have not yet had these consent controls independently tested against the full range of assistive technologies. If you find any part of the cookie banner or Privacy Preferences dialog difficult to use, please tell us using the contact details below — accessibility of the consent experience is a priority for us.

Compatibility with browsers and assistive technology

We aim for the site to work with recent versions of the major web browsers and with commonly used assistive technologies, including screen readers and keyboard navigation.

We have not yet carried out structured testing across a defined matrix of browser and assistive-technology combinations. The specific combinations we have verified, and any that are known not to work well, are still to be confirmed: [PLACEHOLDER — list the browser and assistive-technology combinations tested, and any known incompatibilities].

Known limitations

We want to be open about where the site may not yet fully meet WCAG 2.1 AA. Because a formal audit has not yet taken place, the list below is provisional and based on our own review; it will be updated once the audit is complete.

Known or suspected issues and areas not yet audited: [PLACEHOLDER — list any known issues and not-yet-audited areas, for example third-party embedded content, PDF or other downloadable documents, complex interactive components, media without captions or transcripts, and any dynamic content that has not yet been assessed].

How we tested this website

The accessibility measures described in this statement reflect our own internal assessment carried out during design and development. This has included attention to semantic structure, keyboard operability, focus visibility, reduced-motion support and colour contrast as the site was built.

A formal, independent accessibility audit is still pending: [PLACEHOLDER — formal audit pending; record who will carry out the audit, the method used, the WCAG version and level assessed, and the date it was completed]. Until that audit is complete, the conformance claims in this statement should be read as a self-assessment rather than an independently verified result.

Alternative formats

If you need information from this website in a different format — for example accessible text, large print, or a format that works better with your assistive technology — please contact us and tell us what you need and which page or document it relates to. We will do our best to provide the information in a format that works for you.

The formats we can routinely provide, and any limits on what we can offer, are still to be confirmed: [PLACEHOLDER — confirm which alternative formats can be provided and any limitations].

How to report an accessibility problem

We welcome feedback on the accessibility of this website. If you encounter a barrier, find something difficult to use, or cannot access information you need, please tell us. Your feedback helps us find and fix problems we may not be aware of.

The most reliable way to reach us is through the Contact page on this website. When you get in touch, it helps if you can describe the problem, tell us the web address (URL) of the page concerned, and let us know the browser and any assistive technology you were using, so that we can reproduce and address the issue.

A dedicated accessibility contact address has not yet been confirmed: [PLACEHOLDER — confirm the accessibility contact email address]. Please note that the contact details shown elsewhere on the site are not yet fully harmonised, so the Contact page is the safest route until a single accessibility contact point is published.

Our response and timeframe

We aim to acknowledge accessibility reports and requests for alternative formats promptly, and to keep you informed while we work on a resolution. The specific timeframe within which we aim to respond is still to be confirmed: [PLACEHOLDER — response timeframe, for example the number of working days within which we aim to acknowledge and to respond substantively].

If you are not satisfied with how we have responded to your report, please let us know so that we can try to put things right, and see "Enforcement and escalation" below.

Enforcement and escalation

If you have raised an accessibility problem with us and are not satisfied with our response, you may be able to escalate the matter to a relevant regulator or oversight body. The applicable accessibility regime and the body responsible for enforcement will depend on where the site is provided and used.

The relevant enforcement regime and escalation route have not yet been confirmed for Kulea Hive: [PLACEHOLDER — identify the relevant accessibility regime and the enforcement or escalation body, and how to contact them].

Who is responsible for this website

This website is provided by Kulea Hive, a nonprofit registered as a company limited by guarantee with the National Investment Board of Sierra Leone under company registration number SL060326KULEA29231. Our registered office is at 6 Sanders Street, Freetown, Sierra Leone.

General enquiries, accessibility feedback and requests for alternative formats can be made through the Contact page on this website.

Keeping this statement up to date

We will review and update this statement as the site changes, as we complete accessibility testing, and as we resolve the limitations noted above. When a formal audit has been carried out, we will update the conformance claims and the "How we tested this website" section to reflect its findings.

This statement was last reviewed in July 2026. The date of the next planned review is still to be confirmed: [PLACEHOLDER — date of next planned review].