Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 3 REVIEW 6 FIX

Landmark Structure

Action

6 landmarks

FIX

6 landmarks

No <main> landmark found

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

2 <nav> landmark(s) found

1 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

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

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

Link & Button Quality

Action

22 issue(s) across 223 links and 69 buttons

FIX

22 issue(s) across 223 links and 69 buttons

6 link(s) with no accessible text

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

Got: #; #; #; #; #; #

3 link(s) with generic text

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

Got: /rhsgrow ("Read more"); /rhsgrow ("Read more"); /gardens/bridgewater/garden-highlights/growing-skills-garden ("Read more")

17 link(s) open in new tab without warning

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

Got: /about-us/careers; https://www.rhsplants.co.uk; http://www.rhsprints.co.uk/; https://www.rhsplants.co.uk/rhs-gifting/; /join; /shop#garden-centres; https://www.rhsplants.co.uk/; https://giftcards.rhs.org.uk; https://www.instagram.com/The_RHS/; https://www.youtube.com/@The_RHS (+7 more)

13 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button (#971 on page); button (#983 on page); button (#999 on page); button (#1015 on page); button (#1033 on page); button (#1215 on page); button (#1232 on page); button (#1249 on page); button (#1263 on page); button (#1277 on page) (+3 more)

197 link(s) with descriptive text

223 links

6 empty

3 generic text

17 new tab

13 empty buttons

Element	Text	Issue	Suggested Fix
#	(empty)	empty	Add link text or aria-label
/about-us/careers	Careers	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
https://www.rhsplants.co.uk	Shop plants — rhsplants.co.u…	new tab	Add '(opens in new tab)' to text
http://www.rhsprints.co.uk/	Shop prints — rhsprints.co.u…	new tab	Add '(opens in new tab)' to text
https://www.rhsplants.co.uk/rhs-gifting/	RHS Gifting — rhsplants.co.u…	new tab	Add '(opens in new tab)' to text
/rhsgrow	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Rhsgrow
/rhsgrow	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Rhsgrow
/gardens/bridgewater/garden-highlights/g…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Growing Skills Garden
/join	Gift membership	new tab	Add '(opens in new tab)' to text
/shop#garden-centres	Garden centres	new tab	Add '(opens in new tab)' to text
https://www.rhsplants.co.uk/	Plants online	new tab	Add '(opens in new tab)' to text
https://giftcards.rhs.org.uk	Gift cards and vouchers	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/The_RHS/	Follow the RHS on Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@The_RHS	Subscribe to the RHS YouTube c…	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@the_rhs	Follow the RHS on TikTok	new tab	Add '(opens in new tab)' to text
https://www.threads.com/@the_rhs	Follow the RHS on Threads	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/rhshome	Like the RHS on Facebook	new tab	Add '(opens in new tab)' to text
https://www.pinterest.co.uk/rhshome/	Follow the RHS on Pinterest	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
https://www.rhs.org.uk/privacy/cookies	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.rhs.org.uk/privacy/cookies	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

253 links and buttons have descriptive text

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

#; #; #; #; #; #

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.

/rhsgrow ("Read more"); /rhsgrow ("Read more"); /gardens/bridgewater/garden-highlights/growing-skills-garden ("Read more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

/about-us/careers; https://www.rhsplants.co.uk; http://www.rhsprints.co.uk/; https://www.rhsplants.co.uk/rhs-gifting/; /join; /shop#garden-centres; https://www.rhsplants.co.uk/; https://giftcards.rhs.org.uk; https://www.instagram.com/The_RHS/; https://www.youtube.com/@The_RHS (+7 more)

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

Icon-only buttons need an aria-label so screen readers can announce them.

button (#971 on page); button (#983 on page); button (#999 on page); button (#1015 on page); button (#1033 on page); button (#1215 on page); button (#1232 on page); button (#1249 on page); button (#1263 on page); button (#1277 on page) (+3 more)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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.

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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)

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

Form Accessibility

2 of 25 controls have issues

REVIEW

2 of 25 controls have issues

1 control(s) without accessible label

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

Got: <input type="checkbox" id="modal-1">

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text" name="ctl00$MainMegaMenu$txtUnivSearchSticky" id="txtUnivSearchSticky">

23 control(s) properly labeled

25 controls

23 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
#yxt-SearchBar-input--search-bar	text	Conduct a search	aria-label
#yxt-SearchBar-input--search-bar-mobile	text	Conduct a search	aria-label
#ot-group-id-C0002	checkbox	Performance	for/id
#ot-group-id-C0004	checkbox	Advertising Cookies	for/id
#ot-group-id-IAB2V2_1	checkbox	Store and/or access information on a device	for/id
#ot-group-id-V2STACK42	checkbox	Personalised advertising and content, advertising and content measurement, audience research and services development	for/id
#ot-sub-group-id-IAB2V2_2	checkbox	Use limited data to select advertising	aria-label
#ot-sub-group-id-IAB2V2_3	checkbox	Create profiles for personalised advertising	aria-label
#ot-sub-group-id-IAB2V2_4	checkbox	Use profiles to select personalised advertising	aria-label
#ot-sub-group-id-IAB2V2_5	checkbox	Create profiles to personalise content	aria-label
#ot-sub-group-id-IAB2V2_6	checkbox	Use profiles to select personalised content	aria-label
#ot-sub-group-id-IAB2V2_7	checkbox	Measure advertising performance	aria-label
#ot-sub-group-id-IAB2V2_8	checkbox	Measure content performance	aria-label
#ot-sub-group-id-IAB2V2_9	checkbox	Understand audiences through statistics or combinations of data from different sources	aria-label
#ot-sub-group-id-IAB2V2_10	checkbox	Develop and improve services	aria-label
#ot-sub-group-id-IAB2V2_11	checkbox	Use limited data to select content	aria-label
#ot-group-id-ISF2V2_1	checkbox	Use precise geolocation data	for/id
#ot-group-id-ISF2V2_2	checkbox	Actively scan device characteristics for identification	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id
#txtUnivSearchSticky	text	(Enter keyword(s))	placeholder only
#modal-1	checkbox	(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

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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 Sorry we couldn't find that page / RHS ✓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

h1 The RHS is the UK’s gardening charity,…

2.45:1

#000000

#005747

needs 3.0:1 (large text)

32px · bottom of viewport · over background image/gradient

h2 RHS Flower Shows

2.45:1

#000000

#005747

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Get involved

2.45:1

#000000

#005747

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Join the RHS

2.45:1

#000000

#005747

needs 3.0:1 (large text)

24px · bottom of viewport

h2 We Care About Your Privacy

2.45:1

#000000

#005747

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Privacy Preference Centre

2.45:1

#000000

#005747

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Grow

2.45:1

#000000

#005747

needs 3.0:1 (large text)

19px · bottom of viewport · over background image/gradient

h3 Grow

2.45:1

#000000

#005747

needs 3.0:1 (large text)

19px · bottom of viewport · over background image/gradient

h3 Gardening to save the planet

2.45:1

#000000

#005747

needs 3.0:1 (large text)

19px · bottom of viewport

h3 RHS Bridgewater Growing Skills Garden

2.45:1

#000000

#005747

needs 3.0:1 (large text)

19px · bottom of viewport

h3 RHS Botanical Art & Photography Show

2.45:1

#000000

#005747

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Grow, Visit, Join

2.45:1

#000000

#005747

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Get gardening

2.45:1

#000000

#005747

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Gardening for wellbeing

2.45:1

#000000

#005747

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Protecting wildlife

2.45:1

#000000

#005747

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Ideas for beginners

2.45:1

#000000

#005747

needs 3.0:1 (large text)

19px · bottom of viewport

h3 We and our partners process data to:

2.45:1

#000000

#005747

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Manage Cookies

2.45:1

#000000

#005747

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Cookie List

2.45:1

#000000

#005747

needs 3.0:1 (large text)

19px · bottom of viewport

3 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
h1 The RHS is the UK’…	2.45:1	3.0:1	#000000	#005747	Fail
h2 RHS Flower Shows	2.45:1	3.0:1	#000000	#005747	Fail
h2 Get involved	2.45:1	3.0:1	#000000	#005747	Fail
h2 Join the RHS	2.45:1	3.0:1	#000000	#005747	Fail
h2 We Care About Your P…	2.45:1	3.0:1	#000000	#005747	Fail
h2 Privacy Preference C…	2.45:1	3.0:1	#000000	#005747	Fail
h3 Grow	2.45:1	3.0:1	#000000	#005747	Fail
h3 Grow	2.45:1	3.0:1	#000000	#005747	Fail
h3 Gardening to save th…	2.45:1	3.0:1	#000000	#005747	Fail
h3 RHS Bridgewater Grow…	2.45:1	3.0:1	#000000	#005747	Fail
h3 RHS Botanical Art & …	2.45:1	3.0:1	#000000	#005747	Fail
h3 Grow, Visit, Join	2.45:1	3.0:1	#000000	#005747	Fail
h3 Get gardening	2.45:1	3.0:1	#000000	#005747	Fail
h3 Gardening for wellbe…	2.45:1	3.0:1	#000000	#005747	Fail
h3 Protecting wildlife	2.45:1	3.0:1	#000000	#005747	Fail
h3 Ideas for beginners	2.45:1	3.0:1	#000000	#005747	Fail
h3 We and our partners …	2.45:1	3.0:1	#000000	#005747	Fail
h3 Manage Cookies	2.45:1	3.0:1	#000000	#005747	Fail
h3 Cookie List	2.45:1	3.0:1	#000000	#005747	Fail
title RHS - UK's leading g…	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.

A+

Heading Hierarchy

47 headings

PASS

47 headings

Single H1 present

H1 The RHS is the UK’s gardening charity, helping people and plants to grow
H2 RHS Flower Shows
H3 Grow
H3 Grow
H3 Gardening to save the planet
H3 RHS Bridgewater Growing Skills Garden
H3 RHS Botanical Art & Photography Show
H3 Grow, Visit, Join
H4 Gardening
H4 Days out
H4 Become a member
H4 Get involved
H4 Shop with us
H3 Get gardening
H3 Gardening for wellbeing
H3 Protecting wildlife
H3 Ideas for beginners
H2 Get involved
H2 Join the RHS
H2 We Care About Your Privacy
H3 We and our partners process data to:
H2 Privacy Preference Centre
H3 Manage Cookies
H4 Strictly Necessary
H4 Performance
H4 Advertising Cookies
H4 Store and/or access information on a device 114 partners can use this purpose
H4 Personalised advertising and content, advertising and content measurement, audience research and services development 127 partners can use this purpose
H5 Use limited data to select advertising 102 partners can use this purpose
H5 Create profiles for personalised advertising 96 partners can use this purpose
H5 Use profiles to select personalised advertising 95 partners can use this purpose
H5 Create profiles to personalise content 30 partners can use this purpose
H5 Use profiles to select personalised content 26 partners can use this purpose
H5 Measure advertising performance 120 partners can use this purpose
H5 Measure content performance 48 partners can use this purpose
H5 Understand audiences through statistics or combinations of data from different sources 78 partners can use this purpose
H5 Develop and improve services 94 partners can use this purpose
H5 Use limited data to select content 17 partners can use this purpose
H4 Use precise geolocation data 46 partners can use this special feature
H4 Actively scan device characteristics for identification 19 partners can use this special feature
H4 Ensure security, prevent and detect fraud, and fix errors 93 partners can use this special purpose
H4 Deliver and present advertising and content 86 partners can use this special purpose
H4 Match and combine data from other data sources 74 partners can use this feature
H4 Link different devices 79 partners can use this feature
H4 Identify devices based on information transmitted automatically 84 partners can use this feature
H4 Save and communicate privacy choices 78 partners can use this special purpose
H3 Cookie List

Alt Text Quality

1 of 18 images have issues

PASS

1 of 18 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 decorative image(s) correctly marked

15 image(s) with good alt text

18 images 15 good alt text 2 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+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /wwwroot/css/bundles/print.min.css?v=73043

Print Stylesheet ✓ Print Optimized

Print stylesheet /wwwroot/css/bundles/print.min.css?v=73043 ✓Inline @media print Not detected ✗

Lighthouse Accessibility Audits

Score 91/100 — 4 failing, 28 passed

PASS

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.

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
Find out how `div.card-default > div.card-default__body > a.button > span.button__text`
Read more `div.card-default > div.card-default__body > a.button > span.button__text`
See the entries `div.card-default > div.card-default__body > a.button > span.button__text`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
T&Cs `div.l-module > div.form-inline > p.text-small > a`
privacy policy `div.l-module > div.form-inline > p.text-small > a`

These are opportunities to improve the legibility of your content.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#optimizely-extension-AFEEBA1C-C07B-44A2-B8C6-79D4C1A9498B > div.brand-header-hero__content > div.brand-header-hero__cta > a.button `div#optimizely-extension-AFEEBA1C-C07B-44A2-B8C6-79D4C1A9498B > div.brand-header-hero__content > div.brand-header-hero__cta > a.button`
div.l-col-xs-8 > div.text-center > p.hidden-xl > a.button `div.l-col-xs-8 > div.text-center > p.hidden-xl > a.button`

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

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Our cookie policy `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

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

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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

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

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

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

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

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

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

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