Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 1 REVIEW 5 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Favicon & Branding

Action

8 icon(s) detected

FIX

8 icon(s) detected

favicon.ico present at site root

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

Multiple icon sizes detected

✓ favicon.ico Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Loans that change lives | Kiva ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

A+

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

H1 403 Forbidden

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

No links or buttons

PASS

No links or buttons

No links or buttons on this page

0 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Kiva.org

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Kiva.org ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Kiva.org Display Mode standalone Icons 7 icon(s)

A+

Color Contrast (Screenshot)

2 text elements analyzed, 0 fail WCAG AA

PASS

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

2 pass

Show all checked elements (2)

Element	Ratio	Required	FG	BG	Result
h1 403 Forbidden	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title 403 Forbidden	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.

Lighthouse Accessibility Audits

Score 91/100 — 4 failing, 22 passed

PASS

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
Support someone for Earth Day and earn your limited-edition badge! `div.tw-flex > span > a.tw-text-white > span`
earn your limited-edition badge! `span > a.tw-text-white > span > u`
Lending through Kiva involves risk of principal loss. Kiva does not guarantee r… `div.tw-mx-auto > nav.tw-block > div > p.tw-text-small`

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
Help people threatened by climate change. `div.tw-grid > div.tw-col-span-12 > div.rich-text-content > h3`
$50 to go! `a.loan-card-progress > figure#loanProgress > div > h4.tw-lowercase`
OUR COMMUNITY IMPACT `div.tw-mx-auto > div.tw-grid > div.rich-text-content > h4`
MULTIPLY YOUR IMPACT `div.tw-grid > div.tw-col-span-12 > div.rich-text-content > h4`
POWERED BY PAYPAL `div.tw-mx-auto > div.tw-grid > div.rich-text-content > h4`

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Almost funded `div.tw-flex > div.tw-grow > div.loan-card-active-hover > a.tw-flex`
Almost funded `div.tw-flex > div.tw-grow > div.loan-card-active-hover > a.tw-flex`
Almost funded `div.tw-flex > div.tw-grow > div.loan-card-active-hover > a.tw-flex`
Almost funded `div.tw-flex > div.tw-grow > div.loan-card-active-hover > a.tw-flex`
Privacy policy `div.tw-my-3 > ul.tw-mb-2 > li.tw-inline-block > a.tw-whitespace-nowrap`

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
Philippines `div.tw-grow > div.loan-card-active-hover > div.tw-relative > a.tw-flex`
Almost funded `div.tw-flex > div.tw-grow > div.loan-card-active-hover > a.tw-flex`
$275 helps Maria Elvisa to buy detergent soap, fabric softener, bleach and othe… `div.tw-flex > div.tw-grow > div.loan-card-active-hover > a.loan-card-use`
$50 to go! `div.tw-flex > div.tw-flex > div > a.loan-card-progress`
Paraguay `div.tw-grow > div.loan-card-active-hover > div.tw-relative > a.tw-flex`
Almost funded `div.tw-flex > div.tw-grow > div.loan-card-active-hover > a.tw-flex`
$2,450 helps a member of Kuña Marangatu Group to buy fabric and supplies for he… `div.tw-flex > div.tw-grow > div.loan-card-active-hover > a.loan-card-use`
$95 to go! `div.tw-flex > div.tw-flex > div > a.loan-card-progress`
Philippines `div.tw-grow > div.loan-card-active-hover > div.tw-relative > a.tw-flex`
Almost funded `div.tw-flex > div.tw-grow > div.loan-card-active-hover > a.tw-flex`
$525 helps Rosalie to buy additional items like canned goods, chips, personal c… `div.tw-flex > div.tw-grow > div.loan-card-active-hover > a.loan-card-use`
$75 to go! `div.tw-flex > div.tw-flex > div > a.loan-card-progress`
Philippines `div.tw-grow > div.loan-card-active-hover > div.tw-relative > a.tw-flex`
Almost funded `div.tw-flex > div.tw-grow > div.loan-card-active-hover > a.tw-flex`
$275 helps Ruby Lyn to purchase ingredients for her food production business. `div.tw-flex > div.tw-grow > div.loan-card-active-hover > a.loan-card-use`
$75 to go! `div.tw-flex > div.tw-flex > div > a.loan-card-progress`
Ecuador `div.tw-grow > div.loan-card-active-hover > div.tw-relative > a.tw-flex`
$1,650 helps Maria De Los Angeles to buy trousers, shirts, blouses, children's … `div.tw-flex > div.tw-grow > div.loan-card-active-hover > a.loan-card-use`
$100 to go `div.tw-flex > div.tw-flex > div > a.loan-card-progress`
Philippines `div.tw-grow > div.loan-card-active-hover > div.tw-relative > a.tw-flex`
$675 helps Virginia to buy additional kilos of meat to sell. `div.tw-flex > div.tw-grow > div.loan-card-active-hover > a.loan-card-use`
$100 to go `div.tw-flex > div.tw-flex > div > a.loan-card-progress`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●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

●ARIA `progressbar` elements have accessible names

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[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

○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

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

○Identical links have the same purpose.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.