Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 2 REVIEW 6 FIX

Mobile Keyboard & Autofill

Action

2/2 eligible field(s) missing autocomplete or inputmode

FIX

2/2 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email">

1 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: email.

Got: <input type="email">

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-l14sft

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://aoa-togo.org/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://aoa-togo.org/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #3a6b1a

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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Landmark Structure

6 landmarks

REVIEW

6 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

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

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

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

Favicon & Branding

5 icon(s) detected

REVIEW

5 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 Missing

✓ Multiple Sizes Present

A+

Heading Hierarchy

11 headings

PASS

11 headings

Single H1 present

H1 Offrir un avenir digne aux enfants du Togo
H2 Notre impact en chiffres
H2 Nos trois piliers
H3 Orphelinat
H3 École
H3 Formation Professionnelle
H2 Vous aussi, pouvez faire la différence
H2 Actualités récentes
H3 Navigation
H3 Partenaire fondateur
H3 Restez informé(e)

A+

Heading Text Quality

All 11 heading(s) have substantive, well-formed text

PASS

All 11 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

7 image(s) with good alt text

7 images 7 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
input	email	Votre adresse email	aria-label

Link & Button Quality

33 links, 3 buttons — all OK

PASS

33 links, 3 buttons — all OK

7 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://maps.app.goo.gl/htX4iEtq6dGJHQ4v5; https://wa.me/22890071771; https://www.facebook.com/share/1B85zCgsMm/; https://wa.me/22890071771; https://www.instagram.com/aoa.togo/; https://www.linkedin.com/company/aoa-togo; https://aoa-france.org

26 link(s) with descriptive text

33 links

0 empty

0 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://maps.app.goo.gl/htX4iEtq6dGJHQ4v…	Dalavé, quartier Xévé, Rue …	new tab	Add '(opens in new tab)' to text
https://wa.me/22890071771	+228 90 07 17 71	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/share/1B85zCgsM…	Facebook AOA-Togo	new tab	Add '(opens in new tab)' to text
https://wa.me/22890071771	WhatsApp AOA-Togo	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/aoa.togo/	Instagram AOA-Togo	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/aoa-tog…	LinkedIn AOA-Togo	new tab	Add '(opens in new tab)' to text
https://aoa-france.org	Visiter le site AOA-France (no…	new tab	Add '(opens in new tab)' to text

29 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://maps.app.goo.gl/htX4iEtq6dGJHQ4v5; https://wa.me/22890071771; https://www.facebook.com/share/1B85zCgsMm/; https://wa.me/22890071771; https://www.instagram.com/aoa.togo/; https://www.linkedin.com/company/aoa-togo; https://aoa-france.org

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

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

1 form control(s) checked, no input-semantic issues

PASS

1 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Document Language

Lang attribute set to "fr"

PASS

Lang attribute set to "fr"

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

Got: fr

A+

Tabindex Anti-Patterns

5 explicit tabindex attribute(s) checked, no anti-patterns

PASS

5 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 73 visible text node(s) render at >= 12 CSS pixels

PASS

All 73 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

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

A+

Color Contrast (Screenshot)

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Offrir un avenir dig…	20.17:1	3.0:1	#000000	#FDFAF5	Pass
h2 Notre impact en chif…	20.17:1	3.0:1	#000000	#FDFAF5	Pass
h2 Nos trois piliers	20.17:1	3.0:1	#000000	#FDFAF5	Pass
h2 Vous aussi, pouvez f…	17.04:1	3.0:1	#000000	#F5E6C8	Pass
h2 Actualités récente…	17.04:1	3.0:1	#000000	#F5E6C8	Pass
h3 Orphelinat	20.17:1	3.0:1	#000000	#FDFAF5	Pass
h3 École	20.17:1	3.0:1	#000000	#FDFAF5	Pass
h3 Formation Profession…	17.04:1	3.0:1	#000000	#F5E6C8	Pass
h3 Navigation	17.04:1	3.0:1	#000000	#F5E6C8	Pass
h3 Partenaire fondateur	17.04:1	3.0:1	#000000	#F5E6C8	Pass
h3 Restez informé(e)	17.04:1	3.0:1	#000000	#F5E6C8	Pass
title AOA-Togo ~ Apprentis…	20.17:1	4.5:1	#000000	#FDFAF5	Pass
p Apprentis-Orphelins …	20.17:1	4.5:1	#000000	#FDFAF5	Pass
a Accueil	20.17:1	4.5:1	#000000	#FDFAF5	Pass
a Qui sommes-nous ?	20.17:1	4.5:1	#000000	#FDFAF5	Pass
a Nos actions	20.17:1	4.5:1	#000000	#FDFAF5	Pass
a Impact & Transparenc…	20.17:1	4.5:1	#000000	#FDFAF5	Pass
a Actualités	20.17:1	4.5:1	#000000	#FDFAF5	Pass
a Contact	20.17:1	4.5:1	#000000	#FDFAF5	Pass
a Faire un don	20.17:1	4.5:1	#000000	#FDFAF5	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 Audits

Score 96/100 — 1 failing, 20 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
Faire un don `div.max-w-6xl > div > div.flex > a.px-6`
Venir en visite `div.max-w-6xl > div > div.flex > a.px-6`
Voir tous les articles `section.py-16 > div.max-w-6xl > div.text-center > a.inline-flex`
© 2026 Apprentis-Orphelins d'Afrique — AOA-Togo. Tous droits réservés. `div#root > footer.relative > div.max-w-5xl > p.text-xs`
Mentions légales `footer.relative > div.max-w-5xl > div.flex > a.text-xs`
Contact `footer.relative > div.max-w-5xl > div.flex > a.text-xs`
Politique de confidentialité `footer.relative > div.max-w-5xl > div.flex > a.text-xs`

These are opportunities to improve the legibility of your content.

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

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

●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

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

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

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

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

○Elements with visible text labels have matching accessible names.

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