Online since 1998
HEAVY CAMPAIGNS

HEAVY CAMPAIGNS · Since 1998

Check website quality and accessibility with useful evidence

A practical scope for WCAG-informed development, performance checks and technical website acceptance, with explicit methods and boundaries.

Name what the review actually covers.

“Technically optimised” does not identify the work that was checked. Before engagement we specify relevant pages, components, states and user journeys. A useful result also records the date, method, environment and open findings. An automated score alone cannot describe that scope.

Our packages combine development with a documented review of the agreed foundation. This is a repeatable delivery task. Unknown third-party systems, large document inventories and additional functions need their own test scope.

Use WCAG to guide accessibility work.

WCAG 2.2 Levels A and AA guide development. Within the agreed review, automated checks are complemented by manual checks such as keyboard operation, focus, labels and contrast. Layout review includes narrow views and enlarged presentation.

A bounded review is not a full conformance evaluation. That requires appropriate assessment of all applicable criteria and complete processes within the defined scope. Screen-reader and user testing, and document or video remediation, are expressly commissioned where needed. WCAG-informed development does not itself certify legal compliance.

Measure performance and search foundations honestly.

Images, scripts, hosting, devices and network conditions affect loading and interaction. Lab tests help find problems under known conditions. Real-user data describes different conditions and may be insufficient on a low-traffic website. We distinguish those forms of evidence rather than promise a fixed PageSpeed score.

Within the agreed scope, technical search work includes useful metadata, headings, indexing and internal links. It cannot replace editorial quality or demand. Search positions and citations in AI-generated answers are not guaranteed.

Security requires ongoing ownership.

Current software, controlled access and a manageable component estate provide important foundations. No website package can rule out unknown vulnerabilities or faults in an application, extension or underlying infrastructure. Ongoing care and backups therefore need their own operating responsibilities.

A launch review is neither a penetration test nor a continuous maintenance contract. Define the systems covered and the incident process before commissioning those services.

A record that helps people decide what to do.

A useful test record connects the observation, its impact and a next action. It also identifies what has not been checked. Findings against criteria owed under the engagement must be addressed; an open-items list is not a blanket exclusion of contractual work or liability.

  • The criterion and affected page or component.
  • Method, conditions and observed result.
  • Status: checked, finding present or not yet checked.
  • Owner, action and any required approval.

Sources and boundaries

This is a planning guide, not a certification, legal assessment or promise of rankings, revenue or conversion gains.

Put this into your website scope

Each website package includes a defined quality foundation. A full accessibility audit or specialist testing is an expressly agreed additional scope.

A design system for an editable business website

Plan information architecture for a B2B website

B2B website audit checklist

WordPress care contract: scope and boundaries