Skip to content
https://roblox.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 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
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 (missing!) 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

F
Form Accessibility
Action
5 of 5 controls have issues
FIX
5 of 5 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="birthdayMonth" id="MonthDropdown">; <select name="birthdayDay" id="DayDropdown">; <select name="birthdayYear" id="YearDropdown">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="signupUsername" id="signup-username">; <input type="password" name="signupPassword" id="signup-password">
5 controls
0 labeled
2 placeholder only
3 unlabeled
ControlTypeLabelMethod
#signup-usernametext(Don't use your real name)placeholder only
#signup-passwordpassword(At least 8 characters)placeholder only
#YearDropdownselect(none)none
#MonthDropdownselect(none)none
#DayDropdownselect(none)none

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

<select name="birthdayMonth" id="MonthDropdown">; <select name="birthdayDay" id="DayDropdown">; <select name="birthdayYear" id="YearDropdown">

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

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="signupUsername" id="signup-username">; <input type="password" name="signupPassword" id="signup-password">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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
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.
B
Heading Hierarchy
2 headings
REVIEW
2 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 Sign up and start having fun!
  • H3 Roblox on your device

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Roblox ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
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
h3 Sign up and start having fun!
1.21:1
#000000
on
#191A1F
needs 3.0:1 (large text)
19px · top of page (header area)
h3 Roblox on your device
1.21:1
#000000
on
#191A1F
needs 3.0:1 (large text)
19px · bottom of viewport
title Roblox
1.21:1
#000000
on
#191A1F
needs 4.5:1 (normal text)
16px · top of page (header area)
a Log In
1.21:1
#000000
on
#191A1F
needs 4.5:1 (normal text)
16px · top of page (header area)
label Birthday
1.21:1
#000000
on
#191A1F
needs 4.5:1 (normal text)
16px · top of page (header area)
option Month
1.21:1
#000000
on
#191A1F
needs 4.5:1 (normal text)
16px · above the fold
option January
1.21:1
#000000
on
#191A1F
needs 4.5:1 (normal text)
16px · above the fold
option February
1.21:1
#000000
on
#191A1F
needs 4.5:1 (normal text)
16px · above the fold
option March
1.21:1
#000000
on
#191A1F
needs 4.5:1 (normal text)
16px · above the fold
option April
1.21:1
#000000
on
#191A1F
needs 4.5:1 (normal text)
16px · above the fold
option May
1.21:1
#000000
on
#191A1F
needs 4.5:1 (normal text)
16px · above the fold
option June
1.21:1
#000000
on
#191A1F
needs 4.5:1 (normal text)
16px · above the fold
option July
1.21:1
#000000
on
#191A1F
needs 4.5:1 (normal text)
16px · above the fold
option August
1.21:1
#000000
on
#191A1F
needs 4.5:1 (normal text)
16px · above the fold
option September
1.21:1
#000000
on
#191A1F
needs 4.5:1 (normal text)
16px · mid-page
option October
1.21:1
#000000
on
#191A1F
needs 4.5:1 (normal text)
16px · mid-page
option November
1.21:1
#000000
on
#191A1F
needs 4.5:1 (normal text)
16px · mid-page
option December
1.21:1
#000000
on
#191A1F
needs 4.5:1 (normal text)
16px · mid-page
option Day
1.21:1
#000000
on
#191A1F
needs 4.5:1 (normal text)
16px · mid-page
option Year
1.21:1
#000000
on
#191A1F
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 Sign up and start ha…1.21:13.0:1
#000000
#191A1F
Fail
h3 Roblox on your devic…1.21:13.0:1
#000000
#191A1F
Fail
title Roblox1.21:14.5:1
#000000
#191A1F
Fail
a Log In1.21:14.5:1
#000000
#191A1F
Fail
label Birthday1.21:14.5:1
#000000
#191A1F
Fail
option Month1.21:14.5:1
#000000
#191A1F
Fail
option January1.21:14.5:1
#000000
#191A1F
Fail
option February1.21:14.5:1
#000000
#191A1F
Fail
option March1.21:14.5:1
#000000
#191A1F
Fail
option April1.21:14.5:1
#000000
#191A1F
Fail
option May1.21:14.5:1
#000000
#191A1F
Fail
option June1.21:14.5:1
#000000
#191A1F
Fail
option July1.21:14.5:1
#000000
#191A1F
Fail
option August1.21:14.5:1
#000000
#191A1F
Fail
option September1.21:14.5:1
#000000
#191A1F
Fail
option October1.21:14.5:1
#000000
#191A1F
Fail
option November1.21:14.5:1
#000000
#191A1F
Fail
option December1.21:14.5:1
#000000
#191A1F
Fail
option Day1.21:14.5:1
#000000
#191A1F
Fail
option Year1.21:14.5:1
#000000
#191A1F
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+
Alt Text Quality
All 9 images OK
PASS
All 9 images OK
Info::
1 decorative image(s) correctly marked
Info::
8 image(s) with good alt text
9 images 8 good alt text 1 decorative
All images have appropriate alt text.
A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 20 passed
PASS
100

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.

○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
●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
●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 have a discernible name
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●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
○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
○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
○`<frame>` or `<iframe>` elements have a title
○Heading elements appear in a sequentially-descending order
○`<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.
○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