https://abdalrhmansaid.github.io/my-website

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 3 REVIEW 5 FIX

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

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ 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

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

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

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)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 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

Mobile-Readable Font Sizes

Action

73% of visible text renders at >= 12 CSS px (61 below threshold)

REVIEW

73% of visible text renders at >= 12 CSS px (61 below threshold)

61 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 ("خصم"); <span> 11.0px ("24"); <span> 11.0px ("الأكثر مبيعًا"); <p> 11.0px ("صوتيات"); <span> 11.0px ("خصم").

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 ✗

Heading Hierarchy

30 headings, 1 skip(s)

PASS

30 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

H1 أناقة تُبنى من التفاصيل
H3 توصيل سريع skipped
H3 تسوق آمن
H3 جودة مميزة
H3 دعم عبر واتساب
H2 تسوّق حسب التصنيف
H2 عروض محدودة
H3 سماعة أذن لاسلكية Aurora Pro
H3 ساعة ذكية Pulse Fit 2
H3 حقيبة ظهر Voyager Daily
H3 كرسي مكتب Contour Ergo
H2 منتجات مميزة
H3 سماعة أذن لاسلكية Aurora Pro
H3 ساعة ذكية Pulse Fit 2
H3 حقيبة ظهر Voyager Daily
H3 دمبل قابل للتعديل FlexWeight
H3 كرسي مكتب Contour Ergo
H2 الأكثر مبيعًا
H3 سماعة أذن لاسلكية Aurora Pro
H3 ساعة ذكية Pulse Fit 2
H3 حقيبة ظهر Voyager Daily
H3 كرسي مكتب Contour Ergo
H2 وصل حديثًا
H3 مكبر صوت محمول Nomad Beat
H3 مصباح طاولة Ember Glow
H3 محفظة جلد طبيعي Slate
H3 دفتر ملاحظات Craft Journal
H4 تصفح
H4 التصنيفات
H4 تواصل معنا

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

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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

A+

Alt Text Quality

All 25 images OK

PASS

All 25 images OK

25 image(s) with good alt text

25 images 25 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

55 links, 56 buttons — all OK

PASS

55 links, 56 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://wa.me/201000000000; https://facebook.com/velora.store; https://instagram.com/velora.store; https://wa.me/201000000000; https://wa.me/201000000000

50 link(s) with descriptive text

55 links

0 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://wa.me/201000000000	واتساب	new tab	Add '(opens in new tab)' to text
https://facebook.com/velora.store	فيسبوك	new tab	Add '(opens in new tab)' to text
https://instagram.com/velora.store	إنستغرام	new tab	Add '(opens in new tab)' to text
https://wa.me/201000000000	راسلنا على واتسا…	new tab	Add '(opens in new tab)' to text
https://wa.me/201000000000	واتساب	new tab	Add '(opens in new tab)' to text

106 links and buttons have descriptive text

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

https://wa.me/201000000000; https://facebook.com/velora.store; https://instagram.com/velora.store; https://wa.me/201000000000; https://wa.me/201000000000

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

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "ar"

PASS

Lang attribute set to "ar"

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

Got: ar

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 أناقة تُبن�…	19.37:1	3.0:1	#000000	#F5F6F4	Pass
h2 تسوّق حسب ا…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 عروض محدود�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 منتجات ممي�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 الأكثر مبي�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 وصل حديثًا	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 توصيل سريع	17.65:1	3.0:1	#000000	#E9ECEA	Pass
h3 تسوق آمن	16.18:1	3.0:1	#000000	#DEE3E1	Pass
h3 جودة مميزة	15.51:1	3.0:1	#000000	#D8DFDC	Pass
h3 دعم عبر وات…	19.37:1	3.0:1	#000000	#F5F6F4	Pass
h3 سماعة أذن ل…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 ساعة ذكية Pu…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 حقيبة ظهر Vo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 كرسي مكتب Co…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 سماعة أذن ل…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 ساعة ذكية Pu…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 حقيبة ظهر Vo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 دمبل قابل ل…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 كرسي مكتب Co…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 سماعة أذن ل…	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 98/100 — 1 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.

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
توصيل سريع `section.max-w-7xl > div.grid > div.flex > h3.font-semibold`

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

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

●Document has a main landmark.

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

○Form elements have associated labels

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

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.