Skip to content
https://equifax.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
66
GRADE
D
FIX
3
REVIEW
4
PASS
6
INFO
0
Checks
13
6 PASS 4 REVIEW 3 FIX
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
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 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.

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 ✗
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Navigation UX
Action
2 navigation pattern(s)
REVIEW
2 navigation pattern(s)
Info::
Breadcrumb navigation detected
Got: aria-label
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs aria-label navigation
Search
Skip Link Skip link detected
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
A+
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main" MAIN CONTENTINFO footer
A
Heading Hierarchy
37 headings, 1 skip(s)
PASS
37 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Your Equifax Cookie Preferences
  • H3 Don’t have an account?
  • H3 Don’t have an account?
  • H2 Help look after your family with credit monitoring and ID theft protection features.
  • H2 Take control with a one-stop credit monitoring and identity theft protection solution from Equifax.
  • H2 Don’t let identity theft catch you off guard. Get better prepared to monitor your credit and help better protect your identity with Equifax Complete™.
  • H2 Get the basics with your monthly credit score and report.
  • H2 Credit Scores
  • H2 Credit Reports
  • H2 Fraud & Identity Theft
  • H2 Debt Management
  • H2 Credit Cards
  • H2 Personal Finance
  • H2 Loans
  • H2 Life Stages
  • H2 Cybersecurity
  • H2 Información crediticia de EE. UU.
  • H2 Videos
  • H2 Credit Card Offers
  • H2 Personal Loan Rates
  • H2 Auto Loan Rates
  • H2 Insurance Quotes
  • H5 Free Services for Consumers skipped
  • H5 Tell Us Why You're Here
  • H5 Frequently Asked Questions
  • H5 Your Equifax Support
  • H1 Help better protect your identity with Equifax Complete™.
  • H2 Get robust identity theft protection and feel more secure from fraud
  • H2 EQUIFAX Complete™
  • H2 EQUIFAX COMPLETE™ Premier
  • H2 EQUIFAX COMPLETE™ Family Plan
  • H2 Explore Credit Offers
  • H2 Explore Credit Offers
  • H2 Reach your financial goals
  • H2 Don't fall prey to identity theft
  • H2 Navigate your credit journey with the myEquifax app
  • H3 Visit the Equifax Consumer Services Center

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
1 of 42 images have issues
PASS
1 of 42 images have issues
Warning::
1 image(s) with generic alt text
Info::
32 decorative image(s) correctly marked
Info::
9 image(s) with good alt text
42 images 9 good alt text 32 decorative 1 generic
IssueCount
generic1 image(s)
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="efxNavSiteSearchQuery" id="efxNavSiteSearchQuery">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#efxNavSiteSearchQuerysearch(Search Personal)placeholder only

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

<input type="search" name="efxNavSiteSearchQuery" id="efxNavSiteSearchQuery">

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

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 Help better protect …6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Help look after your…6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Take control with a …6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Don’t let identity…6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Get the basics with …6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Credit Scores6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Credit Reports6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Fraud & Identity The…6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Debt Management6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Credit Cards6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Personal Finance6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Loans6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Life Stages6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Cybersecurity6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Información crediti…6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Videos6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Credit Card Offers6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Personal Loan Rates6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Auto Loan Rates6.15:13.0:1
#000000
#8A8B8C
Pass
h2 Insurance Quotes6.15:13.0:1
#000000
#8A8B8C
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 92/100 — 2 failing, 27 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.

ARIA

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search nav.efx-n-site-navbar > div.navbar-mobile > ul.navbar-nav > li#test
Sign in nav.efx-n-site-navbar > div.navbar-mobile > ul.navbar-nav > li.nav-item

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search Sign in header.efx-n-site-header > nav.efx-n-site-navbar > div.navbar-mobile > ul.navbar-nav

These are opportunities to improve the experience of reading tabular or list data using 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.
●`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
●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
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●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
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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.
○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.
○No element has a `[tabindex]` value greater than 0
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback