Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 4 REVIEW 5 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" id="emailInput">

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" id="emailInput">

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

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://portfolio.nabdz.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://portfolio.nabdz.com/manifest.json

Manifest contains invalid JSON.

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.

Mobile-Readable Font Sizes

Action

76% of visible text renders at >= 12 CSS px (19 below threshold)

REVIEW

76% of visible text renders at >= 12 CSS px (19 below threshold)

19 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 ("Branding • Social Media"); <span> 11.8px ("Print • UI/UX"); <span> 11.8px ("Modern Websites"); <span> 11.8px ("& Web Apps"); <span> 11.8px ("Smart • Intuitive").

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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: 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: #06090a

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 dark ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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 Immocastle Website

1.05:1

#000000

#05090A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Let’s create

1.05:1

#000000

#05090A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 something

1.05:1

#000000

#05090A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 together.

1.05:1

#000000

#05090A

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Send me a

1.05:1

#000000

#05090A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Got a project

1.05:1

#000000

#05090A

needs 3.0:1 (large text)

19px · bottom of viewport

title Mial Zakaria — Creative Designer & Dev…

1.05:1

#000000

#06090A

needs 4.5:1 (normal text)

16px · top of page (header area)

span Mial Zakaria

1.05:1

#000000

#06090A

needs 4.5:1 (normal text)

16px · top of page (header area)

span HOME

1.09:1

#000000

#0C0F10

needs 4.5:1 (normal text)

16px · top of page (header area)

span PROJECTS

1.05:1

#000000

#06090A

needs 4.5:1 (normal text)

16px · top of page (header area)

span CONTACT

1.05:1

#000000

#06090A

needs 4.5:1 (normal text)

16px · above the fold

span LET'S TALK

1.05:1

#000000

#06090A

needs 4.5:1 (normal text)

16px · above the fold

span ▶

1.05:1

#000000

#06090A

needs 4.5:1 (normal text)

16px · above the fold

span CREATIVE DESIGNER & DEVELOPER

1.05:1

#000000

#06090A

needs 4.5:1 (normal text)

16px · above the fold

span Ideas into

1.05:1

#000000

#06090A

needs 4.5:1 (normal text)

16px · above the fold

span stunning

1.05:1

#000000

#06090A

needs 4.5:1 (normal text)

16px · above the fold

span digital experiences.

1.05:1

#000000

#06090A

needs 4.5:1 (normal text)

16px · above the fold

p I'm Mial Zakaria, a

1.05:1

#000000

#06090A

needs 4.5:1 (normal text)

16px · above the fold

strong graphic designer

1.05:1

#000000

#06090A

needs 3.0:1 (large text)

16px · above the fold

strong web developer

1.08:1

#000000

#0B0E0F

needs 3.0:1 (large text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Immocastle Website	1.05:1	3.0:1	#000000	#05090A	Fail
h2 Let’s create	1.05:1	3.0:1	#000000	#05090A	Fail
h2 something	1.05:1	3.0:1	#000000	#05090A	Fail
h2 together.	1.05:1	3.0:1	#000000	#05090A	Fail
h3 Send me a	1.05:1	3.0:1	#000000	#05090A	Fail
h3 Got a project	1.05:1	3.0:1	#000000	#05090A	Fail
title Mial Zakaria — Cre…	1.05:1	4.5:1	#000000	#06090A	Fail
span Mial Zakaria	1.05:1	4.5:1	#000000	#06090A	Fail
span HOME	1.09:1	4.5:1	#000000	#0C0F10	Fail
span PROJECTS	1.05:1	4.5:1	#000000	#06090A	Fail
span CONTACT	1.05:1	4.5:1	#000000	#06090A	Fail
span LET'S TALK	1.05:1	4.5:1	#000000	#06090A	Fail
span ▶	1.05:1	4.5:1	#000000	#06090A	Fail
span CREATIVE DESIGNER & …	1.05:1	4.5:1	#000000	#06090A	Fail
span Ideas into	1.05:1	4.5:1	#000000	#06090A	Fail
span stunning	1.05:1	4.5:1	#000000	#06090A	Fail
span digital experiences.	1.05:1	4.5:1	#000000	#06090A	Fail
p I'm Mial Zakaria, a	1.05:1	4.5:1	#000000	#06090A	Fail
strong graphic designer	1.05:1	3.0:1	#000000	#06090A	Fail
strong web developer	1.08:1	3.0:1	#000000	#0B0E0F	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.

Landmark Structure

9 landmarks

PASS

9 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

5 headings

PASS

5 headings

Single H1 present

H1 Ideas into stunning digital experiences.
H2 Immocastle Website
H2 Let’s create something amazingtogether.
H3 Send me a message
H3 Got a project in mind?

A+

Heading Text Quality

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

PASS

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

1 decorative image(s) correctly marked

6 image(s) with good alt text

7 images 6 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 4 controls labeled

PASS

All 4 controls labeled

4 control(s) properly labeled

4 controls

4 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#nameInput	text	Full Name *	for/id
#emailInput	email	Email Address *	for/id
#projectTypeSelect	select	Project Type *	for/id
#messageTextarea	textarea	Your Message *	for/id

Link & Button Quality

21 links, 13 buttons — all OK

PASS

21 links, 13 buttons — all OK

6 link(s) open in new tab without warning

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

Got: https://wa.me/213541282731; /sitemap.xml; https://linkedin.com; https://instagram.com; https://github.com; https://x.com

15 link(s) with descriptive text

21 links

0 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://wa.me/213541282731	+213 541 28 27 31 Call or What…	new tab	Add '(opens in new tab)' to text
/sitemap.xml	SITEMAP	new tab	Add '(opens in new tab)' to text
https://linkedin.com	LinkedIn	new tab	Add '(opens in new tab)' to text
https://instagram.com	Instagram	new tab	Add '(opens in new tab)' to text
https://github.com	GitHub	new tab	Add '(opens in new tab)' to text
https://x.com	X (Twitter)	new tab	Add '(opens in new tab)' to text

28 links and buttons have descriptive text

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

https://wa.me/213541282731; /sitemap.xml; https://linkedin.com; https://instagram.com; https://github.com; https://x.com

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

4 form control(s) checked, no type mismatches

PASS

4 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

4 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

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

tabindex="-1" on naturally-focusable <input id="contact-bot-field">

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+

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

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+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 23 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
OR REACH OUT DIRECTLY `div.contact-form-card > div.direct-reach-wrapper > div.direct-divider > span.svelte-wt4tt0`

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

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

●Select elements have associated label elements.

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

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

○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

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