Skip to content
https://publicnode.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
7
REVIEW
5
PASS
1
INFO
0
Checks
13
1 PASS 5 REVIEW 7 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 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
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 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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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::
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.
C
Heading Hierarchy
Action
3 headings, 1 skip(s)
REVIEW
3 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 RPC Endpoints
  • H5 Fastest, free-est, and privacy first RPC endpoints for 102 blockchains. Connect reliably to Web3 with ease! skipped
  • H3 Fastest, free-est, and privacy first RPC endpoints for 102 blockchains. Connect reliably to Web3 with ease!

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

B
Form Accessibility
2 of 3 controls have issues
REVIEW
2 of 3 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input>; <input>
Info::
1 control(s) properly labeled
3 controls
1 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputcheckboxnone
inputinput(Search)placeholder only
inputinput(Search blockchains)placeholder only

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

<input>; <input>

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
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title PublicNode ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
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
h3 RPC Endpoints
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · above the fold
h3 Fastest, free-est, and privacy first RPC…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
title PublicNode
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
button RPC Endpoints
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
button Node Snapshots
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
button Seed Service
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
button RPC Endpoints
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
button Node Snapshots
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
button Seed Service
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
p Fastest, free-est, and privacy first RPC…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
button All
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
button Mainnet
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
button Testnet
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
p Total requests
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
p Last 24 hours
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
p 7,422,236,066
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
p Cached requests
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
p Last 24 hours
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
p 38.73%
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
p Average req/sec
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 RPC Endpoints1.00:13.0:1
#000000
#000000
Fail
h3 Fastest, free-est, a…1.00:13.0:1
#000000
#000000
Fail
title PublicNode1.00:14.5:1
#000000
#000000
Fail
button RPC Endpoints1.00:14.5:1
#000000
#000000
Fail
button Node Snapshots1.00:14.5:1
#000000
#000000
Fail
button Seed Service1.00:14.5:1
#000000
#000000
Fail
button RPC Endpoints1.00:14.5:1
#000000
#000000
Fail
button Node Snapshots1.00:14.5:1
#000000
#000000
Fail
button Seed Service1.00:14.5:1
#000000
#000000
Fail
p Fastest, free-est, a…1.00:14.5:1
#000000
#000000
Fail
button All1.00:14.5:1
#000000
#000000
Fail
button Mainnet1.00:14.5:1
#000000
#000000
Fail
button Testnet1.00:14.5:1
#000000
#000000
Fail
p Total requests1.00:14.5:1
#000000
#000000
Fail
p Last 24 hours1.00:14.5:1
#000000
#000000
Fail
p 7,422,236,0661.00:14.5:1
#000000
#000000
Fail
p Cached requests1.00:14.5:1
#000000
#000000
Fail
p Last 24 hours1.00:14.5:1
#000000
#000000
Fail
p 38.73%1.00:14.5:1
#000000
#000000
Fail
p Average req/sec1.00:14.5:1
#000000
#000000
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 82/100 — 4 failing, 15 passed
REVIEW
82

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.TableControlsmobilestyles__Controls-sc-1xsotdo-10 > div.TableControlsmobilestyles__Dropdowns-sc-1xsotdo-8 > div.Popoverstyle__Target-sc-1tmribv-2 > button.IconButtonstyles__Button-sc-4cfc2d-0 div.TableControlsmobilestyles__Controls-sc-1xsotdo-10 > div.TableControlsmobilestyles__Dropdowns-sc-1xsotdo-8 > div.Popoverstyle__Target-sc-1tmribv-2 > button.IconButtonstyles__Button-sc-4cfc2d-0
div#__next > div#portal-target > section.Home__Content-sc-12cgyy3-1 > button.IconButtonstyles__Button-sc-4cfc2d-0 div#__next > div#portal-target > section.Home__Content-sc-12cgyy3-1 > button.IconButtonstyles__Button-sc-4cfc2d-0

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 > div.MobileHeader__Container-sc-cjpd4c-1 > div.MobileHeader__Top-sc-cjpd4c-3 > a div > div.MobileHeader__Container-sc-cjpd4c-1 > div.MobileHeader__Top-sc-cjpd4c-3 > a
div.Footer__Root-sc-198rwdq-7 > div.Adaptive__Container-sc-jyurz-0 > footer.MobileFooter__Container-sc-1w0fiwq-5 > a div.Footer__Root-sc-198rwdq-7 > div.Adaptive__Container-sc-jyurz-0 > footer.MobileFooter__Container-sc-1w0fiwq-5 > 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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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
●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.
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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 a valid value for its `[lang]` attribute
○`<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
○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>`.
○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.
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback