Skip to content
https://Adva.ie

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
5
REVIEW
8
PASS
11
INFO
0
Checks
24
11 PASS 8 REVIEW 5 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-xt6ei3
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://Adva.ie/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://Adva.ie/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 ModeNo Dark Mode Detected
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::
1 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 1 <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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 header NAV MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

C
Alt Text Quality
Action
4 of 41 images have issues
REVIEW
4 of 41 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
37 image(s) with good alt text
41 images 37 good alt text 4 missing
IssueCount
missing4 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
Form Accessibility
2 of 6 controls have issues
REVIEW
2 of 6 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="image">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s" id="keyword">
Info::
4 control(s) properly labeled
6 controls
4 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#cmplz-functional-optincheckboxFunctionalfor/id
#cmplz-preferences-optincheckboxPreferencesfor/id
#cmplz-statistics-optincheckboxStatisticsfor/id
#cmplz-marketing-optincheckboxMarketingfor/id
#keywordtext(Can I help you find something)placeholder only
inputimage(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="image">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="s" id="keyword">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

B
Tap Target Adequacy
3 tap target(s) too small or too close together
REVIEW
3 tap target(s) too small or too close together
Info::
3 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA
title Adva Sign | Leading Print Professionals …
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
div Manage Consent
1.06:1
#000000
on
#0A0A0A
needs 4.5:1 (normal text)
16px · top of page (header area)
div To provide the best experiences, we use …
4.24:1
#000000
on
#707070
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span Always active
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
span The technical storage or access is stric…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
span Preferences
1.05:1
#000000
on
#06080A
needs 4.5:1 (normal text)
16px · above the fold
span Preferences
1.09:1
#000000
on
#0C0F13
needs 4.5:1 (normal text)
16px · above the fold
span The technical storage or access is neces…
1.11:1
#000000
on
#0F1015
needs 4.5:1 (normal text)
16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Adva Sign - Printing…14.88:13.0:1
#000000
#D9D9D9
Pass
h2 Motor Trade14.88:13.0:1
#000000
#D9D9D9
Pass
h2 Shop Signs14.88:13.0:1
#000000
#D9D9D9
Pass
h2 Print & Display14.88:13.0:1
#000000
#D9D9D9
Pass
h3 Specialists14.88:13.0:1
#000000
#D9D9D9
Pass
h3 Online14.88:13.0:1
#000000
#D9D9D9
Pass
h3 Solutions14.88:13.0:1
#000000
#D9D9D9
Pass
h3 Explore14.88:13.0:1
#000000
#D9D9D9
Pass
h3 Policies14.88:13.0:1
#000000
#D9D9D9
Pass
h3 CONTACT US14.88:13.0:1
#000000
#D9D9D9
Pass
title Adva Sign | Leading …1.00:14.5:1
#000000
#000000
Fail
div Manage Consent1.06:14.5:1
#000000
#0A0A0A
Fail
div To provide the best …4.24:14.5:1
#000000
#707070
Fail
span Functional21.00:14.5:1
#000000
#FFFFFF
Pass
span Functional21.00:14.5:1
#000000
#FFFFFF
Pass
span Always active1.00:14.5:1
#000000
#000000
Fail
span The technical storag…1.00:14.5:1
#000000
#000000
Fail
span Preferences1.05:14.5:1
#000000
#06080A
Fail
span Preferences1.09:14.5:1
#000000
#0C0F13
Fail
span The technical storag…1.11:14.5:1
#000000
#0F1015
Fail

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.

B
Lighthouse Accessibility Audits
Score 88/100 — 5 failing, 29 passed
REVIEW
88

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.

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
Talk to our team about your next print or signage project. div.adva-footer > div.adva-quote-inner > div.adva-quote-copy > span

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header#masthead > div.top-myaccount > span.lgoin-btn > a header#masthead > div.top-myaccount > span.lgoin-btn > a

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Show slide 1 div#page > div.home-banner > div#advaHeroCarousel > ol.carousel-indicators

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Show slide 1 div.home-banner > div#advaHeroCarousel > ol.carousel-indicators > li.active
Show slide 2 div.home-banner > div#advaHeroCarousel > ol.carousel-indicators > li
Show slide 3 div.home-banner > div#advaHeroCarousel > ol.carousel-indicators > li

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
(0) div.header-min > header#masthead > div.top-myaccount > span#mincart
○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
●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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`<input type="image">` elements have `[alt]` text
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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.
○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.
○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>`.
○All heading elements contain content.
○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 Hierarchy
20 headings
PASS
20 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Adva Sign - Printing, Signage and Motor Trade Products Ireland
  • H2 Motor Trade
  • H3 Specialists
  • H2 Shop Signs
  • H3 Online
  • H2 Print & Display
  • H3 Solutions
  • H4 Trusted by businesses across Ireland
  • H4 What our Clients say
  • H4 About Adva Sign
  • H3 Explore
  • H3 Policies
  • H3 CONTACT US
  • H1 Adva Sign - Printing, Signage and Motor Trade Products Ireland duplicate H1
  • H2 Motor Trade
  • H3 Specialists
  • H2 Shop Signs
  • H3 Online
  • H2 Print & Display
  • H3 Solutions

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
1 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 1 all-caps heading(s)
A+
Form Input Types
6 form control(s) checked, no type mismatches
PASS
6 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
6 form control(s) checked, no input-semantic issues
PASS
6 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
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
9 explicit tabindex attribute(s) checked, no anti-patterns
PASS
9 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Mobile-Readable Font Sizes
All 65 visible text node(s) render at >= 12 CSS pixels
PASS
All 65 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback