Skip to content
https://agora.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
D
Landmark Structure
Action
7 landmarks
FIX
7 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
6 <nav> landmark(s) found
Warning::
1 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) CONTENTINFO (missing!)

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
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-bm5a8r
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
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://agora.io/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://agora.io/manifest.json

Manifest contains invalid JSON.

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::
6 navigation landmark(s) detected
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 6 <nav> element(s)
Back to Top
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.
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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 Build Real-time
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
32px · bottom of viewport
h1 ‍
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
32px · bottom of viewport
h2 TEN
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
24px · bottom of viewport
h2 App Builder
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Flexible Classroom
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Download SDKs
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Support Plans and Pricing
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Deploy your AI agents using the industry…
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Easily integrate real-time communication…
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Choose how to get started
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
24px · bottom of viewport
h2 with real-time interaction
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Add powerful functionality—fast
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
24px · bottom of viewport
h2 People
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Agora
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Success Stories
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get started with
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
24px · bottom of viewport
h2 10,000 free minutes
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Voice AI Agents with Any LLM
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Live Avatars
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Complete Multi-Platform Solution
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Build Real-time1.13:13.0:1
#000000
#131313
Fail
h1 ‍1.13:13.0:1
#000000
#131313
Fail
h2 TEN1.13:13.0:1
#000000
#131313
Fail
h2 App Builder1.13:13.0:1
#000000
#131313
Fail
h2 Flexible Classroom1.13:13.0:1
#000000
#131313
Fail
h2 Download SDKs1.13:13.0:1
#000000
#131313
Fail
h2 Support Plans and Pr…1.13:13.0:1
#000000
#131313
Fail
h2 Deploy your AI agent…1.13:13.0:1
#000000
#131313
Fail
h2 Easily integrate rea…1.13:13.0:1
#000000
#131313
Fail
h2 Choose how to get st…1.13:13.0:1
#000000
#131313
Fail
h2 with real-time inter…1.13:13.0:1
#000000
#131313
Fail
h2 Add powerful functio…1.13:13.0:1
#000000
#131313
Fail
h2 People1.13:13.0:1
#000000
#131313
Fail
h2 Agora1.13:13.0:1
#000000
#131313
Fail
h2 Success Stories1.13:13.0:1
#000000
#131313
Fail
h2 Get started with1.13:13.0:1
#000000
#131313
Fail
h2 10,000 free minutes1.13:13.0:1
#000000
#131313
Fail
h3 Voice AI Agents with…1.13:13.0:1
#000000
#131313
Fail
h3 Live Avatars1.13:13.0:1
#000000
#131313
Fail
h3 Complete Multi-Platf…1.13:13.0:1
#000000
#131313
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 Hierarchy
24 headings
PASS
24 headings
Info::
Single H1 present
  • H2 TEN
  • H2 App Builder
  • H2 Flexible Classroom
  • H2 Download SDKs
  • H2 Support Plans and Pricing
  • H1 Build Real-time ‍Voice AI, Avatars, & Conversational IoT
  • H2 Deploy your AI agents using the industry-leading infrastructure for Real-Time
  • H3 Voice AI Agents with Any LLM
  • H3 Live Avatars
  • H3 Complete Multi-Platform Solution
  • H3 Carrier Grade Quality and Compliance
  • H2 Easily integrate real-time communication and conversational AI
  • H2 Choose how to get started with real-time interaction
  • H2 Add powerful functionality—fast
  • H3 Bring any experience to life with Agora
  • H2 People
  • H2 Agora
  • H2 Success Stories
  • H3 HTC Vive
  • H3 Gabb
  • H3 Talkspace
  • H2 Get started with 10,000 free minutes
  • H3 Talk to Us
  • H3 Developer Resources
A+
Alt Text Quality
All 175 images OK
PASS
All 175 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
74 decorative image(s) correctly marked
Info::
100 image(s) with good alt text
175 images 100 good alt text 74 decorative
IssueCount
too long1 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 25 passed
PASS
96

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.

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
All systems operational div.footer-health-container > div.agora-health-indicator > div.agora-health-indicator__content > span.agora-health-indicator__text

These are opportunities to improve the legibility of your content.

○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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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 have a discernible name
●No element has a `[tabindex]` value greater than 0
●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
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○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.
○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.
○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