Public accessibility assessment

Accessibility issues detected on legenesis.com

Evolize inspected 5 public pages on legenesis.com and detected 69 automatically identifiable accessibility findings.

69Findings detected
4WCAG criteria affected
5Pages inspected
5 Sep 2026Assessment date

Highest detected severity: High · 2 high-priority findings · 100% inspected-page coverage

Most widespread issueHidden elements can still receive keyboard focusDetected on 5 inspected pages
Most affected page/contact35 findings detected
Most represented WCAG criterionWCAG 1.4.3 — Contrast (Minimum)58 detected findings

Is legenesis.com your website?

Keep this assessment current and get notified when new accessibility issues are detected.

https://

Not your website? Scan your own site →

01 · Accessibility summary

Evolize inspected 5 public pages on legenesis.com and detected 69 accessibility findings. The most widespread issue was "Hidden elements can still receive keyboard focus", detected on 5 inspected pages. The most affected inspected page was "/contact", where 35 findings were detected. The assessment identified findings mapped to 4 WCAG success criterions. The sections below prioritize the broadest issues and provide technical evidence for each detected finding.

02 · Start here

These findings combine the highest severity and broadest reach detected during this assessment.

  1. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 5 inspected pages · 20 instances
    Why this matters

    An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

    Recommended action

    To fix this issue, ensure that the hidden element is removed from the tab order by setting its 'tabindex' attribute to '-1' or by using the 'display: none' or 'visibility: hidden' CSS properties to completely hide it. Alternatively, make the element visible when it receives focus.

    View technical evidence →
  2. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 5 inspected pages · 5 instances
    Why this matters

    An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

    Recommended action

    To fix this issue, ensure that the hidden element is removed from the tab order by setting its 'tabindex' attribute to '-1' or by using 'display: none' instead of 'visibility: hidden' to completely hide it. Alternatively, make the element visible when it receives focus.

    View technical evidence →
  3. Medium

    Text has insufficient colour contrast

    WCAG 1.4.3 (AA) · 5 inspected pages · 38 instances
    Why this matters

    Text and background colours do not meet the minimum contrast ratio, reducing legibility.

    Recommended action

    Increase the contrast between the text color and background color of the 'Join Us' link to meet the minimum contrast ratio thresholds. Consider using a color contrast analyzer tool to determine the optimal colors.

    View technical evidence →
  4. Medium

    Touch targets are too small on mobile

    WCAG 2.5.8 (AA) · 5 inspected pages · 30 instances
    Why this matters

    Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

    Recommended action

    Increase the touch target size of the interactive element to at least 24x24 pixels to make it easier for users to activate by touch on mobile devices. Consider adding padding to the element or its container to achieve the minimum size requirement.

    View technical evidence →
  5. Medium

    Text has insufficient colour contrast

    WCAG 1.4.3 (AA) · 5 inspected pages · 30 instances
    Why this matters

    Text and background colours do not meet the minimum contrast ratio, reducing legibility.

    Recommended action

    Increase the contrast between the text color and the background color to meet the minimum contrast ratio thresholds as defined in WCAG 2.1 SC 1.4.3. Consider using a color contrast analyzer tool to determine the optimal colors. For the given element, try adjusting the 'text-chalk' class or the background color to improve readability.

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
1.4.3Contrast (Minimum)AA5855 / 5
2.5.8Target Size (Minimum)AA855 / 5
2.4.3Focus OrderA255 / 5
2.4.1Bypass BlocksA155 / 5

Absence of a criterion here does not indicate conformance with it — only that no automatically detectable issue was found for it.

Continuous monitoring

A scan shows today's exposure. Monitoring shows what changes next.

Evolize continuously reassesses public website pages, detects newly introduced or recurring accessibility findings, and tracks remediation over time.

04 · All detected findings

High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)25 instances5 inspected pages

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Why it matters

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Recommended correction

To fix this issue, ensure that the hidden element is removed from the tab order by setting its 'tabindex' attribute to '-1' or by using 'display: none' instead of 'visibility: hidden' to completely hide it. Alternatively, make the element visible when it receives focus.

View 25 affected elements
Component · Ref 7VWBMT
Affected pagehttps://legenesis.com/
Elementhtml > body > nav > div > div:nth-of-type(2) > a
Accessible nameLet's Talk
Markup
<a class="btn btn-sm" href="/contact">Let's Talk</a>
Affected pages/ /services/government /contact /services /about
Component · Ref O1U1YA
Affected pagehttps://legenesis.com/
Elementnav > div > div:nth-of-type(1) > div:nth-of-type(1) > span > a
Accessible nameWho We Are
Markup
<a class="font-display text-[13px] font-bold uppercase tracking-[0.10em] text-bone no-underline transition-colors hover:text-emerald-bright" href="/about">Who We Are</a>
Affected pages/ /services/government /contact /services /about
Medium

Text has insufficient colour contrast

WCAG 1.4.3 (AA)313 instances5 inspected pages

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Why it matters

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Recommended correction

Increase the contrast between the text color and the background color to meet the minimum contrast ratio thresholds as defined in WCAG 2.1 SC 1.4.3. Consider using a color contrast analyzer tool to determine the optimal colors. For the given element, try adjusting the 'text-chalk' class or the background color to improve readability.

View 313 affected elements
Component · Ref K8KNV0
Affected pagehttps://legenesis.com/
Element.text-base.text-chalk[href$="about"]
Accessible nameWho We Are
Markup
<a class="font-display text-base font-bold text-chalk no-underline transition-colors hover:text-emerald-bright" href="/about">Who We Are</a>
Affected pages/ /services/government /contact /services /about
Component · Ref KOT9E4
Affected pagehttps://legenesis.com/
Element.tracking-tag.text-base.text-chalk
Accessible nameLEGENESIS
Markup
<span class="font-display text-base font-bold tracking-tag text-chalk">LEGENESIS</span>
Affected pages/ /services/government /contact /services /about
Component · Ref WO73V2
Affected pagehttps://legenesis.com/
Element.max-w-md
Accessible nameNotes on ServiceNow delivery and public sector work.
Markup
<p class="max-w-md text-sm leading-relaxed text-ash">Notes on ServiceNow delivery and public sector work.</p>
Affected pages/ /services/government /contact /services /about
Component · Ref D8PN7G
Affected pagehttps://legenesis.com/
Element.max-w-xs
Accessible nameLegendary Outcomes. Every Client.
Markup
<p class="max-w-xs text-sm leading-relaxed text-ash">Legendary Outcomes. Every Client.</p>
Affected pages/ /services/government /contact /services /about
Component · Ref YUKKUQ
Affected pagehttps://legenesis.com/
Elementa[href$="careers"]
Accessible nameJoin Us
Markup
<a class="text-ash no-underline transition-colors hover:text-emerald-bright" href="/careers">Join Us</a>
Affected pages/ /services/government /contact /services /about
Component · Ref JN46WF
Affected pagehttps://legenesis.com/
Element.mt-3
Accessible nameOccasional updates on what we are building. No spam, and you can unsubscribe at any time.
Markup
<p class="mt-3 text-xs leading-relaxed text-ash">Occasional updates on what we are building. No spam, and you can unsubscribe at any time.</p>
Affected pages/ /services/government /contact /services /about
Component · Ref SYVXK7
Affected pagehttps://legenesis.com/
Elementbutton[aria-label="Who We Are menu"]
Accessible nameWho We Are menu
Markup
<button type="button" aria-label="Who We Are menu" aria-expanded="false" class="text-[9px] text-bone transition-transform hover:text-emerald-bright ">▼</button>
Affected pages/ /services/government /contact /services /about
Component · Ref R1OEIQ
Affected pagehttps://legenesis.com/
Element.tracking-tag.text-\[15px\].text-chalk
Accessible nameLEGENESIS
Markup
<span class="font-display text-[15px] font-bold tracking-tag text-chalk">LEGENESIS</span>
Affected pages/ /contact /services /about
Component · Ref YYBPYV
Affected pagehttps://legenesis.com/
Element.md\:hidden
Accessible nameOpen menu
Markup
<button class="text-emerald-bright md:hidden" aria-label="Open menu" aria-expanded="false">☰</button>
Affected pages/ /services/government /services /about
Component · Ref QJK2E4
Affected pagehttps://legenesis.com/
Element.tracking-\[0\.10em\].text-\[13px\][href$="about"]
Accessible nameWho We Are
Markup
<a class="font-display text-[13px] font-bold uppercase tracking-[0.10em] text-bone no-underline transition-colors hover:text-emerald-bright" href="/about">Who We Are</a>
Affected pages/ /contact /services /about
Component · Ref B677KS
Affected pagehttps://legenesis.com/contact
Elementh1
Accessible nameLet's Talk
Markup
<h1 class="mb-4 font-display text-[clamp(34px,6vw,58px)] font-bold">Let's Talk</h1>
Affected pages/contact /services /about
Component · Ref DB9TAI
Affected pagehttps://legenesis.com/
Element.tag-dim
Accessible name© 2026 Legenesis
Markup
<span class="tag-dim">© <!-- -->2026<!-- --> Legenesis</span>
Affected pages/ /services /about
Component · Ref ZRNBWK
Affected pagehttps://legenesis.com/services
Elementli:nth-child(1) > .no-underline.transition-colors[href$="about"]
Accessible nameOur Story
Markup
<a class="text-ash no-underline transition-colors hover:text-emerald-bright" href="/about">Our Story</a>
Affected pages/services/government /services /about
Component · Ref APQAO9
Affected pagehttps://legenesis.com/services/government
Element.mb-8
Accessible nameTell us the program, the platform, and the timeline. We will tell you honestly whether we are the right fit.
Markup
<p class="mx-auto mb-8 max-w-xl text-ash">Tell us the program, the platform, and the timeline. We will tell you honestly whether we are the right fit.</p>
Affected pages/ /services/government
Component · Ref OBYZDZ
Affected pagehttps://legenesis.com/
Element.no-underline.text-ash[href$="about"]
Accessible nameOur Story
Markup
<a class="text-ash no-underline transition-colors hover:text-emerald-bright" href="/about">Our Story</a>
Affected pages/ /contact
Component · Ref B8JJP4
Affected pagehttps://legenesis.com/contact
Element.max-w-xl
Accessible nameTell us what you are trying to accomplish.
Markup
<p class="max-w-xl text-lg text-bone">Tell us what you are trying to accomplish.</p>
Affected pages/contact /about
Component · Ref IW0Q5Q
Affected pagehttps://legenesis.com/
Element.mb-2
Accessible nameStay in the loop
Markup
<h2 class="mb-2 font-display text-xl font-bold text-chalk">Stay in the loop</h2>
Affected pages/ /about
Component · Ref B9CFXV
Affected pagehttps://legenesis.com/
Element.text-3xl
Accessible nameLegenesis Government & Public Services
Markup
<h2 class="mb-4 font-display text-3xl font-bold">Legenesis Government &amp; Public Services</h2>
Affected pages/ /services
Component · Ref GNI1WR
Affected pagehttps://legenesis.com/contact
Element.relative:nth-child(1) > .gap-1\.5 > .tracking-\[0\.10em\].text-\[13px\].uppercase
Accessible nameWho We Are
Markup
<a class="font-display text-[13px] font-bold uppercase tracking-[0.10em] text-bone no-underline transition-colors hover:text-emerald-bright" href="/about">Who We Are</a>
Affected pages/services/government /contact
Component · Ref RTUYKF
Affected pagehttps://legenesis.com/services
Element.text-lg.leading-relaxed
Accessible nameWe provide end-to-end ServiceNow solutions including platform implementation, cloud migration, workflow automation, and optimization. Our expertise spans ITSM, ITOM, and specialized federal compliance requirements.
Markup
<p class="text-lg leading-relaxed text-ash">We provide end-to-end ServiceNow solutions including platform implementation, cloud migration, workflow automation, and optimization. Our expertise spans ITSM, ITOM, and specialized federal compliance requirements.</p>
Affected pages/services /about
Component · Ref CIJ3IC
Affected pagehttps://legenesis.com/contact
Element.mt-12 > .tag-dim
Accessible name© 2026 Legenesis
Markup
<span class="tag-dim">© <!-- -->2026<!-- --> Legenesis</span>
Affected pages/services/government /contact
Component · Ref XNGJTR
Affected pagehttps://legenesis.com/services/government
Element.text-xl
Accessible nameStay in the loop
Markup
<h2 class="mb-2 font-display text-xl font-bold text-chalk">Stay in the loop</h2>
Affected pages/services/government /contact
Component · Ref Q3K95N
Affected pagehttps://legenesis.com/
Element.text-\[clamp\(15px\,2vw\,17px\)\]
Accessible nameLegendary is a deliberately high bar. It means an implementation that still works a year after we leave, configuration your own team can maintain without calling us, and honest scoping up front, including telling you when a requirement does not need us at all.
Markup
<p class="mt-5 max-w-xl text-[clamp(15px,2vw,17px)] leading-[1.65] text-ash">
Component · Ref IHDFG3
Affected pagehttps://legenesis.com/services
Element.mb-12 > div > .text-xl
Accessible nameStay in the loop
Markup
<h2 class="mb-2 font-display text-xl font-bold text-chalk">Stay in the loop</h2>
Component · Ref KNNY4U
Affected pagehttps://legenesis.com/
Element.items-start.gap-2\.5.flex:nth-child(1) > .mt-\[3px\].text-emerald-bright
Accessible name
Markup
<span class="mt-[3px] text-emerald-bright">▸</span>

Showing 25 representative examples · 33 more affected elements not shown

Medium

Touch targets are too small on mobile

WCAG 2.5.8 (AA)56 instances5 inspected pages

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Why it matters

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Recommended correction

Increase the touch target size of the interactive element to at least 24x24 pixels to make it easier for users to activate by touch on mobile devices. Consider adding padding to the element or its container to achieve the minimum size requirement.

View 56 affected elements
Component · Ref TXRIXD
Affected pagehttps://legenesis.com/
Elementdiv > div:nth-of-type(2) > div:nth-of-type(2) > ul > li:nth-of-type(1) > a
Accessible nameOur Story
Markup
<a class="text-ash no-underline transition-colors hover:text-emerald-bright" href="/about">Our Story</a>
Affected pages/ /services/government /contact /services /about
Component · Ref SOHPVQ
Affected pagehttps://legenesis.com/
Elementhtml > body > nav > div > button
Accessible nameOpen menu
Markup
<button class="text-emerald-bright md:hidden" aria-label="Open menu" aria-expanded="false">☰</button>
Affected pages/ /services/government /contact /services /about
Component · Ref QCB3G8
Affected pagehttps://legenesis.com/
Elementfooter > div > div:nth-of-type(2) > div:nth-of-type(2) > h2 > a
Accessible nameWho We Are
Markup
<a class="font-display text-base font-bold text-chalk no-underline transition-colors hover:text-emerald-bright" href="/about">Who We Are</a>
Affected pages/ /services/government /contact /services /about
Component · Ref FB3KXO
Affected pagehttps://legenesis.com/
Elementsection:nth-of-type(2) > div > div:nth-of-type(2) > div > div > a
Accessible nameLearn more ↗
Markup
<a class="font-mono text-[13px] uppercase tracking-tag text-emerald-bright no-underline" href="/services#servicenow">Learn more ↗</a>
Affected pages/ /contact
Component · Ref UUSEUV
Affected pagehttps://legenesis.com/contact
Elementsection:nth-of-type(2) > div > div:nth-of-type(1) > form > p > a:nth-of-type(1)
Accessible namePrivacy Policy
Markup
<a href="https://policies.google.com/privacy">Privacy Policy</a>
Component · Ref UW81L2
Affected pagehttps://legenesis.com/contact
Elementdiv > section:nth-of-type(2) > div > div:nth-of-type(2) > div:nth-of-type(1) > a
Accessible name[email removed]
Markup
<a href="mailto:[email removed]" class="text-lg no-underline">[email removed]</a>
Component · Ref QI2HRP
Affected pagehttps://legenesis.com/contact
Elementdiv > div:nth-of-type(2) > div:nth-of-type(3) > div:nth-of-type(2) > p > a
Accessible name[email removed]
Markup
<a href="mailto:[email removed]">[email removed]</a>
Medium

Touch targets are too small

WCAG 2.5.8 (AA)10 instances5 inspected pages

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Why it matters

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Recommended correction

Increase the size of the touch target to at least 24x24 pixels to make it easier for users to activate by touch. Consider adding sufficient padding or spacing around the element to meet the minimum target size requirement.

View 10 affected elements
Component · Ref QWW5Z4
Affected pagehttps://legenesis.com/
Elementbutton[aria-label="Who We Are menu"]
Accessible nameWho We Are menu
Markup
<button type="button" aria-label="Who We Are menu" aria-expanded="false" class="text-[9px] text-bone transition-transform hover:text-emerald-bright ">▼</button>
Affected pages/ /services/government /contact /services /about

05 · Most affected inspected pages

06 · About this assessment

Evolize inspects publicly accessible website pages using automated browser-based testing and deterministic accessibility rules. Automated testing can identify many reproducible technical issues but cannot determine complete WCAG or legal compliance.

  • Publicly accessible surfaces only — no credentials, private systems, or source-code access.
  • Findings apply to the pages and states successfully inspected; automated analysis may not detect every issue.
  • Results reflect the site at the scan date and may have changed since.

Evolize provides digital risk intelligence and does not provide legal advice, certify compliance, or guarantee that litigation will not occur. Methodology · Security · Example assessment

07 · Continuous monitoring

This public report captures one assessment. Evolize monitoring rescans the website, detects new and recurring findings, tracks changes over time and verifies corrections.

Is information in this report inaccurate or outdated? Request a correction or removal.