Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 40 -1-on-focusable

FIX

0 positive, 40 -1-on-focusable

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

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

tabindex="-1" on naturally-focusable <a id="sm-1787553434788515-1">

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 <a id="sm-1787553434788515-3">

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

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

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

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

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

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

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

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

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

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

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

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

tabindex="-1" on naturally-focusable <a id="sm-1787553434788515-5">

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

tabindex="-1" on naturally-focusable <button id="e-n-tab-title-541092112">

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 id="e-n-tab-title-541092113">

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 id="e-n-tab-title-541092114">

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 id="e-n-tab-title-541092115">

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 id="e-n-tab-title-541092116">

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 id="e-n-tab-title-541092117">

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 id="e-n-tab-title-541092118">

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

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 ✗

C

Link & Button Quality

Action

2 issue(s) across 169 links and 12 buttons

REVIEW

2 issue(s) across 169 links and 12 buttons

2 link(s) with no accessible text

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

Got: https://eaglepatches.uk; https://eaglepatches.uk

5 link(s) open in new tab without warning

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

Got: https://maps.app.goo.gl/zB6nb53d67nvA29V7; https://www.facebook.com/eaglepatches; https://www.instagram.com/eaglepatchesofficial/; https://www.youtube.com/@eaglepatchesofficial; https://maps.app.goo.gl/QziwsRr32ozDxinM7

162 link(s) with descriptive text

169 links

2 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://eaglepatches.uk	(empty)	empty	Add link text or aria-label
https://maps.app.goo.gl/zB6nb53d67nvA29V…	custom patches	new tab	Add '(opens in new tab)' to text
https://eaglepatches.uk	(empty)	empty	Add link text or aria-label
https://www.facebook.com/eaglepatches	Facebook-f	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/eaglepatchesof…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@eaglepatchesoff…	Youtube	new tab	Add '(opens in new tab)' to text
https://maps.app.goo.gl/QziwsRr32ozDxinM…	18 Fitzwilliam St, Broomhall, …	new tab	Add '(opens in new tab)' to text

174 links and buttons have descriptive text

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

https://eaglepatches.uk; https://eaglepatches.uk

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

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

https://maps.app.goo.gl/zB6nb53d67nvA29V7; https://www.facebook.com/eaglepatches; https://www.instagram.com/eaglepatchesofficial/; https://www.youtube.com/@eaglepatchesofficial; https://maps.app.goo.gl/QziwsRr32ozDxinM7

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

B

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found - Eagle Patches UK ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

C

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

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

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

C

Navigation UX

Action

2 navigation pattern(s)

REVIEW

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

3 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 3 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

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 Top-Rated

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Maker in the UK

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Loved by Thousands

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Sequin Patches

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Embroidered Patches

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Chenille Patches

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Leather Patches

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 PVC Patches

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Sublimated Patches

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Woven Patches

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Applique Patches

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Sequin Patches

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Embroidered Patches

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Precision in Every Stitch — Explore Ou…

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Design Your Own Patch & Get a Free Mocku…

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Design Sketch

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Design Preview

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Final Patch

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Custom Patches for Every Team, Brand, an…

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Looking for Premium Custom Made Patches …

1.05:1

#000000

on

#190100

needs 3.0:1 (large text)

24px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Top-Rated	1.05:1	3.0:1	#000000	#190100	Fail
h1 Maker in the UK	1.05:1	3.0:1	#000000	#190100	Fail
h2 Loved by Thousands	1.05:1	3.0:1	#000000	#190100	Fail
h2 Sequin Patches	1.05:1	3.0:1	#000000	#190100	Fail
h2 Embroidered Patches	1.05:1	3.0:1	#000000	#190100	Fail
h2 Chenille Patches	1.05:1	3.0:1	#000000	#190100	Fail
h2 Leather Patches	1.05:1	3.0:1	#000000	#190100	Fail
h2 PVC Patches	1.05:1	3.0:1	#000000	#190100	Fail
h2 Sublimated Patches	1.05:1	3.0:1	#000000	#190100	Fail
h2 Woven Patches	1.05:1	3.0:1	#000000	#190100	Fail
h2 Applique Patches	1.05:1	3.0:1	#000000	#190100	Fail
h2 Sequin Patches	1.05:1	3.0:1	#000000	#190100	Fail
h2 Embroidered Patches	1.05:1	3.0:1	#000000	#190100	Fail
h2 Precision in Every S…	1.05:1	3.0:1	#000000	#190100	Fail
h2 Design Your Own Patc…	1.05:1	3.0:1	#000000	#190100	Fail
h2 Design Sketch	1.05:1	3.0:1	#000000	#190100	Fail
h2 Design Preview	1.05:1	3.0:1	#000000	#190100	Fail
h2 Final Patch	1.05:1	3.0:1	#000000	#190100	Fail
h2 Custom Patches for E…	1.05:1	3.0:1	#000000	#190100	Fail
h2 Looking for Premium …	1.05:1	3.0:1	#000000	#190100	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

16 landmarks

PASS

16 landmarks

<main> landmark present

3 <nav> landmark(s) found

1 of 3 <nav> elements are unlabeled

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

Skip navigation link present

Search landmark present

Page Structure — as a screen reader sees it

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

46 headings

PASS

46 headings

Single H1 present

H1 Top-Rated Custom Patch Maker in the UK
H2 Loved by Thousands
H3 Free UK Delivery
H3 Free Design Support
H3 Low Minimums, No Hassle
H3 Fair & Friendly Pricing
H2 Sequin Patches
H2 Embroidered Patches
H2 Chenille Patches
H2 Leather Patches
H2 PVC Patches
H2 Sublimated Patches
H2 Woven Patches
H2 Applique Patches
H2 Sequin Patches
H2 Embroidered Patches
H2 Precision in Every Stitch — Explore Our Work
H2 Design Your Own Patch & Get a Free Mockup!
H2 Design Sketch
H2 Design Preview
H2 Final Patch
H2 Custom Patches for Every Team, Brand, and Purpose
H3 BUSINESS & CORPORATE
H3 Military & Tactical
H3 Sports Team
H3 Motorcycle Patches
H3 Police & Fire Departments
H3 School & Scouts
H3 Events & Organization
H3 Events & Organization
H2 Looking for Premium Custom Made Patches in the UK?
H2 Years of Expertise, Excellence, & Experience
H2 From Concept to Threadwork, We Deliver Patch Perfection
H3 Custom Patch Pros You Can Count On
H2 Bulk Custom Patches, Delivered Fast Across the UK
H2 Welcome to Eagle Patches UK
H2 Custom Patches with Purpose, Made to Make a Difference
H3 Inspire:
H3 Unite:
H3 Express:
H2 Why the UK Trusts Eagle Patches
H3 Years of Trusted Craftsmanship
H3 10,000+ Happy Patch Fans
H3 Rated 5-Stars for a Reason
H3 Bulk Orders, No Bottlenecks
H2 We Back Every Patch with Quality, Craft & Confidence

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 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: 1 all-caps heading(s)

A+

Alt Text Quality

All 188 images OK

PASS

All 188 images OK

2 decorative image(s) correctly marked

186 image(s) with good alt text

188 images 186 good alt text 2 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 6 controls labeled

PASS

All 6 controls labeled

6 control(s) properly labeled

6 controls

6 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#elementor-search-form-e087578	search	Search	for/id
#form-field-field_7d76d50	text	Name	for/id
#form-field-field_b138dc6	text	Last Name	for/id
#form-field-email	email	Email	for/id
#form-field-field_0439d2a	tel	Phone	for/id
#form-field-field_52fe3b1	textarea	Message	for/id

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

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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"

<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

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

PASS

All 32 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.

A

Lighthouse Accessibility Audits

Score 91/100 — 3 failing, 29 passed

PASS

91

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
Custom Ptaches for Every Team, Brand, and Purpose `div.elementor-element > div.elementor-icon-box-wrapper > div.elementor-icon-box-content > p.elementor-icon-box-description`
Morale Patches, ID Patches, and Velcro-backed designs made for field use. `div.elementor-element > div.elementor-icon-box-wrapper > div.elementor-icon-box-content > p.elementor-icon-box-description`
Team emblems, jersey patches, league badges, and fan merch patches. `div.elementor-element > div.elementor-icon-box-wrapper > div.elementor-icon-box-content > p.elementor-icon-box-description`
Back patches, vest patches, rider names, rocker patches, and club designs. `div.elementor-element > div.elementor-icon-box-wrapper > div.elementor-icon-box-content > p.elementor-icon-box-description`
Department patches, rank patches, and uniform badges. `div.elementor-element > div.elementor-icon-box-wrapper > div.elementor-icon-box-content > p.elementor-icon-box-description`
Achievements badges, spirit patches, varsity patches, and event patches. `div.elementor-element > div.elementor-icon-box-wrapper > div.elementor-icon-box-content > p.elementor-icon-box-description`
Commemorative ptaches, fundraiser patches, conference patches, and giveaway pat… `div.elementor-element > div.elementor-icon-box-wrapper > div.elementor-icon-box-content > p.elementor-icon-box-description`
Commemorative ptaches, fundraiser patches, conference patches, and giveaway pat… `div.elementor-element > div.elementor-icon-box-wrapper > div.elementor-icon-box-content > p.elementor-icon-box-description`
YEARS OF EXPERTISE, EXCELLENCE, & EXPERIENCE `div.e-con-inner > div.elementor-element > div.elementor-element > h2.elementor-heading-title`
Custom Patch Pros You Can Count On `div.elementor-element > div.elementor-element > div.elementor-element > h3.elementor-heading-title`
At Eagle Patches UK, every patch we create goes through careful hands and watch… `div.elementor-element > div.elementor-element > p > span`
custom name patches `div.elementor-element > p > a > span`
or `div.elementor-element > div.elementor-element > p > span`
printed patches `div.elementor-element > div.elementor-element > p > span`
for your brand, club, or jacket, what you get is crisp, clean, and made to las… `div.elementor-element > div.elementor-element > p > span`
info@eaglepatches.uk `div.e-con-inner > div.elementor-element > p > a`
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-text > input#form-field-field_7d76d50 `form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-text > input#form-field-field_7d76d50`
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-text > input#form-field-field_b138dc6 `form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-text > input#form-field-field_b138dc6`
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-email > input#form-field-email `form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-email > input#form-field-email`
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-tel > input#form-field-field_0439d2a `form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-tel > input#form-field-field_0439d2a`
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-textarea > textarea#form-field-field_52fe3b1 `form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-textarea > textarea#form-field-field_52fe3b1`

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.home > div#v74ma8j3k2go1787553361856 > iframe#u2ohqpaitpl81787553361919 `body.home > div#v74ma8j3k2go1787553361856 > iframe#u2ohqpaitpl81787553361919`
body.home > div#v74ma8j3k2go1787553361856 > iframe#lcdubcbtl4mg1787553361948 `body.home > div#v74ma8j3k2go1787553361856 > iframe#lcdubcbtl4mg1787553361948`

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.e-con-inner > div.elementor-element > div.elementor-element > a `div.e-con-inner > div.elementor-element > div.elementor-element > a`
div.e-con-inner > div.elementor-element > div.elementor-element > a `div.e-con-inner > div.elementor-element > div.elementor-element > a`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

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

●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

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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with 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

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

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