Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 5 REVIEW 3 FIX

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://llamarpc.com/site.webmanifest contains invalid JSON. Browsers cannot parse it.

Got: https://llamarpc.com/site.webmanifest

Manifest contains invalid JSON.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

9 landmarks

REVIEW

9 landmarks

<main> landmark present

No <nav> landmark found

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

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

Alt Text Quality

3 of 12 images have issues

REVIEW

3 of 12 images have issues

3 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

9 image(s) with good alt text

12 images 9 good alt text 3 missing

Issue	Count
missing	3 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color #f56284 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+

Heading Hierarchy

2 headings

PASS

2 headings

Single H1 present

H1 Try the free public RPC
H2 Find out more

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

16 links, 16 buttons — all OK

PASS

16 links, 16 buttons — all OK

10 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://llamanodes.notion.site/LlamaNodes-7c1ba02f174b45d1adff219b543c277f; https://github.com/llamanodes; https://x.com/LlamaNodes; https://medium.com/llamanodes; https://llama-corp.com; https://llama-corp.com; https://defillama.com; https://llamafolio.com; https://llamapay.io; https://dlnews.com

6 link(s) with descriptive text

16 links

0 empty

0 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://llamanodes.notion.site/LlamaNode…	Docs	new tab	Add '(opens in new tab)' to text
https://github.com/llamanodes	GitHub	new tab	Add '(opens in new tab)' to text
https://x.com/LlamaNodes	Twitter	new tab	Add '(opens in new tab)' to text
https://medium.com/llamanodes	Medium	new tab	Add '(opens in new tab)' to text
https://llama-corp.com	check out LlamaCorp	new tab	Add '(opens in new tab)' to text
https://llama-corp.com	LlamaCorp logo	new tab	Add '(opens in new tab)' to text
https://defillama.com	DefiLlama	new tab	Add '(opens in new tab)' to text
https://llamafolio.com	LlamaFolio	new tab	Add '(opens in new tab)' to text
https://llamapay.io	LlamaPay	new tab	Add '(opens in new tab)' to text
https://dlnews.com	DLNews	new tab	Add '(opens in new tab)' to text

22 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://llamanodes.notion.site/LlamaNodes-7c1ba02f174b45d1adff219b543c277f; https://github.com/llamanodes; https://x.com/LlamaNodes; https://medium.com/llamanodes; https://llama-corp.com; https://llama-corp.com; https://defillama.com; https://llamafolio.com; https://llamapay.io; https://dlnews.com

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Color Contrast (Screenshot)

20 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.

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Try the free public …	18.64:1	3.0:1	#000000	#EDF2F7	Pass
h2 Find out more	20.29:1	3.0:1	#000000	#FBFBFB	Pass
title LlamaNodes	18.64:1	4.5:1	#000000	#EDF2F7	Pass
p A reliable public go…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p built for the decent…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Choose your chain	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Ethereum	19.27:1	4.5:1	#000000	#F5F5F6	Pass
span Base	19.43:1	4.5:1	#000000	#F6F6F6	Pass
span BNB Chain	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Ethereum	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span https://eth.llamarpc…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span https://eth.llamarpc…	20.29:1	4.5:1	#000000	#FBFBFB	Pass
span wss://eth.llamarpc.c…	20.29:1	4.5:1	#000000	#FBFBFB	Pass
button Copy	20.29:1	4.5:1	#000000	#FBFBFB	Pass
button Add to Wallet	20.29:1	4.5:1	#000000	#FBFBFB	Pass
span Information:	20.29:1	4.5:1	#000000	#FBFBFB	Pass
span Docs	20.29:1	4.5:1	#000000	#FBFBFB	Pass
span GitHub	20.29:1	4.5:1	#000000	#FBFBFB	Pass
span Socials:	20.29:1	4.5:1	#000000	#FBFBFB	Pass
span Twitter	20.29:1	4.5:1	#000000	#FBFBFB	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.

Lighthouse Accessibility Audits

Score 91/100 — 2 failing, 22 passed

PASS

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
main.css-1vqxhj0 > section.chakra-stack > div.css-dz4xk2 > img.chakra-image `main.css-1vqxhj0 > section.chakra-stack > div.css-dz4xk2 > img.chakra-image`

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.chakra-stack > div.chakra-stack > div.css-13pmxen > a.chakra-link `div.chakra-stack > div.chakra-stack > div.css-13pmxen > a.chakra-link`
div.chakra-stack > div.chakra-stack > div.css-t68593 > a.chakra-link `div.chakra-stack > div.chakra-stack > div.css-t68593 > a.chakra-link`
div.chakra-stack > div.chakra-stack > div.css-13pmxen > a.chakra-link `div.chakra-stack > div.chakra-stack > div.css-13pmxen > a.chakra-link`
div.chakra-stack > div.chakra-stack > div.css-t68593 > a.chakra-link `div.chakra-stack > div.chakra-stack > div.css-t68593 > a.chakra-link`
div.chakra-stack > ul.css-jadf3h > li.css-1bbz3js > a.chakra-link `div.chakra-stack > ul.css-jadf3h > li.css-1bbz3js > a.chakra-link`
div.chakra-stack > ul.css-jadf3h > li.css-1bbz3js > a.chakra-link `div.chakra-stack > ul.css-jadf3h > li.css-1bbz3js > a.chakra-link`
div.chakra-stack > ul.css-jadf3h > li.css-1bbz3js > a.chakra-link `div.chakra-stack > ul.css-jadf3h > li.css-1bbz3js > a.chakra-link`
div.chakra-stack > ul.css-jadf3h > li.css-1bbz3js > a.chakra-link `div.chakra-stack > ul.css-jadf3h > li.css-1bbz3js > a.chakra-link`

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.

○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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●`[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

●`[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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●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 input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[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

○Form elements have associated labels

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.