Skip to content
https://oppo.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 icon(s) detected
Info::
favicon.ico present at site root
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 Present
PNG Icons Present
Apple Touch Missing
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
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.
B
Landmark Structure
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
Info::
Skip navigation link present
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

C
Alt Text Quality
Action
10 of 118 images have issues
REVIEW
10 of 118 images have issues
Critical::
10 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
28 decorative image(s) correctly marked
Info::
80 image(s) with good alt text
118 images 80 good alt text 28 decorative 10 missing
IssueCount
missing10 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

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 404 | OPPO Global Custom Styling Navigation Homepage Link Search Form
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

18 pass 2 fail WCAG AA 4 pass AA only
p OPPO Reno15 Series 5G
3.37:1
#000000
on
#586172
needs 4.5:1 (normal text)
16px · above the fold
a Find X Series
4.24:1
#000000
on
#6D716E
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 OPPO Official Site |…13.88:13.0:1
#000000
#CDD2DF
Pass
h2 New Products19.43:13.0:1
#000000
#F6F6F6
Pass
h2 OPPO Find N619.43:13.0:1
#000000
#F6F6F6
Pass
h2 OPPO Watch X319.43:13.0:1
#000000
#F6F6F6
Pass
h2 OPPO Enco Clip219.43:13.0:1
#000000
#F6F6F6
Pass
h2 Open Earbuds19.43:13.0:1
#000000
#F6F6F6
Pass
h2 OPPO Support19.43:13.0:1
#000000
#F6F6F6
Pass
title OPPO Official Site |…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to main content9.37:14.5:1
#000000
#A5ADC3
Pass
div We use cookies and s…9.16:14.5:1
#000000
#A3ABC2
Pass
a Read More10.52:14.5:1
#000000
#B1B7CD
Pass
a Smartphones12.49:14.5:1
#000000
#C3C7D9
Pass
p OPPO Find X9 Ultra12.88:14.5:1
#000000
#C7CAD9
Pass
p OPPO Find X9s11.17:14.5:1
#000000
#B7BDCD
Pass
p OPPO Find N64.66:14.5:1
#000000
#6E7789
Pass
p OPPO Reno15 Series 5…3.37:14.5:1
#000000
#586172
Fail
p OPPO A6 Pro 5G6.09:14.5:1
#000000
#858A99
Pass
a Find N Series6.77:14.5:1
#000000
#90929B
Pass
a Find X Series4.24:14.5:1
#000000
#6D716E
Fail
a Reno Series5.08:14.5:1
#000000
#7B7E75
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.

B
Lighthouse Accessibility Audits
Score 86/100 — 4 failing, 21 passed
REVIEW
86

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Contact div#oc-wrapper > section.cmp-navigation > div#cmp-float-container > div#contact-pop
Questionnaire div#oc-wrapper > section.cmp-navigation > div#cmp-float-container > div#nps

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.

Tables and lists

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Smartphones OPPO Find X9 Ultra OPPO Find X9s OPPO Find N6 OPPO Reno15 Series 5G… footer#footer > section.main > nav.nav > dl
IoT Products OPPO Pad SE OPPO Pad 3 Pro OPPO Enco Air5 Pro OPPO Watch X3 OPPO W… footer#footer > section.main > nav.nav > dl
Support Contact Us Warranty Status OPPO Lock Android Enterprise User Guide FAQ … footer#footer > section.main > nav.nav > dl
About OPPO Our Story OPPO LUMO IMAGE OPPO Apex Guard OPPO 5G Newsroom Campaign … footer#footer > section.main > nav.nav > dl
OPPO Community OPPO Community OPPO Life Studio footer#footer > section.main > nav.nav > dl

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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.feature-product-main > div.responsive__layout > div.feature-product-header > a.header-link div.feature-product-main > div.responsive__layout > div.feature-product-header > a.header-link
div.feature-product-container > div.feature-product-bottom > div.feature-product-bottom-btns > a.new-button div.feature-product-container > div.feature-product-bottom > div.feature-product-bottom-btns > a.new-button
div.feature-product-container-left > div.feature-product-bottom > div.feature-product-bottom-btns > a.new-button div.feature-product-container-left > div.feature-product-bottom > div.feature-product-bottom-btns > a.new-button
div.feature-product-container-left > div.feature-product-bottom > div.feature-product-bottom-btns > a.new-button div.feature-product-container-left > div.feature-product-bottom > div.feature-product-bottom-btns > a.new-button
div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event
div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event
div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event
div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event
div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event
div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event
div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event
div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event
div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event
div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event div.general-container > div.swiper-wrapper > div.swiper-slide > a.op-trk-event
div.cmty_card-container > div.cmty_card-wrap > div.cmty_card-title > a.mn-link div.cmty_card-container > div.cmty_card-wrap > div.cmty_card-title > a.mn-link

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.

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 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-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[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
Background and foreground colors have a sufficient contrast ratio
Definition list items are wrapped in `<dl>` elements
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
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Deprecated ARIA roles were not used
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
`[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
Buttons have an accessible name
The page contains a heading, skip link, or landmark region
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.
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.
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.
A+
Heading Hierarchy
6 headings
PASS
6 headings
Info::
Single H1 present
  • H1 OPPO Official Site | OPPO Global
  • H2 New Products
  • H2 OPPO Find N6
  • H2 OPPO Watch X3
  • H2 OPPO Enco Clip2 Open Earbuds
  • H2 OPPO Support
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
#searchWordtext{{ attr.txtPlaceholder }}for/id
#searchInputtextSearch OPPO.comfor/id
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback