Skip to content
https://wps.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
6
REVIEW
2
PASS
5
INFO
0
Checks
13
5 PASS 2 REVIEW 6 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-ulplc1
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.

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://wps.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://wps.com/manifest.json

Manifest contains invalid JSON.

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::
3 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 3 <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
Landmark Structure
Action
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (2 found)
A page should have only one <main> landmark.
Info::
3 <nav> landmark(s) found
Warning::
2 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 CONTENTINFO footer

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

A+
Heading Hierarchy
34 headings
PASS
34 headings
Info::
Single H1 present
  • H1 Don't just use Office Upgrade to an AI-Native, Always-in-sync Office
  • H2 Trusted by Millions
  • H2 WPS CopilotRedefine Your WorkflowWPS CopilotRedefine Your Workflow
  • H3 Format documents by hand
  • H3 Beautify documents in one click
  • H3 Write every paragraph yourself
  • H3 Create outlines and full drafts instantly
  • H3 Design slide by slide
  • H3 Turn content into polished slides instantly
  • H3 Analyze data row by row
  • H3 Instant insights from your data
  • H3 Beautify documents in one click
  • H3 Format documents by hand
  • H4 Save Time
  • H4 Easier to Use
  • H4 Better Value
  • H2 Collaborate Without Boundaries
  • H3 01. Cloud Documents
  • H3 02. Real-time Collaboration
  • H3 03. Multi-device Sync
  • H2 All-in-One Productivity Suite
  • H3 Compress PDF
  • H3 Sign & Organize PDF
  • H3 PDF Format Conversion
  • H3 Split & Merge PDF
  • H2 Infinite Creative Resources
  • H2 Globally Certified.Built for Security.
  • H2 Trusted by Experts. Proven by Users
  • H2 Join the Future of Work
  • H3 Products
  • H3 Company
  • H3 Support
  • H3 Follow us
  • H3 Follow us
A+
Alt Text Quality
1 of 168 images have issues
PASS
1 of 168 images have issues
Warning::
1 image(s) with generic alt text
Info::
34 decorative image(s) correctly marked
Info::
133 image(s) with good alt text
168 images 133 good alt text 34 decorative 1 generic
IssueCount
generic1 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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 Don't just use Offic…19.04:13.0:1
#000000
#EFF4FE
Pass
h1 Upgrade to an18.16:13.0:1
#000000
#E7EFFD
Pass
h1 Office17.39:13.0:1
#000000
#E5E9FC
Pass
h2 Trusted by Millions20.83:13.0:1
#000000
#FEFEFF
Pass
h2 Collaborate Without …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 All-in-One Productiv…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Infinite Creative Re…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Globally Certified.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Built for Security.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trusted by Experts. …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Join the Future of W…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Format documents by …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Beautify documents i…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Write every paragrap…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Create outlines and …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Design slide by slid…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Turn content into po…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Analyze data row by …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Instant insights fro…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Beautify documents i…21.00:13.0: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.

A
Lighthouse Accessibility Audits
Score 91/100 — 2 failing, 21 passed
PASS
91

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
Experience the shift from manual labor to intelligent creation. WPS AI is your … section.copilot-section > div.copilot-inner > div.copilot-header > p.copilot-subtitle
Auto-optimize Word layouts, enhance Excel tables, and refine PowerPoint slides.… div.mob-scroll-wrap > div.mob-scroll-inner > div.mob-col > p.content-desc
Content Writing div.copilot-body-mobile > div.mob-accordion > button.mob-accordion-header > span.mob-tab-name
Presentation Creation div.copilot-body-mobile > div.mob-accordion > button.mob-accordion-header > span.mob-tab-name
Data Analysis div.copilot-body-mobile > div.mob-accordion > button.mob-accordion-header > span.mob-tab-name
Write every paragraph yourself. Draft line by line. Build outlines manually. Ed… div.copilot-inner > div.copilot-summary > div.summary-item > p.summary-desc
Natural language commands make complex office tasks accessible to everyone. div.copilot-inner > div.copilot-summary > div.summary-item > p.summary-desc
All-in-one AI features at a fraction of the cost of multiple subscriptions. div.copilot-inner > div.copilot-summary > div.summary-item > p.summary-desc
Experience the shift from manual labor to intelligent creation. WPS AI is your … section.media-section > div.media-inner > div.media-header > p.media-subtitle

These are opportunities to improve the legibility of your content.

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
header.wps-nav > div.wps-nav__bar > div.wps-nav__inner > a.wps-nav__logo header.wps-nav > div.wps-nav__bar > div.wps-nav__inner > a.wps-nav__logo
footer.wps-footer > div.wps-footer__inner > div.wps-footer__brand > a.wps-footer__logo footer.wps-footer > div.wps-footer__inner > div.wps-footer__brand > a.wps-footer__logo

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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○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
○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
○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
○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