publicnode.com Accessibility Report

Accessibility audit of publicnode.com — scanned on Feb 20, 2026

Technology
0 /100
F Critical Issues

6 issues found across 2 categories

4 Critical 2 Major

WCAG Compliance Overview

Perceivable 2 issues
Operable 1 issues
Understandable 1 issues
Robust 2 issues

Issues Found

Page missing language attribute

Critical

The <html> element must have a valid lang attribute to help screen readers pronounce content correctly.

WCAG 3.1.1
1 element(s) affected
  • <html>
How to fix

Add lang attribute to the <html> element, e.g., <html lang="en">.

Links missing accessible name

Critical

Links must have discernible text so screen reader users understand their purpose.

WCAG 2.4.4
4 element(s) affected
  • <a href="https://www.publicnode.com">
  • <a href="https://www.publicnode.com">
  • <a href="https://www.allnodes.com">
  • <a href="https://www.allnodes.com">
How to fix

Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

Form inputs missing labels

Critical

Form elements must have associated labels so users know what information to enter.

WCAG 1.3.1
3 element(s) affected
  • <input type="text" name="(no name)">
  • <input type="checkbox" name="(no name)">
  • <input type="text" name="(no name)">
How to fix

Add <label> elements with matching for attributes, or use aria-label.

Buttons missing accessible name

Critical

Buttons must have discernible text for screen reader users.

WCAG 4.1.2
2 element(s) affected
  • <button>
  • <button>
How to fix

Add text content, aria-label, or title to all <button> elements.

Heading levels skip order

Major

Headings should follow a logical order (h1 → h2 → h3) without skipping levels.

WCAG 1.3.1
1 element(s) affected
  • <h5> "Fastest, free-est, and privacy first RPC endpoints" (after h3)
How to fix

Restructure headings to follow sequential order. Don't skip from h1 to h3.

Duplicate element IDs

Major

Element IDs must be unique to ensure correct assistive technology behavior.

WCAG 4.1.1
262 element(s) affected
  • id="ethereum_svg__a"
  • id="bsc_svg__a"
  • id="chain_arrow_svg__a"
  • id="polygon_svg__a"
  • id="polygon_svg__b"
How to fix

Make each id attribute value unique within the page.

Top Priority Fixes

Here are the most impactful changes publicnode.com should make to improve accessibility:

  1. #1
    Links missing accessible name Critical

    Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

  2. #2
    Form inputs missing labels Critical

    Add <label> elements with matching for attributes, or use aria-label.

  3. #3
    Buttons missing accessible name Critical

    Add text content, aria-label, or title to all <button> elements.

Frequently Asked Questions

Is publicnode.com accessible?

publicnode.com scored 24/100 (grade F) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is publicnode.com WCAG compliant?

Our scan found 6 accessibility issues on publicnode.com. Full WCAG compliance requires addressing all critical and major issues identified above.

Is publicnode.com EAA compliant?

The European Accessibility Act requires websites to meet WCAG 2.1 AA standards. Check the detailed report above to see publicnode.com's compliance status.

What accessibility issues does publicnode.com have?

See the full issue list above with severity levels, affected elements, and recommended fixes for publicnode.com.

Scan Your Own Website

Get a free accessibility report for your website in seconds.

Scan Your Website Free View Pricing