Skip to content
https://guadeloupehub.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
76
GRADE
C
FIX
7
REVIEW
4
PASS
13
INFO
0
Checks
24
13 PASS 4 REVIEW 7 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <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 (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

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

F
404 Error Page
Action
HTTP 503, bare page
FIX
HTTP 503, bare page
Warning::
Unexpected status code: HTTP 503
Expected HTTP 404 but received 503. This may confuse search engine crawlers.
Got: HTTP 503
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 503 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Back-to-top link detected
Info::
3 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 3 <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.
D
Lighthouse Accessibility Audits
Action
Score 65/100 — 4 failing, 8 passed
FIX
65

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

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
div.middle_left > div.header_side_container > div.logo_container > a div.middle_left > div.header_side_container > div.logo_container > a
div.span4 > div#custom_html-2 > div.textwidget > a div.span4 > div#custom_html-2 > div.textwidget > a
div.span4 > div#custom_html-2 > div.textwidget > a div.span4 > div#custom_html-2 > div.textwidget > a
div.span4 > div#custom_html-2 > div.textwidget > a div.span4 > div#custom_html-2 > div.textwidget > a
div.span4 > div#custom_html-2 > div.textwidget > a div.span4 > div#custom_html-2 > div.textwidget > 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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○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-hidden="true"]` is not present on the document `<body>`
●Image elements have `[alt]` attributes
●Background and foreground colors have a sufficient contrast ratio
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●All heading elements contain content.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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.
○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.
○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>`.
○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.
B
Heading Hierarchy
12 headings
REVIEW
12 headings
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H1 (empty)
  • H1 Guadeloupe HuB duplicate H1
  • H2 Featured categories
  • H2 Popular listings
  • H2 How it works
  • H2 HELLO EASTER DAY
  • H3 Tips & Articles
  • H3 Join our community
  • H3 Our Location
  • H3 Emails
  • H3 Contact Us

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

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

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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 Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA
h1 Guadeloupe HuB
1.27:1
#000000
on
#052325
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Featured categories
1.27:1
#000000
on
#052325
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Popular listings
1.27:1
#000000
on
#052325
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How it works
1.27:1
#000000
on
#052325
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Tips & Articles
1.27:1
#000000
on
#052325
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Join our community
1.27:1
#000000
on
#052325
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Our Location
1.27:1
#000000
on
#052325
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Emails
1.27:1
#000000
on
#052325
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Contact Us
1.27:1
#000000
on
#052325
needs 3.0:1 (large text)
19px · bottom of viewport
span Explore
1.59:1
#000000
on
#362F28
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span All Listings
1.31:1
#000000
on
#162423
needs 4.5:1 (normal text)
16px · above the fold
span Listings without Map
1.27:1
#000000
on
#142120
needs 4.5:1 (normal text)
16px · above the fold
span Post a Listing
1.47:1
#000000
on
#192D34
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Listing Dashboard
1.25:1
#000000
on
#10201F
needs 4.5:1 (normal text)
16px · above the fold
span Single Listing
1.15:1
#000000
on
#0F1615
needs 4.5:1 (normal text)
16px · above the fold
span Pages
1.20:1
#000000
on
#0C1C1E
needs 4.5:1 (normal text)
16px · above the fold
span About Us
1.16:1
#000000
on
#0B1818
needs 4.5:1 (normal text)
16px · above the fold

2 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 Guadeloupe HuB1.27:13.0:1
#000000
#052325
Fail
h2 Featured categories1.27:13.0:1
#000000
#052325
Fail
h2 Popular listings1.27:13.0:1
#000000
#052325
Fail
h2 How it works1.27:13.0:1
#000000
#052325
Fail
h3 Tips & Articles1.27:13.0:1
#000000
#052325
Fail
h3 Join our community1.27:13.0:1
#000000
#052325
Fail
h3 Our Location1.27:13.0:1
#000000
#052325
Fail
h3 Emails1.27:13.0:1
#000000
#052325
Fail
h3 Contact Us1.27:13.0:1
#000000
#052325
Fail
span Home21.00:14.5:1
#000000
#FFFFFF
Pass
span Home Variant I21.00:14.5:1
#000000
#FFFFFF
Pass
span Home Variant II21.00:14.5:1
#000000
#FFFFFF
Pass
span Explore1.59:14.5:1
#000000
#362F28
Fail
span All Listings1.31:14.5:1
#000000
#162423
Fail
span Listings without Map1.27:14.5:1
#000000
#142120
Fail
span Post a Listing1.47:14.5:1
#000000
#192D34
Fail
span Listing Dashboard1.25:14.5:1
#000000
#10201F
Fail
span Single Listing1.15:14.5:1
#000000
#0F1615
Fail
span Pages1.20:14.5:1
#000000
#0C1C1E
Fail
span About Us1.16:14.5:1
#000000
#0B1818
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 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+
Alt Text Quality
All 3 images OK
PASS
All 3 images OK
Info::
2 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
3 images 1 good alt text 2 decorative
All images have appropriate alt text.
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 44 visible text node(s) render at >= 12 CSS pixels
PASS
All 44 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