Skip to content
https://fao.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
D
Landmark Structure
Action
5 landmarks
FIX
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV MAIN (missing!) CONTENTINFO footer

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

F
Heading Hierarchy
Action
89 headings, 5 skip(s)
FIX
89 headings, 5 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H5 Organizational chart
  • H5 Director-General
  • H5 Worldwide offices
  • H5 Finance Committee
  • H6 18–22 May 2026
  • H6 (empty)
  • H6 The latest news and updates from FAO
  • H5 News
  • H6 Real-life stories that inspire action and highlight the impact of FAO’s work
  • H5 Stories
  • H5 FAO Blog
  • H5 Multimedia
  • H5 Webcast
  • H6 Interactive
  • H5 Crunching the numbers
  • H5 Hand in Hand
  • H5 Agrifood Systems
  • H5 FAO Investment centre
  • H5 FAO elearning Academy
  • H5 All
  • H6 Food and agriculture data for over 245 countries and territories
  • H5 FAOSTAT
  • H5 Tracking progress on food and agriculture-related SDG indicators
  • H5 Food Price Index
  • H5 Water and agriculture country profile
  • H5 Preserving agricultural heritage around the world
  • H5 FAO Members Gateway
  • H5 Flagship publications
  • H5 Corporate brochures
  • H5 David Lubin Memorial Library
  • H5 Share
  • H6 In focus
  • H1 The four betters and leaving no one behind
  • H5 Highlights skipped
  • H5 Director-General
  • H6 News
  • H5 Strait of Hormuz: Protracted crisis could turn into global agrifood catastrophe
  • H6 Story
  • H5 Starting over in the Gaza Strip
  • H5 Conflict in the Near East region adds pressure on fragile agrifood systems, FAO Director-General warns
  • H6 In Focus
  • H5 FAO Regional Conference for Asia and the Pacific (APRC38)
  • H6 In Focus
  • H5 FAO Regional Conference for the Near East (NERC38)
  • H6 In Focus
  • H5 FAO response to global food security challenges
  • H6 In Focus
  • H5 FAO in emergencies
  • H6 Publication
  • H5 The status of women in agrifood systems in sub-Saharan Africa
  • H6 Interactive story
  • H5 Addressing land degradation for a sustainable future
  • H5 Director-General
  • H5 Conflict in the Near East region adds pressure on fragile agrifood systems, FAO Director-General warns
  • H5 Join the conversation
  • H6 Facebook
  • H5 Why we depend on rangelands and pastoralists more than we think
  • H6 X
  • H5 3 years into conflict, Sudan cannot wait
  • H6 Instagram
  • H5 With diplomacy, countries can still prevent a global food crisis
  • H4 Voices of Impact
  • H5 Mohammed’s Story: Starting over in the Gaza Strip
  • H6 21/04/2026
  • H5 Video
  • H5 Rediscovering the hidden power of Africa's forgotten crops
  • H6 13/04/2026
  • H5 Podcast
  • H5 Update on the Global Agrifood Implications of the 2026 Conflict in the Middle East
  • H6 13/04/2026
  • H4 Hunger map
  • H6 Mapping undernourishment and food insecurity worldwide skipped
  • H6 Explore the latest global estimates in depth
  • H5 2020 World
  • H2 31.2%
  • H5 2010 World skipped
  • H2 31.5%
  • H4 In depth skipped
  • H6 In Focus skipped
  • H5 Discover the enhanced FAO Transparency Portal
  • H6 Publication
  • H5 Medium Term Plan and Programme of Work
  • H6 In Focus
  • H5 FAO Data Lab
  • H4 FAO and the SDGs
  • H5 Hover the mouse over an SDG icon for more information
  • H4 Discover the Globally Important Agricultural Heritage Systems (GIAHS)
  • H5 WeChat
  • H6 Follow us on

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 ▾

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 ▾

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 ▾

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 ▾

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
D
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Breadcrumb navigation detected
Got: aria-label
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs aria-label navigation
Search
Skip Link
Labeled Navigation 2 <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
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Error Page ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA
button English
3.66:1
#000000
on
#476A83
needs 4.5:1 (normal text)
16px · above the fold
a العربية
3.66:1
#000000
on
#476A83
needs 4.5:1 (normal text)
16px · above the fold
a 中文
2.54:1
#000000
on
#3C5160
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Français
1.50:1
#000000
on
#2C2C2C
needs 4.5:1 (normal text)
16px · above the fold
a Русский
1.50:1
#000000
on
#2C2C2C
needs 4.5:1 (normal text)
16px · mid-page
a Español
1.50:1
#000000
on
#2C2C2C
needs 4.5:1 (normal text)
16px · mid-page
a About FAO
1.50:1
#000000
on
#2C2C2C
needs 4.5:1 (normal text)
16px · mid-page
span About Us
1.50:1
#000000
on
#2C2C2C
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)
ElementRatioRequiredFGBGResult
h1 The four betters and…19.60:13.0:1
#000000
#F7F7F7
Pass
h2 31.2%19.60:13.0:1
#000000
#F7F7F7
Pass
h2 31.5%19.60:13.0:1
#000000
#F7F7F7
Pass
title Home | Food and Agri…21.00:14.5:1
#000000
#FFFFFF
Pass
button Discover21.00:14.5:1
#000000
#FFFFFF
Pass
a About FAO21.00:14.5:1
#000000
#FFFFFF
Pass
a In action21.00:14.5:1
#000000
#FFFFFF
Pass
a Media21.00:14.5:1
#000000
#FFFFFF
Pass
a Main topics19.92:14.5:1
#000000
#F8F9FA
Pass
a Resources19.06:14.5:1
#000000
#F3F4F4
Pass
a Member countries19.09:14.5:1
#000000
#F4F4F4
Pass
a Get involved19.09:14.5:1
#000000
#F4F4F4
Pass
button English3.66:14.5:1
#000000
#476A83
Fail
a العربية3.66:14.5:1
#000000
#476A83
Fail
a 中文2.54:14.5:1
#000000
#3C5160
Fail
a Français1.50:14.5:1
#000000
#2C2C2C
Fail
a Русский1.50:14.5:1
#000000
#2C2C2C
Fail
a Español1.50:14.5:1
#000000
#2C2C2C
Fail
a About FAO1.50:14.5:1
#000000
#2C2C2C
Fail
span About Us1.50:14.5:1
#000000
#2C2C2C
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.

B
Lighthouse Accessibility Audits
Score 81/100 — 7 failing, 25 passed
REVIEW
81

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
tbody > tr > td.gsc-search-button > button.gsc-search-button tbody > tr > td.gsc-search-button > button.gsc-search-button
div.sdg-mobile > div.swiper-container > div.swiper-button > button.btn div.sdg-mobile > div.swiper-container > div.swiper-button > button.btn
div.sdg-mobile > div.swiper-container > div.swiper-button > button.btn div.sdg-mobile > div.swiper-container > div.swiper-button > button.btn
div#map > div.ui-giahs > div.zoom-controls-giahs > button#zoom-in div#map > div.ui-giahs > div.zoom-controls-giahs > button#zoom-in
div#map > div.ui-giahs > div.zoom-controls-giahs > button#zoom-out div#map > div.ui-giahs > div.zoom-controls-giahs > button#zoom-out

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#Contentplaceholder1_C017_Col01 > div.d-list > div.d-list-visual > iframe div#Contentplaceholder1_C017_Col01 > div.d-list > div.d-list-visual > iframe

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.

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
NEWS div#Contentplaceholder1_C007_Col00 > div.card > div.card-body > h6.title-category
STORY div#Contentplaceholder1_C007_Col01 > div.card > div.card-body > h6.title-category
IN FOCUS div#Contentplaceholder1_C028_Col00 > div.card > div.card-body > h6.title-category
IN FOCUS div#Contentplaceholder1_C028_Col01 > div.card > div.card-body > h6.title-category
IN FOCUS div#Contentplaceholder1_C028_Col02 > div.card > div.card-body > h6.title-category
IN FOCUS div#Contentplaceholder1_C140_Col00 > div.card > div.card-body > h6.title-category
PUBLICATION div#Contentplaceholder1_C140_Col01 > div.card > div.card-body > h6.title-category
INTERACTIVE STORY div#Contentplaceholder1_C140_Col02 > div.card > div.card-body > h6.title-category
FACEBOOK div#Contentplaceholder1_C013_Col00 > div.card > div.card-body > h6.title-category
INSTAGRAM div#Contentplaceholder1_C013_Col02 > div.card > div.card-body > h6.title-category
IN FOCUS div#Contentplaceholder1_C071_Col00 > div.card > div.card-body > h6.title-category
PUBLICATION div#Contentplaceholder1_C071_Col01 > div.card > div.card-body > h6.title-category
IN FOCUS div#Contentplaceholder1_C071_Col02 > div.card > div.card-body > h6.title-category
FOLLOW US ON div#Contentplaceholder1_T198B1AC4005_Col00 > div.footer-social > div.sfContentBlock > h6.title-category

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
SOFI 2025 div.row > div.col-lg-6 > p > a

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
Highlights div#Contentplaceholder1_C008_Col00 > div > div.sfContentBlock > h5.sub-title
Mapping undernourishment and food insecurity worldwide div.container > div.row > div.col-lg-6 > h6
IN FOCUS div#Contentplaceholder1_C071_Col00 > div.card > div.card-body > h6.title-category
BLOG widget-popup > div.popup-wrapper > div.pop-body > h6.title-category
FOLLOW US ON div#Contentplaceholder1_T198B1AC4005_Col00 > div.footer-social > div.sfContentBlock > h6.title-category

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Next slide div#Contentplaceholder1_C047_Col00 > div.sdg-mobile > div.swiper-container > div.swiper-button
Jobs div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Contact us div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Terms and Conditions div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Data protection and privacy div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Scam Alert div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Report Misconduct div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Transparency and accountability div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a
Procurement div#Contentplaceholder1_T198B1AC4006_Col01 > ul.list-inline > li.list-inline-item > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links 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
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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
○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.
○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+
Alt Text Quality
All 129 images OK
PASS
All 129 images OK
Info::
25 decorative image(s) correctly marked
Info::
104 image(s) with good alt text
129 images 104 good alt text 25 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#gsc-i-id1textsearcharia-label
#gsc-i-id2textsearcharia-label
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback