Skip to content
https://inquisitr.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
D
Landmark Structure
Action
3 landmarks
FIX
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
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 (missing!) NAV "main menu" 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

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

D
Form Accessibility
Action
4 of 5 controls have issues
FIX
4 of 5 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="log">; <input type="password" name="pwd">; <input type="submit" name="wp-submit">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="wpforms[fields][8]" id="wpforms-1226464-field_8">
Info::
1 control(s) properly labeled
5 controls
1 labeled
1 placeholder only
3 unlabeled
ControlTypeLabelMethod
#remembermecheckboxnone
#wpforms-1226464-field_8email(Email Address)placeholder only
pwdpassword(none)none
logtext(none)none
wp-submitsubmit(none)none

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

<input type="text" name="log">; <input type="password" name="pwd">; <input type="submit" name="wp-submit">

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

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

<input type="email" name="wpforms[fields][8]" id="wpforms-1226464-field_8">

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

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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::
2 navigation landmark(s) detected
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 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
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
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A
Heading Hierarchy
35 headings, 1 skip(s)
PASS
35 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Inquisitr News
  • H2 Marjorie Taylor Greene Says Trump “Flat Out” Ordered Pam Bondi Not to Release Epstein Files
  • H3 Meghan Markle Faced Doubts — Then Crew Shared What She Was Really Like
  • H3 Obama Takes Victory Lap After Trump Suffers Setback in Virginia Referendum
  • H3 Kash Patel Lashes Out At Reporters For Asking If He’s Been Drunk At Work
  • H3 Pete Hegseth’s Pentagon Wants $1.5 Trillion, Iran War Could Add Hundreds of Billions More
  • H3 Latest News
  • H2 Mother Won $1.3M Jackpot on Betting App – Days Later, the Company Refused to Pay Even a Penny
  • H4 Chris Nanos, Sheriff Leading Nancy Guthrie Case, Admits Leaving Past Job To Avoid Discipline skipped
  • H4 Army Veteran Dies After Cosmetic Surgery as Husband Awaits $52M in Damages
  • H4 Woman Dies of Overdose After Drone Delivers Drugs in Church Parking Lot; Dealer Sentenced
  • H4 Follow US
  • H3 More Stories
  • H2 Two Siblings With Autism Were Left Home Alone Overnight—Now Their Mother Is Charged in the Death of One
  • H3 Michael Jackson’s Biopic Labeled ‘Ghoulish, Soulless Cash Grab’ as Critics Point Out Its Flaws
  • H3 Murderer on Death Row for 36 Years Delivers Final Message to Victim’s Family Before Execution
  • H4 Meghan Markle’s Estranged Father Finds Love in Rehabilitation Hospital With Nurse 35 Years His Junior
  • H4 Conditions Under Which U.S. Military Leaders Can Refuse Donald Trump’s Orders During the Iran War
  • H4 Psychic Predicts Strain in Melania and Donald Trump’s Relationship: “The Past Creeps Into the Present”
  • H3 Just Published
  • H3 Soldier Who Served 27 Years Says ICE Detained His Wife Despite Legal Protections—And He Still Doesn’t Understand Why
  • H3 Trump Rages at His Own Supreme Court Picks Says They Have ‘Very Little Loyalty’
  • H3 Meghan Markle Spark Backlash Over Alleged “Disposable” Behavior Towards Staff
  • H3 Lauren Sánchez Allegedly Tries To Repair Anna Wintour and Trump Feud
  • H3 Trump Extends Iran Ceasefire in a Move That Leaves Strait of Hormuz Blocked
  • H3 Donald Trump’s Whereabouts Become a Flashpoint as Situation Room Claims Surface
  • H3 Tucker Carlson Says He’s “Sorry” for Supporting Trump, Admits He Misled Americans
  • H3 Trump Says Bombing Iran Is a “Better Attitude” as Ceasefire Nears End
  • H3 Most Recent
  • H3 Netanyahu Could Face Arrest in Hungary, New PM Peter Magyar Says
  • H3 Leavitt Pushes Mental Illness Care Access, Which Some Feel Trump Needs
  • H2 Nancy Guthrie Update — FBI Testing DNA Is A “Very Good Sign”
  • H3 Melania Trump’s Public Absence Raises Questions About Her Role and Marriage
  • H3 Meghan Markle Criticized For ‘Disgusting’ Move On Queen Elizabeth’s 100th Birthday
  • H3 Want the latest updates on news, celeb gossip & political chaos?

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

A+
Alt Text Quality
All 43 images OK
PASS
All 43 images OK
Info::
2 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
40 image(s) with good alt text
43 images 40 good alt text 1 decorative
IssueCount
too long2 image(s)
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 Inquisitr News16.98:13.0:1
#000000
#E7E7E7
Pass
h3 Want the latest upda…16.98:13.0:1
#000000
#E7E7E7
Pass
title Inquisitr News16.98:14.5:1
#000000
#E7E7E7
Pass
p Inquisitr News16.98:14.5:1
#000000
#E7E7E7
Pass
span News16.98:14.5:1
#000000
#E7E7E7
Pass
span Politics16.98:14.5:1
#000000
#E7E7E7
Pass
span Human Interest16.98:14.5:1
#000000
#E7E7E7
Pass
span Crime16.98:14.5:1
#000000
#E7E7E7
Pass
span Entertainment15.76:14.5:1
#000000
#CFE3E4
Pass
span More21.00:14.5:1
#000000
#FFFFFF
Pass
span Money21.00:14.5:1
#000000
#FFFFFF
Pass
span Sports21.00:14.5:1
#000000
#FFFFFF
Pass
span Featured21.00:14.5:1
#000000
#FFFFFF
Pass
span Newsletter21.00:14.5:1
#000000
#FFFFFF
Pass
span Get updates in your …21.00:14.5:1
#000000
#FFFFFF
Pass
span News Alerts21.00:14.5:1
#000000
#FFFFFF
Pass
span News21.00:14.5:1
#000000
#FFFFFF
Pass
span Politics21.00:14.5:1
#000000
#FFFFFF
Pass
span Human Interest16.98:14.5:1
#000000
#E7E7E7
Pass
span Crime16.98:14.5:1
#000000
#E7E7E7
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 93/100 — 2 failing, 25 passed
PASS
93

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
300 partners div#cmpboxcontent > div.cmpboxtxtdiv > div.cmpboxtxt > a.cmplink
Accept all div.cmpboxbtns > span#cmpwelcomebtnyes > a.cmpboxbtn > span#cmpbntyestxt
Settings div.cmpboxbtns > span#cmpwelcomebtncustom > a.cmpboxbtn > span#cmpbntcustomtxt
Privacy notice div.cmpboxinner > div.cmpboxbtns > div.cmpmore > a.cmpmorelink

These are opportunities to improve the legibility of your content.

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
POLITICS div.overlay-wrap > div.overlay-inner > div.p-categories > a.p-category
NEWS div.list-feat-holder > div.feat-holder > div.p-categories > a.p-category

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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●`<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
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○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
○Buttons have an accessible name
○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
○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.
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback