Skip to content
https://www.activatedigital.co.uk

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
81
GRADE
B
FIX
4
REVIEW
6
PASS
14
INFO
0
Checks
24
14 PASS 6 REVIEW 4 FIX
D
Heading Hierarchy
Action
54 headings, 2 skip(s)
FIX
54 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
5 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 (empty)
  • H2 (empty)
  • H2 (empty)
  • H2 (empty)
  • H2 (empty)
  • H2 We're a Digital Marketing Agency That Helps Brands Win With Technology and Strategy.
  • H2 We Are...
  • H2 We Believe...
  • H2 We Deliver...
  • H2 What We Do
  • H3 Attract
  • H3 Engage
  • H3 Convert
  • H3 Retain
  • H2 Our Work
  • H3 CONNECT Aviation
  • H3 CONNECT Aviation
  • H3 Sunday Treat
  • H3 Sunday Treat
  • H3 iXtract
  • H3 iXtract
  • H3 City Explorer
  • H3 City Explorer
  • H3 Stage Security
  • H3 Stage Security
  • H3 iDuct
  • H3 iDuct
  • H3 Hutcheon Law
  • H3 Hutcheon Law
  • H3 Intelligent Scaffolding
  • H3 Intelligent Scaffolding
  • H3 Sugar & Lime
  • H3 Sugar & Lime
  • H1 A High-Performance Digital Marketing Agency in Liverpool - Why Should You Choose Us?
  • H3 Talented Team of Experts skipped
  • H3 Technology-Driven Approach
  • H3 Experienced in Multiple Sectors
  • H3 Focused on Excellent Results
  • H2 New Pixels
  • H2 Customer Journey
  • H6 Reaching Your Audience skipped
  • H6 Engaging Your Users
  • H6 Increasing Your Sales
  • H6 Satisfying Your Customers
  • H6 Related Services
  • H6 Related Services
  • H6 Related Services
  • H6 Related Services
  • H2 Latest News
  • H2 3 Lead-Generation Strategies That Work in 2026
  • H2 Stage Security: Increasing Inbound Enquiries Across East Anglia
  • H2 How to Build Backlinks That Actually Drive Customers (Not Just Rankings)
  • H2 Talk to Us Now
  • H2 Tell Us What You Need

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ff1563
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN ASIDE CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

B
Alt Text Quality
2 of 62 images have issues
REVIEW
2 of 62 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
8 decorative image(s) correctly marked
Info::
52 image(s) with good alt text
62 images 52 good alt text 8 decorative 2 missing
IssueCount
missing2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | Activate Digital ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
5 icon(s) detected
REVIEW
5 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Activate Digital
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Activate Digital ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode standalone ✓
Name Activate Digital Display Mode standalone Theme Color #FF1563 Background Color #ffffff Icons 2 icon(s)
B
Lighthouse Accessibility Audits
Score 89/100 — 3 failing, 23 passed
REVIEW
89

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot
div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot
div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot
div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot
div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot div.col-12 > div#heroCarousel > div.owl-dots > button.owl-dot

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Show More div.block-wrap > div.block > div.inner > a.ts-small-button-tag
Show More div.block-wrap > div.block > div.inner > a.ts-small-button-tag
Show More div.block-wrap > div.block > div.inner > a.ts-small-button-tag
Show More div.block-wrap > div.block > div.inner > a.ts-small-button-tag
Powered By Dribbble div.row > div.content-col > div.powered-by > p.mb-0
Interest div.navbar-nav-scroll > ul.navbar-nav > li.nav-item > a#funnel1MobLink
Action div.navbar-nav-scroll > ul.navbar-nav > li.nav-item > a#funnel2MobLink
Services div.menu-footer-container > ul#menu-footer > li#menu-item-1639 > a
Our Work div.menu-footer-container > ul#menu-footer > li#menu-item-1637 > a
Industries div.menu-footer-container > ul#menu-footer > li#menu-item-1636 > a
About Us div.menu-footer-container > ul#menu-footer > li#menu-item-1633 > a
Blog div.menu-footer-container > ul#menu-footer > li#menu-item-1632 > a
Enquire Now div.menu-footer-container > ul#menu-footer > li#menu-item-1635 > a

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Talented Team of Experts div.block-wrap > div.block > div.inner > h3.h6
Reaching Your Audience div.left > div.inbox > div#funnel0Content > h6

These are opportunities to improve keyboard navigation in your application.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A+
Heading Text Quality
All 54 heading(s) have substantive, well-formed text
PASS
All 54 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
A+
Document Language
Lang attribute set to "en-GB"
PASS
Lang attribute set to "en-GB"
Info::
<html lang="en-GB"> is set and valid
Got: en-GB
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 92 visible text node(s) render at >= 12 CSS pixels
PASS
All 92 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 A High-Performance D…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 We're a Digital Mark…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 We Are...21.00:13.0:1
#000000
#FFFFFF
Pass
h2 We Believe...21.00:13.0:1
#000000
#FFFFFF
Pass
h2 We Deliver...21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What We Do21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our Work21.00:13.0:1
#000000
#FFFFFF
Pass
h2 New Pixels21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Customer Journey21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Latest News21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Talk to Us Now21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Tell Us What You Nee…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 CONNECT Aviation21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Sunday Treat21.00:13.0:1
#000000
#FFFFFF
Pass
h3 iXtract21.00:13.0:1
#000000
#FFFFFF
Pass
h3 City Explorer21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Stage Security21.00:13.0:1
#000000
#FFFFFF
Pass
h3 iDuct21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Hutcheon Law21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Intelligent Scaffold…21.00:13.0:1
#000000
#FFFFFF
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback