Accessibility

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

5 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 5 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

B

Tap Target Adequacy

3 tap target(s) too small or too close together

REVIEW

3 tap target(s) too small or too close together

3 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

B

Mobile-Readable Font Sizes

98% of visible text renders at >= 12 CSS px (3 below threshold)

REVIEW

98% of visible text renders at >= 12 CSS px (3 below threshold)

3 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.8px ("Company"); <span> 11.8px ("Products"); <span> 11.8px ("Legal & trust").

B

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found | Kingdom Impact Ventures ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

B

Favicon & Branding

14 icon(s) detected

REVIEW

14 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

B

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: light dark

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: #1f1a12

Detection limited to meta tags and inline styles

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

Dark Mode✓ Dark Mode Supported

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

Detection limited to meta tags and inline styles.

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

h1 Kingdom Impact Ventures - KCAN, KIV, KIS…

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

32px · bottom of viewport

h2 KIS

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What Kingdom Impact Ventures is

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The product: Kingdom Impact Social

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

24px · bottom of viewport

h2 One trusted app for community, private m…

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How the organisation fits together

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Public hierarchy

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Venture portfolio

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Who the ecosystem is designed to serve

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Launch discipline

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Portfolio sequence

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Production readiness

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Need to reach KIV?

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Social connection

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Broadcast publishing

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Partner spaces

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Bible & study workflows

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

19px · bottom of viewport

h3 KCAN

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

19px · bottom of viewport

h3 KIV

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

19px · bottom of viewport

h3 KIS

1.09:1

#000000

on

#120D08

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Kingdom Impact Ventu…	1.09:1	3.0:1	#000000	#120D08	Fail
h2 KIS	1.09:1	3.0:1	#000000	#120D08	Fail
h2 What Kingdom Impact …	1.09:1	3.0:1	#000000	#120D08	Fail
h2 The product: Kingdom…	1.09:1	3.0:1	#000000	#120D08	Fail
h2 One trusted app for …	1.09:1	3.0:1	#000000	#120D08	Fail
h2 How the organisation…	1.09:1	3.0:1	#000000	#120D08	Fail
h2 Public hierarchy	1.09:1	3.0:1	#000000	#120D08	Fail
h2 Venture portfolio	1.09:1	3.0:1	#000000	#120D08	Fail
h2 Who the ecosystem is…	1.09:1	3.0:1	#000000	#120D08	Fail
h2 Launch discipline	1.09:1	3.0:1	#000000	#120D08	Fail
h2 Portfolio sequence	1.09:1	3.0:1	#000000	#120D08	Fail
h2 Production readiness	1.09:1	3.0:1	#000000	#120D08	Fail
h2 Need to reach KIV?	1.09:1	3.0:1	#000000	#120D08	Fail
h3 Social connection	1.09:1	3.0:1	#000000	#120D08	Fail
h3 Broadcast publishing	1.09:1	3.0:1	#000000	#120D08	Fail
h3 Partner spaces	1.09:1	3.0:1	#000000	#120D08	Fail
h3 Bible & study workfl…	1.09:1	3.0:1	#000000	#120D08	Fail
h3 KCAN	1.09:1	3.0:1	#000000	#120D08	Fail
h3 KIV	1.09:1	3.0:1	#000000	#120D08	Fail
h3 KIS	1.09:1	3.0:1	#000000	#120D08	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.

A+

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

5 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

47 headings

PASS

47 headings

Single H1 present

H1 Kingdom Impact Ventures - KCAN, KIV, KIS and our product portfolio
H2 KIS
H2 What Kingdom Impact Ventures is
H2 The product: Kingdom Impact Social
H2 One trusted app for community, private messaging, Bible study and partner spaces.
H3 Social connection
H3 Broadcast publishing
H3 Partner spaces
H3 Bible & study workflows
H2 How the organisation fits together
H3 KCAN
H3 KIV
H3 KIS
H3 Future ventures
H2 Public hierarchy
H3 KCAN
H3 KIV
H3 KIS
H2 Venture portfolio
H3 Kingdom Impact Social
H3 Kingdom Impact Education
H3 Kingdom Impact Market
H3 Kingdom Impact Payments
H3 Kingdom Impact Health
H2 Who the ecosystem is designed to serve
H3 Individuals and families
H3 Churches and ministries
H3 Creators and teachers
H3 Schools and training partners
H3 Marketplace and service partners
H3 Care and support partners
H2 Launch discipline
H3 1. Define the real workflow
H3 2. Confirm safety and governance
H3 3. Configure availability
H3 4. Gather evidence
H3 5. Publish carefully
H2 Portfolio sequence
H3 Phase 1: KIS foundation
H3 Phase 2: Education pathways
H3 Phase 3: Market and payments
H3 Phase 4: Health-support coordination
H2 Production readiness
H3 Trust and safety
H3 Responsible forms
H3 Deployment handoff
H2 Need to reach KIV?

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

2 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 2 all-caps heading(s)

A+

Alt Text Quality

All 24 images OK

PASS

All 24 images OK

1 image(s) with alt text over 125 characters

14 decorative image(s) correctly marked

9 image(s) with good alt text

24 images 9 good alt text 14 decorative

Issue	Count
too long	1 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

79 links, 12 buttons — all OK

PASS

79 links, 12 buttons — all OK

79 link(s) with descriptive text

79 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

91 links and buttons have descriptive text

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A

Tabindex Anti-Patterns

0 positive, 2 -1-on-focusable

PASS

0 positive, 2 -1-on-focusable

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

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

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Kingdom Impact Ventures

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Kingdom Impact Ventures ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Kingdom Impact Ventures Display Mode standalone Theme Color #1f1a12 Background Color #fffdf7 Icons 5 icon(s)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /print.css

Print Stylesheet ✓ Print Optimized

Print stylesheet /print.css ✓Inline @media print Not detected ✗

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

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.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

A+

Lighthouse Accessibility Audits

Score 97/100 — 1 failing, 27 passed

PASS

97

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.

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
Show KIM `div.product-carousel > div.product-carousel-controls > div.product-carousel-dots > button`
Show KIP `div.product-carousel > div.product-carousel-controls > div.product-carousel-dots > button`
Show KIH `div.product-carousel > div.product-carousel-controls > div.product-carousel-dots > button`

These items highlight common accessibility best practices.

○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

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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links 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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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 the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

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

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