Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 4 REVIEW 7 FIX

Alt Text Quality

Action

7 of 67 images have issues

FIX

7 of 67 images have issues

6 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

6 image-in-link without alt text

An image inside a link with no alt creates an empty link.

1 image(s) with generic alt text

51 decorative image(s) correctly marked

9 image(s) with good alt text

67 images 9 good alt text 51 decorative 1 generic 6 missing

Issue	Count
missing	6 image(s)
generic	1 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Link & Button Quality

Action

11 issue(s) across 80 links and 2 buttons

FIX

11 issue(s) across 80 links and 2 buttons

2 link(s) with no accessible text

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

Got: https://vynoxsecurity.com/; https://vynoxsecurity.com/

7 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://vynoxsecurity.com/services/advanced-cybersecurity-services/ ("Learn more"); https://vynoxsecurity.com/services/advanced-cybersecurity-services/ ("Learn more"); https://vynoxsecurity.com/services/advanced-cybersecurity-services/ ("Learn more"); https://vynoxsecurity.com/services/advanced-cybersecurity-services/ ("Learn more"); https://vynoxsecurity.com/services/advanced-cybersecurity-services/ ("Learn more"); https://vynoxsecurity.com/services/strategic-security-advisory-services-vciso/ ("Learn more"); https://vynoxsecurity.com/services/strategic-security-advisory-services-vciso/ ("Learn more")

6 image-only link(s) without alt text

2 button(s) with no accessible text

65 link(s) with descriptive text

80 links

2 empty

7 generic text

0 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://vynoxsecurity.com/	(empty)	empty	Add link text or aria-label
https://vynoxsecurity.com/	(empty)	empty	Add link text or aria-label
javascript:void(0);	VAPT Services	img no alt	Add alt attribute to the image
javascript:void(0);	Cybersecurity Services	img no alt	Add alt attribute to the image
javascript:void(0);	vCISO & MSS Service	img no alt	Add alt attribute to the image
uc_content_tabs_elementor_10430ec_item1	VAPT Services	img no alt	Add alt attribute to the image
uc_content_tabs_elementor_10430ec_item2	Cybersecurity Services	img no alt	Add alt attribute to the image
https://vynoxsecurity.com/services/advan…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Advanced Cybersecurity Services
https://vynoxsecurity.com/services/advan…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Advanced Cybersecurity Services
https://vynoxsecurity.com/services/advan…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Advanced Cybersecurity Services
https://vynoxsecurity.com/services/advan…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Advanced Cybersecurity Services
https://vynoxsecurity.com/services/advan…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Advanced Cybersecurity Services
uc_content_tabs_elementor_10430ec_item3	vCISO & MSS Service	img no alt	Add alt attribute to the image
https://vynoxsecurity.com/services/strat…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Strategic Security Advisory Services Vciso
https://vynoxsecurity.com/services/strat…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Strategic Security Advisory Services Vciso
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

65 links and buttons have descriptive text

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

https://vynoxsecurity.com/; https://vynoxsecurity.com/

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

Generic link text like 'click here' doesn't describe the destination.

https://vynoxsecurity.com/services/advanced-cybersecurity-services/ ("Learn more"); https://vynoxsecurity.com/services/advanced-cybersecurity-services/ ("Learn more"); https://vynoxsecurity.com/services/advanced-cybersecurity-services/ ("Learn more"); https://vynoxsecurity.com/services/advanced-cybersecurity-services/ ("Learn more"); https://vynoxsecurity.com/services/advanced-cybersecurity-services/ ("Learn more"); https://vynoxsecurity.com/services/strategic-security-advisory-services-vciso/ ("Learn more"); https://vynoxsecurity.com/services/strategic-security-advisory-services-vciso/ ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

✗ PNG Icons Missing

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

Landmark Structure

Action

6 landmarks

REVIEW

6 landmarks

No <main> landmark found

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

4 <nav> landmark(s) found

2 of 4 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

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

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

1 headings

REVIEW

1 headings

No H1 heading found

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

H2 Start and receive your VAPT in just 7 days powered by AI, validated by experts.

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

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 – Vynox Security ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 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 20 fail WCAG AA

h2 Start and receive your VAPT in just 7 da…

1.00:1

#000000

#000001

needs 3.0:1 (large text)

24px · bottom of viewport

title Vynox Security – Enterprise-Grade Cybe…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

div Vynox Security

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.01:1

#000000

#010206

needs 4.5:1 (normal text)

16px · top of page (header area)

a VynoxSecurity

1.02:1

#000000

#02040A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Who We Are?

1.02:1

#000000

#02040A

needs 4.5:1 (normal text)

16px · above the fold

a Services

1.02:1

#000000

#02040A

needs 4.5:1 (normal text)

16px · above the fold

a VAPT

1.02:1

#000000

#02040A

needs 4.5:1 (normal text)

16px · above the fold

a vCISO

1.03:1

#000000

#03050B

needs 4.5:1 (normal text)

16px · above the fold

a Cybersecurity

1.03:1

#000000

#03050B

needs 4.5:1 (normal text)

16px · above the fold

a Partners

1.03:1

#000000

#03050B

needs 4.5:1 (normal text)

16px · above the fold

a Career

1.03:1

#000000

#03050B

needs 4.5:1 (normal text)

16px · above the fold

a Who We Are?

1.03:1

#000000

#03050B

needs 4.5:1 (normal text)

16px · above the fold

a Services

1.03:1

#000000

#03050B

needs 4.5:1 (normal text)

16px · above the fold

a VAPT

1.03:1

#000000

#03050B

needs 4.5:1 (normal text)

16px · mid-page

a vCISO

1.03:1

#000000

#03050B

needs 4.5:1 (normal text)

16px · mid-page

a Cybersecurity

1.03:1

#000000

#03050B

needs 4.5:1 (normal text)

16px · mid-page

a Partners

1.04:1

#000000

#02070D

needs 4.5:1 (normal text)

16px · mid-page

a Career

1.04:1

#000000

#02070E

needs 4.5:1 (normal text)

16px · mid-page

span Get Started

1.03:1

#000000

#02050B

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Start and receive yo…	1.00:1	3.0:1	#000000	#000001	Fail
title Vynox Security – E…	1.00:1	4.5:1	#000000	#000000	Fail
div Vynox Security	1.00:1	4.5:1	#000000	#000000	Fail
a Skip to content	1.01:1	4.5:1	#000000	#010206	Fail
a VynoxSecurity	1.02:1	4.5:1	#000000	#02040A	Fail
a Who We Are?	1.02:1	4.5:1	#000000	#02040A	Fail
a Services	1.02:1	4.5:1	#000000	#02040A	Fail
a VAPT	1.02:1	4.5:1	#000000	#02040A	Fail
a vCISO	1.03:1	4.5:1	#000000	#03050B	Fail
a Cybersecurity	1.03:1	4.5:1	#000000	#03050B	Fail
a Partners	1.03:1	4.5:1	#000000	#03050B	Fail
a Career	1.03:1	4.5:1	#000000	#03050B	Fail
a Who We Are?	1.03:1	4.5:1	#000000	#03050B	Fail
a Services	1.03:1	4.5:1	#000000	#03050B	Fail
a VAPT	1.03:1	4.5:1	#000000	#03050B	Fail
a vCISO	1.03:1	4.5:1	#000000	#03050B	Fail
a Cybersecurity	1.03:1	4.5:1	#000000	#03050B	Fail
a Partners	1.04:1	4.5:1	#000000	#02070D	Fail
a Career	1.04:1	4.5:1	#000000	#02070E	Fail
span Get Started	1.03:1	4.5:1	#000000	#02050B	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.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 27 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.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.uc-tabs-accordion-title > div.ue-graphic-element > span.ue-ge-icon > img `div.uc-tabs-accordion-title > div.ue-graphic-element > span.ue-ge-icon > img`
div.uc-tabs-accordion-title > div.ue-graphic-element > span.ue-ge-icon > img `div.uc-tabs-accordion-title > div.ue-graphic-element > span.ue-ge-icon > img`
div.uc-tabs-accordion-title > div.ue-graphic-element > span.ue-ge-icon > img `div.uc-tabs-accordion-title > div.ue-graphic-element > span.ue-ge-icon > img`

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to content `body.home > a.skip-link`

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.

○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

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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

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

○No form fields have multiple labels

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

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

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

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