Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DLandmark StructureAction4 landmarksFIX
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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.
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.
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
DHeading HierarchyAction14 headings, 2 skip(s)FIX
- H2 Seamlessly join meetings on Google Meet hardware with “Connect Room”
- H2 Google Workspace Updates Weekly Recap - April 17, 2026
- H2 Streamlining admin controls for Gemini Enterprise in the Google Workspace Admin console
- H2 Improved video quality on high-resolution displays in Google Meet
- H2 Now in beta: Download client-side encrypted Google Slides
- 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
Every page should have one H1 that describes the page content.
No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.
Learn more ▾ ▴
The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.
Source: WCAG 2.4.6 / Google Search Central
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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.
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
FAlt Text QualityAction9 of 18 images have issuesFIX
| Issue | Count |
|---|---|
| missing | 8 image(s) |
| generic | 1 image(s) |
Images without alt text are invisible to screen readers.
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.
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
FForm AccessibilityAction8 of 8 controls have issuesFIX
| Control | Type | Label | Method |
|---|---|---|---|
| q | text | (Search blog) | placeholder only |
| #header-mce-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.
<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">
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.
<input type="text" name="q">; <input type="email" name="EMAIL" id="header-mce-EMAIL">
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
FLink & Button QualityAction6 issue(s) across 100 links and 3 buttonsFIX
| 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 |
| http://workspaceupdates.googleblog.com/2… | Read More | generic text | Replace with descriptive text |
Before: Read More Suggested: Seamlessly Join Meetings On Google Meet Hardware With Connect Room.Html | |||
| http://workspaceupdates.googleblog.com/2… | Read More | generic text | Replace with descriptive text |
Before: Read More Suggested: Weekly Recap 04 17 2026.Html | |||
| http://workspaceupdates.googleblog.com/2… | Read More | generic text | Replace with descriptive text |
Before: Read More Suggested: Streamlining Admin Controls For Gemini Enterprise In The Google Workspace Admin Console.Html | |||
| http://workspaceupdates.googleblog.com/2… | Read More | generic text | Replace with descriptive text |
Before: Read More Suggested: Improved Video Quality On High Resolution Displays In Google Meet.Html | |||
| http://workspaceupdates.googleblog.com/2… | Read More | generic text | Replace with descriptive text |
Before: Read More Suggested: Now In Beta Download Client Side Encrypted Google Slides.Html | |||
| 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… | 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 |
Links without text are announced as raw URLs by screen readers.
/
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.
http://workspaceupdates.googleblog.com/2026/04/seamlessly-join-meetings-on-go… ("Read More"); http://workspaceupdates.googleblog.com/2026/04/weekly-recap-04-17-2026.html ("Read More"); http://workspaceupdates.googleblog.com/2026/04/streamlining-admin-controls-fo… ("Read More"); http://workspaceupdates.googleblog.com/2026/04/improved-video-quality-on-high… ("Read More"); http://workspaceupdates.googleblog.com/2026/04/now-in-beta-download-client-si… ("Read More")
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="https://www.youtube.com/googleworkspace"]; a[href="https://x.com/googleworkspace"]; a[href="https://www.linkedin.com/showcase/googleworkspace/"]; a[href="#"]
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)
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
FFavicon & BrandingAction2 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
C404 Error PageActionHTTP 404, custom pageREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 5 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| 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 |
| a Google Voice | 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.
CLighthouse Accessibility AuditsActionScore 74/100 — 8 failing, 21 passedREVIEW
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
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.
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.
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.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.
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 |
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.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.