Skip to content
https://reviewjournal.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 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
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 MAIN (missing!) CONTENTINFO footer

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
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-7iaeb6
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
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://reviewjournal.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://reviewjournal.com/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
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.
B
Form Accessibility
3 of 7 controls have issues
REVIEW
3 of 7 controls have issues
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="s">; <input type="search" name="s">; <input type="email">
Info::
4 control(s) properly labeled
7 controls
4 labeled
3 placeholder only
0 unlabeled
ControlTypeLabelMethod
#osano-cm-dialog-toggle--category_STORAGEcheckboxnone
#osano-cm-dialog-toggle--category_MARKETINGcheckboxnone
#osano-cm-dialog-toggle--category_PERSONALIZATIONcheckboxnone
#osano-cm-dialog-toggle--category_ANALYTICScheckboxnone
ssearch(Enter your search term...)placeholder only
ssearch(search...)placeholder only
inputemail(EMAIL)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="search" name="s">; <input type="search" name="s">; <input type="email">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Featured Local Savings
1.18:1
#000000
on
#180D43
needs 3.0:1 (large text)
24px · bottom of viewport
title Las Vegas News | Breaking News & Headlin…
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · top of page (header area)
span Opens in a new window
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · top of page (header area)
span Opens an external website
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · top of page (header area)
span Opens an external website in a new windo…
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · top of page (header area)
span We and our 8 IAB TCF partners store and …
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · above the fold
span Personal data may be processed to do the…
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · above the fold
span Our third party IAB TCF partners may sto…
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · above the fold
span You may change your settings at any time…
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · above the fold
span You may close this banner to continue wi…
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · above the fold
a Privacy Policy
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · above the fold
a Terms and Conditions
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · above the fold
a Storage Preferences
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · above the fold
a Third Parties
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · above the fold
span Storage
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · mid-page
span Targeted Advertising
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · mid-page
span Personalization
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · mid-page
span Analytics
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · mid-page
button Save
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · mid-page
button Accept All
1.18:1
#000000
on
#180D43
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Featured Local Savin…1.18:13.0:1
#000000
#180D43
Fail
title Las Vegas News | Bre…1.18:14.5:1
#000000
#180D43
Fail
span Opens in a new windo…1.18:14.5:1
#000000
#180D43
Fail
span Opens an external we…1.18:14.5:1
#000000
#180D43
Fail
span Opens an external we…1.18:14.5:1
#000000
#180D43
Fail
span We and our 8 IAB TCF…1.18:14.5:1
#000000
#180D43
Fail
span Personal data may be…1.18:14.5:1
#000000
#180D43
Fail
span Our third party IAB …1.18:14.5:1
#000000
#180D43
Fail
span You may change your …1.18:14.5:1
#000000
#180D43
Fail
span You may close this b…1.18:14.5:1
#000000
#180D43
Fail
a Privacy Policy1.18:14.5:1
#000000
#180D43
Fail
a Terms and Conditions1.18:14.5:1
#000000
#180D43
Fail
a Storage Preferences1.18:14.5:1
#000000
#180D43
Fail
a Third Parties1.18:14.5:1
#000000
#180D43
Fail
span Storage1.18:14.5:1
#000000
#180D43
Fail
span Targeted Advertising1.18:14.5:1
#000000
#180D43
Fail
span Personalization1.18:14.5:1
#000000
#180D43
Fail
span Analytics1.18:14.5:1
#000000
#180D43
Fail
button Save1.18:14.5:1
#000000
#180D43
Fail
button Accept All1.18:14.5:1
#000000
#180D43
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+
Heading Hierarchy
2 headings
PASS
2 headings
Info::
Single H1 present
  • H1 <img width="400" height="59" src="https://www.reviewjournal.com/wp-content/uploads/2020/07/rj_logo_black2.png" alt="Las Vegas News" />
  • H2 Featured Local Savings
A+
Alt Text Quality
All 41 images OK
PASS
All 41 images OK
Info::
6 decorative image(s) correctly marked
Info::
35 image(s) with good alt text
41 images 35 good alt text 6 decorative
All images have appropriate alt text.
A
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 28 passed
PASS
92

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.

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
body.home > img#06db9294 body.home > img#06db9294

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

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
Storage Preferences div#12ed7297-2404-458a-a455-99e6d8c59b69 > div.osano-cm-dialog__content > p.osano-cm-content__drawer-links > a.osano-cm-drawer-links__link
Third Parties div#12ed7297-2404-458a-a455-99e6d8c59b69 > div.osano-cm-dialog__content > p.osano-cm-content__drawer-links > a.osano-cm-drawer-links__link

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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Form elements have associated labels
●`[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
●Background and foreground colors have a sufficient contrast ratio
●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.
●Links have a discernible name
●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
●ARIA IDs are unique
●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
○`[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
○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.
○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