Skip to content

Gridsmith

Operate & Improve

Performance & Accessibility

It is slow, or it is unusable with a keyboard, and you have been told conflicting things about why.

Measuring what a site actually does for real users and fixing what the measurements show: loading performance and interaction responsiveness, and accessibility against WCAG 2.2 AA.

Findings come with the measurement that produced them. An audit that lists issues without the evidence is unarguable in both directions.

Automated testing finds a minority of accessibility problems. Where a full conformance position is needed, manual and assistive-technology testing is scoped explicitly and its limits are stated.

What this covers

  • Performance optimisation
  • Accessibility improvements

What you get

Measured audit
Included
Against real page loads and real assistive-technology behaviour, not a single score.
Prioritised fix list
Included
Ordered by user impact and effort.
Implementation of the fixes
Included
Where implementation is in scope.
Regression checks
Included
So the fixes stay fixed.

What you do not get

Formal accessibility certification
Not included
Not included unless explicitly scoped. We report the standards tested, the evidence, the findings and the residual issues.

How it runs, and what it asks of you

The six stages are the same on every Gridsmith engagement. Where your own time is listed, it is the part of a project that is worth knowing before it starts.

Consultation
We look at the current system, who maintains it, where it is hosted and what actually needs to change.
Planning & Scope
Scope is written as what the system will do, what it will not do, and who owns each account and environment at the end.
Approval & Start
Work starts once scope is agreed. Repository, environment and access arrangements are settled first, on the terms the written agreement sets out.
Design, Development & Updates
Built in reviewable increments on an environment you can see, rather than revealed at the end.
Delivery
Handover covers the running system, written documentation of how it is deployed, and the source-code and account arrangements the written agreement sets out.
Support (if applicable)
Maintenance, monitoring and further development are scoped separately rather than assumed — as further work or as an ongoing engagement.