UXService DesignCourse Work

Accessibility Support Hub

Make court assistance easy to find, understand and intuitive to access for inclusive users.

Cabbage tree illustration used as part of the visual identity.

Aligned with the New Zealand Government’s Disabilities Strategy, this project developed the Accessibility Support Hub to organise fragmented court support information into a clear, inclusive digital experience.

The work streamlined how users find and request support services, creating a scalable information architecture that allows the new hub to merge smoothly with the current website. Through collaborative stakeholder workshops and data-driven usability testing, the project delivered a resilient design system and a repeatable framework.

ClientMinistry of Justice, MUXD Capstone
RoleProject Manager, UX Researcher, UX Designer
Team3 UX Designers
Timeline8 Weeks
ToolsFigma, FigJam, Framer, Microsoft Clarity, Procreate
HENEX LensR15 · Clarity & Accessibility AuditPerception × Empathy × Interface
Skills
Mixed methods researchProject managementDesign systemStakeholder managementSeverity ratingWorkshop facilitationDigital accessibility

Screencast

Prototype walkthrough.

A short walkthrough of the Accessibility Support Hub prototype and support pathway experience.

Background

Serving the NZ Disabilities Strategy.

In support of the New Zealand Government’s Disabilities Strategy, this project worked with the Ministry of Justice to create an Accessibility Support Hub.

The goal was to take scattered accessibility information and turn it into a clear, inclusive digital experience that helps users find and request court support services easily.

Diagram connecting the Ministry of Justice, the New Zealand Government Disabilities Strategy, the Accessibility Support Hub and court users.
MoJ, NZ Disabilities Strategy, Accessibility Support Hub and court users as the core project context.

Problem

How might we create a reusable and scalable pattern which offers an intuitive and supportive experience that makes it easy for people to find, understand, and request court assistance across the website?

Problem framing illustration showing confusion, fragmentation and exclusion.

Solution

A central landing page for all accessibility services.

The solution centralises accessibility services and uses “finding information” and “requesting services” as repeatable templates. The hub sits within the court area of the main site while keeping a clear connection to related pages.

White solution diagram showing the hub, scalability and guidance.

In this project, I wore two hats: Project Manager and UX Designer.

Project Manager

Keeping the project moving

I managed the schedule, led weekly meetings with the Ministry of Justice, and facilitated workshops to keep the project aligned.

UX Designer and Researcher

From research to high-fidelity

I built the roadmap, contributed to research, developed the interpreter service blueprint, designed the information architecture, and created prototypes for the wheelchair access flow.

The project used the Double Diamond framework as a base, while keeping the roadmap flexible enough to respond to research findings and stakeholder feedback.

Discover

Research, workshops and field survey.

Define

Evaluation, prioritisation and scope alignment.

Develop

Information architecture, prototype flows and design system work.

Deliver

High-fidelity prototype and documentation.

The final process looked like four overlapping waves, reflecting how discovery, design and validation happened in parallel rather than in a strict order.

Impacts

My key role across the project lifecycle.

01

Service Blueprint Workshop

Led the development of the service blueprint and facilitated the workshop.

02

Evaluative Workshop

Designed the evaluation framework, led the workshop, and aligned the project scope.

03

Information Architecture

Restructured the relationship between new and existing accessibility content.

04

Usability Test

Used severity rating and Clarity testing to create a prioritised design backlog.

05

Field Survey

Visited Wellington High Court to improve the accuracy of plain-language UX writing.

06

Prototyping

Updated related pages and designed wheelchair access pages from wireframes to high-fidelity prototypes.

I mapped out the Ministry’s current service flow for interpreter requests, covering both internal staff processes and the external website experience.

To ensure accuracy, I co-facilitated a workshop with Ministry of Justice staff to validate the service flow and identify real-world pain points.

Influence

This filled a blank in the Ministry’s documentation. It also helped us see the service as a whole system, where changing a small visible touchpoint affects everything beneath it.

Digital service blueprint covering user actions, frontstage touchpoints, backstage operations and support processes.

After research, the team realised the problems were connected across the whole system. With limited time and resources, the project needed a clear way to prioritise.

I designed a scoring framework based on control, capability, impact, and value. Both teams scored and merged results, placing problems on a feasibility-benefit quadrant.

Evaluation pathway: Summary of Insights → 4-Dimension Evaluation → Score Result → 4-Quadrant Grid.
Influence

This workshop narrowed the focus, improved how resources were used, and gave the Ministry a repeatable decision-making method.

The challenge was to link new pages with old ones without breaking the existing site.

It is like adding a modern bathroom centre to an old apartment building. People still enter through the old building, but each room now has a path into the new centre. Over time, both systems can merge.

Hand-drawn concept diagram explaining the relationship between existing Ministry pages and the Accessibility Support Hub.
Concept sketch for the relationship between existing Ministry content and the new hub structure.
Influence

This solved the problem of old and new pages existing at the same time and created a path for the website’s long-term growth. It also supported high-fidelity prototyping.

Information architecture diagram showing how the hub sits within the existing site structure while creating a path for future integration.

To turn test results into clear actions, I introduced NN/g’s severity rating method and Microsoft Clarity for behavioural analysis.

Severity Rating

Findings were turned into issues and scored by frequency, impact, and persistence. These scores formed a prioritised design backlog.

Severity rating chart. IS11 and IS6 ranked highest; issues rated by reviewers A, B, C with average severity trendline.

MS Clarity Analysis

For the wheelchair access flow, screen recordings alone were not enough, so I moved the Figma prototype into Framer and embedded Clarity tracking.

Microsoft Clarity scroll heatmap for prototype testing.
MS Clarity scroll heatmap. 100% of users reached the average fold; 31.58% reached the Popular Forms section.

Final Design

Clear and confident access to court support information.

The final design focused on making users feel supported and confident, reducing the mental effort required to find help through familiar patterns and clear guidance.

Final Accessibility Support Hub design shown on a laptop screen.
Final design direction for clear and confident access to court support information.

Key Feature

Always Have a Choice

Users should never feel stuck on a page. Related accessibility content is linked using lightweight tiles, clear text, and consistent button styles.

Accessibility Support Hub page showing clear pathways across accessibility support pages.
Clear pathways across both new hub pages and existing Ministry pages.

Key Feature

Search Result Optimisation

Most users start with search on public service sites. The search result pattern helps common keywords lead to structured, easy-to-read results.

Optimised search results page for court accessibility queries.
Helping users find court accessibility information faster.

Key Feature

Just Enough Information

The interface uses progressive disclosure, starting with simple titles and icons, then adding detail as user intent becomes clearer.

Interface showing progressive disclosure of court support information.
Progressive disclosure to reduce cognitive load.

Key Feature

Intuitive Guide

Court visit information follows a time-based journey, from site maps to floor plans, matching real-world expectations before a court visit.

Interface showing court visit guidance with visual information.
Navigation that matches real-world expectations before a court visit.

Design System

A consistent, accessible system built for reuse and growth.

Based on the Care of Children system, I led the creation of the design system, including brand direction, colour guidance, map legends, icon sets, and accessibility compliance.

Design system brand header.

Colour

Cabbage Green signals guidance and navigation. Care Pink expresses warmth and support. MoJ Blue is maintained for universal components.

Cabbage Green#13838AGuidance and navigation
Care Pink#A5205FWarmth and support
MoJ Blue#09397CUniversal components

Iconset

I designed a comprehensive set of icons for accessibility services, court facilities, and map legends.

Icon set for accessibility services, court facilities and map legends.

Accessibility

Main body text meets AAA contrast standards, while supporting text meets at least AA standards.

Accessibility guidance and contrast notes.

Retrospective

Looking back, looking forward.

Value

This capstone project delivered a complete, reusable way of working across management, decision-making, research, and design.

Learnings

The biggest takeaway was learning to be goal-oriented rather than task-oriented, doing less and enough, but doing it right.

Next Steps

  • Conduct testing on the high-fidelity prototypes.
  • Run cognitive testing on the new icon set.
  • Document the methodology into a Knowledge Base for the Ministry team.

Primary recipeR15 · Clarity & Accessibility AuditPerception × Empathy × Interface

This project uses R15 to connect how people understand support information, how the service recognises access needs, and how the interface turns repeated barriers into clearer pathways.

PerceptionEmpathyInterface