Skip to content
https://www.masoncircle.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
76
GRADE
C
FIX
6
REVIEW
4
PASS
14
INFO
0
Checks
24
14 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
21 landmarks
FIX
21 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.
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

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 500, custom page
FIX
HTTP 500, custom page
Warning::
Unexpected status code: HTTP 500
Expected HTTP 404 but received 500. This may confuse search engine crawlers.
Got: HTTP 500
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 500 ✗Page Title Database Error ✓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
No navigation patterns
FIX
No navigation patterns
Info::
3 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 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.
C
Heading Hierarchy
Action
30 headings, 3 skip(s)
REVIEW
30 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
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.
  • H1 Digital Marketing Agency for Restaurants, Real Estate, Hospitality, and Luxury Brands
  • H2 A COLLECTION OF DIVERSE LIFESTYLE BRANDS FUELLED BY CREATIVITY & TECHNOLOGY
  • H5 Club Mason Circle skipped
  • H5 Showcase your business
  • H5 Shop Mason
  • H2 Digital Marketing Services
  • H3 SEO & Local Search
  • H3 Social Media Marketing
  • H3 Paid Ads & PPC
  • H3 Branding & Creative Production
  • H3 Content Marketing
  • H3 Web Design & Conversion Optimisation
  • H2 EXPLORE THE COLLECTION
  • H2 Industry-Specific Solutions
  • H5 Let's Work Together skipped
  • H3 Digital Marketing Agency in London
  • H2 Who is MASON CIRCLE?
  • H3 Official Partners
  • H3 Frequently Asked Questions
  • H2 Why Choose MASON CIRCLE?
  • H2 Start Working with Mason Circle
  • H2 What’s happening
  • H6 Contact Us skipped
  • H6 Partner with us
  • H6 Join Club Mason Circle
  • H2 Mason Circle International
  • H2 Mason Circle International
  • H2 Contact Us
  • H2 Careers
  • H2 Club Mason Circle

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

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

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, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Digital Marketing Agency for Restaurants…
1.77:1
#000000
on
#3C3632
needs 3.0:1 (large text)
32px · bottom of viewport
h2 A COLLECTION OF DIVERSE LIFESTYLE BRANDS
1.77:1
#000000
on
#3C3632
needs 3.0:1 (large text)
24px · bottom of viewport
h2 FUELLED BY CREATIVITY & TECHNOLOGY
1.77:1
#000000
on
#3C3632
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Digital Marketing Services
1.77:1
#000000
on
#3C3632
needs 3.0:1 (large text)
24px · bottom of viewport
h2 EXPLORE THE COLLECTION
1.77:1
#000000
on
#3C3632
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Industry-Specific Solutions
1.77:1
#000000
on
#3C3632
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Who is MASON CIRCLE?
1.77:1
#000000
on
#3C3632
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Why Choose MASON CIRCLE?
1.77:1
#000000
on
#3C3632
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Start Working with Mason Circle
1.77:1
#000000
on
#3C3632
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What’s happening
1.77:1
#000000
on
#3C3632
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mason Circle International
1.77:1
#000000
on
#3C3632
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mason Circle International
1.77:1
#000000
on
#3C3632
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Contact Us
1.77:1
#000000
on
#3C3632
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Careers
1.77:1
#000000
on
#3C3632
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Club Mason Circle
1.77:1
#000000
on
#3C3632
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Digital Marketing Agency in London
1.77:1
#000000
on
#3C3632
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Official Partners
1.77:1
#000000
on
#3C3632
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Frequently Asked Questions
1.77:1
#000000
on
#3C3632
needs 3.0:1 (large text)
19px · bottom of viewport
title Digital Marketing Agency for Restaurants…
1.30:1
#000000
on
#25201A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Home
1.30:1
#000000
on
#26201B
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Digital Marketing Ag…1.77:13.0:1
#000000
#3C3632
Fail
h2 A COLLECTION OF DIVE…1.77:13.0:1
#000000
#3C3632
Fail
h2 FUELLED BY CREATIVIT…1.77:13.0:1
#000000
#3C3632
Fail
h2 Digital Marketing Se…1.77:13.0:1
#000000
#3C3632
Fail
h2 EXPLORE THE COLLECTI…1.77:13.0:1
#000000
#3C3632
Fail
h2 Industry-Specific S…1.77:13.0:1
#000000
#3C3632
Fail
h2 Who is MASON CIRCLE?1.77:13.0:1
#000000
#3C3632
Fail
h2 Why Choose MASON CIR…1.77:13.0:1
#000000
#3C3632
Fail
h2 Start Working with M…1.77:13.0:1
#000000
#3C3632
Fail
h2 What’s happening1.77:13.0:1
#000000
#3C3632
Fail
h2 Mason Circle Interna…1.77:13.0:1
#000000
#3C3632
Fail
h2 Mason Circle Interna…1.77:13.0:1
#000000
#3C3632
Fail
h2 Contact Us1.77:13.0:1
#000000
#3C3632
Fail
h2 Careers1.77:13.0:1
#000000
#3C3632
Fail
h2 Club Mason Circle1.77:13.0:1
#000000
#3C3632
Fail
h3 Digital Marketing Ag…1.77:13.0:1
#000000
#3C3632
Fail
h3 Official Partners1.77:13.0:1
#000000
#3C3632
Fail
h3 Frequently Asked Que…1.77:13.0:1
#000000
#3C3632
Fail
title Digital Marketing Ag…1.30:14.5:1
#000000
#25201A
Fail
a Home1.30:14.5:1
#000000
#26201B
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::
2 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: 2 all-caps heading(s)
A+
Alt Text Quality
All 16 images OK
PASS
All 16 images OK
Info::
16 image(s) with good alt text
16 images 16 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="form_fields[email]" id="form-field-email">
1 controls
0 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#form-field-emailselect(none)none

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

<select name="form_fields[email]" id="form-field-email">

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

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
2 explicit tabindex attribute(s) checked, no anti-patterns
PASS
2 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 60 visible text node(s) render at >= 12 CSS pixels
PASS
All 60 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
2 mobile-depth signal(s) detected
PASS
2 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.
Info::
iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)
The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.
A+
Lighthouse Accessibility Audits
Score 99/100 — 1 failing, 27 passed
PASS
99

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.

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
Club Mason Circle div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h5.elementor-heading-title
Let's Work Together div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h5.elementor-heading-title
Contact Us div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h6.elementor-heading-title

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
●Buttons have an accessible name
●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.
●`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
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○`<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
○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.
○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