Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 3 REVIEW 4 FIX

Web Manifest

Action

Not found

FIX

Not found

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.

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.

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 Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

6 icon(s) detected

REVIEW

6 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, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA

title WalletHub - Credit Cards, Loans, Credit …

1.22:1

#000000

#23123A

needs 4.5:1 (normal text)

16px · top of page (header area)

span Search

1.22:1

#000000

#23123A

needs 4.5:1 (normal text)

16px · top of page (header area)

button Cancel

4.25:1

#000000

#136AE8

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Supercharge	19.16:1	3.0:1	#000000	#F1F5F8	Pass
h1 Your Finances	19.16:1	3.0:1	#000000	#F1F5F8	Pass
h2 Make your money work…	19.16:1	3.0:1	#000000	#F1F5F8	Pass
h2 Improve your credit …	19.16:1	3.0:1	#000000	#F1F5F8	Pass
h2 Personalized offers …	19.16:1	3.0:1	#000000	#F1F5F8	Pass
h2 Monitor and track yo…	19.16:1	3.0:1	#000000	#F1F5F8	Pass
h2 Protect your identit…	19.16:1	3.0:1	#000000	#F1F5F8	Pass
h2 Find the Best Deals	19.16:1	3.0:1	#000000	#F1F5F8	Pass
h2 People Love WalletHu…	19.16:1	3.0:1	#000000	#F1F5F8	Pass
title WalletHub - Credit C…	1.22:1	4.5:1	#000000	#23123A	Fail
span Search	1.22:1	4.5:1	#000000	#23123A	Fail
button Cancel	4.25:1	4.5:1	#000000	#136AE8	Fail
a Credit Cards	19.16:1	4.5:1	#000000	#F1F5F8	Pass
a MyHub	19.16:1	4.5:1	#000000	#F1F5F8	Pass
a Credit Cards	19.16:1	4.5:1	#000000	#F1F5F8	Pass
a Cards for Me	19.16:1	4.5:1	#000000	#F1F5F8	Pass
a Compare Cards	19.16:1	4.5:1	#000000	#F1F5F8	Pass
a Editors' Best	19.16:1	4.5:1	#000000	#F1F5F8	Pass
a CardAdvisor™	19.16:1	4.5:1	#000000	#F1F5F8	Pass
a Payoff Calculator	19.16:1	4.5:1	#000000	#F1F5F8	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.

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

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

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

8 headings

PASS

8 headings

Single H1 present

H1 Supercharge Your Finances
H2 Make your money work for you
H2 Improve your credit & save
H2 Personalized offers for your credit
H2 Monitor and track your investments
H2 Protect your identity
H2 Find the Best Deals
H2 People Love WalletHub

Alt Text Quality

1 of 5 images have issues

PASS

1 of 5 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

4 image(s) with good alt text

5 images 4 good alt text 1 missing

Issue	Count
missing	1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

Form Accessibility

1 of 24 controls have issues

PASS

1 of 24 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" id="logout-button">

23 control(s) properly labeled

24 controls

23 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#search	text	Site Search	aria-label
#toggle0	checkbox	Budgeting Tool	for/id
#toggle1	checkbox	Spending Tracker	for/id
#toggle2	checkbox	Subscription Manager	for/id
#toggle3	checkbox	WalletScore	for/id
#toggle-credit0	checkbox	Credit Scores & Reports	for/id
#toggle-credit1	checkbox	Credit Builder	for/id
#toggle-credit2	checkbox	Credit Report Monitoring	for/id
#toggle-credit3	checkbox	Credit Lock	for/id
#toggle-credit4	checkbox	Credit Improvement Plan	for/id
#toggle-credit5	checkbox	Debt Payoff Plan	for/id
#toggle-offers0	checkbox	Personalized Credit Card Offers	for/id
#toggle-offers1	checkbox	Pre-qualified Personal Loans	for/id
#toggle-offers2	checkbox	Savings Opportunities	for/id
#toggle-investment0	checkbox	Investment Monitoring	for/id
#toggle-investment1	checkbox	News Feed	for/id
#toggle-investment2	checkbox	Retirement Planning	for/id
#toggle-investment3	checkbox	Net Worth	for/id
#toggle-identity0	checkbox	Dark Web Monitoring	for/id
#toggle-identity1	checkbox	$1M Identity Theft Insurance	for/id
#toggle-identity2	checkbox	Identity Monitoring	for/id
#hm-wh-trust	checkbox	WALLETHUBS PICKS ARE THE BEST IN THE INDUSTRY	for/id
#cellphone	text	Enter your cell phone number and we’ll send you a link to install the WalletHub app.	aria-label
#logout-button	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

Link & Button Quality

361 links, 8 buttons — all OK

PASS

361 links, 8 buttons — all OK

4 link(s) open in new tab without warning

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

Got: https://wallethub.com/edu/cc/credit-card-rating-system/125319; https://wallethub.com/edu/wallethub-editorial-policy/25756; https://apps.apple.com/us/app/wallethub/id1110552982?mt=8; https://play.google.com/store/apps/details?id=com.wallethub.mywallet

357 link(s) with descriptive text

361 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://wallethub.com/edu/cc/credit-card…	sophisticated card rating syst…	new tab	Add '(opens in new tab)' to text
https://wallethub.com/edu/wallethub-edit…	100% editorial independence	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/us/app/wallethub/…	get on the app store	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	get on the google play	new tab	Add '(opens in new tab)' to text

365 links and buttons have descriptive text

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

https://wallethub.com/edu/cc/credit-card-rating-system/125319; https://wallethub.com/edu/wallethub-editorial-policy/25756; https://apps.apple.com/us/app/wallethub/id1110552982?mt=8; https://play.google.com/store/apps/details?id=com.wallethub.mywallet

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

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 27 passed

PASS

100

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.

○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

●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

●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

●Uses ARIA roles only on compatible elements

●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

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

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

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