https://arshad-developer-portfolio.netlify.app

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

Mobile Keyboard & Autofill

Action

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

FIX

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

2 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: name, email.

Got: <input type="text" name="name" id="name">, <input type="email" name="email" id="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" name="email" id="email">

Mobile-Readable Font Sizes

Action

59% of visible text renders at >= 12 CSS px (93 below threshold)

FIX

59% of visible text renders at >= 12 CSS px (93 below threshold)

93 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> 10.9px ("Status"); <span> 10.9px ("arshad --profile"); <span> 11.8px ("role"); <span> 11.8px ("\"Aspiring Backend Developer\""); <span> 11.8px ("stack").

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

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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: #0a0a0b

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.

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

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

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 Backend

1.06:1

#000000

#0A0A0B

needs 3.0:1 (large text)

32px · mid-page

h1 systems,

1.06:1

#000000

#0A0A0B

needs 3.0:1 (large text)

32px · mid-page

h2 About

1.06:1

#000000

#0A0A0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Work

1.06:1

#000000

#0A0A0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Stack

1.06:1

#000000

#0A0A0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Experience

1.06:1

#000000

#0A0A0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Got a system

1.06:1

#000000

#0A0A0B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 that needs

1.06:1

#000000

#0A0A0B

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Real-time Enterprise Messaging Engine

1.06:1

#000000

#0A0A0B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Hospital Management System

1.06:1

#000000

#0A0A0B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Languages

1.06:1

#000000

#0A0A0B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Backend

1.06:1

#000000

#0A0A0B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 GenAI & RAG

1.06:1

#000000

#0A0A0B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Databases

1.06:1

#000000

#0A0A0B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Architecture

1.06:1

#000000

#0A0A0B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Tools & DevOps

1.06:1

#000000

#0A0A0B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Testing

1.06:1

#000000

#0A0A0B

needs 3.0:1 (large text)

19px · bottom of viewport

title Arshad — Backend Engineer

1.13:1

#000000

#16120D

needs 4.5:1 (normal text)

16px · top of page (header area)

span Arshad

1.12:1

#000000

#15120D

needs 4.5:1 (normal text)

16px · top of page (header area)

a About

1.12:1

#000000

#15110D

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Backend	1.06:1	3.0:1	#000000	#0A0A0B	Fail
h1 systems,	1.06:1	3.0:1	#000000	#0A0A0B	Fail
h2 About	1.06:1	3.0:1	#000000	#0A0A0B	Fail
h2 Work	1.06:1	3.0:1	#000000	#0A0A0B	Fail
h2 Stack	1.06:1	3.0:1	#000000	#0A0A0B	Fail
h2 Experience	1.06:1	3.0:1	#000000	#0A0A0B	Fail
h2 Got a system	1.06:1	3.0:1	#000000	#0A0A0B	Fail
h2 that needs	1.06:1	3.0:1	#000000	#0A0A0B	Fail
h3 Real-time Enterprise…	1.06:1	3.0:1	#000000	#0A0A0B	Fail
h3 Hospital Management …	1.06:1	3.0:1	#000000	#0A0A0B	Fail
h3 Languages	1.06:1	3.0:1	#000000	#0A0A0B	Fail
h3 Backend	1.06:1	3.0:1	#000000	#0A0A0B	Fail
h3 GenAI & RAG	1.06:1	3.0:1	#000000	#0A0A0B	Fail
h3 Databases	1.06:1	3.0:1	#000000	#0A0A0B	Fail
h3 Architecture	1.06:1	3.0:1	#000000	#0A0A0B	Fail
h3 Tools & DevOps	1.06:1	3.0:1	#000000	#0A0A0B	Fail
h3 Testing	1.06:1	3.0:1	#000000	#0A0A0B	Fail
title Arshad — Backend E…	1.13:1	4.5:1	#000000	#16120D	Fail
span Arshad	1.12:1	4.5:1	#000000	#15120D	Fail
a About	1.12:1	4.5:1	#000000	#15110D	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

6 landmarks

PASS

6 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

15 headings

PASS

15 headings

Single H1 present

H1 Backendsystems,shipped.
H2 About
H2 Work
H3 Real-time Enterprise Messaging Engine
H3 Hospital Management System
H2 Stack
H3 Languages
H3 Backend
H3 GenAI & RAG
H3 Databases
H3 Architecture
H3 Tools & DevOps
H3 Testing
H2 Experience
H2 Got a systemthat needsbuilding?

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

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
#name	text	Name	for/id
#email	email	Email	for/id
#subject	text	Subject	for/id
#message	textarea	Message	for/id

Link & Button Quality

31 links, 2 buttons — all OK

PASS

31 links, 2 buttons — all OK

16 link(s) open in new tab without warning

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

Got: assets/Arshad_Resume_Backend_SDE.pdf; https://github.com/kentakaa; https://www.linkedin.com/in/arshaddev01/; assets/Arshad_Resume_Backend_SDE.pdf; https://github.com/kentakaa; https://www.linkedin.com/in/arshaddev01/; assets/Arshad_Resume_Backend_SDE.pdf; https://chat-application-hvp1.onrender.com; https://chat-application-hvp1.onrender.com; https://github.com/kentakaa/Chat-application (+6 more)

15 link(s) with descriptive text

31 links

0 empty

0 generic text

16 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
assets/Arshad_Resume_Backend_SDE.pdf	Résumé	new tab	Add '(opens in new tab)' to text
https://github.com/kentakaa	GitHub	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/arshaddev01/	LinkedIn	new tab	Add '(opens in new tab)' to text
assets/Arshad_Resume_Backend_SDE.pdf	View Résumé →	new tab	Add '(opens in new tab)' to text
https://github.com/kentakaa	GitHub →	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/arshaddev01/	LinkedIn →	new tab	Add '(opens in new tab)' to text
assets/Arshad_Resume_Backend_SDE.pdf	View résumé	new tab	Add '(opens in new tab)' to text
https://chat-application-hvp1.onrender.c…	Live demo of real-time messagi…	new tab	Add '(opens in new tab)' to text
https://chat-application-hvp1.onrender.c…	Live demo	new tab	Add '(opens in new tab)' to text
https://github.com/kentakaa/Chat-applica…	Source	new tab	Add '(opens in new tab)' to text
http://hopital-management-system-arshad.…	Live demo	new tab	Add '(opens in new tab)' to text
https://github.com/kentakaa/hospital-man…	Source	new tab	Add '(opens in new tab)' to text
http://hopital-management-system-arshad.…	Live demo of hospital manageme…	new tab	Add '(opens in new tab)' to text
https://github.com/kentakaa	GitHub	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/arshaddev01/	LinkedIn	new tab	Add '(opens in new tab)' to text
assets/Arshad_Resume_Backend_SDE.pdf	Résumé PDF	new tab	Add '(opens in new tab)' to text

17 links and buttons have descriptive text

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

assets/Arshad_Resume_Backend_SDE.pdf; https://github.com/kentakaa; https://www.linkedin.com/in/arshaddev01/; assets/Arshad_Resume_Backend_SDE.pdf; https://github.com/kentakaa; https://www.linkedin.com/in/arshaddev01/; assets/Arshad_Resume_Backend_SDE.pdf; https://chat-application-hvp1.onrender.com; https://chat-application-hvp1.onrender.com; https://github.com/kentakaa/Chat-application (+6 more)

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

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

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.

Lighthouse Accessibility Audits

Score 91/100 — 3 failing, 19 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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
About Work Stack Experience Contact View Résumé → GitHub → LinkedIn → `body > div#menu`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
STATUS `div.hero__grid > div.hero__bento > div.bento > span.bento__label`
arshad --profile `div.bento > div.term > div.term__bar > span.term__title`
FEATURED — LIVE - SHIPING UPDATES `div.hero__grid > div.hero__bento > a.bento > span.bento__label`
© 2026 Arshad `body > footer.footer > div.footer__inner > span`
Built end-to-end · deployed to production `body > footer.footer > div.footer__inner > span.footer__mid`
Back to top ↑ `body > footer.footer > div.footer__inner > a.footer__top`

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
A Arshad `body > header#nav > div.nav__inner > a.nav__logo`

○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

●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

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

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

○Image elements have `[alt]` attributes

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

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