Accessibility statement

A website that cannot be used by somebody using a keyboard, a screen reader or a magnifier is not finished, whatever it looks like. This page says what we hold this site to, what we have actually built, and where we know it falls short.

The standard

We aim at the Web Content Accessibility Guidelines 2.2, level AA. We say aim rather than comply because compliance is a claim about every page at every moment, and the honest position is that we test, we fix what we find, and we want to hear about what we missed.

What is built in

• Every interactive thing on the site can be reached and operated with a keyboard alone, in an order that follows the page.
• A visible focus ring in the page ink, offset far enough from a filled button to stay visible on it.
• A skip link as the first thing in the tab order, so a keyboard or screen reader user is not walked through the whole header on every page.
• Semantic markup: real headings in order, real lists, real landmarks, and native disclosure elements for the question lists rather than a JavaScript accordion.
• Body text at 15px with a 1.6 line height on a measure held to roughly 46 to 58 characters, and it reflows rather than scrolling sideways when a page is zoomed.
• Colour contrast checked in both themes, and colour is never the only thing carrying a meaning.
• Every animation on the site stops for a reader whose system asks motion to be reduced, and the moving hero has its own pause control besides.
• Light, dark and system appearance, remembered between visits and applied before the first paint so nothing flashes.
• Text alternatives on images that carry meaning, and decoration marked as decoration so a screen reader passes over it.

What is not fixed yet

• Some photography on the site is still placeholder, and its alternative text describes the intended subject rather than the image now on screen. It is replaced as the commissioned photography lands.
• A very long page of case-study images is heavy on a slow connection, and we are still working on how much to load before you ask for it.
• We test with keyboard, with zoom, and with the screen readers we have. We have not put this site through a formal independent audit, and until we do we will not claim that it has passed one.

Telling us about a problem

Write to info@bonangtech.com or phone +27 72 823 2999. Say what page it was, what you were trying to do and what got in the way. You do not need to know the correct term for the problem. We answer inside two business days, and if a fix is going to take longer than that we tell you how long and then tell you when it is done.

What we do for clients

Everything on this list is in the price of a site we build. Accessibility is not a line item we quote separately, and it is not a phase two, because retrofitting it costs several times what building it in does.