Accessibility Statement

Access to electrical safety information and booking should not depend on how somebody sees a screen, uses a keyboard or pointer, enlarges text, or reads on a smaller device. London EICR Certificates is working to make this website understandable and operable for a broad range of users, including people who use assistive technology or adapt browser settings. We use WCAG 2.2 Level AA as a working reference for important journeys. This statement describes current measures and test coverage; it is not a claim that the whole website is fully compliant, formally audited or certified.

Last reviewed: 2026-08-01.

What this statement covers

This statement covers the current rebuilt website at the address shown in our site configuration. It includes public information pages, guidance, core service pages, location content, legal information and the residential price and booking journey implemented in this application. It does not certify third-party websites reached through external links, email software, telephone services, a user's own device, or historical pages that have not been migrated into the rebuild.

The website is being developed and reviewed in stages. Page templates and shared components mean an improvement can benefit several routes, but passing a check on one representative page does not prove that every page or every content combination is free from barriers. We therefore describe the tested scope precisely and invite reports about issues outside it.

Scope reviewed so far

Accessibility implementation and smoke checks have covered the homepage conversion work from H7 and H8, including navigation, key calls to action, pricing interaction and the route into booking. Reviews have also covered W3 core commercial pages, representative W5 location pages, W7 guidance articles, W9 content and hub templates, and W10 legal and operational routes. The W14-A1 and W14-A2 deepening work has added longer, more structured content to core commercial pages, selected guidance, the blog hub, validity guidance and this statement.

That scope gives us evidence about the main templates and priority user journeys, but it is not a complete accessibility audit of every URL, browser, operating system, viewport, language setting or assistive technology combination. Not every historical WordPress URL has been rebuilt or retested. Newly migrated routes and later content changes need continued checks rather than inheriting a permanent pass from the template.

Measures we take

• Semantic page structure, one primary heading and ordered section headings on core content templates.
• Descriptive page titles, link wording and breadcrumbs intended to make destinations understandable outside the surrounding paragraph.
• Visible labels and instructions for core form controls, with validation messages expressed in text rather than through colour alone.
• Keyboard-operable navigation and controls in reviewed journeys, with a visible focus treatment for interactive elements.
• Responsive layouts designed to reflow at smaller widths and support browser zoom without requiring a separate mobile-only content version.
• Classification-code summaries that include text labels so meaning is not colour-only.
• Consent controls designed not to prevent essential calculator or booking storage from performing its operational purpose.
• Plain-language explanations and qualified legal or technical wording where an oversimplified claim could mislead users.

Keyboard operation

Reviewed menus, links, buttons and core calculator or booking controls are intended to be reachable and usable without a mouse. Focus should remain visible, follow a meaningful order and not become trapped in a component. Native controls are preferred where they can provide the required behaviour. We also avoid relying on hover alone to expose information needed to understand a task.

Keyboard smoke testing is practical evidence, not exhaustive proof. It has focused on priority routes and representative components, and has not covered every browser and hardware combination. If focus disappears, moves unexpectedly, cannot reach a control, or cannot leave a control, please tell us the page, control and keys used.

Responsive layout, zoom and text

The shared layouts are designed to adapt across common desktop, tablet and mobile widths. Content should reflow, navigation should remain available and primary actions should not depend on a precise pointer target. Long guidance and legal pages use headings, paragraphs and lists so readers can scan the subject rather than face one uninterrupted block. Important report classifications combine words with colour.

We have performed responsive and zoom-oriented visual checks on priority templates, but we have not verified every device, custom font, extreme zoom level or browser extension. Very long words, user-generated values, browser translation and unusually narrow viewports may still create overflow or crowded controls. Users can report the viewport, zoom setting and browser involved so we can reproduce a layout problem.

Forms, calculator and booking

Core conversion controls are designed with visible prompts, programmatic labels where appropriate, keyboard interaction and textual error feedback. Required information should not be communicated only by position or colour. The residential price journey and booking route are treated as operationally important because a barrier there can prevent a user from completing the purpose of the site.

A form can still be difficult when instructions are unclear, an error is not announced as expected, or a session behaves differently with a particular browser or assistive setup. Users who cannot complete an online step can contact us by email or telephone using the details below. Contacting us does not imply that every service can be completed in every format, but we will consider a reasonable alternative way to receive the necessary information.

How we test

Our current process combines implementation review, semantic and content checks, keyboard smoke testing, responsive visual checks and automated accessibility tooling on selected routes. Automated tools are useful for detecting issues such as some missing names, structural problems or colour contrast failures. They cannot determine whether all wording is understandable, every focus sequence is sensible, or a complete task is practical for every user.

Chromium-based automated and manual checks are currently more developed than equivalent coverage in Firefox and WebKit or Safari. Testing has not been performed as a formal certification exercise with every major screen reader. In particular, we do not claim NVDA, JAWS, VoiceOver or TalkBack certification. Mentioning those products here describes the limits of our evidence; it must not be read as an assurance from their vendors or as a statement that all journeys have been tested with them.

Known limitations and continuing work

• The rebuilt priority routes have more current evidence than unmigrated or less frequently reviewed historical content.
• Cross-browser and assistive-technology coverage is incomplete, as described in the testing section.
• Some media assets remain within an open media review programme; text alternatives and the purpose of media require route-by-route review.
• Long technical and legal pages can remain cognitively demanding even when divided into headings, paragraphs and lists.
• External destinations and software used to open email or telephone links are outside our direct control.
• Automated test results can contain false positives and can also miss barriers; a clean automated result is not treated as full compliance.

We prioritise problems that block navigation, understanding, pricing, contact or booking, followed by recurring template defects that can affect several pages. Content deepening is reviewed for heading order, readable structure and link purpose, but future edits can introduce regressions. The statement will be updated when the tested scope or known limitations change materially.

Compliance position

Our aim is to work towards WCAG 2.2 Level AA on important user journeys and reusable components. We have not commissioned or completed a whole-site, independent conformance audit and do not state that every page conforms to all Level A and AA success criteria. We also do not use this statement as a quality badge, accessibility certification or guarantee that no individual will encounter a barrier.

Accessibility is an operational responsibility rather than a one-off launch check. Shared components, content, browser behaviour and user needs change. The practical standard is therefore to keep testing, record the limits honestly, respond to specific reports and correct confirmed barriers in proportion to their impact.

Feedback and alternative contact

If you encounter an accessibility barrier, email office@londoneicrcertificates.co.uk or call 0203 811 8331. If possible, include the page URL, what you were trying to do, what happened, and the browser, device or assistive technology involved. Do not include passwords, payment details or unnecessary sensitive information.

We will review the report, ask for clarification if needed and explain the next step. Where a barrier prevents access to information or a core task, tell us what format or contact method would help. Response and remediation time will depend on severity, reproducibility and technical scope; this statement does not promise an automatic deadline for every report.