Skip to content
https://iqiyi.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
47
GRADE
F
FIX
9
REVIEW
3
PASS
1
INFO
0
Checks
13
1 PASS 3 REVIEW 9 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

F
Alt Text Quality
Action
36 of 123 images have issues
FIX
36 of 123 images have issues
Critical::
36 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
6 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
87 decorative image(s) correctly marked
123 images 87 decorative 36 missing
IssueCount
missing36 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 - Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Favicon & Branding
Action
4 icon(s) detected
FIX
4 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 Present
✗ Multiple Sizes Missing
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 60/100 — 5 failing, 8 passed
FIX
60

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
小三上位竟又成职场对手 li > div.piclist-title > div.c-info > a
陈赫演完“拉”又演“丑” li > div.piclist-title > div.c-info > a
银河战舰盼回胜利正轨 li > div.piclist-title > div.c-info > a
诸葛玥醋坛子打翻宣誓主权 li > div.piclist-title > div.c-info > a
释小龙刘峰超零距离搏杀 li > div.piclist-title > div.c-info > a
全员恶人互撕反转不断 li > div.piclist-title > div.c-info > a
老头想二婚遭全家炮轰 li > div.piclist-title > div.c-info > a
灵异少女组团寻妖界秘籍 li > div.piclist-title > div.c-info > a

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul.list-app > li > a > img ul.list-app > li > a > img
ul.list-app > li > a > img ul.list-app > li > a > img
ul.list-app > li > a > img ul.list-app > li > a > img
ul.list-app > li > a > img ul.list-app > li > a > img
ul.list-app > li > a > img ul.list-app > li > a > img
ul.list-app > li > a > img ul.list-app > li > a > img
div > div.page-c-items > footer.m-footer > img div > div.page-c-items > footer.m-footer > img

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.site_header > div.header_search > div.search_box > a.search_icon div.site_header > div.header_search > div.search_box > a.search_icon

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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>`
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
○`[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
○`<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
○Links are distinguishable without relying on color.
○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
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: 爱奇艺
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name 爱奇艺 ✓192×192 icon ✗512×512 icon ✗Start URL /?pmode=pwa ✓Display Mode standalone ✓
Name 爱奇艺 Display Mode standalone Theme Color #111214 Background Color #111214 Icons 1 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA
title 爱奇艺 iQIYI-热门独播剧集在线…
1.49:1
#000000
on
#2E2B27
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
div 筛选
1.13:1
#000000
on
#121314
needs 4.5:1 (normal text)
16px · top of page (header area)
div 蜜语纪
1.18:1
#000000
on
#191817
needs 4.5:1 (normal text)
16px · top of page (header area)
div （昨日更新）
1.24:1
#000000
on
#1F1C1A
needs 4.5:1 (normal text)
16px · top of page (header area)
div 爆
1.28:1
#000000
on
#211F1B
needs 4.5:1 (normal text)
16px · above the fold
div 全网搜
2.38:1
#000000
on
#4A4A4C
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
div 热搜
1.19:1
#000000
on
#1C1815
needs 4.5:1 (normal text)
16px · above the fold
div 未来片单
1.19:1
#000000
on
#1B1816
needs 4.5:1 (normal text)
16px · above the fold
div 短剧
1.15:1
#000000
on
#171515
needs 4.5:1 (normal text)
16px · above the fold
div 免费
1.14:1
#000000
on
#131417
needs 4.5:1 (normal text)
16px · above the fold
div 电影
1.59:1
#000000
on
#2E3035
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
div 综艺
1.28:1
#000000
on
#211E25
needs 4.5:1 (normal text)
16px · above the fold
div 热点
1.06:1
#000000
on
#070A10
needs 4.5:1 (normal text)
16px · mid-page
div 动漫
1.06:1
#000000
on
#070A10
needs 4.5:1 (normal text)
16px · mid-page
div 少儿
1.10:1
#000000
on
#0D0F15
needs 4.5:1 (normal text)
16px · mid-page
div 漫剧
3.07:1
#000000
on
#3A606D
needs 4.5:1 (normal text)
16px · mid-page
div 纪录片
2.31:1
#000000
on
#174D6A
needs 4.5:1 (normal text)
16px · mid-page
div 知识
2.31:1
#000000
on
#214D63
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
div 蜜语纪
3.16:1
#000000
on
#446355
needs 4.5:1 (normal text)
16px · mid-page

4 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
title 爱奇艺 iQIYI-热…1.49:14.5:1
#000000
#2E2B27
Fail
div 筛选1.13:14.5:1
#000000
#121314
Fail
div 蜜语纪1.18:14.5:1
#000000
#191817
Fail
div （昨日更新）1.24:14.5:1
#000000
#1F1C1A
Fail
div 爆1.28:14.5:1
#000000
#211F1B
Fail
div 全网搜2.38:14.5:1
#000000
#4A4A4C
Fail
div 热搜1.19:14.5:1
#000000
#1C1815
Fail
div 电视剧7.19:14.5:1
#000000
#949896
Pass
div 未来片单1.19:14.5:1
#000000
#1B1816
Fail
div 短剧1.15:14.5:1
#000000
#171515
Fail
div 免费1.14:14.5:1
#000000
#131417
Fail
div 电影1.59:14.5:1
#000000
#2E3035
Fail
div 综艺1.28:14.5:1
#000000
#211E25
Fail
div 热点1.06:14.5:1
#000000
#070A10
Fail
div 动漫1.06:14.5:1
#000000
#070A10
Fail
div 少儿1.10:14.5:1
#000000
#0D0F15
Fail
div 漫剧3.07:14.5:1
#000000
#3A606D
Fail
div 纪录片2.31:14.5:1
#000000
#174D6A
Fail
div 知识2.31:14.5:1
#000000
#214D63
Fail
div 蜜语纪3.16:14.5:1
#000000
#446355
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+
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
search-1776801617453textSearcharia-label
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback