Accessibility

D

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 ✗

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 2 <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

Mobile Keyboard & Autofill

Action

2/4 eligible field(s) missing autocomplete or inputmode

REVIEW

2/4 eligible field(s) missing autocomplete or inputmode

2 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">, <input type="tel" name="phone">

B

Tabindex Anti-Patterns

0 positive, 4 -1-on-focusable

REVIEW

0 positive, 4 -1-on-focusable

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

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

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

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>

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

B

Mobile-Readable Font Sizes

92% of visible text renders at >= 12 CSS px (21 below threshold)

REVIEW

92% of visible text renders at >= 12 CSS px (21 below threshold)

21 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> 11.5px ("Featured service"); <span> 10.5px ("Text"); <span> 10.5px ("Image"); <span> 10.5px ("Background"); <span> 11.0px ("Fri · Oct").

C

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title This Page Does Not Exist ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

B

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

B

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: Vendix Designs

192x192 icon present

512x512 icon present

PWA Install Criteria Not Installable

Name Vendix Designs ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode browser ✗

Name Vendix Designs Display Mode browser Theme Color #0E0F11 Background Color #0E0F11 Icons 2 icon(s)

B

PWA Depth

2 PWA signal(s) surfaced

REVIEW

2 PWA signal(s) surfaced

Manifest declares display="browser" -- no PWA UX

When `display` is `browser` (or unset, which is the spec default), the installed app opens in a regular browser tab -- no install prompt, no standalone window, no app-shell experience. The intended values for a PWA are `standalone` (most common; full-screen, no browser chrome) or `fullscreen` (games / immersive apps). `minimal-ui` is a middle ground (basic browser controls but no address bar).

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

B

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color #f5f5f7 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+

Landmark Structure

14 landmarks

PASS

14 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

A+

Heading Hierarchy

44 headings

PASS

44 headings

Single H1 present

H1 Smart Digital Solutions
H2 Tools & platforms we work with
H2 Made to be seen.
H3 A dental clinic, online in 3 languages.
H3 An association site in English, Romanian & Arabic.
H3 The booking app, explained in 45 seconds.
H3 A booking system, with its guide in 3 languages.
H3 A glass digital business card.
H3 Our services profile, in Arabic & Romanian.
H2 Everything your business needs. In one place.
H3 Web Design
H3 Graphic Design
H3 Web Apps
H3 Branding
H3 Social Media Management
H3 Content Creation
H3 Digital Products
H3 Motion Graphics
H3 Digital Marketing & Ads
H3 SEO
H3 Google Business Profile
H2 Four steps from idea to launch.
H3 We understand your idea
H3 We plan & propose
H3 We design & build
H3 We deliver & support
H2 Because we build digital solutions tailored to your business.
H3 Premium quality
H3 On time
H3 Easy communication
H3 Ongoing support
H2 Tell us what you need.
H2 Questions, answered.
H3 How long does a website take?
H3 Do you offer support after launch?
H3 Can you redesign my existing website?
H3 Do you work in Arabic, Romanian and English?
H3 Is the first consultation free?
H2 Ready to start your project?Book your free consultation.
H2 Explore
H2 Contact
H2 Follow us
H3 Vendix Designs
H4 What's included

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 11 images OK

PASS

All 11 images OK

2 decorative image(s) correctly marked

9 image(s) with good alt text

11 images 9 good alt text 2 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 15 controls labeled

PASS

All 15 controls labeled

15 control(s) properly labeled

15 controls

15 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
services[]	checkbox		none
services[]	checkbox		none
services[]	checkbox		none
services[]	checkbox		none
services[]	checkbox		none
services[]	checkbox		none
services[]	checkbox		none
services[]	checkbox		none
services[]	checkbox		none
services[]	checkbox		none
services[]	checkbox		none
name	text	Your name	none
email	email	Email	none
phone	tel	Phone / WhatsApp (optional)	none
#sfIdea	textarea	Your idea	none

A

Link & Button Quality

33 links, 43 buttons — all OK

PASS

33 links, 43 buttons — all OK

7 link(s) open in new tab without warning

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

Got: https://virtual-card-abdou.vercel.app/; https://wa.me/40728596410?text=Hi%20Vendix%2C%20I'd%20like%20to%20start%20a%2…; https://www.facebook.com/vendixdesign; https://wa.me/40728596410; https://www.facebook.com/vendixdesign; https://www.facebook.com/vendixdesign; https://wa.me/40728596410

26 link(s) with descriptive text

33 links

0 empty

0 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://virtual-card-abdou.vercel.app/	Try the live card	new tab	Add '(opens in new tab)' to text
https://wa.me/40728596410?text=Hi%20Vend…	Message us on WhatsApp	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/vendixdesign	Facebookfacebook.com/vendixdes…	new tab	Add '(opens in new tab)' to text
https://wa.me/40728596410	+40 728 596 410	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/vendixdesign	facebook.com/vendixdesign	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/vendixdesign	Facebook	new tab	Add '(opens in new tab)' to text
https://wa.me/40728596410	Ask on WhatsApp	new tab	Add '(opens in new tab)' to text

69 links and buttons have descriptive text

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

https://virtual-card-abdou.vercel.app/; https://wa.me/40728596410?text=Hi%20Vendix%2C%20I'd%20like%20to%20start%20a%2…; https://www.facebook.com/vendixdesign; https://wa.me/40728596410; https://www.facebook.com/vendixdesign; https://www.facebook.com/vendixdesign; https://wa.me/40728596410

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

15 form control(s) checked, no type mismatches

PASS

15 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

15 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

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 UX Depth

2 mobile-depth signal(s) detected

PASS

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

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

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 Digital Solutions	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Tools & platforms we…	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Made to be seen.	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Everything your busi…	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Four steps from idea…	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Because we build dig…	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Tell us what you nee…	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Questions, answered.	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Explore	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Contact	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h2 Follow us	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h3 A dental clinic, onl…	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h3 An association site …	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h3 The booking app, exp…	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h3 A booking system, wi…	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h3 A glass digital busi…	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h3 Our services profile…	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h3 Web Design	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h3 Graphic Design	19.29:1	3.0:1	#000000	#F5F5F7	Pass
h3 Web Apps	19.29:1	3.0:1	#000000	#F5F5F7	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 100/100 — 0 failing, 29 passed

PASS

100

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.

○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

●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

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

●Background and foreground colors have a sufficient contrast ratio

●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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

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