Accessibility

D

Landmark Structure

Action

17 landmarks

FIX

17 landmarks

No <main> landmark found

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

17 <nav> landmark(s) found

1 of 17 <nav> elements are unlabeled

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

No banner (header) landmark

No contentinfo (footer) 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

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

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

F

Heading Hierarchy

Action

82 headings, 17 skip(s)

FIX

82 headings, 17 skip(s)

Multiple H1 headings (15 found)

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

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H5 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

2 empty heading(s)

Empty headings appear in the document outline but provide no information.

H4 Featured Offer: AI Accelerators
H4 Capabilities
H4 Industry Expertise
H4 Discover Our Benefits & Values
H4 Featured Offer: AI Accelerators
H4 Capabilities
H4 Industry Expertise
H4 Discover Our Benefits & Values
H1 Technology doesn’t create stability. It reveals it.
H1 Impose order. Then scale with confidence. duplicate H1
H5 Capital Markets skipped
H1 Compliance risk doesn’t spike. It accumulates. duplicate H1
H5 Capital Markets skipped
H1 Compliance costs rise with complexity duplicate H1
H5 Capital Markets skipped
H1 Risk is reduced where operations are defined duplicate H1
H5 Mortgage skipped
H1 Most inefficiency in mortgage operations is built into the process duplicate H1
H5 Mortgage skipped
H1 Throughput is not the same as progress duplicate H1
H5 Mortgage skipped
H1 Friction is reduced where the process is defined duplicate H1
H5 QSR & Hospitality skipped
H1 Downtime is driven by response, not failure duplicate H1
H5 QSR & Hospitality skipped
H1 More vendors do not mean faster resolution duplicate H1
H5 QSR & Hospitality skipped
H1 One system. One owner. duplicate H1
H5 Medical Device & Healthcare skipped
H1 As you scale, operations become the bottleneck duplicate H1
H5 Medical Device & Healthcare skipped
H1 Support is an operational system, not a function duplicate H1
H5 Medical Device & Healthcare skipped
H1 Stand up a complete support system without rebuilding it duplicate H1
H1 Solutions That Accelerate Growth duplicate H1
H2 Deep Industry Expertise
H4 Capital Markets skipped
H4 Credit Card & Payments
H4 Insurance
H4 Mortgage
H4 Med Device Manufacturing
H4 Multi-Unit Retail & QSRs
H2 Built on Experience, Driven by Innovation
H3 Setting the Standard for Success
H3 Clarity Where It Counts
H3 Discover What’s Possible
H2 Accelerate AI Adoption
H2 (empty)
H2 Meet GENIX Accelerate
H4 Innovation & Agility skipped
H4 Privacy & Governance
H4 Security & Resilience
H4 Efficiency & Competitive Edge
H2 The Power of Right-Shoring
H4 Seamless Expertise Across the Globe skipped
H4 Strategic Solutions Anywhere, Anytime
H4 Driving Success with a Global Mindset
H2 Our Capabilities
H4 Category Tabs skipped
H4 Cloud
H4 Artificial Intelligence
H4 Cybersecurity
H4 Applications
H4 Data Analytics
H4 Business Process Optimization
H4 Professional Talent Solutions
H2 Cloud
H2 Artificial Intelligence
H2 Cybersecurity
H2 Applications
H2 Data & Analytics
H2 Business Process Optimization
H2 Professional Talent Solutions
H3 Achieve More with Solugenix
H2 Why Clients Love Us
H2 Strategic Insights, Superior Outcomes
H3 (empty)
H2 Partnerships & Certifications
H4 About Solugenix → skipped
H4 Solugenix Careers →
H3 Ready to learn more?
H3 Schedule a Consultation

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

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 Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

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.

D

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.

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

No navigation patterns

FIX

No navigation patterns

17 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Search

Skip Link

Labeled Navigation 17 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

C

Link & Button Quality

Action

22 issue(s) across 235 links and 24 buttons

REVIEW

22 issue(s) across 235 links and 24 buttons

19 link(s) with no accessible text

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

Got: a (#70 on page); #; https://www.solugenix.com/capital-markets?hsLang=en; https://www.solugenix.com/payments?hsLang=en; https://www.solugenix.com/insurance?hsLang=en; https://www.solugenix.com/mortgage?hsLang=en; https://www.solugenix.com/medical-device-manufacturing?hsLang=en; https://www.solugenix.com/multi-unit-retail?hsLang=en; https://blog.solugenix.com/ai-already-shaping-hiring-decisions-most-policies-…; https://blog.solugenix.com/rising-gas-prices-are-exposing-the-real-problem-in… (+9 more)

3 link(s) with generic text

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

Got: https://blog.solugenix.com/ai-already-shaping-hiring-decisions-most-policies-… ("Read more"); https://blog.solugenix.com/rising-gas-prices-are-exposing-the-real-problem-in… ("Read more"); https://blog.solugenix.com/ai-guardrails-safe-innovation-qsr-operations ("Read more")

213 link(s) with descriptive text

235 links

19 empty

3 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
https://www.solugenix.com/capital-market…	(empty)	empty	Add link text or aria-label
https://www.solugenix.com/payments?hsLan…	(empty)	empty	Add link text or aria-label
https://www.solugenix.com/insurance?hsLa…	(empty)	empty	Add link text or aria-label
https://www.solugenix.com/mortgage?hsLan…	(empty)	empty	Add link text or aria-label
https://www.solugenix.com/medical-device…	(empty)	empty	Add link text or aria-label
https://www.solugenix.com/multi-unit-ret…	(empty)	empty	Add link text or aria-label
https://blog.solugenix.com/ai-already-sh…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Ai Already Shaping Hiring Decisions Most Policies Havent Caught Up
https://blog.solugenix.com/ai-already-sh…	(empty)	empty	Add link text or aria-label
https://blog.solugenix.com/rising-gas-pr…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Rising Gas Prices Are Exposing The Real Problem In Food Delivery
https://blog.solugenix.com/rising-gas-pr…	(empty)	empty	Add link text or aria-label
https://blog.solugenix.com/ai-guardrails…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Ai Guardrails Safe Innovation Qsr Operations
https://blog.solugenix.com/ai-guardrails…	(empty)	empty	Add link text or aria-label
https://about.solugenix.com?hsLang=en	(empty)	empty	Add link text or aria-label
https://careers.solugenix.com?hsLang=en	(empty)	empty	Add link text or aria-label
https://www.facebook.com/297000626456	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/3758114	(empty)	empty	Add link text or aria-label
https://twitter.com/solugenix	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/solugen…	(empty)	empty	Add link text or aria-label
https://twitter.com/solugenix	(empty)	empty	Add link text or aria-label
https://www.youtube.com/user/solugenix	(empty)	empty	Add link text or aria-label

237 links and buttons have descriptive text

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

a (#70 on page); #; https://www.solugenix.com/capital-markets?hsLang=en; https://www.solugenix.com/payments?hsLang=en; https://www.solugenix.com/insurance?hsLang=en; https://www.solugenix.com/mortgage?hsLang=en; https://www.solugenix.com/medical-device-manufacturing?hsLang=en; https://www.solugenix.com/multi-unit-retail?hsLang=en; https://blog.solugenix.com/ai-already-shaping-hiring-decisions-most-policies-…; https://blog.solugenix.com/rising-gas-prices-are-exposing-the-real-problem-in… (+9 more)

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://blog.solugenix.com/ai-already-shaping-hiring-decisions-most-policies-… ("Read more"); https://blog.solugenix.com/rising-gas-prices-are-exposing-the-real-problem-in… ("Read more"); https://blog.solugenix.com/ai-guardrails-safe-innovation-qsr-operations ("Read 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

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

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

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 Technology doesn’t create stability. I…

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Impose order. Then scale with confidence…

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Compliance risk doesn’t spike. It accu…

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Compliance costs rise with complexity

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Risk is reduced where operations are def…

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Most inefficiency in mortgage operations…

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Throughput is not the same as progress

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Friction is reduced where the process is…

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Downtime is driven by response, not fail…

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

32px · bottom of viewport

h1 More vendors do not mean faster resoluti…

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

32px · bottom of viewport

h1 One system. One owner.

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

32px · bottom of viewport

h1 As you scale, operations become the bott…

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Support is an operational system, not a …

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Stand up a complete support system witho…

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Solutions That Accelerate Growth

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Deep Industry Expertise

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Built on Experience, Driven by Innovatio…

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Accelerate AI Adoption

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Meet GENIX Accelerate

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The Power of Right-Shoring

1.00:1

#000000

on

#000001

needs 3.0:1 (large text)

24px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Technology doesn’t…	1.00:1	3.0:1	#000000	#000001	Fail
h1 Impose order. Then s…	1.00:1	3.0:1	#000000	#000001	Fail
h1 Compliance risk does…	1.00:1	3.0:1	#000000	#000001	Fail
h1 Compliance costs ris…	1.00:1	3.0:1	#000000	#000001	Fail
h1 Risk is reduced wher…	1.00:1	3.0:1	#000000	#000001	Fail
h1 Most inefficiency in…	1.00:1	3.0:1	#000000	#000001	Fail
h1 Throughput is not th…	1.00:1	3.0:1	#000000	#000001	Fail
h1 Friction is reduced …	1.00:1	3.0:1	#000000	#000001	Fail
h1 Downtime is driven b…	1.00:1	3.0:1	#000000	#000001	Fail
h1 More vendors do not …	1.00:1	3.0:1	#000000	#000001	Fail
h1 One system. One owne…	1.00:1	3.0:1	#000000	#000001	Fail
h1 As you scale, operat…	1.00:1	3.0:1	#000000	#000001	Fail
h1 Support is an operat…	1.00:1	3.0:1	#000000	#000001	Fail
h1 Stand up a complete …	1.00:1	3.0:1	#000000	#000001	Fail
h1 Solutions That Accel…	1.00:1	3.0:1	#000000	#000001	Fail
h2 Deep Industry Expert…	1.00:1	3.0:1	#000000	#000001	Fail
h2 Built on Experience,…	1.00:1	3.0:1	#000000	#000001	Fail
h2 Accelerate AI Adopti…	1.00:1	3.0:1	#000000	#000001	Fail
h2 Meet GENIX Accelerat…	1.00:1	3.0:1	#000000	#000001	Fail
h2 The Power of Right-S…	1.00:1	3.0:1	#000000	#000001	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.

B

Lighthouse Accessibility Audits

Score 80/100 — 6 failing, 27 passed

REVIEW

80

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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 `div.row-fluid > div.span12 > ul.nboslick-dots > li#nboslick-slide00`

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Get the foundation right Bring complexity under control `div.industry-panel > div.industry-panel__grid > div.industry-panel__text > div.industry-panel__slide-list`
1 2 3 `div.row-fluid-wrapper > div.row-fluid > div.span12 > ul.nboslick-dots`

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 `div.row-fluid > div.span12 > ul.nboslick-dots > li#nboslick-slide00`

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
“Solugenix has been very responsive. The consistency of your team and the stabi… `div.row-fluid > div.span12 > div.nboslick-list > div.nboslick-track`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Seamless Expertise Across the Globe `div.span9 > div.cell-wrapper > span#hs_cos_wrapper_module_173947397780306 > h4`
About Solugenix → `div.span12 > div.cell-wrapper > span#hs_cos_wrapper_module_164279834167005 > h4`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.hs-rss-module > div.hs-rss-item > div.rss-card > a.full-link `div.hs-rss-module > div.hs-rss-item > div.rss-card > a.full-link`
div.hs-rss-module > div.hs-rss-item > div.rss-card > a.full-link `div.hs-rss-module > div.hs-rss-item > div.rss-card > a.full-link`
div.hs-rss-module > div.hs-rss-item > div.rss-card > a.full-link `div.hs-rss-module > div.hs-rss-item > div.rss-card > a.full-link`
div.span12 > div#hs_cos_wrapper_module_164279834167004 > div.icon-disc > a `div.span12 > div#hs_cos_wrapper_module_164279834167004 > div.icon-disc > a`
div.span12 > div#hs_cos_wrapper_module_164279834167008 > div.icon-disc > a `div.span12 > div#hs_cos_wrapper_module_164279834167008 > div.icon-disc > a`
div.cell-wrapper > span#hs_cos_wrapper_module_399635143 > div > a.fm_button `div.cell-wrapper > span#hs_cos_wrapper_module_399635143 > div > a.fm_button`
div.cell-wrapper > span#hs_cos_wrapper_module_399635143 > div > a.fm_button `div.cell-wrapper > span#hs_cos_wrapper_module_399635143 > div > a.fm_button`
div.cell-wrapper > span#hs_cos_wrapper_module_399635143 > div > a.fm_button `div.cell-wrapper > span#hs_cos_wrapper_module_399635143 > div > a.fm_button`
div > div.hs_cos_wrapper_type_follow_me > div > a.fm_button `div > div.hs_cos_wrapper_type_follow_me > div > a.fm_button`
div > div.hs_cos_wrapper_type_follow_me > div > a.fm_button `div > div.hs_cos_wrapper_type_follow_me > div > a.fm_button`
div > div.hs_cos_wrapper_type_follow_me > div > a.fm_button `div > div.hs_cos_wrapper_type_follow_me > div > a.fm_button`

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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]`s are contained by their required parent element

●`[role]` values are valid

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

●Buttons have an accessible name

●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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●ARIA toggle fields have accessible names

●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 are distinguishable without relying on color.

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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 `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

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○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 82 heading(s) have substantive, well-formed text

PASS

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

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

A+

Alt Text Quality

All 52 images OK

PASS

All 52 images OK

1 image(s) with alt text over 125 characters

51 image(s) with good alt text

52 images 51 good alt text

Issue	Count
too long	1 image(s)

A

Form Accessibility

1 of 6 controls have issues

PASS

1 of 6 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="submit">

5 control(s) properly labeled

6 controls

5 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#firstname-c29c2375-e8d3-429a-a89c-f0cf725b206e_1059	text	First Name*	for/id
#lastname-c29c2375-e8d3-429a-a89c-f0cf725b206e_1059	text	Last Name*	for/id
#email-c29c2375-e8d3-429a-a89c-f0cf725b206e_1059	email	Work Email*	for/id
#phone-c29c2375-e8d3-429a-a89c-f0cf725b206e_1059	tel	Phone Number*	for/id
#what_is_your_biggest_challenge_-c29c2375-e8d3-429a-a89c-f0cf725b206e_1059	text	What is your biggest challenge?	for/id
input	submit	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A+

Form Input Types

6 form control(s) checked, no type mismatches

PASS

6 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

All 3 eligible field(s) carry autocomplete/inputmode

PASS

All 3 eligible field(s) carry autocomplete/inputmode

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

8 explicit tabindex attribute(s) checked, no anti-patterns

PASS

8 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A

Iframe Accessibility

1/5 iframe(s) missing title; 0 placeholder(s)

PASS

1/5 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

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 12 visible text node(s) render at >= 12 CSS pixels

PASS

All 12 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

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.