Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 5 REVIEW 6 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-n560vx

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://it.swiftsignbm.com/site.webmanifest contains invalid JSON. Browsers cannot parse it.

Got: https://it.swiftsignbm.com/site.webmanifest

Manifest contains invalid JSON.

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

Hamburger menu detected (responsive design)

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)

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

Landmark Structure

4 landmarks

REVIEW

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 banner (header) landmark

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

Heading Hierarchy

6 headings

REVIEW

6 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 What Our IT Clients Say About Us
H2 Explore Blogs And News
H3 IT Solution
H3 IT Solution
H3 Quick Link
H3 Location

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Mobile-Readable Font Sizes

98% of visible text renders at >= 12 CSS px (3 below threshold)

REVIEW

98% of visible text renders at >= 12 CSS px (3 below threshold)

3 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> 10.0px ("APR"); <span> 10.0px ("APR"); <span> 10.0px ("APR").

Color Contrast (Screenshot)

Action

18 text elements analyzed, 18 fail WCAG AA

REVIEW

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

0 pass 18 fail WCAG AA

h2 What Our IT Clients Say About Us

1.10:1

#000000

#070F1D

needs 3.0:1 (large text)

24px · above the fold

h2 Explore Blogs And News

1.08:1

#000000

#000E1B

needs 3.0:1 (large text)

24px · above the fold

h3 IT Solution

1.07:1

#000000

#000D19

needs 3.0:1 (large text)

19px · above the fold

h3 IT Solution

1.06:1

#000000

#000C17

needs 3.0:1 (large text)

19px · above the fold

h3 Quick Link

1.06:1

#000000

#000B17

needs 3.0:1 (large text)

19px · above the fold

h3 Location

1.06:1

#000000

#000B16

needs 3.0:1 (large text)

19px · mid-page

title Swift Sign IT

1.13:1

#000000

#051035

needs 4.5:1 (normal text)

16px · top of page (header area)

div Loading slider...

1.19:1

#000000

#14172D

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

div Loading team...

1.08:1

#000000

#0D0C1A

needs 4.5:1 (normal text)

16px · top of page (header area)

p Testimonials

1.08:1

#000000

#0D0B1A

needs 4.5:1 (normal text)

16px · top of page (header area)

p Blog & News

1.08:1

#000000

#000E1B

needs 4.5:1 (normal text)

16px · above the fold

button View All News

1.09:1

#000000

#010F1B

needs 4.5:1 (normal text)

16px · above the fold

p Scan to Connect

1.07:1

#000000

#000C19

needs 4.5:1 (normal text)

16px · above the fold

p Opening Hours:

1.53:1

#000000

#043145

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

p Phone Call:

1.06:1

#000000

#020B17

needs 4.5:1 (normal text)

16px · mid-page

1.10:1

#000000

#001121

needs 4.5:1 (normal text)

16px · mid-page

a Privacy Policy

1.05:1

#000000

#000A14

needs 4.5:1 (normal text)

16px · mid-page

a Terms of Service

1.05:1

#000000

#000A14

needs 4.5:1 (normal text)

16px · mid-page

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (18)

Element	Ratio	Required	FG	BG	Result
h2 What Our IT Clients …	1.10:1	3.0:1	#000000	#070F1D	Fail
h2 Explore Blogs And Ne…	1.08:1	3.0:1	#000000	#000E1B	Fail
h3 IT Solution	1.07:1	3.0:1	#000000	#000D19	Fail
h3 IT Solution	1.06:1	3.0:1	#000000	#000C17	Fail
h3 Quick Link	1.06:1	3.0:1	#000000	#000B17	Fail
h3 Location	1.06:1	3.0:1	#000000	#000B16	Fail
title Swift Sign IT	1.13:1	4.5:1	#000000	#051035	Fail
div Loading slider...	1.19:1	4.5:1	#000000	#14172D	Fail
div Loading team...	1.08:1	4.5:1	#000000	#0D0C1A	Fail
p Testimonials	1.08:1	4.5:1	#000000	#0D0B1A	Fail
p Blog & News	1.08:1	4.5:1	#000000	#000E1B	Fail
button View All News	1.09:1	4.5:1	#000000	#010F1B	Fail
p Scan to Connect	1.07:1	4.5:1	#000000	#000C19	Fail
p Opening Hours:	1.53:1	4.5:1	#000000	#043145	Fail
p Phone Call:	1.06:1	4.5:1	#000000	#020B17	Fail
p © 2026 Swift Sign I…	1.10:1	4.5:1	#000000	#001121	Fail
a Privacy Policy	1.05:1	4.5:1	#000000	#000A14	Fail
a Terms of Service	1.05:1	4.5:1	#000000	#000A14	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 89/100 — 3 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.

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
section.relative > div.reveal-on-scrollrelative > div.flex > button.inline-flex `section.relative > div.reveal-on-scrollrelative > div.flex > button.inline-flex`
section.relative > div.reveal-on-scrollrelative > div.flex > button.inline-flex `section.relative > div.reveal-on-scrollrelative > div.flex > button.inline-flex`
div.sr-hidden > div.absolute > div.group/share > button.flex `div.sr-hidden > div.absolute > div.group/share > button.flex`
div.sr-hidden > div.absolute > div.group/share > button.flex `div.sr-hidden > div.absolute > div.group/share > button.flex`
div.sr-hidden > div.absolute > div.group/share > button.flex `div.sr-hidden > div.absolute > div.group/share > button.flex`
div.sr-hidden > div.absolute > div.group/share > button.flex `div.sr-hidden > div.absolute > div.group/share > button.flex`
div.sr-hidden > div.absolute > div.group/share > button.flex `div.sr-hidden > div.absolute > div.group/share > button.flex`
div.sr-hidden > div.absolute > div.group/share > button.flex `div.sr-hidden > div.absolute > div.group/share > button.flex`
div.sr-hidden > div.absolute > div.group/share > button.flex `div.sr-hidden > div.absolute > div.group/share > button.flex`
div.sr-hidden > div.absolute > div.group/share > button.flex `div.sr-hidden > div.absolute > div.group/share > button.flex`
div.sr-hidden > div.absolute > div.group/share > button.flex `div.sr-hidden > div.absolute > div.group/share > button.flex`
div.sr-hidden > div.absolute > div.group/share > button.flex `div.sr-hidden > div.absolute > div.group/share > button.flex`
div.sr-hidden > div.absolute > div.group/share > button.flex `div.sr-hidden > div.absolute > div.group/share > button.flex`
section.relative > div.mx-auto > div.flex > button.inline-flex `section.relative > div.mx-auto > div.flex > button.inline-flex`
section.relative > div.mx-auto > div.flex > button.inline-flex `section.relative > div.mx-auto > div.flex > button.inline-flex`

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
WHO WE ARE `div.relative > div.grid > div > p.inline-flex`

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
Swift Sign BM `a.group > div.absolute > div.flex > h3.text-white`
Kausar Ahmed `div.group > div.flex > div > h4.text-white`

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

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

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

●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

○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

○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

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

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

4 decorative image(s) correctly marked

3 image(s) with good alt text

7 images 3 good alt text 4 decorative

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

9 links, 4 buttons — all OK

PASS

9 links, 4 buttons — all OK

4 link(s) open in new tab without warning

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

Got: https://wa.me/923158399446; https://www.facebook.com/profile.php?id=61583716060195; https://www.linkedin.com/company/swift-sign-it-cyber-solutions/; https://www.instagram.com/ssitandcybersolutions

5 link(s) with descriptive text

9 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://wa.me/923158399446	Chat on WhatsApp	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/profile.php?id=…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/swift-s…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/ssitandcyberso…	Instagram	new tab	Add '(opens in new tab)' to text

9 links and buttons have descriptive text

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

https://wa.me/923158399446; https://www.facebook.com/profile.php?id=61583716060195; https://www.linkedin.com/company/swift-sign-it-cyber-solutions/; https://www.instagram.com/ssitandcybersolutions

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 "en"

PASS

Lang attribute set to "en"

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

Got: en

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.

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