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

✗ favicon.ico Missing

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

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 ✗

Mobile-Readable Font Sizes

99% of visible text renders at >= 12 CSS px (1 below threshold)

REVIEW

99% of visible text renders at >= 12 CSS px (1 below threshold)

1 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: <p> 11.0px ("Customer Favorites").

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 404 Not Found – ALFAJR KEFFIYEH CO ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass 20 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Item added to your c…	3.06:1	3.0:1	#000000	#5C5A57	Pass
h2 Explore Our Product …	3.06:1	3.0:1	#000000	#5C5A57	Pass
h2 Who We Work With	3.06:1	3.0:1	#000000	#5C5A57	Pass
h2 Manufacturing, Tradi…	3.06:1	3.0:1	#000000	#5C5A57	Pass
h2 Meet Fawad — Your …	3.06:1	3.0:1	#000000	#5C5A57	Pass
h2 Why Global Buyers Ch…	3.06:1	3.0:1	#000000	#5C5A57	Pass
h2 Looking for Wholesal…	3.06:1	3.0:1	#000000	#5C5A57	Pass
h2 Your Global Partner …	3.06:1	3.0:1	#000000	#5C5A57	Pass
h2 Frequently Asked Que…	3.06:1	3.0:1	#000000	#5C5A57	Pass
h2 ALFAJR KEFFIYEH CO.	3.06:1	3.0:1	#000000	#5C5A57	Pass
h2 BUY BEST	3.06:1	3.0:1	#000000	#5C5A57	Pass
h2 TODAY	3.06:1	3.0:1	#000000	#5C5A57	Pass
h2 Our Best Sellers	3.06:1	3.0:1	#000000	#5C5A57	Pass
h3 Keffiyeh	3.06:1	3.0:1	#000000	#5C5A57	Pass
h3 Shemagh	3.06:1	3.0:1	#000000	#5C5A57	Pass
h3 Yemeni Shawls	3.06:1	3.0:1	#000000	#5C5A57	Pass
h3 ALFAJR Gold	3.06:1	3.0:1	#000000	#5C5A57	Pass
h3 Best Seller	3.06:1	3.0:1	#000000	#5C5A57	Pass
h3 Camouflage Scarves	3.06:1	3.0:1	#000000	#5C5A57	Pass
h3 Ghutra	3.06:1	3.0:1	#000000	#5C5A57	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.

Landmark Structure

4 landmarks

PASS

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

No contentinfo (footer) landmark

Skip navigation link present

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

Heading Hierarchy

40 headings

PASS

40 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 ALFAJR KEFFIYEH CO
H2 Item added to your cart
H1 Timeless Heritage. Made for Today. duplicate H1
H2 Explore Our Product Categories
H3 Keffiyeh
H3 Shemagh
H3 Yemeni Shawls
H3 ALFAJR Gold
H3 Best Seller
H3 Camouflage Scarves
H3 Ghutra
H3 Private Label
H2 Who We Work With
H3 Retail Customers
H3 Wholesalers & Importers
H3 Private Label Brands
H3 Sourcing Buyers
H2 Manufacturing, Trading and Global Sourcing Support
H3 Pakistan-Based Expertise
H3 Trusted Production Network
H3 Global Buyer Support
H2 Meet Fawad — Your Keffiyeh & Shemagh Sourcing Contact
H2 Why Global Buyers Choose ALFAJR KEFFIYEH CO.
H3 Specialized Product Focus
H3 Manufacturing & Trading Knowledge
H3 Wholesale & Private Label Support
H3 Traditional Headwear Guide
H3 Export-Focused Mindset
H3 Founder-Led Trust
H2 Looking for Wholesale, Private Label or Bulk Keffiyeh Supply?
H3 Shopping for yourself?
H3 Buying in Bulk ?
H2 Your Global Partner for Keffiyeh, Shemagh, Ghutra and Scarves
H2 Frequently Asked Questions
H2 ALFAJR KEFFIYEH CO.
H3 Explore
H3 Business
H3 Contact
H2 BUY BESTKEFFIYEH TODAY
H2 Our Best Sellers

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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 16 images OK

PASS

All 16 images OK

1 decorative image(s) correctly marked

15 image(s) with good alt text

16 images 15 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#Search-In-Modal	search	Search	for/id

Link & Button Quality

81 links, 13 buttons — all OK

PASS

81 links, 13 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://www.alfajrkeffiyeh.com/pages/traditional-headwear-guide; http://wa.me/+923395311555; https://wa.me/923395311555?text=Assalamualaikum%2C%20I%20visited%20your%20web…

78 link(s) with descriptive text

81 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.alfajrkeffiyeh.com/pages/tra…	Traditional Headwear Guide …	new tab	Add '(opens in new tab)' to text
http://wa.me/+923395311555	WhatsApp	new tab	Add '(opens in new tab)' to text
https://wa.me/923395311555?text=Assalamu…	Chat on WhatsApp	new tab	Add '(opens in new tab)' to text

91 links and buttons have descriptive text

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

https://www.alfajrkeffiyeh.com/pages/traditional-headwear-guide; http://wa.me/+923395311555; https://wa.me/923395311555?text=Assalamualaikum%2C%20I%20visited%20your%20web…

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

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

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

7 explicit tabindex attribute(s) checked, no anti-patterns

PASS

7 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

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, 26 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
Shop Collection `div.ai-luxury-hero-container-awtzrtvj0n3lzt3fjraigenblock4f6018dhtc9xx > div.ai-luxury-hero-content-awtzrtvj0n3lzt3fjraigenblock4f6018dhtc9xx > div.ai-luxury-hero-buttons-awtzrtvj0n3lzt3fjraigenblock4f6018dhtc9xx > a.ai-luxury-hero-btn-primary-awtzrtvj0n3lzt3fjraigenblock4f6018dhtc9xx`
4.6 out of 5 stars based on 86 reviews `div#shopify-block-ATzJkSEdOVCtKRElqe__judge_me_reviews_all_reviews_text_ix4DMh > div.jdgm-widget > a > span.jdgm-all-reviews-text__text`
Verified `div.jdgm-widget > a > span.jdgm-verified-by > span.jdgm-verified-by__text`
Contact ALFAJR KEFFIYEH CO. for sourcing guidance, product options, manufacturi… `div.ai-wholesale-cta-anmtrsezvzvr4ystlmaigenblock984e5e3dqffka > div.ai-wholesale-cta-container-anmtrsezvzvr4ystlmaigenblock984e5e3dqffka > div.ai-wholesale-cta-text-anmtrsezvzvr4ystlmaigenblock984e5e3dqffka > p`

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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

●`[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 with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

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