Skip to content
https://ecunewexperience.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
9
REVIEW
6
PASS
9
INFO
0
Checks
24
9 PASS 6 REVIEW 9 FIX
F
Heading Hierarchy
Action
71 headings, 10 skip(s)
FIX
71 headings, 10 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H4 Personal Loans
  • H4 Vehicle Loans
  • H4 Mortgage Loans
  • H4 Business Loans
  • H6 Quick Resources skipped
  • H4 Share Savings
  • H4 Deposit Account
  • H4 Member Account
  • H6 Quick Resources skipped
  • H4 Insurance
  • H6 Quick Resources skipped
  • H4 Services
  • H6 Quick Resources skipped
  • H4 Membership Benefits
  • H6 Quick Resources skipped
  • H4 Youth Hub
  • H6 Quick Resources skipped
  • H4 About Us
  • H6 Loan Resources skipped
  • H2 Start with Us, Stay with Us: Leading the Way
  • H2 Financing Dreams, Supporting Goals
  • H4 Promotions skipped
  • H4 Personal Loans
  • H4 Vehicle Loans
  • H4 Mortgage Loans
  • H4 Business Loans
  • H4 Promotions
  • H5 Gift of Light Loan
  • H5 Bago Build Up Loan
  • H5 Match Your Backpay Loan
  • H5 Gift of Light Loan
  • H5 Bago Build Up Loan
  • H5 Match Your Backpay Loan
  • H5 Gift of Light Loan
  • H4 Personal Loans
  • H5 Accelerated Approval Disbursement (AAD) Loan
  • H5 Advance Your Education
  • H5 Annual Expenses Loan
  • H5 Debt Consolidation Loan
  • H5 Education Loan
  • H5 Medical Expenses Loan
  • H5 Vacation Loan
  • H5 Wedding Expenses Loan
  • H4 Vehicle Loans
  • H5 Maxi Taxi Loan
  • H5 Vehicle Insurance Loan
  • H5 Vehicle Loan
  • H4 Mortgage Loans
  • H5 Approved Service Providers
  • H5 Bridge Financing Loan
  • H5 Home Equity Loan
  • H5 Land Purchases Loan
  • H5 Residential Mortgage Loan
  • H4 Business Loans
  • H5 Overdraft Facility loan
  • H5 Start Up Investment Loan
  • H5 Working Capital and Fixed Assets Loan
  • H4 Share Savings Account
  • H4 Deposit Accounts
  • H2 Convenience at Your Fingertips
  • H4 Online Banking skipped
  • H4 Member Experience
  • H4 News Articles
  • H4 Jingle All The Way – Tobago Edition
  • H4 Trinidad – Jingle All The Way
  • H4 Secure your legacy – Estate Planning Webinar
  • H6 About Us skipped
  • H6 Loans
  • H6 Head Office
  • H6 Call Center
  • H6 Newsletter

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

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

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

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

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

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

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

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

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

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

D
Alt Text Quality
Action
9 of 107 images have issues
FIX
9 of 107 images have issues
Critical::
9 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
97 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
107 images 1 good alt text 97 decorative 9 missing
IssueCount
missing9 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
Form Accessibility
Action
7 of 8 controls have issues
FIX
7 of 8 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="type-of-experience" id="dhvc_form_control_type-of-experience">; <input type="text" id="essb_copy_link_field">
Warning::
5 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="full-name" id="dhvc_form_control_full-name">; <input type="tel" name="contact-number" id="dhvc_form_control_contact-number">; <input type="email" name="email" id="dhvc_form_control_email">; <textarea name="comments" id="dhvc_form_control_comments">; <input type="email" name="newsletter-email" id="dhvc_form_control_newsletter-email">
Info::
1 control(s) properly labeled
8 controls
1 labeled
5 placeholder only
2 unlabeled
ControlTypeLabelMethod
stextSearcharia-label
#dhvc_form_control_full-nametext(Full Name)placeholder only
#dhvc_form_control_contact-numbertel(Contact Number)placeholder only
#dhvc_form_control_emailemail(Email Address)placeholder only
#dhvc_form_control_commentstextarea(Comments)placeholder only
#dhvc_form_control_newsletter-emailemail(Email)placeholder only
#dhvc_form_control_type-of-experienceselect(none)none
#essb_copy_link_fieldtext(none)none

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

<select name="type-of-experience" id="dhvc_form_control_type-of-experience">; <input type="text" id="essb_copy_link_field">

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="full-name" id="dhvc_form_control_full-name">; <input type="tel" name="contact-number" id="dhvc_form_control_contact-number">; <input type="email" name="email" id="dhvc_form_control_email">; <textarea name="comments" id="dhvc_form_control_comments">; <input type="email" name="newsletter-email" id="dhvc_form_control_newsletter-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

D
Mobile Keyboard & Autofill
Action
3/4 eligible field(s) missing autocomplete or inputmode
FIX
3/4 eligible field(s) missing autocomplete or inputmode
Warning::
3 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: tel, email.
Got: <input type="tel" name="contact-number" id="dhvc_form_control_contact-number">, <input type="email" name="email" id="dhvc_form_control_email">, <input type="email" name="newsletter-email" id="dhvc_form_control_newsletter-email">
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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #f5f5f5
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 ModePartial Dark Mode
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::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 6 <nav> element(s)
Back to Top
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.
B
Landmark Structure
9 landmarks
REVIEW
9 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
6 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 header NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

C
Tabindex Anti-Patterns
Action
0 positive, 8 -1-on-focusable
REVIEW
0 positive, 8 -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 <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.)
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Start with Us, Stay with Us: Leading the…
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Financing Dreams, Supporting Goals
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Convenience at Your Fingertips
1.61:1
#000000
on
#313131
needs 3.0:1 (large text)
24px · bottom of viewport
title Eastern Credit Union | Member-Owned in T…
1.64:1
#000000
on
#323232
needs 4.5:1 (normal text)
16px · top of page (header area)
span ATMs/Locations
1.64:1
#000000
on
#323232
needs 4.5:1 (normal text)
16px · top of page (header area)
span EPL Properties Ltd
1.47:1
#000000
on
#2C2A28
needs 4.5:1 (normal text)
16px · top of page (header area)
span Become a Member
1.35:1
#000000
on
#28231F
needs 4.5:1 (normal text)
16px · top of page (header area)
span Contact Us
1.29:1
#000000
on
#261F18
needs 4.5:1 (normal text)
16px · above the fold
span Loans
1.36:1
#000000
on
#2A231D
needs 4.5:1 (normal text)
16px · above the fold
span Personal Loan
1.36:1
#000000
on
#2B231C
needs 4.5:1 (normal text)
16px · above the fold
span Accelerated Approval Disbursement Loan
1.29:1
#000000
on
#281E17
needs 4.5:1 (normal text)
16px · above the fold
span Advance Your Education
1.12:1
#000000
on
#1B0F06
needs 4.5:1 (normal text)
16px · above the fold
span Annual Expenses Loan
1.16:1
#000000
on
#231206
needs 4.5:1 (normal text)
16px · above the fold
span Debt Consolidation Loan
1.16:1
#000000
on
#231206
needs 4.5:1 (normal text)
16px · above the fold
span Education Loan
1.21:1
#000000
on
#291607
needs 4.5:1 (normal text)
16px · above the fold
span Medical Expenses Loan
1.22:1
#000000
on
#2B1608
needs 4.5:1 (normal text)
16px · above the fold
span Vacation Loan
1.20:1
#000000
on
#271506
needs 4.5:1 (normal text)
16px · mid-page
span Wedding Expenses Loan
1.22:1
#000000
on
#2A1708
needs 4.5:1 (normal text)
16px · mid-page
span Vehicle Loans
1.25:1
#000000
on
#2D1808
needs 4.5:1 (normal text)
16px · mid-page
span New Vehicle Loan
1.28:1
#000000
on
#301A0A
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Start with Us, Stay …1.61:13.0:1
#000000
#313131
Fail
h2 Financing Dreams, Su…1.61:13.0:1
#000000
#313131
Fail
h2 Convenience at Your …1.61:13.0:1
#000000
#313131
Fail
title Eastern Credit Union…1.64:14.5:1
#000000
#323232
Fail
span ATMs/Locations1.64:14.5:1
#000000
#323232
Fail
span EPL Properties Ltd1.47:14.5:1
#000000
#2C2A28
Fail
span Become a Member1.35:14.5:1
#000000
#28231F
Fail
span Contact Us1.29:14.5:1
#000000
#261F18
Fail
span Loans1.36:14.5:1
#000000
#2A231D
Fail
span Personal Loan1.36:14.5:1
#000000
#2B231C
Fail
span Accelerated Approval…1.29:14.5:1
#000000
#281E17
Fail
span Advance Your Educati…1.12:14.5:1
#000000
#1B0F06
Fail
span Annual Expenses Loan1.16:14.5:1
#000000
#231206
Fail
span Debt Consolidation L…1.16:14.5:1
#000000
#231206
Fail
span Education Loan1.21:14.5:1
#000000
#291607
Fail
span Medical Expenses Loa…1.22:14.5:1
#000000
#2B1608
Fail
span Vacation Loan1.20:14.5:1
#000000
#271506
Fail
span Wedding Expenses Loa…1.22:14.5:1
#000000
#2A1708
Fail
span Vehicle Loans1.25:14.5:1
#000000
#2D1808
Fail
span New Vehicle Loan1.28:14.5:1
#000000
#301A0A
Fail

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 82/100 — 5 failing, 23 passed
REVIEW
82

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Thousand + div.wpb_wrapper > div.stats-block > div#counter-responsv-wrap-5505 > div.counter_suffix
Million + div.wpb_wrapper > div.stats-block > div#counter-responsv-wrap-2398 > div.counter_suffix
Billon + div.wpb_wrapper > div.stats-block > div#counter-responsv-wrap-1866 > div.counter_suffix
Published: 09/28/2026 article.w-grid-item > div.w-grid-item-h > div.w-vwrapper > time.w-post-elm
Published: div.w-grid-item-h > div.w-vwrapper > time.w-post-elm > span.w-post-elm-before
Read More div.w-grid-item-h > div.w-vwrapper > a.w-btn > span.w-btn-label
Published: 10/08/2026 article.w-grid-item > div.w-grid-item-h > div.w-vwrapper > time.w-post-elm
Published: div.w-grid-item-h > div.w-vwrapper > time.w-post-elm > span.w-post-elm-before
Read More div.w-grid-item-h > div.w-vwrapper > a.w-btn > span.w-btn-label
Published: 10/08/2026 article.w-grid-item > div.w-grid-item-h > div.w-vwrapper > time.w-post-elm
Published: div.w-grid-item-h > div.w-vwrapper > time.w-post-elm > span.w-post-elm-before
Read More div.w-grid-item-h > div.w-vwrapper > a.w-btn > span.w-btn-label

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
Promotions div#promotions > div.vc_column-inner > div.wpb_wrapper > h4.vc_custom_heading
Online Banking div.vc_col-sm-6 > div.vc_column-inner > div.wpb_wrapper > h4.vc_custom_heading
About Us div.vc_col-sm-4 > div.vc_column-inner > div.wpb_wrapper > h6.vc_custom_heading

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
div.cp-row > div.col-lg-12 > a > img.entered div.cp-row > div.col-lg-12 > a > img.entered

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Type of Experience Compliment Complaint Suggestion div.wpb_wrapper > div.dhvc-form-group > div.dhvc-form-select > select#dhvc_form_control_type-of-experience

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.cp-modal-body > div.cp-row > div.col-lg-12 > a div.cp-modal-body > div.cp-row > div.col-lg-12 > a

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.

○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
●`[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
●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.
●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
●Identical links have the same purpose.
●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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
A+
Heading Text Quality
All 71 heading(s) have substantive, well-formed text
PASS
All 71 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "s" should use type="search" (currently type="text")
Field name "s" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
8 form control(s) checked, no input-semantic issues
PASS
8 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Iframe Accessibility
All 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
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 Sizes
All 112 visible text node(s) render at >= 12 CSS pixels
PASS
All 112 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback