https://seomeal.com/blog/how-to-choose-the-right-seo-services-in-lahore-without-wasting-money-or-time

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 3 REVIEW 4 FIX

Mobile Keyboard & Autofill

Action

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

FIX

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

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="bcName">, <input type="email" name="email" id="bcEmail">

3 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, tel.

Got: <input type="email" name="email" id="bcEmail">, <input type="email" name="email" id="scEmail">, <input type="tel" name="phone" id="scPhone">

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.

Got: #2563eb

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 ✗

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 Page Not Found — SEOMeal ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 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

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Navigation UX

Action

2 navigation pattern(s)

REVIEW

2 navigation pattern(s)

Breadcrumb navigation detected

Got: aria-label

Skip navigation link detected

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs aria-label navigation

Skip Link Skip link detected

Labeled Navigation 2 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

A+

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

15 headings

PASS

15 headings

Multiple H1 headings (2 found)

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

H1 How to Choose the Right SEO Services in Lahore Without Wasting Money or Time
H1 How to Choose the Right SEO Services in Lahore Without Wasting Money or Time duplicate H1
H2 Clarify Your Business Objectives Before Starting the Search
H2 Do Your Homework on Local SEO Experts in Lahore
H2 Scrutinize Their Service Offerings and Commitment to Transparency
H2 Assess Pricing Structures and Value for Your Investment
H2 Ensure They Know How to Maximize Local SEO Opportunities
H2 Evaluate Their Content and Technical SEO Skills
H2 Dig Into Client Success Stories and Testimonials
H2 Clarify Reporting and Communication Practices
H2 Don’t Rush: Take Your Time to Find the Perfect Fit
H2 Start Small and Test the Waters
H2 Final Takeaway: Invest in a Partnership That Grows With Your Business
H2 Comments
H3 Leave a comment

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

All 15 heading(s) have substantive, well-formed text

PASS

All 15 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

3 image(s) with good alt text

3 images 3 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 7 controls labeled

PASS

All 7 controls labeled

7 control(s) properly labeled

7 controls

7 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#bcName	text	Your name	aria-label
#bcEmail	email	Email (not published)	aria-label
#bcBody	textarea	Your comment	aria-label
#scName	input	Name	for/id
#scEmail	email	Email	for/id
#scPhone	tel	Phone (optional)	for/id
#scMessage	textarea	How can we help?	for/id

Link & Button Quality

33 links, 8 buttons — all OK

PASS

33 links, 8 buttons — all OK

9 link(s) open in new tab without warning

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

Got: https://wa.me/15795030012; https://t.me/seomeal; https://wa.me/15795030012; https://wa.me/15795030012; https://t.me/seomeal; https://wa.me/15795030012; https://wa.me/15795030012; https://t.me/seomeal; mailto:hello@seomeal.com

24 link(s) with descriptive text

33 links

0 empty

0 generic text

9 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://wa.me/15795030012	Get Started	new tab	Add '(opens in new tab)' to text
https://t.me/seomeal	Telegram	new tab	Add '(opens in new tab)' to text
https://wa.me/15795030012	Get Started	new tab	Add '(opens in new tab)' to text
https://wa.me/15795030012	WA	new tab	Add '(opens in new tab)' to text
https://t.me/seomeal	TG	new tab	Add '(opens in new tab)' to text
https://wa.me/15795030012	Chat on WhatsApp	new tab	Add '(opens in new tab)' to text
https://wa.me/15795030012	WhatsApp	new tab	Add '(opens in new tab)' to text
https://t.me/seomeal	Telegram	new tab	Add '(opens in new tab)' to text
mailto:hello@seomeal.com	hello@seomeal.com	new tab	Add '(opens in new tab)' to text

32 links and buttons have descriptive text

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

https://wa.me/15795030012; https://t.me/seomeal; https://wa.me/15795030012; https://wa.me/15795030012; https://t.me/seomeal; https://wa.me/15795030012; https://wa.me/15795030012; https://t.me/seomeal; mailto:hello@seomeal.com

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

7 form control(s) checked, no type mismatches

PASS

7 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

7 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

Tabindex Anti-Patterns

0 positive, 2 -1-on-focusable

PASS

0 positive, 2 -1-on-focusable

tabindex="-1" on naturally-focusable <input id="bcWebsite">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <input>

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+

Mobile-Readable Font Sizes

All 85 visible text node(s) render at >= 12 CSS pixels

PASS

All 85 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

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+

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 How to Choose the Ri…	13.46:1	3.0:1	#000000	#CECFD0	Pass
h1 How to Choose the Ri…	11.41:1	3.0:1	#000000	#BEBFC1	Pass
h2 Clarify Your Busines…	9.33:1	3.0:1	#000000	#ABADAF	Pass
h2 Do Your Homework on …	9.33:1	3.0:1	#000000	#ABADAF	Pass
h2 Scrutinize Their Ser…	9.33:1	3.0:1	#000000	#ABADAF	Pass
h2 Assess Pricing Struc…	9.33:1	3.0:1	#000000	#ABADAF	Pass
h2 Ensure They Know How…	9.33:1	3.0:1	#000000	#ABADAF	Pass
h2 Evaluate Their Conte…	9.33:1	3.0:1	#000000	#ABADAF	Pass
h2 Dig Into Client Succ…	9.33:1	3.0:1	#000000	#ABADAF	Pass
h2 Clarify Reporting an…	9.33:1	3.0:1	#000000	#ABADAF	Pass
h2 Don’t Rush: Take Y…	9.33:1	3.0:1	#000000	#ABADAF	Pass
h2 Start Small and Test…	9.33:1	3.0:1	#000000	#ABADAF	Pass
h2 Final Takeaway: Inve…	9.33:1	3.0:1	#000000	#ABADAF	Pass
h2 Comments	9.33:1	3.0:1	#000000	#ABADAF	Pass
h3 Leave a comment	9.33:1	3.0:1	#000000	#ABADAF	Pass
title How to Choose the Ri…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span SEOMeal	20.12:1	4.5:1	#000000	#FAFAFA	Pass
a Home	19.06:1	4.5:1	#000000	#F3F4F4	Pass
a Services	18.44:1	4.5:1	#000000	#F0F0F1	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 96/100 — 1 failing, 22 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
Get Started `div.container > nav#navMenu > div.navbar__mobile-actions > a.btn`
Support `body > div#supportChatRoot > button#supportChatToggle > span.support-chat__toggle-label`

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

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

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

●Buttons have an accessible name

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

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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●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

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

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