Skip to content
https://uptimerobot.com

Accessibility

· 20 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
3
REVIEW
6
PASS
11
INFO
0
Checks
20
11 PASS 6 REVIEW 3 FIX
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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Mobile Keyboard & Autofill
Action
1/2 eligible field(s) missing autocomplete or inputmode
REVIEW
1/2 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.
Got: <input type="email" id="quote-email">
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::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title It's 404 | UptimeRobot ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 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
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: dark
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #3bd671
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 dark ✓Dark theme-color Not set ✗CSS indicators Not 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 service
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Catch downtime before your users do
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trusted by over
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 developers and teams
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Real-time status pages for your website,…
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Start monitoring in seconds.
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Deep insights
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Full control
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Zero blind spots
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Need more than 1,000 monitors?
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Frequently asked questions
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Start monitoring
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How many monitors do you need?
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Website monitoring
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Keyword monitoring
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Ping monitoring
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Port monitoring
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Cron job monitoring
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 DNS record monitoring
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Multi-location checks
1.28:1
#000000
on
#17202D
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 service1.28:13.0:1
#000000
#17202D
Fail
h2 Catch downtime befor…1.28:13.0:1
#000000
#17202D
Fail
h2 Trusted by over1.28:13.0:1
#000000
#17202D
Fail
h2 developers and teams1.28:13.0:1
#000000
#17202D
Fail
h2 Real-time status pag…1.28:13.0:1
#000000
#17202D
Fail
h2 Start monitoring in …1.28:13.0:1
#000000
#17202D
Fail
h2 Deep insights1.28:13.0:1
#000000
#17202D
Fail
h2 Full control1.28:13.0:1
#000000
#17202D
Fail
h2 Zero blind spots1.28:13.0:1
#000000
#17202D
Fail
h2 Need more than 1,000…1.28:13.0:1
#000000
#17202D
Fail
h2 Frequently asked que…1.28:13.0:1
#000000
#17202D
Fail
h2 Start monitoring1.28:13.0:1
#000000
#17202D
Fail
h2 How many monitors do…1.28:13.0:1
#000000
#17202D
Fail
h3 Website monitoring1.28:13.0:1
#000000
#17202D
Fail
h3 Keyword monitoring1.28:13.0:1
#000000
#17202D
Fail
h3 Ping monitoring1.28:13.0:1
#000000
#17202D
Fail
h3 Port monitoring1.28:13.0:1
#000000
#17202D
Fail
h3 Cron job monitoring1.28:13.0:1
#000000
#17202D
Fail
h3 DNS record monitorin…1.28:13.0:1
#000000
#17202D
Fail
h3 Multi-location check…1.28:13.0:1
#000000
#17202D
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
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
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 "Global" MAIN CONTENTINFO footer

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

A+
Heading Hierarchy
32 headings
PASS
32 headings
Info::
Single H1 present
  • H1 Meet the #1uptime monitoring service.
  • H2 Catch downtime before your users do.
  • H3 Website monitoring
  • H3 Keyword monitoring
  • H3 Ping monitoring
  • H3 Port monitoring
  • H3 Cron job monitoring
  • H3 DNS record monitoring
  • H2 Trusted by over 3.2M+ developers and teams.
  • H2 Real-time status pages for your website, API, or service.
  • H2 Start monitoring in seconds.Seriously.
  • H2 Deep insights. Full control. Zero blind spots.
  • H3 Multi-location checks
  • H3 Response time alerts
  • H3 Incident management tools
  • H3 Role-based team access
  • H3 Maintenance windows
  • H3 Integrations that keep your whole team in the loop.
  • H3 Monitor on the go. Stay in control anywhere.
  • H2 Need more than 1,000 monitors? Get an enterprise demo.
  • H2 Frequently asked questions.
  • H3 What is UptimeRobot?
  • H3 What is an uptime monitor?
  • H3 How do I monitor the uptime of a website?
  • H3 How do I create a status page?
  • H3 What can I monitor with UptimeRobot?
  • H3 How often does UptimeRobot check my website?
  • H3 Can I monitor from multiple locations/regions?
  • H3 How do I get an alert when a website is down (by email, SMS/IM, or phone)?
  • H3 How does UptimeRobot reduce false alarms (false positives)?
  • H2 Start monitoring in 30 seconds.
  • H2 How many monitors do you need?
A+
Alt Text Quality
All 33 images OK
PASS
All 33 images OK
Info::
33 image(s) with good alt text
33 images 33 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#monitor-sliderrangeNumber of monitorsfor/id
#quote-emailemailEmailfor/id
A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
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
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
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+
Mobile-Readable Font Sizes
All 25 visible text node(s) render at >= 12 CSS pixels
PASS
All 25 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 26 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.

Names and labels

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.ur-grid > div > div.ur-flex > a.ur-no-underline div.ur-grid > div > div.ur-flex > a.ur-no-underline

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
●`[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
●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
●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.
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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.
○Image elements do not have `[alt]` attributes that are redundant text.
○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