Accessibility examination
Review key journeys across websites, forms, and documents. Plan automated checks alongside keyboard and assistive-technology testing.
The record: scoped findings, evidence, and user impact.
Digital accessibility / Public-facing services
Find out where you stand.
Then make a plan to put things right.
Accessibility examination and remediation support in development for municipalities, public bodies, and organizations. Starting with the websites, documents, and media people rely on.
01 / The proposed practice
Not every organization needs the same engagement. Start with a defined scope, the people affected, and a deliverable your team can actually use.
Review key journeys across websites, forms, and documents. Plan automated checks alongside keyboard and assistive-technology testing.
The record: scoped findings, evidence, and user impact.
Turn findings into work your staff or web vendor can act on. Agree priorities, ownership, and how each fix will be checked.
The record: an action plan and verification notes.
Organize supporting evidence and unresolved questions for the client's review. Ontario portal assistance remains subject to ministry clarification.
The record: an evidence index and readiness summary.
Scope caption, transcript, and description needs for meetings, briefings, and recordings. Separate draft generation from quality review.
The record: a media inventory and review plan.
02 / A finding, not just a score
A useful report connects a barrier to a real task. It explains what happened, who it affects, and what to do next.
03 / Start small
You do not need to know the name of a standard to start a conversation. Choose a starting point for a practical project brief.
Runs in your browser. Nothing is submitted or saved by this guide.
Your starting plan
Choose something people need to do: request a service, read a notice, or follow a meeting. Bring the public link and describe where someone gets stuck. That gives us a useful starting point for the scope.
This guide helps scope a conversation. It does not determine legal obligations, deadlines, or compliance.
Before an engagement
Agree the scope, deliverables, timetable, access needs, data handling, and fees in writing before work begins. Procurement requirements should be discussed, not assumed.
A scan or accessibility menu does not establish compliance. Our proposed deliverables are not legal advice, government certification, or a guarantee of compliance.
Our proposed reporting role is to prepare supporting evidence, not to certify on a client's behalf. Legal questions belong with qualified counsel.
The name / The purpose
The running joke about maps missing New Zealand inspired our promise: nobody gets left off the map.
Digital services can leave people out, too. A form that cannot be completed with a keyboard. A meeting without captions. A document that a screen reader cannot navigate. Our work starts by looking for the people and tasks a design has missed.
Our name comes from te reo Māori. Te Aka Māori Dictionary includes the meanings to include
and to form an alliance
. Those meanings inform our focus on participation and working together.
Access to this site
Our design target is WCAG 2.2 Level AA. This site is under development; this is a target, not a conformance claim or independent certification.
Use the text-size and theme controls in the header, or your browser's zoom. The site includes keyboard focus indicators and respects reduced-motion preferences.
Found a barrier? Tell us the page, what you were trying to do, and your preferred way to receive a reply. Please leave out sensitive personal information. Use the same contact below for accessibility enquiries.
bob@whakauru.comA good place to begin
A website, a document, a council meeting.
Start with the service and the people it needs to reach.