Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 REVIEW 11 FIX

Landmark Structure

Action

3 landmarks

FIX

3 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

2 of 2 <nav> elements are unlabeled

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

No banner (header) landmark

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

Heading Hierarchy

Action

19 headings, 3 skip(s)

FIX

19 headings, 3 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

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: H2 → H4 (missing H3)

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

3 empty heading(s)

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

H1 New community features for Google Chat and an update on Currents
H3 (empty)
H3 What's Changing
H3 (empty)
H3 Who's impacted
H3 (empty)
H3 Why it’s important
H3 Recommended action
H3 Availability
H3 Resources
H2 Useful Links
H4 Join the official community for Google Workspace administrators skipped
H4 Learn about more Google Workspace launches
H4 Learn about our customers
H2 Subscribe to Our Blog Updates
H4 Follow Google Workspace skipped
H4 Learning & Support
H4 Resources
H4 More from Google

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

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

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

Alt Text Quality

Action

16 of 24 images have issues

FIX

16 of 24 images have issues

15 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

10 image-in-link without alt text

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

1 image(s) with generic alt text

4 decorative image(s) correctly marked

4 image(s) with good alt text

24 images 4 good alt text 4 decorative 1 generic 15 missing

Issue	Count
missing	15 image(s)
generic	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

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

8 of 8 controls have issues

FIX

8 of 8 controls have issues

6 control(s) without accessible label

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

Got: <input type="checkbox" id="nav-hamburger-input">; <input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">

2 control(s) rely on placeholder only

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

Got: <input type="text" name="q">; <input type="email" name="EMAIL" id="header-mce-EMAIL">

8 controls

0 labeled

2 placeholder only

6 unlabeled

Control	Type	Label	Method
q	text	(Search blog)	placeholder only
#header-mce-EMAIL	email	(Enter Your Email)	placeholder only
#nav-hamburger-input	checkbox	(none)	none
#goog-gt-votingInputSrcLang	text	(none)	none
#goog-gt-votingInputTrgLang	text	(none)	none
#goog-gt-votingInputSrcText	text	(none)	none
#goog-gt-votingInputTrgText	text	(none)	none
#goog-gt-votingInputVote	text	(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

Link & Button Quality

Action

3 issue(s) across 138 links and 3 buttons

FIX

3 issue(s) across 138 links and 3 buttons

3 link(s) with no accessible text

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

Got: /; https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEil-tQSvWkISdvbujn8…; https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEju6vwVM1NkDnhCoOqj…

8 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#social-link-mail; a#social-link-linkedin; a#social-link-facebook; a#social-link-twitter; a[href="https://www.youtube.com/googleworkspace"]; a[href="https://x.com/googleworkspace"]; a[href="https://www.linkedin.com/showcase/googleworkspace/"]; a[href="#"]

32 link(s) open in new tab without warning

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

Got: https://workspace.google.com/features/; https://workspace.google.com/products/admin/; http://support.google.com; https://workspace.google.com/whatsnew/calendar/; https://workspaceupdates.googleblog.com/atom.xml; https://www.googlecloudcommunity.com/gc/Google-Workspace/ct-p/google-workspace; https://workspace.google.com/whatsnew/calendar/; https://workspace.google.com/customers/; http://workspaceupdates.googleblog.com/atom.xml; https://support.google.com/a/ (+22 more)

95 link(s) with descriptive text

138 links

3 empty

0 generic text

32 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://workspace.google.com/features/	Products	new tab	Add '(opens in new tab)' to text
https://workspace.google.com/products/ad…	For Admins	new tab	Add '(opens in new tab)' to text
http://support.google.com	Help Center	new tab	Add '(opens in new tab)' to text
https://workspace.google.com/whatsnew/ca…	Release Calendar	new tab	Add '(opens in new tab)' to text
/	(empty)	empty	Add link text or aria-label
https://workspaceupdates.googleblog.com/…	rss_feed	new tab	Add '(opens in new tab)' to text
#	Share via Email	img no alt	Add alt attribute to the image
#	Share on LinkedIn	img no alt	Add alt attribute to the image
#	Share on Facebook	img no alt	Add alt attribute to the image
#	Share on X	img no alt	Add alt attribute to the image
https://blogger.googleusercontent.com/im…	(empty)	empty	Add link text or aria-label
https://blogger.googleusercontent.com/im…	(empty)	empty	Add link text or aria-label
https://www.googlecloudcommunity.com/gc/…	Join the official community fo…	new tab	Add '(opens in new tab)' to text
https://workspace.google.com/whatsnew/ca…	Learn about more Google Worksp…	new tab	Add '(opens in new tab)' to text
https://workspace.google.com/customers/	Learn about our customers	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/googleworkspace	Youtube	new tab	Add '(opens in new tab)' to text
https://x.com/googleworkspace	X (Twitter)	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/showcase/google…	Linkedin	new tab	Add '(opens in new tab)' to text
http://workspaceupdates.googleblog.com/a…	rss_feed	new tab	Add '(opens in new tab)' to text
https://support.google.com/a/	Admin Help	new tab	Add '(opens in new tab)' to text
https://support.google.com/a/users	Learning Center for Users	new tab	Add '(opens in new tab)' to text
https://www.googlecloudcommunity.com/gc/…	Community Forum	new tab	Add '(opens in new tab)' to text
https://support.google.com/	Google Help	new tab	Add '(opens in new tab)' to text
https://www.google.com/appsstatus	Workspace Dashboard	new tab	Add '(opens in new tab)' to text
https://workspace.google.com/whatsnew/	What's New	new tab	Add '(opens in new tab)' to text
https://workspace.google.com/security/	Security	new tab	Add '(opens in new tab)' to text
https://workspace.google.com/customers/	Customer Stories	new tab	Add '(opens in new tab)' to text
https://workspace.google.com/resources/w…	Working Remotely	new tab	Add '(opens in new tab)' to text
https://cloud.withgoogle.com/partners/?p…	Find a Partner	new tab	Add '(opens in new tab)' to text
https://workspace.google.com/marketplace…	Marketplace	new tab	Add '(opens in new tab)' to text
https://workspace.google.com/faq/	FAQs	new tab	Add '(opens in new tab)' to text
https://workspace.google.com/integration…	Integrations	new tab	Add '(opens in new tab)' to text
https://workspace.google.com/training/	Training & Certification	new tab	Add '(opens in new tab)' to text
https://cloud.google.com/	Google Cloud	new tab	Add '(opens in new tab)' to text
https://domains.google.com/about/	Google Domains	new tab	Add '(opens in new tab)' to text
https://chromeenterprise.google/	Chrome Enterprise	new tab	Add '(opens in new tab)' to text
https://www.google.com/intl/en/services	Google Business Solutions	new tab	Add '(opens in new tab)' to text
https://businessmessages.google/	Business Messages	new tab	Add '(opens in new tab)' to text
https://userresearch.google.com/?reserve…	Join User Studies	new tab	Add '(opens in new tab)' to text
https://policies.google.com/privacy?hl=e…	Privacy	new tab	Add '(opens in new tab)' to text
https://policies.google.com/terms?hl=en	Terms	new tab	Add '(opens in new tab)' to text
#	Seleccionar idioma▼	img no alt	Add alt attribute to the image
https://www.blogger.com/go/blogspot-cook…	Más información	new tab	Add '(opens in new tab)' to text

98 links and buttons have descriptive text

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

/; https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEil-tQSvWkISdvbujn8…; https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEju6vwVM1NkDnhCoOqj…

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

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

a#social-link-mail; a#social-link-linkedin; a#social-link-facebook; a#social-link-twitter; a[href="https://www.youtube.com/googleworkspace"]; a[href="https://x.com/googleworkspace"]; a[href="https://www.linkedin.com/showcase/googleworkspace/"]; a[href="#"]

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://workspace.google.com/features/; https://workspace.google.com/products/admin/; http://support.google.com; https://workspace.google.com/whatsnew/calendar/; https://workspaceupdates.googleblog.com/atom.xml; https://www.googlecloudcommunity.com/gc/Google-Workspace/ct-p/google-workspace; https://workspace.google.com/whatsnew/calendar/; https://workspace.google.com/customers/; http://workspaceupdates.googleblog.com/atom.xml; https://support.google.com/a/ (+22 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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-ev9of1

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 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

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://plus.google.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://plus.google.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 5 fail WCAG AA

REVIEW

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

15 pass 5 fail WCAG AA

a For Admins

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · top of page (header area)

a Help Center

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · top of page (header area)

a Release Calendar

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · above the fold

a Subscribe

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · above the fold

span email

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 New community featur…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Useful Links	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Subscribe to Our Blo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Google Workspace Upd…	19.09:1	4.5:1	#000000	#F4F4F4	Pass
a Products	7.77:1	4.5:1	#000000	#999EA2	Pass
a For Admins	3.66:1	4.5:1	#000000	#666666	Fail
a Help Center	3.66:1	4.5:1	#000000	#666666	Fail
a Release Calendar	3.66:1	4.5:1	#000000	#666666	Fail
a Subscribe	3.66:1	4.5:1	#000000	#666666	Fail
span email	3.66:1	4.5:1	#000000	#666666	Fail
div This official feed f…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Comms & Meetings	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span ▾	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Gmail	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Google Chat	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Google Calendar	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Google Tasks	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Google Groups	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Google Meet	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Google Meet hardware	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.

Lighthouse Accessibility Audits

Action

Score 71/100 — 9 failing, 21 passed

REVIEW

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
Join the official community for Google Workspace administrators `div.useful-links-columns > div.useful-link-item > h4 > a`
Learn about more Google Workspace launches `div.useful-links-columns > div.useful-link-item > h4 > a`
Learn about our customers `div.useful-links-columns > div.useful-link-item > h4 > 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
article.blog-post-full > section.blog-post-full__right-column > div.blog-post-full__body > h3 `article.blog-post-full > section.blog-post-full__right-column > div.blog-post-full__body > h3`
Join the official community for Google Workspace administrators `div.useful-links-content > div.useful-links-columns > div.useful-link-item > h4`
Follow Google Workspace `section.glue-footer__upper > section.glue-social > div.glue-social__group > h4.glue-social__title`

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.nav__content > div.nav__logo-lock > label.nav__hamburger-image-container > img.glue-icon `div.nav__content > div.nav__logo-lock > label.nav__hamburger-image-container > img.glue-icon`
div.header__content > div.site-branding > a.site-branding__link > img.site-branding__logo `div.header__content > div.site-branding > a.site-branding__link > img.site-branding__logo`
ul.social-links > li.social-link > a#social-link-mail > img.glue-icon `ul.social-links > li.social-link > a#social-link-mail > img.glue-icon`
ul.social-links > li.social-link > a#social-link-linkedin > img.glue-icon `ul.social-links > li.social-link > a#social-link-linkedin > img.glue-icon`
ul.social-links > li.social-link > a#social-link-facebook > img.glue-icon `ul.social-links > li.social-link > a#social-link-facebook > img.glue-icon`
ul.social-links > li.social-link > a#social-link-twitter > img.glue-icon `ul.social-links > li.social-link > a#social-link-twitter > img.glue-icon`
div.blog-post-full__body > div.separator > a > img `div.blog-post-full__body > div.separator > a > img`
div.blog-post-full__body > div.separator > a > img `div.blog-post-full__body > div.separator > a > img`
ul.glue-social__list > li.glue-social__item > a.glue-social__link > img.glue-icon `ul.glue-social__list > li.glue-social__item > a.glue-social__link > img.glue-icon`
ul.glue-social__list > li.glue-social__item > a.glue-social__link > img.glue-icon `ul.glue-social__list > li.glue-social__item > a.glue-social__link > img.glue-icon`
ul.glue-social__list > li.glue-social__item > a.glue-social__link > img.glue-icon `ul.glue-social__list > li.glue-social__item > a.glue-social__link > img.glue-icon`
div#column-3 > h4.glue-footer__site-links-header > span#column-3-toggle > img.glue-icon `div#column-3 > h4.glue-footer__site-links-header > span#column-3-toggle > img.glue-icon`
div#column-4 > h4.glue-footer__site-links-header > span#column-4-toggle > img.glue-icon `div#column-4 > h4.glue-footer__site-links-header > span#column-4-toggle > img.glue-icon`
div#column-4 > h4.glue-footer__site-links-header > span#column-4-toggle > img.glue-icon `div#column-4 > h4.glue-footer__site-links-header > span#column-4-toggle > img.glue-icon`

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.header > div.header__content > div.site-branding > a.site-branding__link `div.header > div.header__content > div.site-branding > a.site-branding__link`
section.blog-post-full__right-column > div.blog-post-full__body > div.separator > a `section.blog-post-full__right-column > div.blog-post-full__body > div.separator > a`
section.blog-post-full__right-column > div.blog-post-full__body > div.separator > a `section.blog-post-full__right-column > div.blog-post-full__body > div.separator > a`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Admins: Review the Change Management Guide. Use Takeout to explore your organ… `div.blog-post-full__body > div > span#docs-internal-guid-09d44d4a-7fff-31ce-9161-9c045842b7e3 > ul`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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
Comms & Meetings ▾ `div.header__bottom > ul.header__bottom__links > li.header__bottom__link-item > a.header__bottom__link`
Content & Collaboration ▾ `div.header__bottom > ul.header__bottom__links > li.header__bottom__link-item > a.header__bottom__link`
Gemini ▾ `div.header__bottom > ul.header__bottom__links > li.header__bottom__link-item > a.header__bottom__link`
Admin & Security ▾ `div.header__bottom > ul.header__bottom__links > li.header__bottom__link-item > a.header__bottom__link`
Education ▾ `div.header__bottom > ul.header__bottom__links > li.header__bottom__link-item > a.header__bottom__link`
More ▾ `div.header__bottom > ul.header__bottom__links > li.header__bottom__link-item > a.header__bottom__link`

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]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Form elements have associated labels

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

●Links are distinguishable without relying on color.

●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

●ARIA IDs are unique

●All heading elements contain content.

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[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 a valid value for its `[lang]` attribute

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

○Uses ARIA roles only on compatible elements

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

○Elements with visible text labels have matching accessible names.

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

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

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