Accessibility on this site

Our target

Every page, component, and form on this site is designed and built against WCAG 2.1 Level AA. Where we discover something that falls short, we treat it as a defect to fix rather than a limitation to document and leave.

This commitment covers the whole public site, in both its light and dark themes, from a 320-pixel-wide screen upwards.

How this site is built

These are not intentions. Each one is a decision already made in the code, and each is something you can test for yourself.

Keyboard

• Everything interactive can be reached and operated with a keyboard alone — navigation, the mega-menu, dialogs, the theme toggle, filters, and every form control.
• A visible focus indicator follows you everywhere. It is a two-pixel ring with an offset, drawn in a colour tested against both themes, and it is never removed — only replaced with a higher-contrast equivalent on controls that need one.
• A “Skip to content” link is the first thing you reach on every page, so you do not have to tab through the navigation to get to the article.
• Dialogs and menus return focus to whatever opened them when they close, and can be dismissed with the Escape key.

Motion

• If your device is set to reduce motion, the site honours it. Scroll-reveal animations become a short fade or nothing at all, decorative movement stops, smooth scrolling is turned off, and animated counters settle straight on their final value.
• Nothing on the site flashes, blinks, or auto-plays with sound. Carousels advance only while you leave them alone and can be controlled directly.

Colour and contrast

• Text and interface colours are chosen to meet AA contrast ratios in both the light and the dark theme, not just in whichever one the designer happened to be using.
• Colour is never the only carrier of meaning. Form errors combine a colour, an icon, and a sentence. Status and provenance labels carry words as well as tints. Chart series are labelled, and the palette is chosen to stay separable for readers with colour-vision deficiency.
• Links inside body text are underlined, so they are distinguishable without relying on colour.

Structure and assistive technology

• Pages use real landmarks — header, navigation, main, and footer — with one h1 per page and headings that descend in order.
• Buttons are buttons and links are links, so they behave the way your software expects. Icon-only controls carry an accessible name; purely decorative icons are hidden from assistive technology entirely.
• The document language is declared, so screen readers use the right pronunciation rules.

Forms

• Every field has a visible, permanent label — never a placeholder standing in for one — and required fields are marked in text as well as with an asterisk.
• Error messages are attached to the control that caused them, describe what to do rather than only what went wrong, and move focus to the first field that needs attention.
• The result of a submission is announced through a polite live region, so you learn what happened without having to go looking for a message that appeared somewhere else on screen.
• Fields carry the browser's autocomplete hints, so stored details fill in as they should.

Content and layout

• Photographs carry alt text written to describe what is actually visible in the frame.
• Text sizes are fluid and respect your browser's text settings. The layout works from 320 pixels wide, and the page never scrolls sideways — wide tables and charts scroll inside their own container instead.
• The map of our operational footprint publishes the same information as a text list, so it can be read without a pointer, a basemap, or colour.

Known limitations

Listing these is more useful to you than pretending they do not exist.

• Scanned documents. The certificates annexed to our organizational profile are photographs of paper documents. They are images, not machine-readable text, and a screen reader cannot read them aloud. The information they contain — the registering authority, the reference number, and the date of issue — is written out as text on the registration page alongside each scan.
• The downloadable profile. The PDF of the organizational profile was produced by the organization and has not been remediated for accessibility. Ask us and we will supply the information in another format.
• The interactive maps. Map tiles come from a third-party basemap service and panning is a pointer interaction. Everything a marker says is also available as text beside the map.
• Charts. Figures shown in a chart are supported by the same numbers in the surrounding text. If you find a chart where they are not, that is a defect — please tell us.

Report a barrier

If any part of this site stopped you doing what you came to do, we want to hear about it — including the small things.

Email contact@wecareforyouinternational.org with “Accessibility” in the subject line, call +2348036492425 or +2347033502310, or use the contact form. It helps if you can tell us:

1. The page you were on, or its address.
2. What you were trying to do, and what happened instead.
3. The browser, device, and any assistive technology you were using — if you know, and if you would rather not say, report it anyway.

We will not promise a response time we cannot keep. What we will do is acknowledge your report, give you the information you were after by another route if we cannot fix the barrier immediately, and fix it in the site itself.

What we do not claim

This is a statement of target and commitment, not a certified conformance claim. This site has not been through an independent accessibility audit, and we have not published formal testing results against every assistive technology. Saying otherwise would be easy and dishonest.

If you carry out an audit of this site and share the findings with us, we will act on them. If you need a statement of our accessibility position for a procurement or funding process, ask and we will describe exactly what has and has not been tested.

Related: our privacy policy and terms of use.