Accessibility

D

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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

4 of 4 images have issues

FIX

4 of 4 images have issues

4 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image-in-link without alt text

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

4 images 4 missing

Issue	Count
missing	4 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

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-alkw4g

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

D

Favicon & Branding

Action

6 icon(s) detected

FIX

6 icon(s) detected

favicon.ico present at site root

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'>.

Multiple icon sizes detected

✓ favicon.ico Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

D

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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

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

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.

F

Lighthouse Accessibility Audits

Action

Score 39/100 — 5 failing, 4 passed

FIX

39

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
Click to feedback > `div.wrapper > div.copyright > div.bx-pu-qrcode-wrap > a#bx-feedback-btn`

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.portrait `html.portrait`

These are opportunities to improve the interpretation of your content by users in different locales.

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
div.wrapper > div.content-inside > div.bannar > img#bg-img `div.wrapper > div.content-inside > div.bannar > img#bg-img`

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.portrait `html.portrait`

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

●Links have a discernible name

●The page contains a heading, skip link, or landmark region

○`[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

○`<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 a valid value for its `[lang]` attribute

○`<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.

○No element has a `[tabindex]` value greater than 0

○Touch targets have sufficient size and spacing.

○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

Link & Button Quality

1 issue(s) across 3 links and 0 buttons

REVIEW

1 issue(s) across 3 links and 0 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://youku.com/

1 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://tudou.com/"]

1 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://tudou.com//_____tmd_____/page/feedback?rand=S3WxGHAgAt756EpznwfNzJq2A…

3 links

1 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://youku.com/	(empty)	empty	Add link text or aria-label
https://tudou.com//_____tmd_____/page/fe…	Click to feedback >	new tab	Add '(opens in new tab)' to text
https://tudou.com/	BACK	img no alt	Add alt attribute to the image

Links without text are announced as raw URLs by screen readers.

https://youku.com/

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://tudou.com/"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://tudou.com//_____tmd_____/page/feedback?rand=S3WxGHAgAt756EpznwfNzJq2A…

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

C

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

Name present: 优酷桌面版

No 192x192 icon

A 192px icon is required for PWA installation.

Display mode: standalone

PWA Install Criteria Not Installable

Name 优酷桌面版 ✓192×192 icon ✗512×512 icon ✗Start URL /channel?host=www.youku.com ✓Display Mode standalone ✓

Name 优酷桌面版 Display Mode standalone Theme Color #000000 Background Color #ffffff Icons 5 icon(s)

A+

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 (empty)

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Color Contrast (Screenshot)

5 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.

5 pass

Show all checked elements (5)

Element	Ratio	Required	FG	BG	Result
title Access denied	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div We have detected unu…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Click to feedback >	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a BACK	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span © 2006-2022 Youku.c…	21.00:1	4.5:1	#000000	#FFFFFF	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.