Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 6 REVIEW 2 FIX

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 ✗

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Urban Dictionary: beavercheck-404-test-sh0ehm ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

13 icon(s) detected

REVIEW

13 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 Present

✓ Multiple Sizes Present

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 9 icon(s)

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color #eeeeee ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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

title Urban Dictionary, April 21: Wasian

1.44:1

#000000

#212936

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.44:1

#000000

#212936

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Urban Dictionary	18.10:1	3.0:1	#000000	#EEEEEE	Pass
title Urban Dictionary, Ap…	1.44:1	4.5:1	#000000	#212936	Fail
a Skip to main content	1.44:1	4.5:1	#000000	#212936	Fail
a Home	18.10:1	4.5:1	#000000	#EEEEEE	Pass
a Add a Definition	18.10:1	4.5:1	#000000	#EEEEEE	Pass
a UrbanDictionary.stor…	18.10:1	4.5:1	#000000	#EEEEEE	Pass
a Blog	18.10:1	4.5:1	#000000	#EEEEEE	Pass
a World	18.10:1	4.5:1	#000000	#EEEEEE	Pass
a Advertise	18.10:1	4.5:1	#000000	#EEEEEE	Pass
a User Settings	18.10:1	4.5:1	#000000	#EEEEEE	Pass
a Wasian	18.10:1	4.5:1	#000000	#EEEEEE	Pass
span Listen to pronunciat…	18.10:1	4.5:1	#000000	#EEEEEE	Pass
span Share definition	18.10:1	4.5:1	#000000	#EEEEEE	Pass
div 50%	18.10:1	4.5:1	#000000	#EEEEEE	Pass
a white	18.10:1	4.5:1	#000000	#EEEEEE	Pass
div 50%	18.10:1	4.5:1	#000000	#EEEEEE	Pass
a asian	18.10:1	4.5:1	#000000	#EEEEEE	Pass
div 100%	18.10:1	4.5:1	#000000	#EEEEEE	Pass
a awesome	18.10:1	4.5:1	#000000	#EEEEEE	Pass
a Kevin	18.10:1	4.5:1	#000000	#EEEEEE	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.

Lighthouse Accessibility Audits

Score 84/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 999 partners `div.cky-notice-group > div.cky-notice-des > p > button#ckyIABNoticeButton`
Reject All `div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn`
Accept All `div.cky-notice > div.cky-notice-group > div.cky-notice-btn-wrapper > button.cky-btn`
Get the `section.flex-1 > div.definition > a.flex > span`
Wasian `section.flex-1 > div.definition > a.flex > span.px-1`
mug. `section.flex-1 > div.definition > a.flex > span`
Get the `section.flex-1 > div.definition > a.flex > span`
whitelisted `section.flex-1 > div.definition > a.flex > span.px-1`
mug. `section.flex-1 > div.definition > a.flex > span`
Get the `section.flex-1 > div.definition > a.flex > span`
Moon Joy `section.flex-1 > div.definition > a.flex > span.px-1`
mug. `section.flex-1 > div.definition > a.flex > span`

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.bg-yankees > div.container > div.flex > a.flex-shrink-0 `header.bg-yankees > div.container > div.flex > a.flex-shrink-0`

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`

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
help `div.text-sm > ul > li.inline > a.whitespace-nowrap`
privacy `div.text-sm > ul > li.inline > a.whitespace-nowrap`
terms of service `div.text-sm > ul > li.inline > a.whitespace-nowrap`
accessibility statement `div.text-sm > ul > li.inline > a.whitespace-nowrap`
report a bug `div.text-sm > ul > li.inline > a.whitespace-nowrap`
information collection notice `div.text-sm > ul > li.inline > a.whitespace-nowrap`
system status `div.text-sm > ul > li.inline > a.whitespace-nowrap`
data subject access request `div.text-sm > ul > li.inline > a.whitespace-nowrap`
reCAPTCHA privacy `div.text-sm > ul > li.inline > a.whitespace-nowrap`
reCAPTCHA terms `div.text-sm > ul > li.inline > a.whitespace-nowrap`

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

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

●Form elements have associated labels

●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

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

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

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

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

8 headings

PASS

8 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 Urban Dictionary
H1 Wasian duplicate H1
H2 whitelisted
H2 futch
H2 deinfluence
H2 boy kibble
H2 FoMo
H2 Moon Joy

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

7 image(s) with good alt text

7 images 7 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search-input	input	Search	aria-label

Link & Button Quality

1 issue(s) across 131 links and 18 buttons

PASS

1 issue(s) across 131 links and 18 buttons

1 link(s) with no accessible text

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

Got: /

130 link(s) with descriptive text

131 links

1 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label

148 links and buttons have descriptive text

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

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

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