Skip to content
https://beacons.ai

Accessibility

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

No landmarks detected

Screen reader users have no way to navigate by region.

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

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-otqgn8
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
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://beacons.ai/site.webmanifest contains invalid JSON. Browsers cannot parse it.
Got: https://beacons.ai/site.webmanifest

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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Lighthouse Accessibility Audits
Score 83/100 — 6 failing, 22 passed
REVIEW
83

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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Heather Gardner Comedy div.framer-1b86wtn-container > section > ul > li
Elena Shinohara Gymnastics div.framer-1b86wtn-container > section > ul > li
Chipmunksoftiktok Chipmunks div.framer-1b86wtn-container > section > ul > li
Andrea Botez Lifestyle div.framer-1b86wtn-container > section > ul > li

These are opportunities to improve the usage of ARIA in your application which 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
div.framer-y01nmy > div.framer-1cjgeda > div#desktopUsername > input.framer-form-input div.framer-y01nmy > div.framer-1cjgeda > div#desktopUsername > input.framer-form-input

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
Get started fast, at any size div.framer-nn8qd9 > div.framer-ivmyyg > div.framer-1rc0yfd > h4.framer-text
Need help? support@beacons.ai div.framer-1tjd21b > div.framer-rb928b > div.framer-1swld0h > h5.framer-text

These are opportunities to improve keyboard navigation in your application.

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
div.framer-ztlhpn > div.framer-i4hzyi > div.framer-16r24bq > a.framer-ur7dp2 div.framer-ztlhpn > div.framer-i4hzyi > div.framer-16r24bq > a.framer-ur7dp2
div.framer-i4hzyi > div.framer-16r24bq > div.framer-12043lv > a.framer-1ja19jk div.framer-i4hzyi > div.framer-16r24bq > div.framer-12043lv > a.framer-1ja19jk
div.framer-i4hzyi > div.framer-16r24bq > div.framer-12043lv > a.framer-tnypyi div.framer-i4hzyi > div.framer-16r24bq > div.framer-12043lv > a.framer-tnypyi
div.framer-i4hzyi > div.framer-16r24bq > div.framer-12043lv > a.framer-18sh66s div.framer-i4hzyi > div.framer-16r24bq > div.framer-12043lv > a.framer-18sh66s
div.framer-i4hzyi > div.framer-1tjd21b > div.framer-1box02p > a.framer-4d8www div.framer-i4hzyi > div.framer-1tjd21b > div.framer-1box02p > a.framer-4d8www
div.framer-i4hzyi > div.framer-1tjd21b > div.framer-1box02p > a.framer-1j5jpa2 div.framer-i4hzyi > div.framer-1tjd21b > div.framer-1box02p > a.framer-1j5jpa2
div.framer-ztlhpn > div.framer-t8nas3 > div.framer-g07wa3 > a.framer-rgpqph div.framer-ztlhpn > div.framer-t8nas3 > div.framer-g07wa3 > a.framer-rgpqph
div.framer-ztlhpn > div.framer-t8nas3 > div.framer-g07wa3 > a.framer-lwwwig div.framer-ztlhpn > div.framer-t8nas3 > div.framer-g07wa3 > a.framer-lwwwig
div.framer-ztlhpn > div.framer-t8nas3 > div.framer-g07wa3 > a.framer-ywzaa6 div.framer-ztlhpn > div.framer-t8nas3 > div.framer-g07wa3 > a.framer-ywzaa6
div.framer-ztlhpn > div.framer-t8nas3 > div.framer-g07wa3 > a.framer-15psgo9 div.framer-ztlhpn > div.framer-t8nas3 > div.framer-g07wa3 > a.framer-15psgo9
div.framer-ztlhpn > div.framer-t8nas3 > div.framer-g07wa3 > a.framer-15x2j70 div.framer-ztlhpn > div.framer-t8nas3 > div.framer-g07wa3 > a.framer-15x2j70

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 require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
OSEA Holiday promotion campaign 10:04 AM Paid Affiliate $ div.framer-1o4jxyl > div.framer-1nnjw73 > ul > li.ticker-item
Fenty Beauty Holiday promotion campaign Jan 31 Gifted Paid $ div.framer-1o4jxyl > div.framer-1nnjw73 > ul > li.ticker-item
Lululemon Holiday promotion campaign Jan 28 Paid $ div.framer-1o4jxyl > div.framer-1nnjw73 > ul > li.ticker-item
Armani Beauty Spring and Lunar New Year Promoion Feb 1 Paid Affiliate $ div.framer-1o4jxyl > div.framer-1nnjw73 > ul > li.ticker-item
Blue Bottle New Product Line Launch Promotion Jan 31 Paid Gifted $ TBD div.framer-1o4jxyl > div.framer-1nnjw73 > ul > li.ticker-item

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

Best practices

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-*]` 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
●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 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 are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●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
○`<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
○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.
A+
Heading Hierarchy
4 headings
PASS
4 headings
Info::
Single H1 present
  • H1 Sorry, you have been blocked
  • H2 You are unable to access beacons.ai
  • H2 Why have I been blocked?
  • H2 What can I do to resolve this?
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Color Contrast (Screenshot)
18 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.

18 pass
Show all checked elements (18)
ElementRatioRequiredFGBGResult
h1 Sorry, you have been…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 beacons.ai21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Why have I been bloc…19.43:13.0:1
#000000
#F6F6F6
Pass
h2 What can I do to res…17.62:13.0:1
#000000
#EBEBEB
Pass
title Attention Required! …21.00:14.5:1
#000000
#FFFFFF
Pass
div Please enable cookie…21.00:14.5:1
#000000
#FFFFFF
Pass
span You are unable to ac…21.00:14.5:1
#000000
#FFFFFF
Pass
p This website is usin…17.62:14.5:1
#000000
#EBEBEB
Pass
p You can email the si…17.62:14.5:1
#000000
#EBEBEB
Pass
span Cloudflare Ray ID:17.62:14.5:1
#000000
#EBEBEB
Pass
strong 9f003d11cd46fc2817.62:13.0:1
#000000
#EBEBEB
Pass
span •18.76:14.5:1
#000000
#F2F2F2
Pass
span Your IP:21.00:14.5:1
#000000
#FFFFFF
Pass
button Click to reveal21.00:14.5:1
#000000
#FFFFFF
Pass
span 2a03:90c0:15:be::121.00:14.5:1
#000000
#FFFFFF
Pass
span •21.00:14.5:1
#000000
#FFFFFF
Pass
span Performance & securi…21.00:14.5:1
#000000
#FFFFFF
Pass
a Cloudflare21.00:14.5: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