Accessibility

F

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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 Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

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.

D

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.

D

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 ✗

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

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

C

Heading Hierarchy

Action

68 headings, 2 skip(s)

REVIEW

68 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 HASEEB UR REHMAN
H2 WHO I AM
H3 // STUDENT DOSSIER
H2 ACADEMIC PATH
H3 BS Software Engineering
H3 AI For Everyone — Skills of Tomorrow
H3 F.Sc Pre-Engineering
H3 Matriculation — Science
H3 3-Year Computer Diploma
H2 AREAS OF INTEREST
H3 Software Engineering
H3 Artificial Intelligence
H3 Cybersecurity
H3 Computer Technology
H3 Programming
H3 Digital Tools
H3 AI Tools
H3 Technology Research
H3 Intelligence Studies
H3 Computer Systems
H3 Digital Innovation
H3 Technology Education
H2 INTELLIGENCE BLACK SQUAD
H3 INTELLIGENCE BLACK SQUAD
H4 // WHAT IT IS — AND WHAT IT IS NOT
H2 SARDAR AK
H3 Personal Technology & Intelligence Identity
H2 MY VISION
H2 WHAT GUIDES ME
H3 LOYALTY
H3 DISCIPLINE
H3 TECHNOLOGY
H3 KNOWLEDGE
H3 PEACE
H3 SERVICE
H2 INTERESTS & RESEARCH
H4 Artificial Intelligence skipped
H4 Cybersecurity
H4 Software Engineering
H4 Digital Intelligence
H4 Technology Research
H4 AI Tools
H4 Computer Systems
H4 Digital Investigation Concepts
H4 Emerging Technologies
H4 Intelligence Studies
H2 THE WRITING PROJECT
H4 BLACKPSYCHOLOGY skipped
H3 BLACK PSYCHOLOGY / BLACK PROTOCOL
H2 PEOPLE WHO INSPIRE MY JOURNEY
H3 Sarmad Saleem Akram
H3 Afrasiyab Hundal
H3 AK
H2 MY FUTURE
H3 Build Skills
H3 Give Back
H3 Earn It
H2 PROJECT ARCHIVE
H3 School Management System
H3 C++ Programming Projects
H3 Artificial Intelligence Learning Projects
H3 Cybersecurity Learning & Research
H3 Digital Technology Projects
H3 Intelligence Black Squad
H2 GET IN TOUCH
H3 Haseeb Ur Rehman
H3 Send a Message
H3 (empty)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

C

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="f-email">

C

Mobile-Readable Font Sizes

Action

70% of visible text renders at >= 12 CSS px (116 below threshold)

REVIEW

70% of visible text renders at >= 12 CSS px (116 below threshold)

116 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.5px ("PORTFOLIO —"); <b> 11.5px ("ABBOTTABAD · KPK · PAKISTAN"); <span> 11.5px ("// DIGITAL IDENTITY —"); <span> 10.6px ("BSSE — 3rd SEMESTER"); <span> 10.6px ("AUST ABBOTTABAD").

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 Site not found · GitHub Pages ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

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 HASEEB UR REHMAN

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

32px · mid-page

h2 WHO I

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

24px · bottom of viewport

h2 ACADEMIC

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

24px · bottom of viewport

h2 AREAS OF

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

24px · bottom of viewport

h2 INTELLIGENCE

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

24px · bottom of viewport

h2 SARDAR

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

24px · bottom of viewport

h2 WHAT

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

24px · bottom of viewport

h2 INTERESTS &

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

24px · bottom of viewport

h2 THE

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

24px · bottom of viewport

h2 PEOPLE WHO

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

24px · bottom of viewport

h2 PROJECT

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

24px · bottom of viewport

h2 GET IN

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

24px · bottom of viewport

h3 // STUDENT DOSSIER

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

19px · bottom of viewport

h3 BS Software Engineering

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

19px · bottom of viewport

h3 AI For Everyone — Skills of Tomorrow

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

19px · bottom of viewport

h3 F.Sc Pre-Engineering

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Matriculation — Science

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

19px · bottom of viewport

h3 3-Year Computer Diploma

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Software Engineering

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Artificial Intelligence

1.03:1

#000000

on

#050507

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 HASEEB UR REHMAN	1.03:1	3.0:1	#000000	#050507	Fail
h2 WHO I	1.03:1	3.0:1	#000000	#050507	Fail
h2 ACADEMIC	1.03:1	3.0:1	#000000	#050507	Fail
h2 AREAS OF	1.03:1	3.0:1	#000000	#050507	Fail
h2 INTELLIGENCE	1.03:1	3.0:1	#000000	#050507	Fail
h2 SARDAR	1.03:1	3.0:1	#000000	#050507	Fail
h2 WHAT	1.03:1	3.0:1	#000000	#050507	Fail
h2 INTERESTS &	1.03:1	3.0:1	#000000	#050507	Fail
h2 THE	1.03:1	3.0:1	#000000	#050507	Fail
h2 PEOPLE WHO	1.03:1	3.0:1	#000000	#050507	Fail
h2 PROJECT	1.03:1	3.0:1	#000000	#050507	Fail
h2 GET IN	1.03:1	3.0:1	#000000	#050507	Fail
h3 // STUDENT DOSSIER	1.03:1	3.0:1	#000000	#050507	Fail
h3 BS Software Engineer…	1.03:1	3.0:1	#000000	#050507	Fail
h3 AI For Everyone — …	1.03:1	3.0:1	#000000	#050507	Fail
h3 F.Sc Pre-Engineering	1.03:1	3.0:1	#000000	#050507	Fail
h3 Matriculation — Sc…	1.03:1	3.0:1	#000000	#050507	Fail
h3 3-Year Computer Dipl…	1.03:1	3.0:1	#000000	#050507	Fail
h3 Software Engineering	1.03:1	3.0:1	#000000	#050507	Fail
h3 Artificial Intellige…	1.03:1	3.0:1	#000000	#050507	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

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Skip link target(s) don't exist on page: #about

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Page Structure — as a screen reader sees it

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A

Heading Text Quality

2 heading-text-quality issue(s) detected

PASS

2 heading-text-quality issue(s) detected

1 heading(s) are too short (≤2 characters) to convey meaning

Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H3: "AK"

Got: 1 ≤2-char heading(s)

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

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

A

Link & Button Quality

21 links, 11 buttons — all OK

PASS

21 links, 11 buttons — all OK

5 link(s) open in new tab without warning

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

Got: https://github.com/Sardar-Ak-008; https://www.linkedin.com/in/haseeburrehmansoftwareengineer/; https://www.facebook.com/share/1KZoormLsj/; https://www.instagram.com/sardar_ak_08/; https://www.tiktok.com/@sardar.ak8

16 link(s) with descriptive text

21 links

0 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://github.com/Sardar-Ak-008	GitHub	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/haseeburrehm…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/share/1KZoormLs…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/sardar_ak_08/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@sardar.ak8	TikTok	new tab	Add '(opens in new tab)' to text

27 links and buttons have descriptive text

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

https://github.com/Sardar-Ak-008; https://www.linkedin.com/in/haseeburrehmansoftwareengineer/; https://www.facebook.com/share/1KZoormLsj/; https://www.instagram.com/sardar_ak_08/; https://www.tiktok.com/@sardar.ak8

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

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+

Lighthouse Accessibility Audits

Score 98/100 — 1 failing, 25 passed

PASS

98

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ARTIFICIAL INTELLIGENCE `div.wrap > div.res-grid > div.res > h4`
BLACK PSYCHOLOGY `div.book-grid > div.book-stage > div.book > h4`

These are opportunities to improve keyboard navigation in your application.

○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

●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

●Background and foreground colors have a sufficient contrast ratio

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

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

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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

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