Skip to content
https://froga.io

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
76
GRADE
C
FIX
6
REVIEW
2
PASS
16
INFO
0
Checks
24
16 PASS 2 REVIEW 6 FIX
D
Mobile-Readable Font Sizes
Action
67% of visible text renders at >= 12 CSS px (51 below threshold)
FIX
67% of visible text renders at >= 12 CSS px (51 below threshold)
Warning::
51 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.5px ("81"); <span> 10.5px ("public rooms"); <span> 9.5px ("MC"); <span> 9.5px ("MS"); <span> 9.5px ("T/F").
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-mjy3ux
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
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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 Missing
✓ PNG Icons Present
✗ 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://froga.io/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://froga.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::
1 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 1 <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
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) 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 NAV 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

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.

A+
Heading Hierarchy
24 headings
PASS
24 headings
Info::
Single H1 present
  • H1 Learn by doing,not by reading.
  • H2 A computer can compare two lists of numbers, but not two words directly. So before it can tell that "big" and "large" are alike, it has to…
  • H2 Rooms ask you questions. Labs hand you the parts.
  • H2 Newly added rooms
  • H3 Before words become arrows
  • H2 Share this room
  • H3 Database Isolation Levels: How Concurrent Transactions Avoid Chaos
  • H2 Share this room
  • H3 Nobelpriset i fysik 2026: Neutriner och IceCube
  • H2 Share this room
  • H3 Dört modern web uygulama açığı
  • H2 Share this room
  • H3 Zafiyet avına çıkmadan önce
  • H2 Share this room
  • H3 Compound Interest: How Money Grows Faster Over Time
  • H2 Share this room
  • H3 Cyrillic False Friends: Reading Russian Letters
  • H2 Share this room
  • H3 Before the chance machine
  • H2 Share this room
  • H2 Ready to start learning smarter?
  • H2 Product
  • H2 Support
  • H2 Legal
A
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Warning::
1 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H2: 139 chars
Got: 1 >120-char heading(s)
A+
Alt Text Quality
All 18 images OK
PASS
All 18 images OK
Info::
18 image(s) with good alt text
18 images 18 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
Info::
Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices
The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.
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)
ElementRatioRequiredFGBGResult
h1 Learn by doing,17.91:13.0:1
#000000
#E7EFE8
Pass
h1 not by reading.17.91:13.0:1
#000000
#E7EFE8
Pass
h2 A computer can compa…17.91:13.0:1
#000000
#E7EFE8
Pass
h2 Rooms ask you questi…17.91:13.0:1
#000000
#E7EFE8
Pass
h2 Newly added rooms17.91:13.0:1
#000000
#E7EFE8
Pass
h2 Share this room17.91:13.0:1
#000000
#E7EFE8
Pass
h2 Share this room17.91:13.0:1
#000000
#E7EFE8
Pass
h2 Share this room17.91:13.0:1
#000000
#E7EFE8
Pass
h2 Share this room17.91:13.0:1
#000000
#E7EFE8
Pass
h2 Share this room17.91:13.0:1
#000000
#E7EFE8
Pass
h2 Share this room17.91:13.0:1
#000000
#E7EFE8
Pass
h2 Share this room17.91:13.0:1
#000000
#E7EFE8
Pass
h2 Share this room17.91:13.0:1
#000000
#E7EFE8
Pass
h2 Ready to start learn…17.91:13.0:1
#000000
#E7EFE8
Pass
h2 Product17.91:13.0:1
#000000
#E7EFE8
Pass
h2 Support17.91:13.0:1
#000000
#E7EFE8
Pass
h2 Legal17.91:13.0:1
#000000
#E7EFE8
Pass
h3 Before words become …17.91:13.0:1
#000000
#E7EFE8
Pass
h3 Database Isolation L…17.91:13.0:1
#000000
#E7EFE8
Pass
h3 Nobelpriset i fysik …17.91:13.0:1
#000000
#E7EFE8
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.

A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 23 passed
PASS
94

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
Rooms of questions you can finish on a bus, labs where you build things that ac… div.flex > section.mx-auto > div.pt-2 > p.mt-4
No account needed to build div.flex > div.min-w-0 > div.mt-6 > span.text-sm
Create your account and start now section.mx-auto > div.mb-7 > div > p.mt-1
#machine-learning div.key-static > div.flex > div.flex > a.rounded-full
#embeddings div.key-static > div.flex > div.flex > a.rounded-full
#labs div.key-static > div.flex > div.flex > a.rounded-full
#databases div.key-static > div.flex > div.flex > a.rounded-full
#transactions div.key-static > div.flex > div.flex > a.rounded-full
#concurrency div.key-static > div.flex > div.flex > a.rounded-full
#nobelpriset div.key-static > div.flex > div.flex > a.rounded-full
#fysik div.key-static > div.flex > div.flex > a.rounded-full
#neutriner div.key-static > div.flex > div.flex > a.rounded-full
#security div.key-static > div.flex > div.flex > a.rounded-full
#web-security div.key-static > div.flex > div.flex > a.rounded-full
#cve div.key-static > div.flex > div.flex > a.rounded-full
#security div.key-static > div.flex > div.flex > a.rounded-full
#web-security div.key-static > div.flex > div.flex > a.rounded-full
#cve div.key-static > div.flex > div.flex > a.rounded-full
#maths div.key-static > div.flex > div.flex > a.rounded-full
#compound-interest div.key-static > div.flex > div.flex > a.rounded-full
#finance div.key-static > div.flex > div.flex > a.rounded-full
#russian div.key-static > div.flex > div.flex > a.rounded-full
#alphabet div.key-static > div.flex > div.flex > a.rounded-full
#beginner-russian div.key-static > div.flex > div.flex > a.rounded-full
#probability div.key-static > div.flex > div.flex > a.rounded-full
#markov-chains div.key-static > div.flex > div.flex > a.rounded-full
#labs div.key-static > div.flex > div.flex > a.rounded-full
Interactive learning rooms you can build, share and play — solo or live with a … div.mx-auto > div.grid > div.col-span-2 > p.mt-3
Free to join · No credit card div.mx-auto > div.grid > div.col-span-2 > p.mt-4
Explore rooms div > ul.mt-3 > li > a.text-muted-foreground
Live mode div > ul.mt-3 > li > a.text-muted-foreground
For teachers div > ul.mt-3 > li > a.text-muted-foreground
Help & FAQ div > ul.mt-3 > li > a.text-muted-foreground
Contact us div > ul.mt-3 > li > a.text-muted-foreground
Privacy policy div > ul.mt-3 > li > a.text-muted-foreground
Terms of service div > ul.mt-3 > li > a.text-muted-foreground
© 2026 Froga. All rights reserved. footer.mt-auto > div.mx-auto > div.mt-10 > p

These are opportunities to improve the legibility of your content.

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.light html.light

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
●`[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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●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
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[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
○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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○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
○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.

Send Feedback