https://Bankrate.com
Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.SCORE
71
GRADE
C
FIX
7
REVIEW
5
PASS
12
INFO
0
Checks
2412 PASS 5 REVIEW 7 FIX
DTabindex Anti-PatternsAction0 positive, 42 -1-on-focusableFIX
Tabindex Anti-Patterns
Action0 positive, 42 -1-on-focusable
0 positive, 42 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-1-1">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-1-2">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-1-3">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-1-4">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-2-1">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-2-2">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-2-3">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-3-1">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-3-2">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-3-3">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-4-1">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-4-2">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-4-3">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-4-4">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-5-1">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-5-2">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-5-3">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-5-4">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-6-1">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-6-2">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-7-1">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-7-2">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="subcategory-7-3">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <input id="siteSearchInput">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="rates-trends-1-2">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="rates-trends-subsection-1-2">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="rates-trends-subsection-2-2">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
F404 Error PageActionHTTP 405, custom pageFIX
404 Error Page
ActionHTTP 405, custom page
HTTP 405, custom page
Warning::
Unexpected status code: HTTP 405
Expected HTTP 404 but received 405. This may confuse search engine crawlers.
Got: HTTP 405
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 405 ✗Page Title Human Verification ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
FFavicon & BrandingAction2 icon(s) detectedFIX
Favicon & Branding
Action2 icon(s) detected
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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 Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
FWeb ManifestActionValid manifestFIX
Web Manifest
ActionValid manifest
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
PWA Install Criteria Not Installable
Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗
DDark Mode SupportActionNo dark mode signalsFIX
Dark Mode Support
ActionNo dark mode signals
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.
DPrint StylesheetActionNo print stylesFIX
Print Stylesheet
ActionNo print styles
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 ✗
BLandmark Structure6 landmarksREVIEW
Landmark Structure
6 landmarks
6 landmarks
Info::
<main> landmark present
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::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #main-content
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Page Structure — as a screen reader sees it
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
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Why this matters
Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.
Learn more ▾ ▴
Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.
Source: WCAG 2.1 SC 2.4.1
BAlt Text Quality2 of 91 images have issuesREVIEW
Alt Text Quality
2 of 91 images have issues
2 of 91 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
45 decorative image(s) correctly marked
Info::
44 image(s) with good alt text
91 images 44 good alt text 45 decorative 2 missing
| Issue | Count |
|---|---|
| missing | 2 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
BForm Accessibility2 of 20 controls have issuesREVIEW
Form Accessibility
2 of 20 controls have issues
2 of 20 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <textarea>
Info::
18 control(s) properly labeled
20 controls
18 labeled
1 placeholder only
1 unlabeled
| Control | Type | Label | Method |
|---|---|---|---|
| #product-30_conventional | radio | 30-year fixed 5.97% Trend Up Icon Trend Down Icon Trend Unchanged Icon 0.25% | for/id |
| #product-15_conventional | radio | 15-year fixed 5.55% Trend Up Icon Trend Down Icon Trend Unchanged Icon 0.49% | for/id |
| #product-30_fha | radio | 30-year FHA 5.61% Trend Up Icon Trend Down Icon Trend Unchanged Icon 0.34% | for/id |
| #product-30_va | radio | 30-year VA 5.38% Trend Up Icon Trend Down Icon Trend Unchanged Icon 0.10% | for/id |
| #timeline-60_d | radio | 60 D | for/id |
| #timeline-6_m | radio | 6 M | for/id |
| #timeline-1_y | radio | 1 Y | for/id |
| #timeline-5_y | radio | 5 Y | for/id |
| #timeline-all | radio | All | for/id |
| #loan-purpose-purchase | radio | Purchase | for/id |
| #loan-purpose-refinance | radio | Refinance | for/id |
| #ot-group-id-C0004 | checkbox | Targeting Cookies | for/id |
| #ot-group-id-C0005 | checkbox | Social Media Cookies | for/id |
| #vendor-search-handler | text | Cookie list search | aria-label |
| #chkbox-id | checkbox | checkbox label | for/id |
| #select-all-hosts-groups-handler | checkbox | checkbox label | for/id |
| #select-all-vendor-groups-handler | checkbox | checkbox label | for/id |
| #select-all-vendor-leg-handler | checkbox | checkbox label | for/id |
| textarea | textarea | (Share your thoughts...) | placeholder only |
| input | checkbox | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="checkbox">
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.
<textarea>
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
CLink & Button QualityAction7 issue(s) across 373 links and 73 buttonsREVIEW
Link & Button Quality
Action7 issue(s) across 373 links and 73 buttons
7 issue(s) across 373 links and 73 buttons
Critical::
1 link(s) with no accessible text
Links without text are announced as raw URLs by screen readers.
Got: a (#1381 on page)
Warning::
10 link(s) open in new tab without warning
Add '(opens in new tab)' to link text or aria-label.
Got: http://www.nmlsconsumeraccess.org/EntityDetails.aspx/COMPANY/1427381; http://www.nmlsconsumeraccess.org/EntityDetails.aspx/COMPANY/1743443; https://www.facebook.com/Bankrate/; https://twitter.com/bankrate; https://www.instagram.com/bankrate/?hl=en; https://www.linkedin.com/company/bankrate/; https://www.youtube.com/user/bankrate; https://www.tiktok.com/@bankrate/; https://cookiepedia.co.uk/giving-consent-to-cookies; https://www.onetrust.com/products/cookie-consent/
Critical::
6 button(s) with no accessible text
Icon-only buttons need an aria-label so screen readers can announce them.
Got: button.w-7 (#2780 on page); button (#2900 on page); button (#2910 on page); button (#2920 on page); button (#2930 on page); button (#2944 on page)
Info::
362 link(s) with descriptive text
373 links
1 empty
0 generic text
10 new tab
6 empty buttons
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| /banking/savings/how-to-open-a-savings-a… | Savings basics 5 min read | img no alt | Add alt attribute to the image |
| /banking/savings/start-saving-from-scrat… | How to start saving 4 min read | img no alt | Add alt attribute to the image |
| /banking/cds/what-is-a-cd/ | CD basics 7 min read | img no alt | Add alt attribute to the image |
| /banking/cds/how-to-invest-in-cds/ | How to invest with CDs 6 min r… | img no alt | Add alt attribute to the image |
| /banking/reviews/capital-one/ | Capital One review Our take on… | img no alt | Add alt attribute to the image |
| /banking/reviews/marcus/ | Marcus review Our take on Marc… | img no alt | Add alt attribute to the image |
| /mortgages/how-to-get-a-mortgage/ | How to get a mortgage 11 min r… | img no alt | Add alt attribute to the image |
| /mortgages/first-time-homebuyer-loans-an… | First-time homebuyer programs … | img no alt | Add alt attribute to the image |
| /mortgages/how-does-refinancing-a-mortga… | How to refinance your mortgage… | img no alt | Add alt attribute to the image |
| /mortgages/cash-out-refinancing/ | Cash-out refinancing guide 9 m… | img no alt | Add alt attribute to the image |
| /mortgages/how-to-buy-a-house/ | Buying a home 12 min read | img no alt | Add alt attribute to the image |
| /mortgages/how-to-sell-your-house/ | Selling a home 10 min read | img no alt | Add alt attribute to the image |
| /investing/passive-income-ideas/ | Passive income ideas 26 min re… | img no alt | Add alt attribute to the image |
| /investing/how-to-start-investing/ | How to start investing 7 min r… | img no alt | Add alt attribute to the image |
| /retirement/best-and-worst-states-for-re… | Best & worst states for retire… | img no alt | Add alt attribute to the image |
| /retirement/how-to-save-for-retirement/ | How to save for retirement 15 … | img no alt | Add alt attribute to the image |
| /investing/financial-advisors/when-to-ge… | When to get an advisor 4 min r… | img no alt | Add alt attribute to the image |
| /investing/financial-advisors/pros-cons-… | Pros & cons of financial advis… | img no alt | Add alt attribute to the image |
| /credit-cards/tools/cardmatch/ | CardMatch™ Get personalized … | img no alt | Add alt attribute to the image |
| /credit-cards/tools/compare/ | Card comparison tool Compare c… | img no alt | Add alt attribute to the image |
| /credit-cards/building-credit/best-for-n… | Best cards for building credit… | img no alt | Add alt attribute to the image |
| /credit-cards/tools/spender-type-tool/ | Spender type tool Find cards t… | img no alt | Add alt attribute to the image |
| /loans/personal-loans/what-is-a-personal… | Personal loan basics 9 min rea… | img no alt | Add alt attribute to the image |
| /loans/personal-loans/how-to-get-persona… | How to get a personal loan 11 … | img no alt | Add alt attribute to the image |
| /loans/auto-loans/how-to-get-the-best-au… | How to get the best auto loan … | img no alt | Add alt attribute to the image |
| /loans/auto-loans/what-is-an-auto-loan/ | Auto loan basics 5 min read | img no alt | Add alt attribute to the image |
| /loans/student-loans/private-student-loa… | Private student loan basics 10… | img no alt | Add alt attribute to the image |
| /loans/student-loans/how-to-get-student-… | How to get a student loan 11 m… | img no alt | Add alt attribute to the image |
| /loans/small-business/how-do-small-busin… | How small business loans work … | img no alt | Add alt attribute to the image |
| /loans/small-business/how-to-get-a-busin… | How to get a business loan 9 m… | img no alt | Add alt attribute to the image |
| /home-equity/what-is-home-equity/ | What is home equity? 8 min rea… | img no alt | Add alt attribute to the image |
| /home-equity/home-equity-loan-lenders/ | Best home equity loan lenders … | img no alt | Add alt attribute to the image |
| /insurance/car/ | Car insurance resources Learn … | img no alt | Add alt attribute to the image |
| /insurance/homeowners-insurance/homeowne… | Home insurance cost Average co… | img no alt | Add alt attribute to the image |
| /insurance/homeowners-insurance/ | Home insurance resources Learn… | img no alt | Add alt attribute to the image |
| (empty) | empty | Add link text or aria-label | |
| http://www.nmlsconsumeraccess.org/Entity… | NMLS Consumer Access | new tab | Add '(opens in new tab)' to text |
| http://www.nmlsconsumeraccess.org/Entity… | NMLS Consumer Access | new tab | Add '(opens in new tab)' to text |
| https://www.facebook.com/Bankrate/ | new tab | Add '(opens in new tab)' to text | |
| https://twitter.com/bankrate | new tab | Add '(opens in new tab)' to text | |
| https://www.instagram.com/bankrate/?hl=e… | new tab | Add '(opens in new tab)' to text | |
| https://www.linkedin.com/company/bankrat… | new tab | Add '(opens in new tab)' to text | |
| https://www.youtube.com/user/bankrate | Youtube | new tab | Add '(opens in new tab)' to text |
| https://www.tiktok.com/@bankrate/ | TikTok | new tab | Add '(opens in new tab)' to text |
| https://cookiepedia.co.uk/giving-consent… | More information about your pr… | new tab | Add '(opens in new tab)' to text |
| https://www.onetrust.com/products/cookie… | Powered by OneTrust Opens in a… | new tab | Add '(opens in new tab)' to text |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
429 links and buttons have descriptive text
Links without text are announced as raw URLs by screen readers.
a (#1381 on page)
Why this matters
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
Add '(opens in new tab)' to link text or aria-label.
http://www.nmlsconsumeraccess.org/EntityDetails.aspx/COMPANY/1427381; http://www.nmlsconsumeraccess.org/EntityDetails.aspx/COMPANY/1743443; https://www.facebook.com/Bankrate/; https://twitter.com/bankrate; https://www.instagram.com/bankrate/?hl=en; https://www.linkedin.com/company/bankrate/; https://www.youtube.com/user/bankrate; https://www.tiktok.com/@bankrate/; https://cookiepedia.co.uk/giving-consent-to-cookies; https://www.onetrust.com/products/cookie-consent/
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
Icon-only buttons need an aria-label so screen readers can announce them.
button.w-7 (#2780 on page); button (#2900 on page); button (#2910 on page); button (#2920 on page); button (#2930 on page); button (#2944 on page)
Why this matters
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
BPWA Depth3 PWA signal(s) surfacedREVIEW
PWA Depth
3 PWA signal(s) surfaced
3 PWA signal(s) surfaced
Warning::
Manifest is missing `display` -- defaults to browser, no PWA UX
When `display` is `browser` (or unset, which is the spec default), the installed app opens in a regular browser tab -- no install prompt, no standalone window, no app-shell experience. The intended values for a PWA are `standalone` (most common; full-screen, no browser chrome) or `fullscreen` (games / immersive apps). `minimal-ui` is a middle ground (basic browser controls but no address bar).
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
Info::
Manifest is missing `theme_color`
Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.
A+Heading Hierarchy63 headingsPASS
Heading Hierarchy
63 headings
63 headings
Info::
Single H1 present
- H1 Your bank has a mortgage rate. We have a better one.
- H2 The proof is in the $73,000 you keep
- H2 The latest top mortgage rates from Bankrate
- H3 How the rates in this chart are calculated
- H2 Build your home on a stronger financial foundation
- H2 Bankrate connects people to trusted ways to save, borrow and thrive.
- H2 How to avoid 3 mortgage industry traps
- H2 Experts in all things finance
- H2 Confidence shouldn't be a feeling. It should be a calculation.
- H2 Homebuying in America: From homeless to homeowner of “a place where my family can come”
- H3 Mortgage rates rise again as inflation, Iran undermine confidence
- H3 When should you refinance your mortgage?
- H3 Mortgage rates rise as Iran conflict rattles confidence
- H2 Current CD rates for May 2026
- H3 Historical CD interest rates: 1984-2025
- H3 The 10 largest credit unions in the US
- H3 What is a good interest rate on a savings account?
- H2 Current credit card interest rates
- H3 How to get cash from a credit card at the ATM
- H3 Why did my interest rate go up on my credit card?
- H3 How long does it take to increase your credit score?
- H2 High-yield savings account vs. money market fund: Which is better?
- H3 What is the S&P 500?
- H3 Low-cost index funds: A beginner’s guide
- H3 6 best investing and trading apps for beginners
- H2 How to get a low interest loan in 7 steps
- H3 What is an unsecured loan?
- H3 What is the APR on a personal loan?
- H3 What is the average personal loan rate for May 2026?
- H2 Can you use home equity to buy another house?
- H3 HELOC, home equity rates spike higher
- H3 How to shop for a HELOC: 10 ways to get the best HELOC rate
- H3 Where to get a home equity loan or HELOC: finding the best lender
- H2 Why teen driver insurance averages a sizeable $5,700 a year — and the policy detail that could cost you more
- H3 Study: Americans pay $575 per month in hidden car ownership costs
- H3 Not what I signed up for: High insurance rates leave some homeowners with buyers remorse
- H3 Extreme weather puts $12.7 trillion in homes at risk, many underinsured
- H2 Taxes on mutual funds: How they work and 4 strategies to minimize what you owe
- H3 Cryptocurrency taxes: A guide to tax rules for Bitcoin, Ethereum and more
- H3 Biden’s proposed Child Tax Credit extension: See if you’d qualify for the ramped-up credit
- H3 3 ways Biden’s American Families Plans could change your taxes
- H2 Can you use home equity to buy another house?
- H3 How to get a low interest loan in 7 steps
- H3 What is an unsecured loan?
- H3 What is the APR on a personal loan?
- H2 Today’s top CD rates
- H2 Current CD trends
- H2 Today’s top savings rates
- H2 Current savings trends
- H2 Bankrate logo Bankrate
- H3 About
- H3 Help
- H3 Legal
- H3 How we make money
- H3 How the rates in this chart are calculated
- H2 Privacy Settings
- H3 Manage Consent Preferences
- H4 Strictly Necessary Cookies
- H4 Functional Cookies
- H4 Performance Cookies
- H4 Targeting Cookies
- H4 Social Media Cookies
- H3 Cookie List
A+Heading Text QualityAll 63 heading(s) have substantive, well-formed textPASS
Heading Text Quality
All 63 heading(s) have substantive, well-formed text
All 63 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+Form Input Types1 input(s) using type=text where a specific type would helpPASS
Form Input Types
1 input(s) using type=text where a specific type would help
1 input(s) using type=text where a specific type would help
Info::
Input "vendor-search-handler" should use type="search" (currently type="text")
Field name "vendor-search-handler" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+Form Input Quality20 form control(s) checked, no input-semantic issuesPASS
Form Input Quality
20 form control(s) checked, no input-semantic issues
20 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+Mobile Keyboard & AutofillNo autofill-eligible form controlsPASS
Mobile Keyboard & Autofill
No autofill-eligible form controls
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+Document LanguageLang attribute set to "en"PASS
Document Language
Lang attribute set to "en"
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
AIframe Accessibility1/3 iframe(s) missing title; 0 placeholder(s)PASS
Iframe Accessibility
1/3 iframe(s) missing title; 0 placeholder(s)
1/3 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+Mobile-Readable Font SizesAll 36 visible text node(s) render at >= 12 CSS pixelsPASS
Mobile-Readable Font Sizes
All 36 visible text node(s) render at >= 12 CSS pixels
All 36 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
Mobile UX Depth
1 mobile-depth signal(s) detected
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
A+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
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)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h2 The proof is in the … | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 The latest top mortg… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Build your home on a… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Bankrate connects pe… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 How to avoid 3 mortg… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Experts in all thing… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Confidence shouldn't… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Today’s top CD rat… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Current CD trends | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Today’s top saving… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Current savings tren… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Privacy Settings | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 About | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Help | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Legal | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 How we make money | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 How the rates in thi… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Manage Consent Prefe… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Cookie List | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title Bankrate: Trusted wa… | 21.00:1 | 4.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.
A+Lighthouse Accessibility AuditsScore 100/100 — 1 failing, 31 passedPASS
Lighthouse Accessibility Audits
Score 100/100 — 1 failing, 31 passed
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.
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 |
|---|
All div#siteNavCategory-flyout-banking > div.SiteNavCategory-panel > div.SiteNavMobile-sticky > button.SiteNavMobile-back |
Banking div.SiteNavSubcategory-content > div.SiteNavSubcategory-panelsContainer > div.SiteNavMobile-sticky > button.SiteNavMobile-back |
All div#siteNavCategory-flyout-mortgages > div.SiteNavCategory-panel > div.SiteNavMobile-sticky > button.SiteNavMobile-back |
Mortgages div.SiteNavSubcategory-content > div.SiteNavSubcategory-panelsContainer > div.SiteNavMobile-sticky > button.SiteNavMobile-back |
All div#siteNavCategory-flyout-investing > div.SiteNavCategory-panel > div.SiteNavMobile-sticky > button.SiteNavMobile-back |
Investing div.SiteNavSubcategory-content > div.SiteNavSubcategory-panelsContainer > div.SiteNavMobile-sticky > button.SiteNavMobile-back |
All div#siteNavCategory-flyout-credit-cards > div.SiteNavCategory-panel > div.SiteNavMobile-sticky > button.SiteNavMobile-back |
Credit cards div.SiteNavSubcategory-content > div.SiteNavSubcategory-panelsContainer > div.SiteNavMobile-sticky > button.SiteNavMobile-back |
All div#siteNavCategory-flyout-loans > div.SiteNavCategory-panel > div.SiteNavMobile-sticky > button.SiteNavMobile-back |
Loans div.SiteNavSubcategory-content > div.SiteNavSubcategory-panelsContainer > div.SiteNavMobile-sticky > button.SiteNavMobile-back |
All div#siteNavCategory-flyout-home-equity > div.SiteNavCategory-panel > div.SiteNavMobile-sticky > button.SiteNavMobile-back |
Home equity div.SiteNavSubcategory-content > div.SiteNavSubcategory-panelsContainer > div.SiteNavMobile-sticky > button.SiteNavMobile-back |
All div#siteNavCategory-flyout-insurance > div.SiteNavCategory-panel > div.SiteNavMobile-sticky > button.SiteNavMobile-back |
Insurance div.SiteNavSubcategory-content > div.SiteNavSubcategory-panelsContainer > div.SiteNavMobile-sticky > button.SiteNavMobile-back |
Log in div#desktop-auth-section > div.flex > div.pr-4 > a#auth-button |
Share your thoughts body > div#fountain-embed-root > div.fountain > button.fn-floating-pill |
○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]`s are contained by their required parent element
●`[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
●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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●ARIA `tooltip` elements have accessible names
●Background and foreground colors have a sufficient contrast ratio
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●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
●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
●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 the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○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
○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.
○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.