Skip to content
https://random.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
D
Landmark Structure
Action
No landmarks
FIX
No 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
Info::
No banner (header) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

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.
D
Lighthouse Accessibility Audits
Action
Score 65/100 — 6 failing, 10 passed
FIX
65

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
Search RANDOM.ORG div#invisible > div#search > form > div
What's this fuss about true randomness? body > div#invisible > div#homepage-wide-column > h2
true div#invisible > div#homepage-wide-column > h2 > em
Prof. Mads Haahr div#invisible > div#homepage-wide-column > p > a
School of Computer Science and Statistics div#invisible > div#homepage-wide-column > p > a
Trinity College, Dublin div#invisible > div#homepage-wide-column > p > a
Randomness and Integrity Services Ltd div#invisible > div#homepage-wide-column > p > a
Games and Lotteries div > div.mainindent > h3 > a
Lottery Quick Pick div > div.mainindent > p > a
Keno Quick Pick div > div.mainindent > p > a
Coin Flipper div > div.mainindent > p > a
Dice Roller div > div.mainindent > p > a
Playing Card Shuffler div > div.mainindent > p > a
Birdie Fund Generator div > div.mainindent > p > a
Random Drawings div > div.mainindent > h3 > a
Q3.1 in the FAQ div > div.mainindent > p > a
Third-Party Draw Service div > div.mainindent > p > a
Step by Step Guide div > div.mainindent > p > a
Step by Step Video div > div.mainindent > p > a
Price Calculator div > div.mainindent > p > a
Drawing FAQ div > div.mainindent > p > a
Public Records div > div.mainindent > p > a
Drawing Result Widget div > div.mainindent > p > a
Multi-Round Giveaway Service div > div.mainindent > p > a
Numbers div > div.mainindent > h3 > a
Integer Generator div > div.mainindent > p > a
Sequence Generator div > div.mainindent > p > a
Integer Set Generator div > div.mainindent > p > a
Gaussian Generator div > div.mainindent > p > a
Decimal Fraction Generator div > div.mainindent > p > a
Raw Random Bytes div > div.mainindent > p > a
Lists and Strings and Maps, Oh My! div > div.mainindent > h3 > a
List Randomizer div > div.mainindent > p > a
String Generator div > div.mainindent > p > a
Password Generator div > div.mainindent > p > a
Clock Time Generator div > div.mainindent > p > a
Calendar Date Generator div > div.mainindent > p > a
Geographic Coordinate Generator div > div.mainindent > p > a
Bitmaps div > div.mainindent > p > a
Hexadecimal Color Code Generator div > div.mainindent > p > a
Pregenerated Files div > div.mainindent > p > a
Pure White Audio Noise div > div.mainindent > p > a
Jazz Scales div > div.mainindent > p > a
Samuel Beckett div > div.mainindent > p > a
DNA Protein Sequence Randomizer div > div.mainindent > p > a
Web Tools and Widgets for Your Pages div > div.mainindent > h3 > a
Integer Widget Wizard div > div.mainindent > p > a
Draw Widget Wizard div > div.mainindent > p > a
HTTP API div > div.mainindent > p > a
Guidelines div > div.mainindent > p > a
Banned Hosts div > div.mainindent > p > a
Learn about Randomness div > div.mainindent > h3 > a
Introduction to Randomness div > div.mainindent > p > a
History div > div.mainindent > p > a
Many Testimonials div > div.mainindent > p > a
Acknowledgements div > div.mainindent > p > a
Quotations div > div.mainindent > p > a
Media Coverage and Scientific Citations div > div.mainindent > p > a
News div > div.mainindent > p > a
Statistics div > div.mainindent > h3 > a
Real-Time Statistics div > div.mainindent > p > a
Statistical Analysis div > div.mainindent > p > a
Bit Tally div > div.mainindent > p > a
Your Quota div > div.mainindent > p > a
Contact and Help div#invisible > div > div.mainindent > h3
FAQ div > div.mainindent > p > a
Newsletter div > div.mainindent > p > a
Contact Details div > div.mainindent > p > a
BlueSky div#invisible > div > div > a
Terms and Conditions div#invisible > div > div > a
About Us div#invisible > div > div > a

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#search > form > div > input div#search > form > div > input

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div#invisible > div#homepage-generator > iframe body > div#invisible > div#homepage-generator > iframe

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home div#invisible > ul#navigation > li > a.active
Games div#invisible > ul#navigation > li > a
Numbers div#invisible > ul#navigation > li > a
Lists & More div#invisible > ul#navigation > li > a
Drawings div#invisible > ul#navigation > li > a
Web Tools div#invisible > ul#navigation > li > a
Statistics div#invisible > ul#navigation > li > a
Testimonials div#invisible > ul#navigation > li > a
Learn More div#invisible > ul#navigation > li > a
Login div#invisible > ul#navigation > li > a
Terms and Conditions div#invisible > div > div > a
About Us div#invisible > div > div > a

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-hidden="true"]` is not present on the document `<body>`
●Input buttons have discernible text.
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Document has a `<title>` element
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●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
●Heading elements appear in a sequentially-descending order
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[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]`s are contained by their required parent element
○`[role]` values are valid
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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.
○Image elements have `[alt]` attributes
○`<input type="image">` elements have `[alt]` text
○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.
B
Form Accessibility
2 of 5 controls have issues
REVIEW
2 of 5 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="q">; <input type="submit">
Info::
3 control(s) properly labeled
5 controls
3 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#cookie-banner-necessarycheckboxnone
#cookie-banner-preferencescheckboxnone
#cookie-banner-statisticscheckboxnone
inputsubmit(none)none
qtext(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="text" name="q">; <input type="submit">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - Page Not Found - RANDOM.ORG ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
B
Favicon & Branding
8 icon(s) detected
REVIEW
8 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A+
Heading Hierarchy
10 headings
PASS
10 headings
Info::
Single H1 present
  • H1 True Random Number Service
  • H2 What's this fuss about true randomness?
  • H3 Games and Lotteries
  • H3 Random Drawings
  • H3 Numbers
  • H3 Lists and Strings and Maps, Oh My!
  • H3 Web Tools and Widgets for Your Pages
  • H3 Learn about Randomness
  • H3 Statistics
  • H3 Contact and Help
A+
Alt Text Quality
All 3 images OK
PASS
All 3 images OK
Info::
3 image(s) with good alt text
3 images 3 good alt text
All images have appropriate alt text.
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
h2 What's this fuss abo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 randomness?21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Contact and Help21.00:13.0:1
#000000
#FFFFFF
Pass
title RANDOM.ORG - True Ra…17.41:14.5:1
#000000
#D9EDF7
Pass
a Home17.41:14.5:1
#000000
#D9EDF7
Pass
a Games17.41:14.5:1
#000000
#D9EDF7
Pass
a Lottery Quick Pick17.41:14.5:1
#000000
#D9EDF7
Pass
a Keno Quick Pick17.41:14.5:1
#000000
#D9EDF7
Pass
a Coin Flipper17.41:14.5:1
#000000
#D9EDF7
Pass
a Dice Roller17.41:14.5:1
#000000
#D9EDF7
Pass
a Playing Card Shuffle…17.41:14.5:1
#000000
#D9EDF7
Pass
a Birdie Fund Generato…13.08:14.5:1
#000000
#CCCCCC
Pass
a Numbers20.12:14.5:1
#000000
#FAFAFA
Pass
a Integers19.60:14.5:1
#000000
#F7F7F7
Pass
a Sequences21.00:14.5:1
#000000
#FFFFFF
Pass
a Integer Sets21.00:14.5:1
#000000
#FFFFFF
Pass
a Gaussian Numbers21.00:14.5:1
#000000
#FFFFFF
Pass
a Decimal Fractions21.00:14.5:1
#000000
#FFFFFF
Pass
a Raw Bytes21.00:14.5:1
#000000
#FFFFFF
Pass
a Lists & More18.26:14.5:1
#000000
#EFEFEF
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.

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

Send Feedback