Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 4 REVIEW 7 FIX

Alt Text Quality

Action

7 of 29 images have issues

FIX

7 of 29 images have issues

3 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

3 image-in-link without alt text

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

4 image(s) with filename as alt text

3 image(s) with alt text over 125 characters

19 image(s) with good alt text

29 images 19 good alt text 4 generic 3 missing

Issue	Count
missing	3 image(s)
filename	4 image(s)
too long	3 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

Form Accessibility

Action

17 of 41 controls have issues

FIX

17 of 41 controls have issues

15 control(s) without accessible label

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

Got: <input type="text" name="digit1">; <input type="text" name="digit2">; <input type="text" name="digit3">; <input type="text" name="digit4">; <input type="text" name="digit5">; <input type="text" name="digit6">; <input type="text" name="digit1">; <input type="text" name="digit2">; <input type="text" name="digit3">; <input type="text" name="digit4"> (+5 more)

2 control(s) rely on placeholder only

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

Got: <input type="text" name="query">; <input type="text" name="query">

24 control(s) properly labeled

41 controls

24 labeled

2 placeholder only

15 unlabeled

Control	Type	Label	Method
#form-text-2115489281	email	Email address*	for/id
#form-text-208518935	password	Password*	for/id
#j_rememberme	checkbox	Remember me	for/id
#form-text-750794882	text	First name*	for/id
#form-text-1528023840	text	Family name*	for/id
#form-text-1167070308	email	Email address*	for/id
#form-text-305044190	password	Password*	for/id
#form-text-1630075779	password	Repeat password*	for/id
#form-options-1515311382	select	Occupation	for/id
#form-options-1503118544	select	Nationality	for/id
checkAccept	checkbox		none
#form-text-1890421038	email	Email address	for/id
#form-text-317469183	password	Password*	for/id
#form-text-567319611	password	Repeat password*	for/id
#email	text	Email adress *	for/id
#firstName	text	First name *	for/id
#familyName	text	Family name *	for/id
#update	checkbox	Update	for/id
#press	checkbox	Press	for/id
#multimedia	checkbox	Multimedia	for/id
#day	text	Day	for/id
#month	text	Month	for/id
#year	text	Year	for/id
#subscribe-input	email	Write your email to subscribe	for/id
query	text	(PRESS ENTER TO SEARCH)	placeholder only
query	text	(PRESS ENTER TO SEARCH)	placeholder only
digit2	text	(none)	none
digit3	text	(none)	none
digit4	text	(none)	none
digit5	text	(none)	none
digit6	text	(none)	none
digit1	text	(none)	none
digit1	text	(none)	none
digit2	text	(none)	none
digit3	text	(none)	none
digit4	text	(none)	none
digit5	text	(none)	none
#occupation	select	(none)	none
#organisation	text	(none)	none
digit6	text	(none)	none
#g-recaptcha-response-100000	textarea	(none)	none

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

<input type="text" name="digit1">; <input type="text" name="digit2">; <input type="text" name="digit3">; <input type="text" name="digit4">; <input type="text" name="digit5">; <input type="text" name="digit6">; <input type="text" name="digit1">; <input type="text" name="digit2">; <input type="text" name="digit3">; <input type="text" name="digit4"> (+5 more)

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

Link & Button Quality

Action

7 issue(s) across 387 links and 30 buttons

FIX

7 issue(s) across 387 links and 30 buttons

5 link(s) with generic text

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

Got: /en/about-us/organization/what-is-nato ("LEARN MORE"); /en/what-we-do/introduction-to-nato/defence-expenditures-and-natos-5-commitme… ("LEARN MORE"); /en/what-we-do/deterrence-and-defence/strengthening-natos-eastern-flank ("LEARN MORE"); /en/what-we-do/partnerships-and-cooperation/natos-support-for-ukraine ("LEARN MORE"); /en/what-is-nato.html ("Learn more")

3 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/en/what-we-do/deterrence-and-defence/arctic-security"]; a[href="/en/what-we-do/deterrence-and-defence/natos-role-in-defence-industry-production"]; a[href="/en/multimedia/multimedia/videos/2026/03/30/allied-carriers-set-sail-for-nept…"]

11 link(s) open in new tab without warning

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

Got: https://policies.google.com/privacy; https://policies.google.com/terms; https://shape.nato.int/; http://www.act.nato.int/; https://jfcnaples.nato.int/kfor; https://x.com/nato; https://www.instagram.com/nato/; https://www.linkedin.com/company/nato/; https://www.facebook.com/NATO; https://www.youtube.com/NATO (+1 more)

2 button(s) with no accessible text

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

Got: button#close-form-subscription; button.close-form-subscription (#2617 on page)

368 link(s) with descriptive text

387 links

0 empty

5 generic text

11 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://policies.google.com/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://policies.google.com/terms	Terms of Serviceopens in a new…	new tab	Add '(opens in new tab)' to text
/en/about-us/organization/what-is-nato	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: What Is Nato
/en/what-we-do/introduction-to-nato/defe…	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: Defence Expenditures And Natos 5 Commitment#Five Percent
/en/what-we-do/deterrence-and-defence/st…	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: Strengthening Natos Eastern Flank
/en/what-we-do/partnerships-and-cooperat…	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: Natos Support For Ukraine
/en/what-we-do/deterrence-and-defence/ar…	Arctic security	img no alt	Add alt attribute to the image
/en/what-we-do/deterrence-and-defence/na…	NATO’s role in defence indus…	img no alt	Add alt attribute to the image
/en/multimedia/multimedia/videos/2026/03…	Allied carriers set sail for N…	img no alt	Add alt attribute to the image
/en/what-is-nato.html	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: What Is Nato.Html
https://shape.nato.int/	Allied Command Operations (ACO…	new tab	Add '(opens in new tab)' to text
http://www.act.nato.int/	Allied Command Transformation …	new tab	Add '(opens in new tab)' to text
https://jfcnaples.nato.int/kfor	KFOR (Kosovo Force) …	new tab	Add '(opens in new tab)' to text
https://x.com/nato	opens in a new tab	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/nato/	opens in a new tab	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/nato/	opens in a new tab	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/NATO	opens in a new tab	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/NATO	opens in a new tab	new tab	Add '(opens in new tab)' to text
https://www.flickr.com/photos/nato/	opens in a new tab	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

396 links and buttons have descriptive text

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

/en/about-us/organization/what-is-nato ("LEARN MORE"); /en/what-we-do/introduction-to-nato/defence-expenditures-and-natos-5-commitme… ("LEARN MORE"); /en/what-we-do/deterrence-and-defence/strengthening-natos-eastern-flank ("LEARN MORE"); /en/what-we-do/partnerships-and-cooperation/natos-support-for-ukraine ("LEARN MORE"); /en/what-is-nato.html ("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

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/en/what-we-do/deterrence-and-defence/arctic-security"]; a[href="/en/what-we-do/deterrence-and-defence/natos-role-in-defence-industry-production"]; a[href="/en/multimedia/multimedia/videos/2026/03/30/allied-carriers-set-sail-for-nept…"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://policies.google.com/privacy; https://policies.google.com/terms; https://shape.nato.int/; http://www.act.nato.int/; https://jfcnaples.nato.int/kfor; https://x.com/nato; https://www.instagram.com/nato/; https://www.linkedin.com/company/nato/; https://www.facebook.com/NATO; https://www.youtube.com/NATO (+1 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#close-form-subscription; button.close-form-subscription (#2617 on page)

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

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

15 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 15 <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

Action

19 landmarks

REVIEW

19 landmarks

<main> landmark present

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

15 <nav> landmark(s) found

4 of 15 <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

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

Heading Hierarchy

46 headings, 2 skip(s)

REVIEW

46 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H3 → H5 (missing H4)

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

H5 NATO MULTIMEDIA ACCOUNT
H2 Download NATO’s broadcast-quality video content free of charge
H2 Log in
H4 NATO MULTIMEDIA ACCOUNT skipped
H2 Access NATO’s broadcast-quality video content free of charge
H2 Create an account
H2 Check your inbox and enter verification code
H2 You have successfully created your account
H3 Subscribe to our newsletter
H2 Your password has been updated
H1 NATO's purpose is to safeguard the freedom and security of all its members
H2 NATO's 5% commitment
H2 Strengthening NATO's eastern flank
H2 Support for Ukraine
H2 News
H2 In focus
H3 The NATO Secretary General's Annual Report 2025
H3 Collective defence and Article 5
H3 Arctic security
H3 NATO’s role in defence industry production
H3 Deterrence and defence
H3 Relations with Ukraine
H3 Resilience, civil preparedness and Article 3
H3 NATO exercises
H2 Multimedia highlights
H3 NATO Secretary General visits Türkiye
H3 NATO Secretary General visits Czechia
H3 NATO Secretary General attends Ukraine Defence Contact Group meeting
H3 Minister of Defence of Albania visits NATO Headquarters
H3 NATO Secretary General visits the United States
H3 NATO Secretary General visits the United States
H3 Allied carriers set sail for Neptune Strike
H2 What is NATO?
H3 Member countries
H3 Organization
H3 Secretary General
H3 Subscribe to newsletters
H3 Step 1 of 2
H2 Personal data
H3 Step 2 of 2
H2 Subscription preferences
H3 Thanks! You're almost there...
H5 Do you have time to provide us with some additional information? skipped
H3 Thank you for providing the additional information
H2 Subscribe to our newsletters
H2 This email is already subscribed. To adjust your subscription, use the “Preferences” link in any of our emails.

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

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

404 Error Page

Action

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

404 Page Quality ✓ Custom 404 Page

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

Favicon & Branding

Action

13 icon(s) detected

REVIEW

13 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

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 NATO's purpose is to…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Download NATO’s br…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Log in	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Access NATO’s broa…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Create an account	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Check your inbox and…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 You have successfull…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Your password has be…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 NATO's 5% commitment	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Strengthening NATO's…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Support for Ukraine	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 News	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 In focus	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Multimedia highlight…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What is NATO?	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Personal data	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Subscription prefere…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Subscribe to our new…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 This email is alread…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Subscribe to our new…	21.00:1	3.0: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+

Lighthouse Accessibility Audits

Score 97/100 — 2 failing, 30 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.

ARIA

When a `progressbar` element 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 how to label `progressbar` elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.hero-home > div.section-wrapper > div.slider-progress-wrapper > div.slider-progress `div.hero-home > div.section-wrapper > div.slider-progress-wrapper > div.slider-progress`

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.

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
The NATO Secretary General's Annual Report 2025 `div.section-row > div.section-col-12 > div.card-normal > a`
Collective defence and Article 5 `div.section-row > div.section-col-12 > div.card-normal > a`
Arctic security `div.section-row > div.section-col-12 > div.card-normal > a`
NATO’s role in defence industry production `div.section-row > div.section-col-12 > div.card-normal > a`
Deterrence and defence `div.section-row > div.section-col-12 > div.card-normal > a`
Relations with Ukraine `div.section-row > div.section-col-12 > div.card-normal > a`
Resilience, civil preparedness and Article 3 `div.section-row > div.section-col-12 > div.card-normal > a`
NATO exercises `div.section-row > div.section-col-12 > div.card-normal > a`
Photos NATO Secretary General visits Türkiye 21 April 2026 `div.section-row > div.section-col-12 > div.card-normal > a`
Photos NATO Secretary General visits Czechia 16 April 2026 `div.section-row > div.section-col-12 > div.card-normal > a`
Photos NATO Secretary General attends Ukraine Defence Contact Group meeting 1… `div.section-row > div.section-col-12 > div.card-normal > a`
Photos Minister of Defence of Albania visits NATO Headquarters 14 April 2026 `div.section-row > div.section-col-12 > div.card-normal > a`
Videos NATO Secretary General visits the United States 08 April 2026 `div.section-row > div.section-col-12 > div.card-normal > a`
Photos NATO Secretary General visits the United States 08 April 2026 `div.section-row > div.section-col-12 > div.card-normal > a`
Videos Allied carriers set sail for Neptune Strike 30 March 2026 `div.section-row > div.section-col-12 > div.card-normal > a`

○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

●ARIA input fields have accessible names

●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

●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

●ARIA IDs are unique

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

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

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

○ARIA `meter` 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

○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

○Links are distinguishable without relying on color.

○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

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