Skip to content
https://oxylabs.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
D
Landmark Structure
Action
5 landmarks
FIX
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Page Title Just a moment... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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::
2 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 2 <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.
B
Heading Hierarchy
44 headings, 2 skip(s)
REVIEW
44 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Access Any Public Data. Power Any Workflow.
  • H2 Built for every use case - powered by one platform
  • H3 AI training & RAG
  • H4 < 1 sec
  • H4 99%+
  • H2 Solutions covering every step of your data extraction journey
  • H3 Reach difficult targets easily for reliable scraping
  • H3 Visit targets at scale with fast throughput at low cost
  • H4 2M+
  • H4 188+
  • H4 0.25s
  • H3 Reach tough targets with high-speed, premium ASN IPs
  • H4 Premium
  • H4 Unlimited
  • H4 99.9%
  • H3 Fetch public data from modern websites reliably
  • H3 Retrieve parsed data from any target with scraping solutions
  • H3 Build custom datasets tailored to your exact needs
  • H2 Power your workflows
  • H3 AI-Scraper
  • H2 All your data – one view
  • H4 Product management skipped
  • H4 Limits & spending
  • H4 Advanced statistics
  • H2 Trusted by innovators worldwide
  • H2 Why top companies choose us
  • H2 Driven by transparency and excellence
  • H3 Best proxy service of 2026
  • H3 Leader in the G2 Enterprise Grid® Report
  • H3 Best Enterprise Provider
  • H3 Certified data centers and upstream providers
  • H3 Guaranteed insurance
  • H2 Fits easily into your projects
  • H5 Scraping Experts skipped
  • H5 Github
  • H5 Discord community
  • H5 YouTube channel
  • H2 Seamless integration with 30+ tools
  • H2 Begin your journey
  • H3 Documentation
  • H3 Blog
  • H3 Help Center
  • H3 Developers Hub
  • H2 What's new

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 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::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 87/100 — 5 failing, 29 passed
REVIEW
87

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AI-Scraper Generate structured data quickly with natural-language prompts. Go… div.grid > div.relative > div.flex > div.grid

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AI training & RAG AI training & RAG div.relative > div.absolute > div.mx-md > button#tab-AI training & RAG
AI-Scraper div.relative > div.absolute > div.mx-md > button#ai-studio-tab-ai-scraper

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
here div#CybotCookiebotDialogBodyContent > div#CybotCookiebotDialogBodyContentText > p > a
Show details div#CybotCookiebotDialogBody > div.CybotCookiebotDialogBodyBottomWrapper > div#CybotCookiebotDialogBodyEdgeMoreDetails > a#CybotCookiebotDialogBodyEdgeMoreDetailsLink
Access layer div#product-stack-Unblockers > div.grid > div.flex > p.font-width-normal
Data layer div#product-stack-Datasets > div.grid > div.flex > p.font-width-normal
10 div.relative > div.relative > div.absolute > div.font-code
11 div.relative > div.relative > div.absolute > div.font-code
12 div.relative > div.relative > div.absolute > div.font-code
13 div.relative > div.relative > div.absolute > div.font-code
14 div.relative > div.relative > div.absolute > div.font-code
15 div.relative > div.relative > div.absolute > div.font-code
16 div.relative > div.relative > div.absolute > div.font-code
import div.relative > div.relative > pre.-mt-1 > span.token
"customer-USER" div.relative > div.relative > pre.-mt-1 > span.token
"PASS" div.relative > div.relative > pre.-mt-1 > span.token
"pr.oxylabs.io:7777" div.relative > div.relative > pre.-mt-1 > span.token
'http' div.relative > div.relative > pre.-mt-1 > span.token
'https' div.relative > div.relative > pre.-mt-1 > span.token
request div.relative > div.relative > pre.-mt-1 > span.token
'GET' div.relative > div.relative > pre.-mt-1 > span.token
hello@oxylabs.io div.max-w-container-content > div.grid > div.flex > a.font-width-normal
support@oxylabs.io div.max-w-container-content > div.grid > div.flex > a.font-width-normal
career@oxylabs.io div.max-w-container-content > div.grid > div.flex > a.font-width-normal

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Product management div.relative > div.grid > div.[&>*]:text-heading4 > h4.m-0
Scraping Experts div.grid > div.box-shadow-sm > div.grid > h5.m-0

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
“Vast proxy network and almost 100% uptime, we execute crucial data operations … div.relative > div.absolute > div.max-w-[1332px] > div.dark
“With Oxylabs we not only revolutionized our approach but also significantly en… div.relative > div.absolute > div.max-w-[1332px] > div.dark
“Oxylabs offered one of the best price-to-value combinations in the market and … div.relative > div.absolute > div.max-w-[1332px] > div.dark
“We managed to find a way to monitor certain sites that we couldn't monitor bef… div.relative > div.absolute > div.max-w-[1332px] > div.dark
Residential Proxies div > div.oxy-zrcozk > div.oxy-ln1kbk > div.!bg-light
○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]`s are contained by their required parent element
●`[role]` values are valid
●`[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.
●Select elements have associated label elements.
●`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 are distinguishable without relying on color.
●Links have a discernible name
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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
○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
○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.
○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.
○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.
A+
Alt Text Quality
All 163 images OK
PASS
All 163 images OK
Info::
16 decorative image(s) correctly marked
Info::
147 image(s) with good alt text
163 images 147 good alt text 16 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
selectselectSelect Languagearia-label
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 Access Any Public Da…17.68:13.0:1
#000000
#F6E6FF
Pass
h2 Built for every use …17.68:13.0:1
#000000
#F6E6FF
Pass
h2 Solutions covering e…17.68:13.0:1
#000000
#F6E6FF
Pass
h2 Power your workflows17.68:13.0:1
#000000
#F6E6FF
Pass
h2 All your data – on…17.68:13.0:1
#000000
#F6E6FF
Pass
h2 Trusted by innovator…17.68:13.0:1
#000000
#F6E6FF
Pass
h2 Why top companies ch…17.68:13.0:1
#000000
#F6E6FF
Pass
h2 Driven by transparen…17.68:13.0:1
#000000
#F6E6FF
Pass
h2 Fits easily into you…17.68:13.0:1
#000000
#F6E6FF
Pass
h2 Seamless integration…17.68:13.0:1
#000000
#F6E6FF
Pass
h2 Begin your journey17.68:13.0:1
#000000
#F6E6FF
Pass
h2 What's new17.68:13.0:1
#000000
#F6E6FF
Pass
h3 AI training & RAG17.68:13.0:1
#000000
#F6E6FF
Pass
h3 Reach difficult targ…17.68:13.0:1
#000000
#F6E6FF
Pass
h3 Visit targets at sca…17.68:13.0:1
#000000
#F6E6FF
Pass
h3 Reach tough targets …17.68:13.0:1
#000000
#F6E6FF
Pass
h3 Fetch public data fr…17.68:13.0:1
#000000
#F6E6FF
Pass
h3 Retrieve parsed data…17.68:13.0:1
#000000
#F6E6FF
Pass
h3 Build custom dataset…17.68:13.0:1
#000000
#F6E6FF
Pass
h3 AI-Scraper17.68:13.0:1
#000000
#F6E6FF
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