Accessibility Statement
WCAG 2.2 Level AA · UK GDPR & Data Protection Act 2018 Compliant · Last updated: July 2026
1. Our Commitment
Network Consultancy ("we", "us", "our") is committed to making this website usable by as many people as possible, including people with disabilities and people who rely on assistive technologies such as screen readers, switch devices, or voice navigation.
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the World Wide Web Consortium (W3C). These guidelines explain how to make web content perceivable, operable, understandable, and robust for people with a wide range of visual, auditory, physical, cognitive, and neurological conditions.
We treat accessibility as an ongoing responsibility rather than a one-off task, and we welcome feedback from anyone who runs into a barrier while using our site.
2. Conformance Status
Partially conformant — actively improving. This means some parts of the site do not yet fully meet WCAG 2.2 Level AA. The specific gaps are listed in Section 5 (Known Limitations) below. A formal, tool-verified colour contrast audit and a full interactive-component review have not yet been completed; everything else has been assessed through developer self-review and browser-based accessibility tooling.
| WCAG Principle | Status | Notes |
|---|---|---|
| 1. Perceivable | Partial | Colour contrast not formally verified across all pages |
| 2. Operable | Meets | Skip link, keyboard-operable navigation, and on-site search all present |
| 3. Understandable | Partial | Consistent navigation and labelled form fields; some error handling not fully confirmed |
| 4. Robust | Partial | Newer forms not yet confirmed as ARIA live regions; GTM iframe title being rolled out |
3. What WCAG 2.2 Level AA Requires
WCAG 2.2 is organised around four principles. Each groups the specific requirements ("success criteria") a website must meet at Level AA. WCAG 2.2 (published October 2023) extends WCAG 2.1 with six additional success criteria focused on low vision, cognitive, and motor disabilities; this statement covers the full WCAG 2.2 Level AA set, which includes all WCAG 2.1 AA criteria.
- Perceivable — text and images must reach a 4.5:1 colour contrast minimum (3:1 for large text), interface components must reach 3:1 non-text contrast, text must resize to 200% without breaking layout, meaningful images need real alternative text, and content must reflow at 400% zoom without two-dimensional scrolling.
- Operable — all functionality must work by keyboard alone with no traps, a skip link must let users bypass repeated navigation, focus must be clearly visible, more than one way must exist to find a page, focused elements must not be hidden by sticky headers or banners, no feature may require dragging without a single-click alternative, and interactive targets must be at least 24×24 CSS pixels or adequately spaced.
- Understandable — the page language must be correctly declared, form errors must be identified in text with a fix suggested where possible, help contact details must appear consistently across pages, information already entered should not be requested again in the same process, and any authentication step must not rely solely on memory or puzzle-solving.
- Robust — every interface component must expose its name, role, and state programmatically, and status messages such as form confirmations must be announced to screen reader users without requiring them to move focus manually (e.g. via
aria-live).
The Network Consultancy website does not currently host embedded pre-recorded video or live audio/video streams. Should any be added, captions and audio descriptions will be provided in line with WCAG 2.2 §1.2.4 and §1.2.5.
4. How We Address These Requirements
Perceivable
- Meaningful images carry descriptive alternative text; purely decorative images use empty
alt=""so they are skipped by screen readers - The site is responsive and built mobile-first; content reflows correctly down to 320 px viewports
- Typography uses relative units so text resizes cleanly to 200% browser zoom
- No informational content is presented as an image of text
- Colour is never the sole way we convey information, indicate an action, or distinguish an element
Operable
- A skip-to-main-content link is present on every page and becomes visible on keyboard focus
- Navigation, buttons, and form fields are reachable and operable by keyboard alone
- Site search is available site-wide as an additional way to locate a page, alongside the main navigation menu
- Every page has a unique, descriptive
<title>, a logical heading hierarchy, and semantic landmark regions (<header>,<nav>,<main>,<footer>) - No part of the site relies on drag-only interactions
Understandable
- Every page declares
<html lang="en"> - Header and footer navigation appear in the same order on every page
- Every form field is paired with a visible, programmatically associated
<label>— we do not rely on placeholder text alone - Our main enquiry form identifies required fields, validates before submission, and surfaces a clear text error if a required consent or field is missing
- Contact details (phone and email) appear in the footer in a consistent position on every page
- The site has no user login, so no authentication-related cognitive test applies
Robust
- Our main enquiry form's success and error messages are marked up as ARIA live regions (
role="status"/aria-live="polite"androle="alert"/aria-live="assertive") so screen reader users are notified automatically - HTML is written to semantic standards, favouring landmark elements over generic containers
- Compatibility is targeted at current versions of Chrome, Firefox, Safari, and Edge together with common assistive technology pairings (NVDA/JAWS with Chrome, VoiceOver with Safari)
5. Known Limitations
We are aware of the following gaps and are actively working through them:
Colour contrast — not formally tool-verified
Our primary body text and link colours have not yet been run through an automated contrast checker (such as axe or the WCAG Contrast Analyser) across every colour pairing on every page. We expect most combinations meet the 4.5:1 minimum, but this has not been formally confirmed.
Newer form status messages — ARIA live region not yet confirmed
Some newer forms added to the site (including specialist enquiry forms outside our main contact form) display a success or error message after submission, but it has not yet been confirmed that every one of these is exposed as an ARIA live region. Screen reader users may not always be notified automatically that a submission succeeded or failed.
Touch target size — not fully verified
Some smaller interface elements, such as footer icon links, have not been formally measured against the 24×24 CSS pixel minimum required by WCAG 2.2.
Google Tag Manager iframe — title attribute being rolled out
Every page includes a hidden, zero-dimension Google Tag Manager <noscript> iframe. A title="Google Tag Manager" attribute is being added across the site; its impact is negligible since the element is never visible, but it is a technical non-conformance until complete.
No formal third-party audit
Our assessment to date is based on developer self-review and automated browser tooling rather than an independent, accredited accessibility audit. We plan to commission a full third-party review in the future.
If you encounter a barrier not listed here, please tell us — we treat all accessibility reports as priority issues and aim to respond within five working days.
6. Exceptions — Where Contrast Requirements Do Not Apply
WCAG 2.2 explicitly excludes the following from the colour contrast requirements (criteria 1.4.3 and 1.4.11). These are not limitations — they are specified exceptions in the standard itself:
- Disabled interface elements — a greyed-out submit button on an incomplete form is exempt; its reduced contrast intentionally signals that the control is not yet active.
- Purely decorative or hidden text — text that conveys no information, or is hidden from all users, is exempt. Background imagery used purely for visual texture falls into this category on our site.
- Logotypes — text that forms part of a brand logo is exempt. The Network Consultancy logo is treated as a logotype under WCAG 2.2 and is not subject to the 4.5:1 minimum.
7. Feedback and Contact
We welcome feedback on the accessibility of this website. If you experience a barrier, find something difficult to use, or have a suggestion for how we could improve, please get in touch:
- Email: info@network-consultancy.com
- Phone: +44 (0) 203 150 1401
- DPA/GDPR-specific complaints: our Complaint Form
We aim to respond to accessibility enquiries within five working days. If a fix requires development work, we will provide an estimated timeframe for resolution.
8. Technical Specifications
This website is built with HTML5, CSS3, and vanilla JavaScript, deployed on Vercel with clean URLs (pages are reachable at paths such as /accessibility rather than /accessibility.html). Accessibility relies on:
- HTML5 semantic elements and landmark roles (
<header>,<nav>,<main>,<footer>,<section>) - CSS3 for responsive layout, focus styles, and colour contrast
- Vanilla JavaScript for interactive components such as the navigation, on-site search, and enquiry forms
- WAI-ARIA roles, states, and properties where interactive components require them
- A global skip-to-content link present on every page
9. Assessment Approach
We assessed this website against WCAG 2.2 Level AA using:
- Developer self-review of each success criterion
- Automated browser-based accessibility inspection tools to catch structural issues such as missing alt text, unlabelled form fields, or improper heading order
- Keyboard navigation testing across key pages for full operability and visible focus
No formal, accredited third-party audit has been conducted to date. The W3C provides a full reference at How to Meet WCAG (Quick Reference).
10. Date of This Statement
This accessibility statement was created in July 2026 and reflects the state of the Network Consultancy website at that date. It will be reviewed whenever significant content or structural changes are made, and at least once annually.
See also: Privacy Policy · Terms and Conditions · Cookies Policy · DPA/GDPR Complaint Form