Durban · KwaZulu-Natal

Readable interfaces, audited with care

We partner with product teams on frontend implementation decisions and run accessibility audits that map findings to WCAG 2.2—so your site works for keyboard users, screen-reader visitors, and everyone in between.

Accessibility audit scope Describe your site

Consultants reviewing interface markup together at a desk

What we take on

Engagements are billed by the day or as fixed-scope audits. We do not sell subscriptions or host your code— we review, document, and pair with your developers.

Developer typing HTML and CSS on a laptop

Frontend consulting

Component structure, semantic HTML, performance budgets, and CSS architecture for marketing sites and web apps your team already maintains.

Consulting details

Person using assistive technology with a large monitor

Accessibility audits

Manual and assistive-technology testing with a prioritised defect log, severity ratings, and remediation notes your engineers can implement.

Audit deliverables

Video call between client and consultant

Remediation pairing

Short blocks of live pairing after an audit so fixes land correctly the first time—especially for focus order, labels, and live regions.

All consulting offers

A recent municipal forms project

A KwaZulu-Natal council needed their permit application flow to meet public-sector accessibility expectations before go-live. We audited twelve screens, flagged missing field associations on three steps, and rewrote error summaries so screen readers announced failures in plain language. Delivery took nine working days including one on-site review with their vendor.

From the journal

When `:focus-visible` beats removing outlines

Outline resets are still common in legacy CSS. Here is how we document focus styles for audit clients.

Colour contrast for inline field errors

Red text on white often fails 4.5:1. Practical combinations we recommend in South African government palettes.