Sample UX review

Here’s what a useful
finding looks like.

I reviewed the previous version of usability.ie in August 2026. These are real findings from that review, written the way I want a client report to read: what I saw, what changed and what I checked afterwards.

Previous usability.ie site · 22 August 2026 · Expert review

About this sample

Real findings from the previous version of this site, written the way I write client reports.

Usability.ie · Sample UX review22 Aug 2026 · Previous site

Three findings

What I found on my own old site.

Site

The previous usability.ie

Date

22 August 2026

Method

Expert review

What I covered

Homepage on desktop and mobile, the contact and About pages, keyboard use and selected colours

Finding 01Fixed on the old site

The main action was too hard to read.

2.80:1

Before · #d96c4f on #1f4d4a

5.24:1

After · #ffad8f on #1f4d4a

What I saw: The old coral-on-teal primary action (#d96c4f on #1f4d4a) measured 2.80:1 contrast.
What I changed: I changed the coral to #ffad8f against the same teal. The recorded contrast became 5.24:1.
How I checked it: I recalculated the contrast and checked the result in the browser at the time.

Finding 02Changed on the old site

The homepage gave people too many places to start.

What I saw: Several introduction and card sections were competing to be the first thing someone acted on.
What I changed: I reduced the competing choices and gave the page a simpler starting point.
Why it mattered: A first-time visitor needs one obvious place to start.

Finding 03Corrected on the old site

One accessibility explanation was simply wrong.

What I saw: The old About page described a universal text-size requirement that does not exist.
What I changed: I removed the claim and replaced it with an accurate explanation.
Why it mattered: If I’m selling accessibility work, my own explanation of the standard has to be right.

For client work

A client report goes further.

For client work, each finding also shows where the problem happened, who it affected, how to reproduce it, how serious it is, what I recommend changing, who owns the fix and what still needs testing with real people.

Screenshot of the screen
The task it affects
What happened
How serious it is, and why
What I recommend changing
Who owns the fix
Status
What still needs checking

The point

Short enough
to act on.

Someone should be able to read a finding on Monday morning and know what to do next.

Show me the problem See what I deliver ↗

Here’s what a usefulfinding looks like.