Free checklist Book a call →
Home/ Solutions/ UX optimisation and accessibility

Grow

UX optimisation and accessibility

For teams whose site or product works, but not for everyone and not quickly enough. We find where journeys stall, where people using keyboards or screen readers get stuck, then fix it and keep it fixed.

Book a call → Get the CTO checklist

What this covers

UX optimisation and accessibility, end to end.

WCAG audit against 2.2 AA

A full pass over your key templates and journeys, tested with real assistive technology rather than a scanner alone. Every issue gets a location, a success criterion, a severity and a fix, not a score out of a hundred.

Keyboard and focus order

Every control reachable with a keyboard, in an order that matches the visual layout, with a focus ring you can actually see. Modals trap focus and return it. Skip links work. Nothing becomes unreachable at 200% zoom.

Screen reader behaviour

We test with NVDA, VoiceOver and TalkBack. Headings form a real outline, form fields have labels tied to them, errors are announced, and dynamic content changes are read out instead of happening silently.

Colour and contrast

Text, icons, form borders and focus states checked against the AA ratios. Where a brand colour fails, we propose the nearest passing value rather than telling you to abandon your palette.

Journey and funnel work

We map the steps between arriving and converting, find where people drop out, and cut what is not needed. Fewer fields, clearer errors, obvious next actions. Changes are measured, not just asserted.

Accessible design system

Components hardened once so the fixes hold: form fields with proper label and error patterns, buttons with real states, tables that navigate correctly. Built into Webflow, Shopify or your own front end.

How it runs

Plan. Build. Run.

01

Thirty minute call

You tell us the site, the journeys that matter and whether anything has forced this on you, such as a complaint or a procurement question. We say what we would look at first and whether we are the right people.

02

Audit and prioritise

We test the key templates and journeys with real assistive technology and produce a list ordered by who is blocked and how badly. You get fixed scope, timeline and price before any work starts.

03

Build the fixes

We work through the list, starting with anything that blocks people outright. Each fix is retested against the criterion it was raised under, and we hand back the before and after so you can see what changed.

04

Run it

Accessibility regresses the moment someone ships a new component. We can stay on to check new work, rerun the audit on a schedule, and report what we found and fixed each month.

Why infoloop

We do not hand over and leave.

  • We stay on afterwardsMost audits arrive as a PDF and nothing changes. We fix what we find, then run the site: monitoring, fixes with response targets, security updates and a monthly report.
  • Tested with real assistive techAutomated tools catch a fraction of the problems and miss almost everything about whether a journey makes sense. We use them as a first pass, then test by hand.
  • Fixed scope and priceYou know the cost and the timeline before the work starts. Accessibility work has a habit of expanding, so we agree what is in and what is a later phase up front.
  • We build the thing tooWe build Webflow and Shopify sites and put AI systems into production. Fixes land in your actual codebase or Webflow project, not in a document describing what someone else should do.
  • Plain reportingEach issue names the criterion, where it appears, who it affects and what we did. No score out of a hundred that hides three blocking problems behind ninety passing checks.

What you get

Every engagement includes these, in writing, before work starts.

  • A written audit of your key templates and journeys against WCAG 2.2 AA, issue by issue
  • A prioritised fix list ordered by who is blocked, with effort and severity on each item
  • Keyboard and screen reader test notes covering NVDA, VoiceOver and TalkBack
  • A contrast report with passing replacement values for any brand colour that fails
  • Accessible component patterns built into your Webflow project, Shopify theme or front end
  • A retest after the fixes ship, showing each issue and its status before and after

Who this is for

Three situations where this is the right call.

A procurement question you cannot answer

A prospect or public sector buyer has asked for an accessibility statement or a conformance report and nobody knows what to send. You need the site tested honestly and the gaps closed before the deal moves on.

A journey that leaks people

Traffic arrives and does not convert, and analytics tells you where people leave but not why. You want the steps mapped, the friction removed and the change measured rather than argued about.

A rebuild going live soon

You are about to launch a new site or store and would rather not discover a fortnight later that the checkout cannot be completed with a keyboard. Cheaper to fix in the design system than across forty live pages.

Proof

Software we built, and still run.

How we work

Read it →

Questions

What buyers ask us first.

What does an accessibility and UX engagement cost?
We quote a fixed price after a thirty minute call and a short look at the site, because the cost depends on how many distinct templates and journeys exist rather than how many pages you have. A site with eight templates and one checkout is a much smaller job than a product with forty screens. The audit is priced separately from the fixes, so you can take the findings and hand them to your own team if you prefer. You get scope, timeline and price in writing before anything starts, and the ongoing run retainer is quoted separately again.
Which standard do you test against?
WCAG 2.2 at level AA, which is the level referenced by most procurement requirements, the European Accessibility Act and public sector rules in the UK and elsewhere. We test the AA success criteria that apply to your content and tell you plainly which ones you fail and where. We are not a certification body and we do not issue conformance certificates. What we give you is an honest audit, the fixes, and a retest showing what changed, which is what an accessibility statement needs to be based on anyway.
Is an automated scan not enough?
No. Automated tools reliably catch missing alternative text, some contrast failures and malformed markup, which is useful, but they check a minority of the success criteria and cannot judge whether anything makes sense. A scanner will pass an image with alternative text reading "image1.jpg" and pass a form whose error message says only "invalid". It cannot tell you that the focus order jumps from the header to the footer. We run scanners as a first pass, then test by keyboard and with NVDA, VoiceOver and TalkBack.
Will accessibility changes break our brand or design?
Very rarely, and where there is genuine tension we bring you options rather than a verdict. Most fixes are invisible to sighted mouse users: correct heading structure, labels tied to fields, focus management in modals, sensible names on controls. The visible ones are usually a focus ring and a contrast adjustment. Where a brand colour fails against its background we work out the nearest value that passes and show it beside the original, so the change is a small shift rather than a new palette. Your designers keep the final say.
What happens after the fixes ship?
Accessibility is not a one off. It regresses the first time someone adds a component, changes a colour token or ships a new landing page. Our run retainer covers that: monitoring, fixes within agreed response targets, security updates, improvements, and a monthly report on what we found and what we did. We can also review new work before it goes live and rerun the audit on a schedule you choose. If you would rather run it yourselves, we hand over the patterns and test notes so your team can.
How long does it take?
The audit on a typical marketing site or store takes a small number of weeks, because the work is bounded by the number of distinct templates and journeys rather than the page count. The fixes take longer and depend on what we find and where it lives, which is why we scope them after the audit rather than guessing beforehand. Anything that blocks people outright, such as a checkout that cannot be completed with a keyboard, we raise as soon as we find it rather than holding it for the final report.

Related

You might also need.

Performance Marketing Services

Paid acquisition measured against pipeline, not impressions.

See more →

eCommerce Growth Solutions

Merchandising, retention and checkout work that moves store revenue.

See more →

IT Strategy & Process Optimization

Deciding what to build, buy or retire, per workflow.

See more →

Find out what your site is costing you

Thirty minutes on a call. Tell us the journeys that matter and what has prompted this. We will tell you what we would test first, what it would cost and whether we are the right people for it.

Book a call → Get the CTO checklist
Book a call Checklist