Skip to content
http://nexpixelhub.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
4
REVIEW
7
PASS
13
INFO
0
Checks
24
13 PASS 7 REVIEW 4 FIX
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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Form Accessibility
3 of 10 controls have issues
REVIEW
3 of 10 controls have issues
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="npx-lead-name">; <input type="text" id="npx-lead-contact">; <input type="text" id="npx-chat-input">
Info::
7 control(s) properly labeled
10 controls
7 labeled
3 placeholder only
0 unlabeled
ControlTypeLabelMethod
#e-form-first-nametextFirst namefor/id
#e-form-last-nametextLast namefor/id
#e-form-emailemailEmailfor/id
#e-form-messagetextareaMessagefor/id
#e-form-checkboxcheckboxCheckboxfor/id
#form-field-emailemailEmailfor/id
#form-field-field_a13498etelMobile Nofor/id
#npx-chat-inputtext(Type or tap an option above…)placeholder only
#npx-lead-nametext(Your name)placeholder only
#npx-lead-contacttext(Phone or email)placeholder only

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

<input type="text" id="npx-lead-name">; <input type="text" id="npx-lead-contact">; <input type="text" id="npx-chat-input">

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

C
Tabindex Anti-Patterns
Action
0 positive, 7 -1-on-focusable
REVIEW
0 positive, 7 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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
Tap Target Adequacy
3 tap target(s) too small or too close together
REVIEW
3 tap target(s) too small or too close together
Info::
3 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.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found - nexpixelhub.com ✓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
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
h1 Turn Digital Attention
1.06:1
#000000
on
#050B10
needs 3.0:1 (large text)
32px · mid-page
h1 Into Business Growth.
1.19:1
#000000
on
#071B23
needs 3.0:1 (large text)
32px · mid-page
h2 Digital Marketing
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Graphic Design
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Website Design & Development
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Social Media Management
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Digital Marketing
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Graphic Design
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Website Design & Development
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Social Media Management
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 CORE SERVICES BY NEXPIXEL
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 DIGITAL MARKETING-PREMIUM
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 DIGITAL MARKETING-GROWTH
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 DIGITAL MARKETING-STARTER
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 SOCIAL MEDIA MANAGEMENT-PREMIUM
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ABOUT NEXPIXEL
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Nexpixel Hub brings digital marketing, c…
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ABOUT NEXPIXEL
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Nexpixel Hub brings digital marketing, c…
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Frequently Asked Questions
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Turn Digital Attenti…1.06:13.0:1
#000000
#050B10
Fail
h1 Into Business Growth…1.19:13.0:1
#000000
#071B23
Fail
h2 Digital Marketing1.07:13.0:1
#000000
#0B0B0B
Fail
h2 Graphic Design1.07:13.0:1
#000000
#0B0B0B
Fail
h2 Website Design & Dev…1.07:13.0:1
#000000
#0B0B0B
Fail
h2 Social Media Managem…1.07:13.0:1
#000000
#0B0B0B
Fail
h2 Digital Marketing1.07:13.0:1
#000000
#0B0B0B
Fail
h2 Graphic Design1.07:13.0:1
#000000
#0B0B0B
Fail
h2 Website Design & Dev…1.07:13.0:1
#000000
#0B0B0B
Fail
h2 Social Media Managem…1.07:13.0:1
#000000
#0B0B0B
Fail
h2 CORE SERVICES BY NEX…1.07:13.0:1
#000000
#0B0B0B
Fail
h2 DIGITAL MARKETING-PR…1.07:13.0:1
#000000
#0B0B0B
Fail
h2 DIGITAL MARKETING-GR…1.07:13.0:1
#000000
#0B0B0B
Fail
h2 DIGITAL MARKETING-ST…1.07:13.0:1
#000000
#0B0B0B
Fail
h2 SOCIAL MEDIA MANAGEM…1.07:13.0:1
#000000
#0B0B0B
Fail
h2 ABOUT NEXPIXEL1.07:13.0:1
#000000
#0B0B0B
Fail
h2 Nexpixel Hub brings …1.07:13.0:1
#000000
#0B0B0B
Fail
h2 ABOUT NEXPIXEL1.07:13.0:1
#000000
#0B0B0B
Fail
h2 Nexpixel Hub brings …1.07:13.0:1
#000000
#0B0B0B
Fail
h2 Frequently Asked Que…1.07:13.0:1
#000000
#0B0B0B
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
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Menu" MAIN CONTENTINFO footer

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

A
Heading Hierarchy
34 headings, 1 skip(s)
PASS
34 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Turn Digital Attention  Into Business Growth.
  • H2 Digital Marketing
  • H2 Graphic Design
  • H2 Website Design & Development
  • H2 Social Media Management
  • H2 Digital Marketing
  • H2 Graphic Design
  • H2 Website Design & Development
  • H2 Social Media Management
  • H2 CORE SERVICES BY NEXPIXEL
  • H2 DIGITAL MARKETING-PREMIUM
  • H2 DIGITAL MARKETING-GROWTH
  • H2 DIGITAL MARKETING-STARTER
  • H2 SOCIAL MEDIA MANAGEMENT-PREMIUM
  • H2 ABOUT NEXPIXEL
  • H2 Nexpixel Hub brings digital marketing, creative design, website development and social media management together under one connected strategy.
  • H2 ABOUT NEXPIXEL
  • H2 Nexpixel Hub brings digital marketing, creative design, website development and social media management together under one connected strategy.
  • H2 Our Approach
  • H3 Understand → Strategize → Create → Launch → Measure → Optimize
  • H3 VISIBILITY
  • H3 ENGAGEMENT
  • H3 CONVERSIONS & GROWTH
  • H2 Frequently Asked Questions
  • H2 What does NEXPIXEL HUB do?
  • H2 What services does NEXPIXEL HUB offer?
  • H2 How can NEXPIXEL HUB help my business grow?
  • H2 What is included in NEXPIXEL HUB's digital marketing services?
  • H2 Does NEXPIXEL HUB provide website design and development?
  • H5 let’s talk skipped
  • H4 Your digital presence is about to take off
  • H5 quick links
  • H4 Contact Info
  • H4 join our Newsletter

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

A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
2 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H2: 142 chars - H2: 142 chars
Got: 2 >120-char heading(s)
Info::
10 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 10 all-caps heading(s)
A+
Alt Text Quality
All 19 images OK
PASS
All 19 images OK
Info::
4 decorative image(s) correctly marked
Info::
15 image(s) with good alt text
19 images 15 good alt text 4 decorative
All images have appropriate alt text.
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "npx-lead-contact" should use type="email" (currently type="text")
Field name "npx-lead-contact" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
A+
Form Input Quality
10 form control(s) checked, no input-semantic issues
PASS
10 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
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+
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 132 visible text node(s) render at >= 12 CSS pixels
PASS
All 132 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
Lighthouse Accessibility Audits
Score 93/100 — 3 failing, 28 passed
PASS
93

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
Social Media Management div.deensimc-marquee-track-wrapper > div.deensimc-marquee-track > div.deensimc-text-wrapper > h2.deensimc-scroll-text
Graphic Design div.deensimc-marquee-track-wrapper > div.deensimc-marquee-track > div.deensimc-text-wrapper > h2.deensimc-scroll-text
Website Design & Development div.deensimc-marquee-track-wrapper > div.deensimc-marquee-track > div.deensimc-text-wrapper > h2.deensimc-scroll-text
Social Media Management div.deensimc-marquee-track-wrapper > div.deensimc-marquee-track > div.deensimc-text-wrapper > h2.deensimc-scroll-text

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
Your digital presence is about to take off div.elementor-element > div.e-con-inner > div.elementor-element > h4.elementor-heading-title

These are opportunities to improve keyboard navigation in your application.

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
Go to slide 1 div.elementor-element > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.elementor-element > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.elementor-element > div.elementor-main-swiper > div.swiper-pagination > span.swiper-pagination-bullet

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
●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.
●`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
●Elements with the `role=text` attribute do not have focusable descendents.
●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
●No element has a `[tabindex]` value greater than 0
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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
○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.
○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.

Send Feedback