Accessibility

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

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

5 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 5 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

B

Heading Hierarchy

7 headings, 1 skip(s)

REVIEW

7 headings, 1 skip(s)

Multiple H1 headings (3 found)

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

Heading level skipped: H1 → H3 (missing H2)

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

H4 Contact UKUAT
H4 Confirmation
H1 Mobilising the UK’s urban farming and agritech community.
H3 UKUAT is amembers’ network skipped
H3 …and UKUAT partnerson projects
H1 Our members duplicate H1
H1 Join our network duplicate H1

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

B

Form Accessibility

2 of 7 controls have issues

REVIEW

2 of 7 controls have issues

2 control(s) without accessible label

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

Got: <input type="submit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

5 control(s) properly labeled

7 controls

5 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
your-name	text		none
your-email	email		none
tel-119	tel		none
your-subject	text		none
your-message	textarea		none
input	submit	(none)	none
#g-recaptcha-response-100000	textarea	(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

B

Link & Button Quality

1 issue(s) across 118 links and 13 buttons

REVIEW

1 issue(s) across 118 links and 13 buttons

1 link(s) with generic text

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

Got: https://ukuat.org/about/ ("Learn more")

4 link(s) open in new tab without warning

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

Got: https://docs.google.com/forms/d/e/1FAIpQLSfEzBDyTUpKXX0AmkBGmJBegKtoLqT1GgVdp…; https://docs.google.com/forms/d/e/1FAIpQLSfEzBDyTUpKXX0AmkBGmJBegKtoLqT1GgVdp…; https://docs.google.com/forms/d/e/1FAIpQLSfEzBDyTUpKXX0AmkBGmJBegKtoLqT1GgVdp…; https://docs.google.com/forms/d/e/1FAIpQLSfEzBDyTUpKXX0AmkBGmJBegKtoLqT1GgVdp…

113 link(s) with descriptive text

118 links

0 empty

1 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://docs.google.com/forms/d/e/1FAIpQ…	Requests for Proposals	new tab	Add '(opens in new tab)' to text
https://ukuat.org/about/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: About
https://docs.google.com/forms/d/e/1FAIpQ…	Submit a Request for Proposals	new tab	Add '(opens in new tab)' to text
https://docs.google.com/forms/d/e/1FAIpQ…	Requests for Proposals	new tab	Add '(opens in new tab)' to text
https://docs.google.com/forms/d/e/1FAIpQ…	Requests for Proposals	new tab	Add '(opens in new tab)' to text

126 links and buttons have descriptive text

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

https://ukuat.org/about/ ("Learn 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://docs.google.com/forms/d/e/1FAIpQLSfEzBDyTUpKXX0AmkBGmJBegKtoLqT1GgVdp…; https://docs.google.com/forms/d/e/1FAIpQLSfEzBDyTUpKXX0AmkBGmJBegKtoLqT1GgVdp…; https://docs.google.com/forms/d/e/1FAIpQLSfEzBDyTUpKXX0AmkBGmJBegKtoLqT1GgVdp…; https://docs.google.com/forms/d/e/1FAIpQLSfEzBDyTUpKXX0AmkBGmJBegKtoLqT1GgVdp…

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

C

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

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

B

Lighthouse Accessibility Audits

Score 87/100 — 4 failing, 25 passed

REVIEW

87

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

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
Nature-of-business `span.select2 > span.selection > span.select2-selection > span#select2-Nature-of-business-container`

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.

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
Nature-of-business `span.selection > span.select2-selection > span#select2-Nature-of-business-container > span.select2-selection__placeholder`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
UKUAT is a members’ network `div.wp-block-uagb-container > div.wp-block-group > div.wp-block-uagb-advanced-heading > h3.uagb-heading-text`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 `div.um > div.um-members-pagination-box > div.um-members-pagidrop > select.um-s2`

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

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

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

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

●Touch targets have sufficient size and spacing.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

○`<object>` elements have alternate text

○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

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

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

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

A

Landmark Structure

16 landmarks

PASS

16 landmarks

<main> landmark present

5 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Skip link target(s) don't exist on page: #content

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Page Structure — as a screen reader sees it

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+

Heading Text Quality

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

PASS

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

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

A

Alt Text Quality

1 of 48 images have issues

PASS

1 of 48 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

3 decorative image(s) correctly marked

44 image(s) with good alt text

48 images 44 good alt text 3 decorative 1 missing

Issue	Count
missing	1 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

A+

Form Input Types

7 form control(s) checked, no type mismatches

PASS

7 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

PASS

Lang attribute set to "en-GB"

<html lang="en-GB"> is set and valid

Got: en-GB

A+

Tabindex Anti-Patterns

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

tabindex="-1" on naturally-focusable <select id="Nature-of-business">

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

A

Iframe Accessibility

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

PASS

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

PASS

All 20 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+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Mobilising the UK’…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 urban farming and	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 agritech community.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Our members	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Join our network	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 UKUAT is a	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 members’ network	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 …and UKUAT partner…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 on projects	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Home - UKUAT.org	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a About	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Mission/Vision/Scope	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Key activity areas	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Method	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Definitions	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Projects	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Current Projects	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Requests for Proposa…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Rural request for pr…	21.00:1	4.5:1	#000000	#FFFFFF	Pass

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.