Skip to content
https://smartasset.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
6
REVIEW
7
PASS
0
INFO
0
Checks
13
7 REVIEW 6 FIX
D
Form Accessibility
Action
4 of 6 controls have issues
FIX
4 of 6 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="submit">; <input type="submit">; <input type="button">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="email">
Info::
2 control(s) properly labeled
6 controls
2 labeled
1 placeholder only
3 unlabeled
ControlTypeLabelMethod
#searchtextSearchfor/id
#searchtextSearchfor/id
emailtext(Email Address)placeholder only
inputsubmit(none)none
inputbutton(none)none
inputsubmit(none)none

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

<input type="submit">; <input type="submit">; <input type="button">

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="text" name="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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 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 1 <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
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 CONTENTINFO footer

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

B
Heading Hierarchy
19 headings, 1 skip(s)
REVIEW
19 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
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 Get Clarity.
  • H2 Find Your Advisor.
  • H2 "How Can I Reduce My RMD Tax Burden After Age 75?"
  • H4 Answer SmartAsset advisor match quiz skipped
  • H4 Review your vetted matches
  • H4 Introductory call with advisors at no cost to you
  • H3 Guides
  • H3 Calculators
  • H3 Reviews
  • H3 Rates
  • H2 The Latest In SmartReads
  • H3 How Much Can Financial Advisors Make at Morgan Stanley?
  • H3 Custody Rule FAQ for Registered Advisors
  • H3 How to Use the Double Consolidation Loophole for Student Loans
  • H3 How Financial Advisors Should Segment Their Book
  • H3 Errors and Omissions (E&O) Insurance for RIAs and Advisors
  • H3 I Have $1.4 Million Invested with My Advisor Who Charges a 1% Fee. Am I Paying Too Much?
  • H2 Financial Advisors, Get Matched With Investors
  • H1 Subscribe To SmartMoney Minute duplicate H1

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

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

B
Alt Text Quality
3 of 35 images have issues
REVIEW
3 of 35 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
2 decorative image(s) correctly marked
Info::
30 image(s) with good alt text
35 images 30 good alt text 2 decorative 3 missing
IssueCount
missing3 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

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
Info::
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 ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA 1 pass AA only
title SmartAsset.com | Empowering You to Make …
2.18:1
#000000
on
#00496E
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Get21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Subscribe To21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Minute21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Find Your Advisor.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 "How Can I Reduce My…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The Latest In21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Financial Advisors, …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 How Much Can Financi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Custody Rule FAQ for…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 How to Use the Doubl…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 How Financial Adviso…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Errors and Omissions…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 I Have $1.4 Million …21.00:13.0:1
#000000
#FFFFFF
Pass
title SmartAsset.com | Emp…2.18:14.5:1
#000000
#00496E
Fail
li Mortgage6.24:14.5:1
#000000
#6692A8
Pass
li Taxes21.00:14.5:1
#000000
#FFFFFF
Pass
li Retirement21.00:14.5:1
#000000
#FFFFFF
Pass
li Financial Advisors21.00:14.5:1
#000000
#FFFFFF
Pass
li Banking21.00:14.5:1
#000000
#FFFFFF
Pass
li Investing21.00:14.5:1
#000000
#FFFFFF
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.

B
Lighthouse Accessibility Audits
Score 80/100 — 6 failing, 21 passed
REVIEW
80

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Mortgage Taxes Retirement Financial Advisors Banking Investing Credit Cards Lif… body > nav.Header_header__SQD4u > ul.Header_navCategories__f7Wov > ul.Header_mainMenuMobile__3Z38d

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.

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
Find an Advisor body > nav.Header_header__SQD4u > div.Header_falcCta__bzGq2 > a.Header_orange__DIr6S
Clarity. div.Hero_topSection__S2wLm > div.Hero_textContent__gTGbY > h1 > span.Hero_highlight__cIMhk
I'm An Advisor div.Hero_topSection__S2wLm > div.Hero_textContent__gTGbY > div > a.Hero_advisorCta__KLmaH
Works section.HowOurServiceWorks_howOurServiceWorksSection__0z1cW > div.Homepage_defaultSection__V4xo_ > div.HowOurServiceWorks_sectionTitle__yZ4Sj > span.HowOurServiceWorks_sectionTitleBlue__TNCb4
Tools & Resources section.ContentGuideShared_contentGuideSection__NZefp > div.Homepage_defaultSection__V4xo_ > div.ContentGuideShared_sectionTitle__jensn > span.ContentGuideShared_sectionTitleBlue__Z9ztk
Guides div.MobileContentGuideAccordion_accordion__Rz8o1 > div > h3.MobileContentGuideAccordion_accordionHeader__rnprw > button#radix-_r_0_
Calculators div.MobileContentGuideAccordion_accordion__Rz8o1 > div > h3.MobileContentGuideAccordion_accordionHeader__rnprw > button#radix-_r_2_
How Much Can Financial Advisors Make at Morgan Stanley? div.RecentArticles_slide__kjDnk > a.RecentArticles_articleCard__c27sz > div.RecentArticles_content__ftm1Z > h3.RecentArticles_title__b4ICx
Investors div.HomepageAmpCta_contentContainer__qkLmE > div.HomepageAmpCta_contentLeft__nfzMA > h2.HomepageAmpCta_mainHeading__maAZF > span.HomepageAmpCta_headingBlue__Z2nTz
Learn More div.HomepageAmpCta_contentContainer__qkLmE > div.HomepageAmpCta_contentLeft__nfzMA > div.HomepageAmpCta_ctaContainer__TsAQn > a.HomepageAmpCta_secondaryCta__d0h8k

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Answer SmartAsset advisor match quiz div.HowOurServiceWorks_stepsContainer__ONN0h > div.HowOurServiceWorks_stepCardWrapper__EYKgZ > div.HowOurServiceWorks_stepCard__K1I5N > h4.HowOurServiceWorks_stepTitle__ZovEi

These are opportunities to improve keyboard navigation in your application.

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 > img body > img

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

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Take Matching Quiz div.Hero_topSection__S2wLm > div.Hero_textContent__gTGbY > div > a.Hero_heroCta__qC5QW
I'm An Advisor div.Hero_topSection__S2wLm > div.Hero_textContent__gTGbY > div > a.Hero_advisorCta__KLmaH
Find An Advisor div.Homepage_defaultSection__V4xo_ > div.AdvisorValue_pills__Mtmdn > div.AdvisorValue_ctaContainer__huzA_ > a.AdvisorValue_ctaButton__cr54Q
Get Started section.HowOurServiceWorks_howOurServiceWorksSection__0z1cW > div.Homepage_defaultSection__V4xo_ > div.HowOurServiceWorks_ctaContainer__DxSqj > a.HowOurServiceWorks_ctaButton__SraZZ
Get Started main.Homepage_main__xXUe4 > section.Homepage_alternatingSection___wf6N > section.HomepageMap_mapSection__wtQi0 > a.HomepageMap_mapCta__QeYkH
PROFESSIONAL DEVELOPMENT How Much Can Financial Advisors Make at Morgan Stanley… div.RecentArticles_viewport__EKG88 > div.RecentArticles_emblaContainer__k03fs > div.RecentArticles_slide__kjDnk > a.RecentArticles_articleCard__c27sz
Careers footer.Footer_footer__x7vJd > div.Footer_column__uTh4D > div.Footer_columnItem__7JpYI > a
SmartReads footer.Footer_footer__x7vJd > div.Footer_column__uTh4D > div.Footer_columnItem__7JpYI > a
Advisor Testimonials footer.Footer_footer__x7vJd > div.Footer_column__uTh4D > div.Footer_columnItem__7JpYI > a
Like on Facebook footer.Footer_footer__x7vJd > div.Footer_column__uTh4D > div.Footer_columnItem__7JpYI > a.Footer_social__cb1G5
Like on X footer.Footer_footer__x7vJd > div.Footer_column__uTh4D > div.Footer_columnItem__7JpYI > a.Footer_x__knf3T
Follow on LinkedIn footer.Footer_footer__x7vJd > div.Footer_column__uTh4D > div.Footer_columnItem__7JpYI > a.Footer_linkedin__j6XJf
AdChoices footer.Footer_footer__x7vJd > div.Footer_column__uTh4D > div.Footer_columnItem__7JpYI > a
GLB Notice footer.Footer_footer__x7vJd > div.Footer_column__uTh4D > div.Footer_columnItem__7JpYI > a
○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
●Form elements have associated labels
●ARIA attributes are used as specified for the element's role
●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 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
●Touch targets have sufficient size and spacing.
●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
○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
○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
○Links are distinguishable without relying on color.
○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