Google google.com
Accessibility score
League position
4thof 9
Issues found
6
Audits passed
36
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
SeriousFocusing an element must not trigger an unexpected change of context3 elements
Keyboard and switch-device users move focus carefully before deciding to activate anything. When focusing an element opens a new window, submits a form, steals focus, or navigates away, they are thrown off course before they have chosen to act.
Failing Elements
<div jscontroller="lpsUAf" jsname="R5mgy" class="etxtjc" data-is-images-mode="false" aria-label="Search by image" role="button" tabindex="0" jsaction="rcuQ6b:npT2md;h5M12e;AMruCe:Zpug7c" data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQhqEICCc">
<button jsname="B6rgad" tabindex="0" jscontroller="jNZDL" class="plR5qb" role="link" jsaction="click:bujKIf;mouseenter:vG60uf;mouseleave:NS5Xl;C7..." type="button" data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQteYPCCg">
<div class="gbqfba gbqfba-hvr" role="button" style="display: block; font-family: "Google Sans&quo..." tabindex="0" aria-label="I'm Feeling Stellar">
SeriousContent must reflow without two-dimensional scrolling33 elements
People who zoom to 400% or use a narrow viewport must be able to scroll in one direction only. A layout that still requires horizontal scrolling at 320 CSS pixels forces magnified readers to pan left and right line by line, which makes the page close to unusable.
Failing Elements
<div jsname="dtlGSb" jsmodel="" class="plsC5e RqyYHe" jscontroller="HGv0mf" jsaction="rcuQ6b:npT2md;IQOavd:DfLYCc;CRW1we:y4Phc;vmxUb:gYK..." data-hale="0" data-hveid="1">
<div id="ZnpjSd">
<div id="ZnpjSd">
<div class="acUsEb Qi40Vc CoM3Df" role="navigation">
<div class="k5vh8d">
<div>
<div class="acUsEb lGdWHf sI1XGe" id="sI1XGe">
<div class="acUsEb Q6KTif KEY6ib">
<div class="acUsEb gwogMd">
<div>
Showing first 10 of 33 failing elements.
ModerateDocument should have one main landmark1 element
Every page should have exactly one main landmark that identifies the primary content. Without a main landmark, screen reader users must navigate through all content linearly to find what they're looking for, making page navigation difficult and time-consuming.
Failing Elements
<html itemscope="" itemtype="http://schema.org/WebPage" lang="en">
Fix all of the following:
- Document does not have a main landmark
ModeratePage should contain a level-one heading1 element
Screen reader users use keyboard shortcuts to jump directly to the first h1, expecting to land at the main content. Without an h1 or with a misplaced one, users must listen to more of the page to understand its structure, wasting valuable time on every page visit.
Failing Elements
<html itemscope="" itemtype="http://schema.org/WebPage" lang="en">
Fix all of the following:
- Page must have a level-one heading
ModerateAll page content should be contained by landmarks2 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Failing Elements
<picture><img class="ESTs9d" alt="Labor Day 2026" height="400" src="/logos/doodles/2026/labor-day-2026-6753651837111014.3-2x.png" title="Labor Day 2026" width="1000" id="hplogo" data-csiid="E1SeaszGHpPz0PEP_f3giQg_2" data-atf="1"></picture>
Fix any of the following:
- Some page content is not contained by landmarks
<div jsslot="">
Fix any of the following:
- Some page content is not contained by landmarks
MinorARIA role should be appropriate for the element1 element
Invalid ARIA role and HTML element combinations can break accessibility for entire sections of your application. When roles are used incorrectly, assistive technologies may report confusing or nonsensical information to users, making it impossible for them to understand and interact with the interface properly.
Failing Elements
<textarea jsname="yZiJbe" class="gLFyf" aria-controls="Alh6id" aria-owns="Alh6id" autofocus="" aria-label="Search" placeholder="" aria-autocomplete="both" aria-expanded="false" aria-haspopup="false" autocapitalize="off" autocomplete="off" autocorrect="off" id="ti6dpd" maxlength="2048" name="q" ...>
Fix any of the following:
- ARIA role combobox is not allowed for given element
Passed audits36 across 1 page
<html> element must have a lang attribute1 element
Screen readers need language information to switch between pronunciation libraries. Without a specified language, screen readers default to the user's preferred language, resulting in incorrect pronunciation that sounds like a strange accent and makes content difficult or impossible to understand.
Audit Elements
<html itemscope="" itemtype="http://schema.org/WebPage" lang="en">
<html> element must have a valid value for the lang attribute1 element
Screen readers use language-specific sound libraries for proper pronunciation. Invalid language attributes cause screen readers to use the wrong library, making text sound like a confusing accent or completely unintelligible, especially for multilingual users who access content in multiple languages.
Audit Elements
<html itemscope="" itemtype="http://schema.org/WebPage" lang="en">
All page content should be contained by landmarks129 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Audit Elements
<div id="ZnpjSd"></div>
<div jsname="dtlGSb" jsmodel="" class="plsC5e RqyYHe" jscontroller="HGv0mf" jsaction="rcuQ6b:npT2md;IQOavd:DfLYCc;CRW1we:y4Phc;vmxUb:gYK4dd;zbpGPd:zdnavd;yGaBb:ugZYQd;rBQ22:cLZhNe;krs7Sc:yeoiVc;qBi8wc:Klozif;" data-hale="0" data-hveid="1">
<div id="ZnpjSd"></div>
<div class="acUsEb Qi40Vc CoM3Df" role="navigation">
<a class="w5hRs" href="https://about.google..." ping="/url?sa=t&rct=j&sour...">
Showing first 5 of 129 audited elements.
Alternative text of images should not be repeated as text1 element
Duplicating alternative text adjacent to an image or link forces screen readers to announce the same information twice. This redundancy is unnecessary and confusing, especially when image buttons repeat their labels in nearby text.
Audit Elements
<img class="ESTs9d" alt="Labor Day 2026" height="400" src="/logos/doodles/2026/labor-day-2026-6753651837111014.3-2x.png" title="Labor Day 2026" width="1000" id="hplogo" data-csiid="E1SeaszGHpPz0PEP_f3giQg_2" data-atf="1">
ARIA attributes must be used as specified for the element's role13 elements
Using ARIA attributes where they're not expected causes unpredictable behavior in assistive technologies. Following the ARIA specification ensures that screen readers and other tools can properly interpret and communicate your content's meaning to people with disabilities.
Audit Elements
<a class="gb_6" aria-label="Gmail " data-pid="23" href="https://mail.google.com/mail/&ogbl" target="_top">Gmail</a>
<a class="gb_6" aria-label="Search for Images " data-pid="2" href="https://www.google.com/imghp?hl=en&ogbl" target="_top">Images</a>
<a class="gb_C" aria-label="Google apps" href="https://www.google.com/intl/en/about/products" aria-expanded="false" role="button" tabindex="0">
<a class="gb_A" aria-label="Sign in" href="https://accounts.google.com/ServiceLogin?hl=en&passive=true&continue=https://www.google.com/&ec=futura_exp_og_so_72776762_e" target="_top"><span class="gb_2">Sign in</span></a>
<div jscontroller="Wct42" data-dt="" data-sem="epsd1 rimspwouoe" data-sf="50" data-sm="1" role="button" tabindex="0" jsaction="KjsqPd;rcuQ6b:npT2md..." aria-label="Share" jsdata="B34zmc;_;E1SeaszGHpP..." data-hveid="9" data-ved="0ahUKEwiMnJqz5tuWAxW...">
Showing first 5 of 13 audited elements.
ARIA attributes must conform to valid names13 elements
Misspelled or non-existent ARIA attributes cannot perform their intended accessibility function. Assistive technologies rely on correctly spelled, current ARIA attributes to convey proper user interface behaviors and structural information to people with disabilities.
Audit Elements
<a class="gb_6" aria-label="Gmail " data-pid="23" href="https://mail.google.com/mail/&ogbl" target="_top">Gmail</a>
<a class="gb_6" aria-label="Search for Images " data-pid="2" href="https://www.google.com/imghp?hl=en&ogbl" target="_top">Images</a>
<a class="gb_C" aria-label="Google apps" href="https://www.google.com/intl/en/about/products" aria-expanded="false" role="button" tabindex="0">
<a class="gb_A" aria-label="Sign in" href="https://accounts.google.com/ServiceLogin?hl=en&passive=true&continue=https://www.google.com/&ec=futura_exp_og_so_72776762_e" target="_top"><span class="gb_2">Sign in</span></a>
<div jscontroller="Wct42" data-dt="" data-sem="epsd1 rimspwouoe" data-sf="50" data-sm="1" role="button" tabindex="0" jsaction="KjsqPd;rcuQ6b:npT2md..." aria-label="Share" jsdata="B34zmc;_;E1SeaszGHpP..." data-hveid="9" data-ved="0ahUKEwiMnJqz5tuWAxW...">
Showing first 5 of 13 audited elements.
ARIA attributes must conform to valid values12 elements
ARIA attributes must contain correctly spelled values that match the attribute's expected options. Invalid values prevent the accessibility feature from working, making content inaccessible to assistive technology users who depend on these attributes for navigation and interaction.
Audit Elements
<a class="gb_6" aria-label="Gmail " data-pid="23" href="https://mail.google.com/mail/&ogbl" target="_top">Gmail</a>
<a class="gb_6" aria-label="Search for Images " data-pid="2" href="https://www.google.com/imghp?hl=en&ogbl" target="_top">Images</a>
<a class="gb_C" aria-label="Google apps" href="https://www.google.com/intl/en/about/products" aria-expanded="false" role="button" tabindex="0">
<a class="gb_A" aria-label="Sign in" href="https://accounts.google.com/ServiceLogin?hl=en&passive=true&continue=https://www.google.com/&ec=futura_exp_og_so_72776762_e" target="_top"><span class="gb_2">Sign in</span></a>
<div jscontroller="Wct42" data-dt="" data-sem="epsd1 rimspwouoe" data-sf="50" data-sm="1" role="button" tabindex="0" jsaction="KjsqPd;rcuQ6b:npT2md..." aria-label="Share" jsdata="B34zmc;_;E1SeaszGHpP..." data-hveid="9" data-ved="0ahUKEwiMnJqz5tuWAxW...">
Showing first 5 of 12 audited elements.
ARIA commands must have an accessible name5 elements
Screen reader users cannot determine the purpose of interactive elements with role="link", role="button", or role="menuitem" that lack an accessible name. Without a name, these controls are essentially invisible to assistive technology users.
Audit Elements
<div jscontroller="Wct42" data-dt="" data-sem="epsd1 rimspwouoe" data-sf="50" data-sm="1" role="button" tabindex="0" jsaction="KjsqPd;rcuQ6b:npT2md..." aria-label="Share" jsdata="B34zmc;_;E1SeaszGHpP..." data-hveid="9" data-ved="0ahUKEwiMnJqz5tuWAxW...">
<div jscontroller="unV4T" jsname="F7uqIe" class="fzj3ad" data-hp="1" aria-label="Search by voice" role="button" tabindex="0" jsaction="h5M12e;rcuQ6b:npT2md;KHxBOb:EANhx;HINvVc:OUwavc;hATt5e:AkD3se;CQJmec:efDZmf" data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQvs8DCCY">
<div jscontroller="lpsUAf" jsname="R5mgy" class="etxtjc" data-is-images-mode="false" aria-label="Search by image" role="button" tabindex="0" jsaction="rcuQ6b:npT2md;h5M12e;AMruCe:Zpug7c" data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQhqEICCc">
<a jscontroller="Jlf2lc" class="m5Qfy" jsdata="fXexJ;_;E1SeaofPOJeh0PEP-PLfkQc1" rel="nofollow" role="link" tabindex="0" jsaction="UEmoBd" data-ved="2ahUKEwjHpLSz5tuWAxWXEDQIHXj5N3IQ8IcBegQIAhAB"> 🇺🇸 Honoring the contributions of American workers this Labor Day</a>
<div jsname="oYxtQd" class="CcNe6e" aria-expanded="false" aria-haspopup="true" role="button" tabindex="0" jsaction="WFrRFb;keydown:uYT2Vb"><div jsname="LgbsSe" class="JQmN7b eQtdDf" aria-controls="_E1SeaszGHpPz0PEP_f3giQg_21" aria-haspopup="true">Settings</div></div>
ARIA hidden element must not be focusable or contain focusable elements41 elements
Elements with aria-hidden="true" are removed from the accessibility API but remain keyboard-focusable, creating confusion about their visibility state. When users tab to these hidden elements, screen readers stay silent, leaving users unaware of what they've focused on or why nothing is being announced.
Audit Elements
<svg class="gb_H" aria-hidden="true" focusable="false" viewBox="0 0 24 24">
<svg focusable="false" aria-hidden="true" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24">
<svg focusable="false" aria-hidden="true" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M19 6.41L17.59 5 12 10.59 6.41 5 5 6.41 10.59 12 5 17.59 6.41 19 12 13.41 17.59 19 19 17.59 13.41 12z"></path></svg>
<svg aria-hidden="true" height="100%" viewBox="0 0 188 64" width="100%" xmlns="http://www.w3.org/2000/svg">
<g-left-button jsname="sIJmDf" class="pQXcHc wgbRNb bCwlI tHT0l OZ5bRd T9Wh5" style="top:0px;left:12px" aria-hidden="true" jsaction="PfjCMb" tabindex="-1" aria-label="Previous" role="button">
Showing first 5 of 41 audited elements.
ARIA role should be appropriate for the element79 elements
Invalid ARIA role and HTML element combinations can break accessibility for entire sections of your application. When roles are used incorrectly, assistive technologies may report confusing or nonsensical information to users, making it impossible for them to understand and interact with the interface properly.
Audit Elements
<div class="acUsEb Qi40Vc CoM3Df" role="navigation">
<header class="gb_y gb_Nd" id="gb" role="none">
<a class="gb_C" aria-label="Google apps" href="https://www.google.com/intl/en/about/products" aria-expanded="false" role="button" tabindex="0">
<div jscontroller="Wct42" data-dt="" data-sem="epsd1 rimspwouoe" data-sf="50" data-sm="1" role="button" tabindex="0" jsaction="KjsqPd;rcuQ6b:npT2md..." aria-label="Share" jsdata="B34zmc;_;E1SeaszGHpP..." data-hveid="9" data-ved="0ahUKEwiMnJqz5tuWAxW...">
<div class="naW5gc mL3MVc DYz2A" aria-level="1" role="heading">
Showing first 5 of 79 audited elements.
ARIA roles used must conform to valid values14 elements
Invalid ARIA role values prevent assistive technologies from understanding and communicating the element's purpose to users. Without valid roles, screen readers cannot provide information about the element's features, properties, or how users should interact with it.
Audit Elements
<div class="acUsEb Qi40Vc CoM3Df" role="navigation">
<header class="gb_y gb_Nd" id="gb" role="none">
<a class="gb_C" aria-label="Google apps" href="https://www.google.com/intl/en/about/products" aria-expanded="false" role="button" tabindex="0">
<div jscontroller="Wct42" data-dt="" data-sem="epsd1 rimspwouoe" data-sf="50" data-sm="1" role="button" tabindex="0" jsaction="KjsqPd;rcuQ6b:npT2md..." aria-label="Share" jsdata="B34zmc;_;E1SeaszGHpP..." data-hveid="9" data-ved="0ahUKEwiMnJqz5tuWAxW...">
<form action="/search" autocomplete="off" method="GET" role="search">
Showing first 5 of 14 audited elements.
aria-hidden="true" must not be present on the document body1 element
Setting <body aria-hidden="true" hides all page content from assistive technologies while leaving it visible on screen. This creates a confusing experience where keyboard users can still tab to elements, but screen readers remain completely silent, providing no information about what's focused.
Audit Elements
<body jsmodel="hspDDf " jsaction="xjhTIf:.CLIENT;O2vyse:.CLIENT;IVKTfe:.CLIENT;Ez7VMc:.CLIENT;R6Slyc:.CLIENT;ydZCDf:.CLIENT;idyTR:.CLIENT;yhGVIb:.CLIENT">
autocomplete attribute must be used correctly1 element
Missing or incorrect autocomplete values make forms inaccessible to screen reader users. Screen readers cannot provide adequate information about form fields without proper autocomplete attributes, preventing users from understanding what information is required and how to complete forms correctly.
Audit Elements
<textarea jsname="yZiJbe" class="gLFyf" aria-controls="Alh6id" aria-owns="Alh6id" autofocus="" aria-label="Search" placeholder="" aria-autocomplete="both" aria-expanded="false" aria-haspopup="false" autocapitalize="off" autocomplete="off" autocorrect="off" id="ti6dpd" maxlength="2048" name="q" ...>
Buttons must have discernible text2 elements
Screen reader users cannot determine the purpose of buttons without an accessible name. Without a name, users don't know what action the button will perform when activated.
Audit Elements
<button jsname="ko0Zye" class="UbbAWe" aria-label="Add files and tools" aria-haspopup="menu" tabindex="0" type="button" jsaction="AO4mJ;blur:dOOLne;keydown:YR8sId" data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQ0J0RCB8">
<button jsname="B6rgad" tabindex="0" jscontroller="jNZDL" class="plR5qb" role="link" jsaction="click:bujKIf;mouseen..." type="button" data-ved="0ahUKEwiMnJqz5tuWAxW...">
Contentinfo landmark should not be contained in another landmark1 element
The contentinfo landmark must be at the top level to help screen reader users quickly navigate to footer information. When nested inside another landmark, it becomes harder to find, defeating its purpose of providing quick access to content information.
Audit Elements
<div class="Ij8KCd" role="contentinfo">
Deprecated ARIA roles must not be used14 elements
Deprecated ARIA roles are not recognized by modern screen readers and assistive technologies. Using outdated roles means some users cannot access essential information or functionality on your site.
Audit Elements
<div class="acUsEb Qi40Vc CoM3Df" role="navigation">
<header class="gb_y gb_Nd" id="gb" role="none">
<a class="gb_C" aria-label="Google apps" href="https://www.google.com/intl/en/about/products" aria-expanded="false" role="button" tabindex="0">
<div jscontroller="Wct42" data-dt="" data-sem="epsd1 rimspwouoe" data-sf="50" data-sm="1" role="button" tabindex="0" jsaction="KjsqPd;rcuQ6b:npT2md..." aria-label="Share" jsdata="B34zmc;_;E1SeaszGHpP..." data-hveid="9" data-ved="0ahUKEwiMnJqz5tuWAxW...">
<form action="/search" autocomplete="off" method="GET" role="search">
Showing first 5 of 14 audited elements.
Document should not have more than one contentinfo landmark1 element
Multiple contentinfo landmarks force screen reader users to sort through extra options to find footer information. Each page should have only one content info landmark to enable quick, predictable navigation without overwhelming users with duplicate structural markers.
Audit Elements
<div class="Ij8KCd" role="contentinfo">
Documents must have <title> element to aid in navigation1 element
The page title is the first thing screen reader users hear when loading a page. Without a descriptive, unique title, users must read through the entire page to understand its contents and purpose, wasting valuable time on every page visit.
Audit Elements
<html itemscope="" itemtype="http://schema.org/WebPage" lang="en">
Elements must meet minimum color contrast ratio thresholds19 elements
People with low vision or color blindness cannot read text that lacks sufficient contrast with its background. With nearly three times more people having low vision than total blindness, and 8% of men and 0.4% of women having color deficiencies, adequate contrast is essential for making text readable to millions of users.
Audit Elements
<a class="w5hRs" href="https://about.google..." ping="/url?sa=t&rct=j&sour...">
<a class="w5hRs" href="https://store.google..." ping="/url?sa=t&rct=j&sour...">
<a class="gb_6" aria-label="Gmail " data-pid="23" href="https://mail.google.com/mail/&ogbl" target="_top">Gmail</a>
<a class="gb_6" aria-label="Search for Images " data-pid="2" href="https://www.google.com/imghp?hl=en&ogbl" target="_top">Images</a>
<span class="gb_2">Sign in</span>
Showing first 5 of 19 audited elements.
Elements must only use permitted ARIA attributes13 elements
Using prohibited ARIA attributes prevents important information from reaching assistive technology users. It also causes assistive technologies to behave inconsistently as they attempt to compensate for the error.
Audit Elements
<a class="gb_6" aria-label="Gmail " data-pid="23" href="https://mail.google.com/mail/&ogbl" target="_top">Gmail</a>
<a class="gb_6" aria-label="Search for Images " data-pid="2" href="https://www.google.com/imghp?hl=en&ogbl" target="_top">Images</a>
<a class="gb_C" aria-label="Google apps" href="https://www.google.com/intl/en/about/products" aria-expanded="false" role="button" tabindex="0">
<a class="gb_A" aria-label="Sign in" href="https://accounts.google.com/ServiceLogin?hl=en&passive=true&continue=https://www.google.com/&ec=futura_exp_og_so_72776762_e" target="_top"><span class="gb_2">Sign in</span></a>
<div jscontroller="Wct42" data-dt="" data-sem="epsd1 rimspwouoe" data-sf="50" data-sm="1" role="button" tabindex="0" jsaction="KjsqPd;rcuQ6b:npT2md..." aria-label="Share" jsdata="B34zmc;_;E1SeaszGHpP..." data-hveid="9" data-ved="0ahUKEwiMnJqz5tuWAxW...">
Showing first 5 of 13 audited elements.
Elements must only use supported ARIA attributes13 elements
Using ARIA attributes in roles where they're not allowed can disable accessibility for entire sections of your application. Invalid attribute-role combinations create conflicts that cause assistive technologies to report incorrect or nonsensical information about your interface.
Audit Elements
<a class="gb_6" aria-label="Gmail " data-pid="23" href="https://mail.google.com/mail/&ogbl" target="_top">Gmail</a>
<a class="gb_6" aria-label="Search for Images " data-pid="2" href="https://www.google.com/imghp?hl=en&ogbl" target="_top">Images</a>
<a class="gb_C" aria-label="Google apps" href="https://www.google.com/intl/en/about/products" aria-expanded="false" role="button" tabindex="0">
<a class="gb_A" aria-label="Sign in" href="https://accounts.google.com/ServiceLogin?hl=en&passive=true&continue=https://www.google.com/&ec=futura_exp_og_so_72776762_e" target="_top"><span class="gb_2">Sign in</span></a>
<div jscontroller="Wct42" data-dt="" data-sem="epsd1 rimspwouoe" data-sf="50" data-sm="1" role="button" tabindex="0" jsaction="KjsqPd;rcuQ6b:npT2md..." aria-label="Share" jsdata="B34zmc;_;E1SeaszGHpP..." data-hveid="9" data-ved="0ahUKEwiMnJqz5tuWAxW...">
Showing first 5 of 13 audited elements.
Elements should not have tabindex greater than zero10 elements
Using tabindex values greater than 0 creates unexpected tab orders that disorient users. It makes elements appear to be skipped when users tab past them, requires setting tabindex on every element to maintain order, and forces all tabindex items to be visited before any normal elements, breaking natural navigation flow.
Audit Elements
<a class="gb_C" aria-label="Google apps" href="https://www.google.com/intl/en/about/products" aria-expanded="false" role="button" tabindex="0">
<div jscontroller="Wct42" data-dt="" data-sem="epsd1 rimspwouoe" data-sf="50" data-sm="1" role="button" tabindex="0" jsaction="KjsqPd;rcuQ6b:npT2md..." aria-label="Share" jsdata="B34zmc;_;E1SeaszGHpP..." data-hveid="9" data-ved="0ahUKEwiMnJqz5tuWAxW...">
<button jsname="ko0Zye" class="UbbAWe" aria-label="Add files and tools" aria-haspopup="menu" tabindex="0" type="button" jsaction="AO4mJ;blur:dOOLne;keydown:YR8sId" data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQ0J0RCB8">
<div jscontroller="unV4T" jsname="F7uqIe" class="fzj3ad" data-hp="1" aria-label="Search by voice" role="button" tabindex="0" jsaction="h5M12e;rcuQ6b:npT2md;KHxBOb:EANhx;HINvVc:OUwavc;hATt5e:AkD3se;CQJmec:efDZmf" data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQvs8DCCY">
<div jscontroller="lpsUAf" jsname="R5mgy" class="etxtjc" data-is-images-mode="false" aria-label="Search by image" role="button" tabindex="0" jsaction="rcuQ6b:npT2md;h5M12e;AMruCe:Zpug7c" data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQhqEICCc">
Showing first 5 of 10 audited elements.
Focused elements must not be entirely hidden by author-created content13 elements
Keyboard users have no pointer to show where they are. The focus indicator is their only cue, and a sticky header, footer, cookie banner, or other author-created overlay that completely hides the focused control strands them with no idea what will activate next.
Audit Elements
<div jscontroller="unV4T" jsname="F7uqIe" class="fzj3ad" data-hp="1" aria-label="Search by voice" role="button" tabindex="0" jsaction="h5M12e;rcuQ6b:npT2md;KHxBOb:EANhx;HINvVc:OUwavc;hA..." data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQvs8DCCY">
<div jscontroller="lpsUAf" jsname="R5mgy" class="etxtjc" data-is-images-mode="false" aria-label="Search by image" role="button" tabindex="0" jsaction="rcuQ6b:npT2md;h5M12e;AMruCe:Zpug7c" data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQhqEICCc">
<button jsname="B6rgad" tabindex="0" jscontroller="jNZDL" class="plR5qb" role="link" jsaction="click:bujKIf;mouseenter:vG60uf;mouseleave:NS5Xl;C7..." type="button" data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQteYPCCg">
<input class="gNO89b" value="Google Search" aria-label="Google Search" name="btnK" role="button" tabindex="0" type="submit" data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQ4dUDCDU">
<div class="gbqfba gbqfba-hvr" role="button" style="display: block; font-family: "Google Sans&quo..." tabindex="0" aria-label="I'm Feeling Stellar">
Showing first 5 of 13 audited elements.
Form elements must have labels1 element
Form labels are essential for screen reader users to understand what information each field requires. Without proper labels, screen readers cannot identify input expectations, fields don't receive focus when announced, and users with motor impairments lose the benefit of larger clickable areas that labels provide.
Audit Elements
<textarea jsname="yZiJbe" class="gLFyf" aria-controls="Alh6id" aria-owns="Alh6id" autofocus="" aria-label="Search" placeholder="" aria-autocomplete="both" aria-expanded="false" aria-haspopup="false" autocapitalize="off" autocomplete="off" autocorrect="off" id="ti6dpd" maxlength="2048" name="q" ...>
Form elements should have a visible label1 element
The title and aria-describedby attributes provide supplementary hints, not labels. Screen readers treat these as advisory information rather than true labels, which prevents them from properly conveying the form element's purpose. Form fields need proper labels that can be programmatically determined.
Audit Elements
<textarea jsname="yZiJbe" class="gLFyf" aria-controls="Alh6id" aria-owns="Alh6id" autofocus="" aria-label="Search" placeholder="" aria-autocomplete="both" aria-expanded="false" aria-haspopup="false" autocapitalize="off" autocomplete="off" autocorrect="off" id="ti6dpd" maxlength="2048" name="q" ...>
Form field must not have multiple label elements1 element
Multiple labels on the same form field cause inconsistent behavior across screen reader and browser combinations. Some will read the first label, others the last, and some will read both, creating confusion about what information the field requires.
Audit Elements
<textarea jsname="yZiJbe" class="gLFyf" aria-controls="Alh6id" aria-owns="Alh6id" autofocus="" aria-label="Search" placeholder="" aria-autocomplete="both" aria-expanded="false" aria-haspopup="false" autocapitalize="off" autocomplete="off" autocorrect="off" id="ti6dpd" maxlength="2048" name="q" ...>
IDs used in ARIA and labels must be unique4 elements
Duplicate IDs break the accessibility of ARIA elements, form labels, and table headers. When IDs are duplicated, assistive technologies and scripts only reference the first instance, causing subsequent elements with the same ID to be ignored or incorrectly associated.
Audit Elements
<div class="h8bBW" id="_E1SeaszGHpPz0PEP_f3giQg_6" aria-hidden="true">Tools</div>
<span style="display:none" id="sb-accessible-label-4">Remove Create Images</span>
<span style="display:none" id="sb-accessible-label-2">Remove Canvas</span>
<div class="gDtRnb" id="Alh6id" role="presentation"><div jsname="erkvQe" class="erkvQe"></div><div jsname="tovEib" class="e1R9Ud" role="presentation"></div></div>
Images must have alternative text1 element
Screen readers cannot translate images into text without alt attributes. Alternative text is essential for blind users and beneficial for users with low vision or color blindness, providing the same information that sighted users get from viewing the image.
Audit Elements
<img class="ESTs9d" alt="Labor Day 2026" height="400" src="/logos/doodles/2026/labor-day-2026-6753651837111014.3-2x.png" title="Labor Day 2026" width="1000" id="hplogo" data-csiid="E1SeaszGHpPz0PEP_f3giQg_2" data-atf="1">
Inline text spacing must be adjustable with custom stylesheets4 elements
Single-spaced text makes it difficult for people with cognitive disabilities to track lines while reading. Providing line spacing between 1.5 to 2 helps these users start a new line more easily after finishing the previous one.
Audit Elements
<div style="height:calc(100% - 400px)"></div>
<span class="CdXeWb z1asCe Fp7My" style="height:18px;line-height:18px;width:18px">
<div jsname="IVmF1e" class="CcxW7b BznTFe" style="--BgHDjb: 100px; --bFlrOb: 4px; --HM63Tc: -1px; --sjdAce: 4; --mWus4b: 1.5;">
<span class="PD3zdc L0nkUd z1asCe" style="height:20px;line-height:20px;width:20px">
Input buttons must have discernible text2 elements
Screen reader users cannot understand an input type="button"'s purpose without an accessible name. Unnamed button images provide no description of their destination, purpose, or function, leaving users unable to make informed decisions about activating them.
Audit Elements
<input class="gNO89b" value="Google Search" aria-label="Google Search" name="btnK" role="button" tabindex="0" type="submit" data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQ4dUDCDU">
<input id="gbqfbb" value="I'm Feeling Lucky" aria-label="I'm Feeling Lucky" name="btnI" role="button" tabindex="0" type="submit" data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQnRsINg">
Interactive controls must not be nested9 elements
Nested interactive elements create empty tab stops where screen readers remain silent. When users tab to a focusable element inside another interactive control, they receive no information about its name, role, or state, creating a confusing and broken navigation experience.
Audit Elements
<a class="gb_C" aria-label="Google apps" href="https://www.google.com/intl/en/about/products" aria-expanded="false" role="button" tabindex="0">
<img class="ESTs9d" alt="Labor Day 2026" height="400" src="/logos/doodles/2026/labor-day-2026-6753651837111014.3-2x.png" title="Labor Day 2026" width="1000" id="hplogo" data-csiid="E1SeaszGHpPz0PEP_f3giQg_2" data-atf="1">
<div jscontroller="Wct42" data-dt="" data-sem="epsd1 rimspwouoe" data-sf="50" data-sm="1" role="button" tabindex="0" jsaction="KjsqPd;rcuQ6b:npT2md..." aria-label="Share" jsdata="B34zmc;_;E1SeaszGHpP..." data-hveid="9" data-ved="0ahUKEwiMnJqz5tuWAxW...">
<button jsname="ko0Zye" class="UbbAWe" aria-label="Add files and tools" aria-haspopup="menu" tabindex="0" type="button" jsaction="AO4mJ;blur:dOOLne;keydown:YR8sId" data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQ0J0RCB8">
<div jscontroller="unV4T" jsname="F7uqIe" class="fzj3ad" data-hp="1" aria-label="Search by voice" role="button" tabindex="0" jsaction="h5M12e;rcuQ6b:npT2md;KHxBOb:EANhx;HINvVc:OUwavc;hATt5e:AkD3se;CQJmec:efDZmf" data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQvs8DCCY">
Showing first 5 of 9 audited elements.
Interactive elements must have a visible focus indicator13 elements
Sighted keyboard users rely on a visible focus indicator to know where they are on the page. When focus styles are missing, too subtle, or have insufficient contrast against the surrounding colors, users cannot tell which element will respond when they press Enter or Space, making keyboard navigation slow and error-prone. This especially affects people with motor impairments who cannot use a mouse and people with low vision who need clear, high-contrast indicators.
Audit Elements
<div jscontroller="unV4T" jsname="F7uqIe" class="fzj3ad" data-hp="1" aria-label="Search by voice" role="button" tabindex="0" jsaction="h5M12e;rcuQ6b:npT2md;KHxBOb:EANhx;HINvVc:OUwavc;hA..." data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQvs8DCCY">
<div jscontroller="lpsUAf" jsname="R5mgy" class="etxtjc" data-is-images-mode="false" aria-label="Search by image" role="button" tabindex="0" jsaction="rcuQ6b:npT2md;h5M12e;AMruCe:Zpug7c" data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQhqEICCc">
<button jsname="B6rgad" tabindex="0" jscontroller="jNZDL" class="plR5qb" role="link" jsaction="click:bujKIf;mouseenter:vG60uf;mouseleave:NS5Xl;C7..." type="button" data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQteYPCCg">
<input class="gNO89b" value="Google Search" aria-label="Google Search" name="btnK" role="button" tabindex="0" type="submit" data-ved="0ahUKEwiMnJqz5tuWAxWTOTQIHf0-OIEQ4dUDCDU">
<div class="gbqfba gbqfba-hvr" role="button" style="display: block; font-family: "Google Sans&quo..." tabindex="0" aria-label="I'm Feeling Stellar">
Showing first 5 of 13 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination3 elements
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Audit Elements
<div class="acUsEb Qi40Vc CoM3Df" role="navigation">
<form action="/search" autocomplete="off" method="GET" role="search">
<div class="Ij8KCd" role="contentinfo">
Links must have discernible text13 elements
Keyboard users and screen reader users can only interact with links that have accessible names and can receive focus. Without proper names, users don't know where links lead. Without keyboard focus, users who cannot use a mouse cannot activate the links at all.
Audit Elements
<a class="w5hRs" href="https://about.google..." ping="/url?sa=t&rct=j&sour...">
<a class="w5hRs" href="https://store.google..." ping="/url?sa=t&rct=j&sour...">
<a class="gb_6" aria-label="Gmail " data-pid="23" href="https://mail.google.com/mail/&ogbl" target="_top">Gmail</a>
<a class="gb_6" aria-label="Search for Images " data-pid="2" href="https://www.google.com/imghp?hl=en&ogbl" target="_top">Images</a>
<a class="gb_C" aria-label="Google apps" href="https://www.google.com/intl/en/about/products" aria-expanded="false" role="button" tabindex="0">
Showing first 5 of 13 audited elements.
Required ARIA attributes must be provided14 elements
ARIA widget roles need required attributes to describe their current state. Without these attributes, screen readers cannot communicate essential information like whether a checkbox is checked or a slider's current value, leaving users unable to interact effectively with the widget.
Audit Elements
<div class="acUsEb Qi40Vc CoM3Df" role="navigation">
<header class="gb_y gb_Nd" id="gb" role="none">
<a class="gb_C" aria-label="Google apps" href="https://www.google.com/intl/en/about/products" aria-expanded="false" role="button" tabindex="0">
<div jscontroller="Wct42" data-dt="" data-sem="epsd1 rimspwouoe" data-sf="50" data-sm="1" role="button" tabindex="0" jsaction="KjsqPd;rcuQ6b:npT2md..." aria-label="Share" jsdata="B34zmc;_;E1SeaszGHpP..." data-hveid="9" data-ved="0ahUKEwiMnJqz5tuWAxW...">
<form action="/search" autocomplete="off" method="GET" role="search">
Showing first 5 of 14 audited elements.
Text must remain readable when spacing is increased0 elements
People with low vision and dyslexia increase line height, letter spacing, word spacing, and paragraph spacing so they can read. Fixed-height boxes and overflow: hidden containers clip or overlap that text, which is a loss of content under WCAG 1.4.12.
How does your site stack up against Google?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Search Engine