Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

11 PASS 5 REVIEW 8 FIX

Form Accessibility

Action

8 of 16 controls have issues

FIX

8 of 16 controls have issues

5 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <select>; <input type="submit" name="shopsmart-submit">; <input type="submit" name="shopsmart-submit">; <input type="number" name="shopsmart-redeemable-amt">; <input type="submit" name="shopsmart-submit">

3 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="email" name="contact[email]">; <input type="text" name="q">; <input type="text" name="shopsmart-pin">

8 control(s) properly labeled

16 controls

8 labeled

3 placeholder only

5 unlabeled

Control	Type	Label	Method
#RecoverEmail	email	Email address	for/id
#CustomerEmail	email	Email *	for/id
#CustomerPassword	password	Password *	for/id
#RegisterForm-FirstName	text	First Name	for/id
#RegisterForm-LastName	text	Last Name	for/id
#RegisterForm-email	email	Email *	for/id
#RegisterForm-password	password	Password *	for/id
shopsmart-phone	number	Phone number...	aria-label
contact[email]	email	(Your email address)	placeholder only
q	text	(Search)	placeholder only
shopsmart-pin	text	(PIN)	placeholder only
shopsmart-submit	submit	(none)	none
select	select	(none)	none
shopsmart-submit	submit	(none)	none
shopsmart-redeemable-amt	number	(none)	none
shopsmart-submit	submit	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Link & Button Quality

Action

12 issue(s) across 144 links and 34 buttons

FIX

12 issue(s) across 144 links and 34 buttons

3 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /; /search; /

13 link(s) open in new tab without warning

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

Got: https://www.khasstores.com/policies/privacy-policy; https://khasstores.asaanretail.pk/order-tracking#/store/SHP_002; https://www.facebook.com/khasstores; https://twitter.com/khasofficial; https://www.instagram.com/khasstorespakistan/; https://www.pinterest.com/khasstores/; https://www.youtube.com/channel/UCE6Sr00KFGTqmfetyhsYunw; http://tiktok.com/@khasstores; https://www.facebook.com/khasstores; https://twitter.com/khasofficial (+3 more)

9 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.t4s-modal-close (#760 on page); button.pswp__button (#772 on page); button.pswp__button (#773 on page); button.pswp__button (#774 on page); button.pswp__button (#775 on page); button.pswp__button (#782 on page); button.pswp__button (#783 on page); button.t4s-mini-search__submit (#1005 on page); input[type="submit"].button (#1289 on page)

128 link(s) with descriptive text

144 links

3 empty

0 generic text

13 new tab

9 empty buttons

Element	Text	Issue	Suggested Fix
https://www.khasstores.com/policies/priv…	Privacy Policy	new tab	Add '(opens in new tab)' to text
/	(empty)	empty	Add link text or aria-label
/search	(empty)	empty	Add link text or aria-label
https://khasstores.asaanretail.pk/order-…	Tracking	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/khasstores	Follow on Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/khasofficial	Follow on Twitter	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/khasstorespaki…	Follow on Instagram	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/khasstores/	Follow on Pinterest	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCE6Sr00…	Follow on YouTube	new tab	Add '(opens in new tab)' to text
http://tiktok.com/@khasstores	Follow on Tiktok	new tab	Add '(opens in new tab)' to text
/	(empty)	empty	Add link text or aria-label
https://www.facebook.com/khasstores	Follow on Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/khasofficial	Follow on Twitter	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/khasstorespaki…	Follow on Instagram	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/khasstores/	Follow on Pinterest	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCE6Sr00…	Follow on YouTube	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<input>	(empty)	empty	Add button text or aria-label

153 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/; /search; /

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://www.khasstores.com/policies/privacy-policy; https://khasstores.asaanretail.pk/order-tracking#/store/SHP_002; https://www.facebook.com/khasstores; https://twitter.com/khasofficial; https://www.instagram.com/khasstorespakistan/; https://www.pinterest.com/khasstores/; https://www.youtube.com/channel/UCE6Sr00KFGTqmfetyhsYunw; http://tiktok.com/@khasstores; https://www.facebook.com/khasstores; https://twitter.com/khasofficial (+3 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

Icon-only buttons need an aria-label so screen readers can announce them.

button.t4s-modal-close (#760 on page); button.pswp__button (#772 on page); button.pswp__button (#773 on page); button.pswp__button (#774 on page); button.pswp__button (#775 on page); button.pswp__button (#782 on page); button.pswp__button (#783 on page); button.t4s-mini-search__submit (#1005 on page); input[type="submit"].button (#1289 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Mobile Keyboard & Autofill

Action

6/7 eligible field(s) missing autocomplete or inputmode

FIX

6/7 eligible field(s) missing autocomplete or inputmode

6 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, numeric.

Got: <input type="email" name="contact[email]">, <input type="email" name="email" id="RecoverEmail">, <input type="email" name="customer[email]" id="CustomerEmail">, <input type="email" name="customer[email]" id="RegisterForm-email">, <input type="number" name="shopsmart-phone">

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

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 ✗

Form Input Quality

2 input-semantic issue(s) across 16 form control(s)

REVIEW

2 input-semantic issue(s) across 16 form control(s)

1 password field(s) missing or with invalid `autocomplete`

Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="customer[password]">.

1 login form field(s) missing `autocomplete=username` (or `email`)

On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="email" name="contact[email]">.

Mobile-Readable Font Sizes

96% of visible text renders at >= 12 CSS px (2 below threshold)

REVIEW

96% of visible text renders at >= 12 CSS px (2 below threshold)

2 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: <button> 10.0px ("Deny"); <button> 10.0px ("Ok").

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found – KHAS STORES ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 4 fail WCAG AA

REVIEW

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

16 pass 4 fail WCAG AA 1 pass AA only

title Pakistani Dresses Online | Unstitched an…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Privacy Policy

2.44:1

#000000

#464C58

needs 4.5:1 (normal text)

16px · top of page (header area)

span Manage preferences

2.80:1

#000000

#4F5561

needs 4.5:1 (normal text)

16px · above the fold

button Accept

3.13:1

#000000

#565C68

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 KHAS STORES	3.88:1	3.0:1	#000000	#656A77	Pass
h2 Cookie consent	18.26:1	3.0:1	#000000	#EFEFEF	Pass
h2 PRE-WINTER'26	6.99:1	3.0:1	#000000	#9693A2	Pass
h2 Loyalty Points	6.99:1	3.0:1	#000000	#9693A2	Pass
h3 Get in touch	6.99:1	3.0:1	#000000	#9693A2	Pass
h3 Contact Us	6.99:1	3.0:1	#000000	#9693A2	Pass
h3 Customer Support	6.99:1	3.0:1	#000000	#9693A2	Pass
h3 Customer Support	6.99:1	3.0:1	#000000	#9693A2	Pass
h3 Customer Queries	6.99:1	3.0:1	#000000	#9693A2	Pass
h3 Customer Queries	6.99:1	3.0:1	#000000	#9693A2	Pass
h3 Quick Links	6.99:1	3.0:1	#000000	#9693A2	Pass
h3 Quick Links	6.99:1	3.0:1	#000000	#9693A2	Pass
h3 Sign up and save	6.99:1	3.0:1	#000000	#9693A2	Pass
h3 Sign up and save	6.99:1	3.0:1	#000000	#9693A2	Pass
h3 KHAS for you!🛍️	6.99:1	3.0:1	#000000	#9693A2	Pass
title Pakistani Dresses On…	1.00:1	4.5:1	#000000	#000000	Fail
p We and our partners,…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Privacy Policy	2.44:1	4.5:1	#000000	#464C58	Fail
span Manage preferences	2.80:1	4.5:1	#000000	#4F5561	Fail
button Accept	3.13:1	4.5:1	#000000	#565C68	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.

Lighthouse Accessibility Audits

Score 83/100 — 4 failing, 22 passed

REVIEW

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
Pre-Winter Collection '26 - LIVE NOW `div.t4s-announcement-bar__wrap > div.flickityt4s-viewport > div.flickityt4s-slider > div#b_announcement_FEzeAq`

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
Powered by TryVerse `div.tv-modal > div.tv-footer > a.tv-powered`
Ok `body.template-index > div.pop-model-wrapper-app > div.pop-model-btn-container > button#mt-pn-app-allow-button`

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.t4s-section-header__mid > div.t4s-row > div.t4s-col-md-4 > a.t4s-push-menu-btn `div.t4s-section-header__mid > div.t4s-row > div.t4s-col-md-4 > a.t4s-push-menu-btn`
div.t4s-col-lg-3 > div.t4s-site-nav__icons > div.t4s-site-nav__icon > a.t4s-pr `div.t4s-col-lg-3 > div.t4s-site-nav__icons > div.t4s-site-nav__icon > a.t4s-pr`
div.t4s-custom-col > div.t4s-col-inner > div.t4s-footer-content > a.t4s-d-block `div.t4s-custom-col > div.t4s-col-inner > div.t4s-footer-content > a.t4s-d-block`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

○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

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●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 are distinguishable without relying on color.

●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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

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

○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

○Form elements have associated labels

○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

○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

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

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

A+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

15 headings

PASS

15 headings

Single H1 present

H2 Cookie consent
H1 KHAS STORES
H2 PRE-WINTER'26
H3 Get in touch
H3 Contact Us
H3 Customer Support
H3 Customer Support
H3 Customer Queries
H3 Customer Queries
H3 Quick Links
H3 Quick Links
H3 Sign up and save
H3 Sign up and save
H2 Loyalty Points
H3 KHAS for you!🛍️

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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

A+

Alt Text Quality

All 21 images OK

PASS

All 21 images OK

11 decorative image(s) correctly marked

10 image(s) with good alt text

21 images 10 good alt text 11 decorative

All images have appropriate alt text.

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "q" should use type="search" (currently type="text")

Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

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

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

PASS

4 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

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.

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