Skip to content
https://www.fabsound.ie

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
5
REVIEW
3
PASS
16
INFO
0
Checks
24
16 PASS 3 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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::
2 navigation landmark(s) detected
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
7 landmarks
REVIEW
7 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.
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 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
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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title fabsound.ie ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 13 fail WCAG AA
REVIEW

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

7 pass 13 fail WCAG AA 3 pass AA only
a Previous Work
1.98:1
#000000
on
#363F50
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Contact
1.19:1
#000000
on
#171823
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span fabsound.ie
3.39:1
#000000
on
#625F6F
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Home
2.06:1
#000000
on
#3B4150
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Previous Work
2.90:1
#000000
on
#5B555D
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Contact
2.59:1
#000000
on
#4F4F58
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a More
1.18:1
#000000
on
#131724
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Home
1.81:1
#000000
on
#323945
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Previous Work
1.07:1
#000000
on
#0B0B11
needs 4.5:1 (normal text)
16px · mid-page
a Contact
1.20:1
#000000
on
#17191F
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
span FABsound
1.63:1
#000000
on
#2D323C
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
span Booming is Business
1.12:1
#000000
on
#0E121E
needs 4.5:1 (normal text)
16px · mid-page
span About Me
1.10:1
#000000
on
#0C1019
needs 4.5:1 (normal text)
16px · mid-page

10 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
title fabsound.ie6.02:14.5:1
#000000
#668CB9
Pass
div Search this site6.37:14.5:1
#000000
#6A91BA
Pass
span Embedded Files6.68:14.5:1
#000000
#6E95BB
Pass
span Skip to main content7.18:14.5:1
#000000
#769BBB
Pass
span Skip to navigation7.70:14.5:1
#000000
#909EB0
Pass
span fabsound.ie7.94:14.5:1
#000000
#89A2BA
Pass
a Home7.17:14.5:1
#000000
#8A98AC
Pass
a Previous Work1.98:14.5:1
#000000
#363F50
Fail
a Contact1.19:14.5:1
#000000
#171823
Fail
span fabsound.ie3.39:14.5:1
#000000
#625F6F
Fail
a Home2.06:14.5:1
#000000
#3B4150
Fail
a Previous Work2.90:14.5:1
#000000
#5B555D
Fail
a Contact2.59:14.5:1
#000000
#4F4F58
Fail
a More1.18:14.5:1
#000000
#131724
Fail
a Home1.81:14.5:1
#000000
#323945
Fail
a Previous Work1.07:14.5:1
#000000
#0B0B11
Fail
a Contact1.20:14.5:1
#000000
#17191F
Fail
span FABsound1.63:14.5:1
#000000
#2D323C
Fail
span Booming is Business1.12:14.5:1
#000000
#0E121E
Fail
span About Me1.10:14.5:1
#000000
#0C1019
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.

A
Heading Hierarchy
3 headings
PASS
3 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 FABsound
  • H1 Booming is Business duplicate H1
  • H2 About Me

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
All 3 heading(s) have substantive, well-formed text
PASS
All 3 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputsearchSearch this sitearia-label
A+
Form Input Types
1 form control(s) checked, no type mismatches
PASS
1 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 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-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tabindex Anti-Patterns
36 explicit tabindex attribute(s) checked, no anti-patterns
PASS
36 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+
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 19 visible text node(s) render at >= 12 CSS pixels
PASS
All 19 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.
A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 22 passed
PASS
100

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.

○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
●Buttons have an accessible name
●`[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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○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.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback