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 1 REVIEW 7 FIX

Mobile-Readable Font Sizes

Action

67% of visible text renders at >= 12 CSS px (57 below threshold)

FIX

67% of visible text renders at >= 12 CSS px (57 below threshold)

57 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.0px ("Emmanuel Alade"); <a> 11.0px ("Start a Project"); <span> 11.0px ("Brand Strategy · Graphic Design · Websit..."); <span> 11.0px ("Featured Case"); <p> 11.0px ("Website Design · Digital Experience").

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

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.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://emmanuelalade.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://emmanuelalade.com/manifest.json

Manifest contains invalid JSON.

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 ✗

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Back-to-top link detected

1 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 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

Mobile Keyboard & Autofill

Action

1/3 eligible field(s) missing autocomplete or inputmode

REVIEW

1/3 eligible field(s) missing autocomplete or inputmode

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" name="email" id="email">

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

A+

Heading Hierarchy

20 headings

PASS

20 headings

Single H1 present

H1 I build brands and digital experiences people trust.
H2 Property4Naija
H3 Property4Naija
H3 The Red Onion
H3 Aurelia Estates
H3 Nexora Tech Academy
H2 Design is not the decoration.
H2 A practice across five disciplines.
H3 Brand Strategy
H3 Website Design
H3 Digital Experience
H3 Brand Identity
H3 Content Strategy
H2 Think · Build · Refine.
H3 THINK
H3 BUILD
H3 REFINE
H2 Digital Systems.
H2 Designer. Strategist. Builder.
H2 Have something worth building?

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

3 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: 3 all-caps heading(s)

A+

Alt Text Quality

All 13 images OK

PASS

All 13 images OK

13 image(s) with good alt text

13 images 13 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 5 controls labeled

PASS

All 5 controls labeled

5 control(s) properly labeled

5 controls

5 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#name	text	Name	for/id
#email	email	Email	for/id
#service	select	Service	for/id
#budget	select	Budget	for/id
#message	textarea	Project Details	for/id

Link & Button Quality

40 links, 3 buttons — all OK

PASS

40 links, 3 buttons — all OK

3 link(s) open in new tab without warning

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

Got: https://wa.me/2348089165528?text=Hi%20Emmanuel%2C%20I%20found%20your%20portfo…; https://wa.me/2348089165528?text=Hi%20Emmanuel%2C%20I%20found%20your%20portfo…; https://wa.me/2348089165528?text=Hi%20Emmanuel%2C%20I%20found%20your%20portfo…

37 link(s) with descriptive text

40 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://wa.me/2348089165528?text=Hi%20Em…	Chat on WhatsApp	new tab	Add '(opens in new tab)' to text
https://wa.me/2348089165528?text=Hi%20Em…	Chat on WhatsApp	new tab	Add '(opens in new tab)' to text
https://wa.me/2348089165528?text=Hi%20Em…	WhatsApp	new tab	Add '(opens in new tab)' to text

40 links and buttons have descriptive text

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

https://wa.me/2348089165528?text=Hi%20Emmanuel%2C%20I%20found%20your%20portfo…; https://wa.me/2348089165528?text=Hi%20Emmanuel%2C%20I%20found%20your%20portfo…; https://wa.me/2348089165528?text=Hi%20Emmanuel%2C%20I%20found%20your%20portfo…

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

5 form control(s) checked, no type mismatches

PASS

5 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

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

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

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+

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

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 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 I build brands and	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 people trust.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Property4Naija	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Design is not	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 A practice across	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Think	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Build	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Digital	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Designer.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Builder.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Have something	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Property4Naija	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The Red Onion	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Aurelia Estates	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Nexora Tech Academy	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Brand Strategy	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Website Design	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Digital Experience	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Brand Identity	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Content Strategy	21.00:1	3.0: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 Audits

Score 96/100 — 2 failing, 21 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
EMMANUEL ALADE `div.grid > div.col-span-12 > a.inline-flex > span.font-sans`
NAVIGATE `div.section-padding > div.grid > div.col-span-6 > p.eyebrow`
CONNECT `div.section-padding > div.grid > div.col-span-6 > p.eyebrow`
IBADAN — WORKING GLOBALLY `div.section-padding > div.flex > div.flex > span.eyebrow`
© 2026 Emmanuel Alade. All rights reserved. `div.section-padding > div.flex > div.flex > p.font-sans`

These are opportunities to improve the legibility of your content.

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
FEATURED CASE 01 / 04 WEBSITE DESIGN · DIGITAL EXPERIENCE Property4Naija VIEW… `div.section-padding > div.grid > aside.col-span-12 > a.group`
EMMANUEL ALADE `div.section-padding > div.grid > div.col-span-12 > a.inline-flex`

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

●Select elements have associated label elements.

●ARIA attributes are used as specified for the element's role

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Image elements do not have `[alt]` attributes that are redundant text.

○`[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-hidden="true"]` elements do not contain focusable descendents

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

○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

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