Skip to content
https://hifsakhansalon.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
6
REVIEW
8
PASS
10
INFO
0
Checks
24
10 PASS 8 REVIEW 6 FIX
D
Mobile Keyboard & Autofill
Action
3/3 eligible field(s) missing autocomplete or inputmode
FIX
3/3 eligible field(s) missing autocomplete or inputmode
Warning::
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">
Warning::
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">
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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
Info::
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 ✗
D
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link
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
Landmark Structure
Action
4 landmarks
REVIEW
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Warning::
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

C
Heading Hierarchy
Action
32 headings, 2 skip(s)
REVIEW
32 headings, 2 skip(s)
Warning::
Multiple H1 headings (7 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Let’s Talk
  • H1 Enriching lives, nourishing talent, and building lasting bonds.
  • H1 Enriching lives, nourishing talent, and building lasting bonds. duplicate H1
  • H1 Your Journey to Lasting Beauty Starts Here! duplicate H1
  • H2 Four ways we care for you
  • H3 Makeup
  • H3 Hair
  • H3 Spa
  • H3 HK Aesthetics
  • H2 Bridal is where we made our name
  • H2 Why Lahore keeps coming back
  • H3 Since 2009
  • H3 Real products, real training
  • H3 Four branches, one standard
  • H3 A welcome you will remember
  • H1 The Expert’s Guide to Effortless Radiance duplicate H1
  • H1 Special Promotions duplicate H1
  • H1 Create Memories at Hifsa Khan Sets duplicate H1
  • H2 We are here to answer all your questions.
  • H2 Real TransformationsReal Stories
  • H4 — Ayeza Khan skipped
  • H4 — Dananir
  • H1 Join Our Exclusive Circle of Timeless Elegance duplicate H1
  • H2 @hifsa.khan.salon
  • H4 Address skipped
  • H3 Contact Us
  • H3 Info
  • H3 More
  • H3 Business Hours
  • H3 Contact Us
  • H4 Address
  • H2 Let’s Talk

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

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

C
Alt Text Quality
Action
36 of 167 images have issues
REVIEW
36 of 167 images have issues
Critical::
36 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
6 decorative image(s) correctly marked
Info::
125 image(s) with good alt text
167 images 125 good alt text 6 decorative 36 missing
IssueCount
missing36 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B
Form Accessibility
4 of 5 controls have issues
REVIEW
4 of 5 controls have issues
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="searchInputmbl">; <input type="text" id="searchInput">; <input type="text" name="name" id="name">; <input type="email" name="email" id="email">
Info::
1 control(s) properly labeled
5 controls
1 labeled
4 placeholder only
0 unlabeled
ControlTypeLabelMethod
textareatextareaYour messagearia-label
#searchInputtext(Search...)placeholder only
#nametext(Name)placeholder only
#emailemail(Email Address)placeholder only
#searchInputmbltext(Search...)placeholder only

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

<input type="text" id="searchInputmbl">; <input type="text" id="searchInput">; <input type="text" name="name" id="name">; <input type="email" name="email" id="email">

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

B
Tap Target Adequacy
2 tap target(s) too small or too close together
REVIEW
2 tap target(s) too small or too close together
Info::
2 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found – Hifsa Khan Salon ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Lighthouse Accessibility Audits
Action
Score 79/100 — 7 failing, 21 passed
REVIEW
79

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.home > div#hksc-root > button.hksc-fab body.home > div#hksc-root > button.hksc-fab

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
navbar.nav_main_top > nav.navbar > div.container-fluid > a.navbar-brand navbar.nav_main_top > nav.navbar > div.container-fluid > a.navbar-brand
body.home > a body.home > a
body.home > section.insta_follow > a body.home > section.insta_follow > a
section.insta_follow > div.container > div.row > a section.insta_follow > div.container > div.row > a
div.container > div.row > div.col-md-2 > a div.container > div.row > div.col-md-2 > a
ul.footer_items > ul.footer_icons > li > a ul.footer_items > ul.footer_icons > li > a
ul.footer_items > ul.footer_icons > li > a ul.footer_items > ul.footer_icons > li > a
ul.footer_items > ul.footer_icons > li > a ul.footer_items > ul.footer_icons > li > a
ul.footer_items > ul.footer_icons > li > a ul.footer_items > ul.footer_icons > li > a

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.

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
Book Appointment div.col-md-6 > div.buttons_cont > a.btn_banner1 > button
Subscribe div.col-md-3 > div.buttons_cont > a.btn_banner1 > button#submit
Need a beauty remake? div.container > a.row > div.col-md-10 > p.footer_heading_label
CONTACT body.home > a.hks_contact_fab > span.hks_contact_fab_label

These are opportunities to improve the legibility of your content.

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
— Ayeza Khan div.col-md-6 > div.hks_testi_inner > div.hks_testi_slide > h4.hks_testi_name

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Humans of HKS Careers Refund Policy Privacy Policy BUSINESS HOURS Mon-Sun 11:00… div.container > div.row > div.col-md-3 > ul.footer_items
+92 304 1111820 info@hifsakhansalon.com div.container > div.row > div.col-md-2 > ul.footer_items

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Next slide div.container > div.mobile_show > div.swiper > div.swiper-button-next
Previous slide div.container > div.mobile_show > div.swiper > div.swiper-button-prev

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●Image elements have `[alt]` attributes
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●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.
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○`<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
○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.
A+
Heading Text Quality
All 32 heading(s) have substantive, well-formed text
PASS
All 32 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Form Input Types
2 input(s) using type=text where a specific type would help
PASS
2 input(s) using type=text where a specific type would help
Info::
Input "searchInputmbl" should use type="search" (currently type="text")
Field name "searchInputmbl" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "searchInput" should use type="search" (currently type="text")
Field name "searchInput" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
5 form control(s) checked, no input-semantic issues
PASS
5 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tabindex Anti-Patterns
9 explicit tabindex attribute(s) checked, no anti-patterns
PASS
9 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Mobile-Readable Font Sizes
All 27 visible text node(s) render at >= 12 CSS pixels
PASS
All 27 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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)
ElementRatioRequiredFGBGResult
h1 Enriching lives, nou…19.27:13.0:1
#000000
#F6F5F3
Pass
h1 Enriching lives, nou…19.27:13.0:1
#000000
#F6F5F3
Pass
h1 Your Journey to Last…19.27:13.0:1
#000000
#F6F5F3
Pass
h1 The Expert’s Guide…19.27:13.0:1
#000000
#F6F5F3
Pass
h1 Special Promotions19.27:13.0:1
#000000
#F6F5F3
Pass
h1 Create Memories at H…19.27:13.0:1
#000000
#F6F5F3
Pass
h1 Join Our Exclusive C…19.27:13.0:1
#000000
#F6F5F3
Pass
h2 Let’s Talk19.27:13.0:1
#000000
#F6F5F3
Pass
h2 Four ways we care fo…19.27:13.0:1
#000000
#F6F5F3
Pass
h2 Bridal is where we m…19.27:13.0:1
#000000
#F6F5F3
Pass
h2 Why Lahore keeps com…19.27:13.0:1
#000000
#F6F5F3
Pass
h2 We are here to answe…19.27:13.0:1
#000000
#F6F5F3
Pass
h2 Real Transformations19.27:13.0:1
#000000
#F6F5F3
Pass
h2 Real Stories19.27:13.0:1
#000000
#F6F5F3
Pass
h2 @hifsa.khan.salon19.27:13.0:1
#000000
#F6F5F3
Pass
h2 Let’s Talk19.27:13.0:1
#000000
#F6F5F3
Pass
h3 Makeup19.27:13.0:1
#000000
#F6F5F3
Pass
h3 Hair19.27:13.0:1
#000000
#F6F5F3
Pass
h3 Spa19.27:13.0:1
#000000
#F6F5F3
Pass
h3 HK Aesthetics19.27:13.0:1
#000000
#F6F5F3
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.

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

Send Feedback