Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 6 REVIEW 5 FIX

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-ujc8mn

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.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://oxforddictionaries.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://oxforddictionaries.com/manifest.json

Manifest contains invalid JSON.

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.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

4 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 4 <nav> element(s)

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.

Landmark Structure

Action

6 landmarks

REVIEW

6 landmarks

No <main> landmark found

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

4 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

Heading Hierarchy

22 headings, 1 skip(s)

REVIEW

22 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

3 empty heading(s)

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

H1 Leading the way in language data
H2 Trusted by leading organizations and research institutions
H2 Oxford Languages is committed to unlocking the power of language for learning and for life
H2 Why choose Oxford Languages?
H3 Expertise
H3 Quality
H3 Integrity
H3 Authority
H3 Customer Success
H3 Innovation
H2 What our customers say
H4 Ready to get started? skipped
H2 Products
H2 Solutions
H2 About Us
H3 © 2026 Oxford University Press. All rights reserved.
H3 Cookie Policy
H3 Privacy Policy
H3 Legal Notice
H2 (empty)
H2 (empty)
H3 (empty)

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

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

Link & Button Quality

Action

3 issue(s) across 61 links and 7 buttons

REVIEW

3 issue(s) across 61 links and 7 buttons

3 link(s) with no accessible text

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

Got: https://languages.oup.com/; https://corp.oup.com/; #

10 link(s) open in new tab without warning

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

Got: https://corp.oup.com/word-of-the-year/; https://www.oed.com/?tl=true; https://corp.oup.com/; https://account.oxforddictionaries.com/pricing; https://www.oed.com/?tl=true; https://oed.com/; https://corp.oup.com/; https://global.oup.com/cookiepolicy; https://corp.oup.com/privacy-policy/; https://www.linkedin.com/showcase/oxford-languages-oup

48 link(s) with descriptive text

61 links

3 empty

0 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://corp.oup.com/word-of-the-year/	Word of the Year	new tab	Add '(opens in new tab)' to text
https://www.oed.com/?tl=true	Oxford English Dictionary	new tab	Add '(opens in new tab)' to text
https://corp.oup.com/	Oxford University Press	new tab	Add '(opens in new tab)' to text
https://account.oxforddictionaries.com/p…	Trial our API	new tab	Add '(opens in new tab)' to text
https://www.oed.com/?tl=true	Oxford English Dictionary	new tab	Add '(opens in new tab)' to text
https://languages.oup.com/	(empty)	empty	Add link text or aria-label
https://oed.com/	Oxford English Dictionary	new tab	Add '(opens in new tab)' to text
https://corp.oup.com/	Oxford University Press	new tab	Add '(opens in new tab)' to text
https://corp.oup.com/	(empty)	empty	Add link text or aria-label
https://global.oup.com/cookiepolicy	Cookie Policy	new tab	Add '(opens in new tab)' to text
https://corp.oup.com/privacy-policy/	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/showcase/oxford…	LinkedIn	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label

55 links and buttons have descriptive text

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

https://languages.oup.com/; https://corp.oup.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

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

https://corp.oup.com/word-of-the-year/; https://www.oed.com/?tl=true; https://corp.oup.com/; https://account.oxforddictionaries.com/pricing; https://www.oed.com/?tl=true; https://oed.com/; https://corp.oup.com/; https://global.oup.com/cookiepolicy; https://corp.oup.com/privacy-policy/; https://www.linkedin.com/showcase/oxford-languages-oup

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

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 17 fail WCAG AA

REVIEW

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

3 pass 17 fail WCAG AA

h2 Trusted by leading organizations and res…

1.26:1

#000000

#011E41

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Oxford Languages is committed to unlocki…

1.26:1

#000000

#011E41

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Why choose Oxford Languages?

1.26:1

#000000

#011E41

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What our customers say

1.26:1

#000000

#011E41

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Products

1.26:1

#000000

#011E41

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Solutions

1.26:1

#000000

#011E41

needs 3.0:1 (large text)

24px · bottom of viewport

h2 About Us

1.26:1

#000000

#011E41

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Expertise

1.26:1

#000000

#011E41

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Quality

1.26:1

#000000

#011E41

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Integrity

1.26:1

#000000

#011E41

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Authority

1.26:1

#000000

#011E41

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Customer Success

1.26:1

#000000

#011E41

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Innovation

1.26:1

#000000

#011E41

needs 3.0:1 (large text)

19px · bottom of viewport

1.26:1

#000000

#011E41

needs 3.0:1 (large text)

19px · bottom of viewport

span Word Lists

4.41:1

#000000

#727372

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

span Pronunciations Data & Audio

1.29:1

#000000

#20201D

needs 4.5:1 (normal text)

16px · top of page (header area)

span Dictionary Language Datasets

1.28:1

#000000

#1D201C

needs 4.5:1 (normal text)

16px · above the fold

1 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)

Element	Ratio	Required	FG	BG	Result
h1 Leading the way in l…	16.48:1	3.0:1	#FEFEFE	#011E41	Pass
h2 Trusted by leading o…	1.26:1	3.0:1	#000000	#011E41	Fail
h2 Oxford Languages is …	1.26:1	3.0:1	#000000	#011E41	Fail
h2 Why choose Oxford La…	1.26:1	3.0:1	#000000	#011E41	Fail
h2 What our customers s…	1.26:1	3.0:1	#000000	#011E41	Fail
h2 Products	1.26:1	3.0:1	#000000	#011E41	Fail
h2 Solutions	1.26:1	3.0:1	#000000	#011E41	Fail
h2 About Us	1.26:1	3.0:1	#000000	#011E41	Fail
h3 Expertise	1.26:1	3.0:1	#000000	#011E41	Fail
h3 Quality	1.26:1	3.0:1	#000000	#011E41	Fail
h3 Integrity	1.26:1	3.0:1	#000000	#011E41	Fail
h3 Authority	1.26:1	3.0:1	#000000	#011E41	Fail
h3 Customer Success	1.26:1	3.0:1	#000000	#011E41	Fail
h3 Innovation	1.26:1	3.0:1	#000000	#011E41	Fail
h3 © 2026 Oxford Unive…	1.26:1	3.0:1	#000000	#011E41	Fail
title Oxford Languages - T…	19.24:1	4.5:1	#000000	#F3F5F9	Pass
span Products	19.24:1	4.5:1	#000000	#F3F5F9	Pass
span Word Lists	4.41:1	4.5:1	#000000	#727372	Fail
span Pronunciations Data …	1.29:1	4.5:1	#000000	#20201D	Fail
span Dictionary Language …	1.28:1	4.5:1	#000000	#1D201C	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.

Lighthouse Accessibility Audits

Score 88/100 — 4 failing, 24 passed

REVIEW

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
Our solutions `div.wp-block-column > div.wp-block-buttons > div.wp-block-button > a.wp-block-button__link`
Oxford English Dictionary `div.wp-block-column > p.has-text-align-left > a > em`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookie Policy `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a`

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
Ready to get started? `div.wp-site-blocks > div.wp-block-cover > div.wp-block-cover__inner-container > h4.wp-block-heading`

These are opportunities to improve keyboard navigation in your application.

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.wp-block-column > div.wp-block-group > figure.wp-block-image > a `div.wp-block-column > div.wp-block-group > figure.wp-block-image > a`
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a `div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a`

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

●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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

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

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

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

Alt Text Quality

All 19 images OK

PASS

All 19 images OK

18 decorative image(s) correctly marked

1 image(s) with good alt text

19 images 1 good alt text 18 decorative

All images have appropriate alt text.

Form Accessibility

1 of 5 controls have issues

PASS

1 of 5 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="submit" name="submit" id="jp-carousel-comment-form-button-submit">

4 control(s) properly labeled

5 controls

4 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#jp-carousel-comment-form-comment-field	textarea	Write a Comment...	for/id
#jp-carousel-comment-form-email-field	text	Email (Required)	for/id
#jp-carousel-comment-form-author-field	text	Name (Required)	for/id
#jp-carousel-comment-form-url-field	text	Website	for/id
#jp-carousel-comment-form-button-submit	submit	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.