Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 4 REVIEW 6 FIX

Alt Text Quality

Action

2 of 4 images have issues

FIX

2 of 4 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image-in-link without alt text

An image inside a link with no alt creates an empty link.

2 image(s) with good alt text

4 images 2 good alt text 2 missing

Issue	Count
missing	2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Favicon & Branding

Action

1 icon(s) detected

FIX

1 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

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 Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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.

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.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 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

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Landmark Structure

8 landmarks

REVIEW

8 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

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

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

Link & Button Quality

2 issue(s) across 32 links and 2 buttons

REVIEW

2 issue(s) across 32 links and 2 buttons

1 link(s) with no accessible text

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

Got: /about-me-rugby

1 link(s) with generic text

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

Got: ("More")

5 link(s) open in new tab without warning

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

Got: https://www.alinasdogservices.co.uk/dog-training-rugby; tel:07838166934; mailto:alina@alinasdogservices.co.uk; mailto:alina@alinasdogservices.co.uk; tel:+447838166934

25 link(s) with descriptive text

32 links

1 empty

1 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/about-me-rugby	(empty)	empty	Add link text or aria-label
/about-me-rugby	Alinas Dog Services	img no alt	Add alt attribute to the image
	More	generic text	Replace with descriptive text
Before: More Suggested: Home page
https://www.alinasdogservices.co.uk/dog-…	Positive Dog Trainer in Rugby	new tab	Add '(opens in new tab)' to text
tel:07838166934	07838 166934	new tab	Add '(opens in new tab)' to text
mailto:alina@alinasdogservices.co.uk	alina@alinasdogservices.co.uk	new tab	Add '(opens in new tab)' to text
mailto:alina@alinasdogservices.co.uk	alina@alinasdogservices.co.uk	new tab	Add '(opens in new tab)' to text
tel:+447838166934	07838 166934	new tab	Add '(opens in new tab)' to text

27 links and buttons have descriptive text

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

/about-me-rugby

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.

("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

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

https://www.alinasdogservices.co.uk/dog-training-rugby; tel:07838166934; mailto:alina@alinasdogservices.co.uk; mailto:alina@alinasdogservices.co.uk; tel:+447838166934

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

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Alinas Dog Services ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

1 pass 19 fail WCAG AA 1 pass AA only

title Alinas Dog Services

3.27:1

#000000

#526071

needs 4.5:1 (normal text)

16px · top of page (header area)

div Search this site

3.13:1

#000000

#565D5F

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

span Embedded Files

3.50:1

#000000

#67644B

needs 4.5:1 (normal text)

16px · top of page (header area)

span Skip to main content

4.06:1

#000000

#6F6F4E

needs 4.5:1 (normal text)

16px · top of page (header area)

span Skip to navigation

3.36:1

#000000

#5D643D

needs 4.5:1 (normal text)

16px · above the fold

span Alinas Dog Services

2.79:1

#000000

#4C5937

needs 4.5:1 (normal text)

16px · above the fold

a About Me

3.01:1

#000000

#525E36

needs 4.5:1 (normal text)

16px · above the fold

a Dog Walking

2.63:1

#000000

#4B543B

needs 4.5:1 (normal text)

16px · above the fold

a Dog Training

2.13:1

#000000

#444437

needs 4.5:1 (normal text)

16px · above the fold

a Pet Sitting

3.27:1

#000000

#526070

needs 4.5:1 (normal text)

16px · above the fold

a Pet Portraits

3.27:1

#000000

#526070

needs 4.5:1 (normal text)

16px · above the fold

a Classes

3.27:1

#000000

#526070

needs 4.5:1 (normal text)

16px · above the fold

a Contact Me

3.27:1

#000000

#526070

needs 4.5:1 (normal text)

16px · mid-page

span Alinas Dog Services

3.27:1

#000000

#526070

needs 4.5:1 (normal text)

16px · mid-page

a About Me

3.27:1

#000000

#526070

needs 4.5:1 (normal text)

16px · mid-page

a Dog Walking

3.27:1

#000000

#526070

needs 4.5:1 (normal text)

16px · mid-page

a Dog Training

3.27:1

#000000

#526070

needs 4.5:1 (normal text)

16px · mid-page

a Pet Sitting

3.27:1

#000000

#526070

needs 4.5:1 (normal text)

16px · mid-page

a Pet Portraits

3.27:1

#000000

#526070

needs 4.5:1 (normal text)

16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
title Alinas Dog Services	3.27:1	4.5:1	#000000	#526071	Fail
div Search this site	3.13:1	4.5:1	#000000	#565D5F	Fail
span Embedded Files	3.50:1	4.5:1	#000000	#67644B	Fail
span Skip to main content	4.06:1	4.5:1	#000000	#6F6F4E	Fail
span Skip to navigation	3.36:1	4.5:1	#000000	#5D643D	Fail
p ☏ 07838 166934 �…	5.72:1	4.5:1	#FFFFFF	#65694A	Pass
span Alinas Dog Services	2.79:1	4.5:1	#000000	#4C5937	Fail
a About Me	3.01:1	4.5:1	#000000	#525E36	Fail
a Dog Walking	2.63:1	4.5:1	#000000	#4B543B	Fail
a Dog Training	2.13:1	4.5:1	#000000	#444437	Fail
a Pet Sitting	3.27:1	4.5:1	#000000	#526070	Fail
a Pet Portraits	3.27:1	4.5:1	#000000	#526070	Fail
a Classes	3.27:1	4.5:1	#000000	#526070	Fail
a Contact Me	3.27:1	4.5:1	#000000	#526070	Fail
span Alinas Dog Services	3.27:1	4.5:1	#000000	#526070	Fail
a About Me	3.27:1	4.5:1	#000000	#526070	Fail
a Dog Walking	3.27:1	4.5:1	#000000	#526070	Fail
a Dog Training	3.27:1	4.5:1	#000000	#526070	Fail
a Pet Sitting	3.27:1	4.5:1	#000000	#526070	Fail
a Pet Portraits	3.27:1	4.5:1	#000000	#526070	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+

Heading Hierarchy

5 headings

PASS

5 headings

Single H1 present

H1 Accredited Dog Walking & Dog Training Rugby Warwickshire
H2 Professional Dog Walking in Rugby
H2 Positive Dog Trainer in Rugby
H3 Get in Touch
H3 Areas Covered

A+

Heading Text Quality

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

PASS

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

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

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
input	search	Search this site	aria-label

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

1 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+

Tabindex Anti-Patterns

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

PASS

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

No tabindex anti-patterns detected

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

PASS

All 45 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 100/100 — 0 failing, 24 passed

PASS

100

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

○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

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

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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○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

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

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.