Bing bing.com
Accessibility score
League position
7thof 9
Issues found
11
Audits passed
54
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
SeriousElements must only use permitted ARIA attributes1 element
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.
Failing Elements
<div id="sw_as" data-island="as" style="display: block; margin-left: 0px; margin-right: 0px;" aria-label="Suggestions">
Fix all of the following:
- aria-label attribute cannot be used on "div" elements with no valid role attribute.
SeriousElements must have their visible text as part of their accessible name16 elements
Interactive widgets that support name from content must have aria-label or aria-labelledby values that match their visible text. Mismatches confuse voice control users who speak the visible label but activate a different function based on the hidden accessible name.
Failing Elements
<a target="_blank" class="card-item-ntp card-i..." data-t="{"n":"CarouselCard",..." href="https://www.msn.com/..." aria-label="Bike Racing 1">Fix any of the following:
- Text inside the element is not included in the accessible name
<a target="_blank" class="card-item-ntp card-i..." data-t="{"n":"RandomGameExpl..." href="https://www.msn.com/..." aria-label="Darts FRVR">Fix any of the following:
- Text inside the element is not included in the accessible name
<a target="_blank" class="card-item-ntp card-i..." data-t="{"n":"CarouselCard",..." href="https://www.msn.com/..." aria-label="Pass The Ball">Fix any of the following:
- Text inside the element is not included in the accessible name
<a target="_blank" class="card-item-ntp card-i..." data-t="{"n":"CarouselCard",..." href="https://www.msn.com/..." aria-label="Jelly Run 2048">Fix any of the following:
- Text inside the element is not included in the accessible name
<a target="_blank" class="card-item-ntp card-i..." data-t="{"n":"CarouselCard",..." href="https://www.msn.com/..." aria-label="Drift Boss">Fix any of the following:
- Text inside the element is not included in the accessible name
<a target="_blank" class="card-item-ntp card-i..." data-t="{"n":"CarouselCard",..." href="https://www.msn.com/..." aria-label="Fragen">Fix any of the following:
- Text inside the element is not included in the accessible name
<a target="_blank" class="card-item-ntp card-i..." data-t="{"n":"CarouselCard",..." href="https://www.msn.com/..." aria-label="Driving School Simul...">Fix any of the following:
- Text inside the element is not included in the accessible name
<a target="_blank" class="card-item-ntp card-i..." data-t="{"n":"CarouselCard",..." href="https://www.msn.com/..." aria-label="Real Car Driving">Fix any of the following:
- Text inside the element is not included in the accessible name
<a target="_blank" class="card-item-ntp card-i..." data-t="{"n":"CarouselCard",..." href="https://www.msn.com/..." aria-label="Penalty Shooter">Fix any of the following:
- Text inside the element is not included in the accessible name
<a target="_blank" class="card-item-ntp card-i..." data-t="{"n":"CarouselCard",..." href="https://www.msn.com/..." aria-label="Super Racing GT : Dr...">Fix any of the following:
- Text inside the element is not included in the accessible name
Showing first 10 of 16 failing elements.
SeriousForm 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.
Failing Elements
<textarea id="sb_form_q" class="sb_form_q" name="q" type="search" rows="1" style="width: 843px;" placeholder="Search the web" maxlength="2000" autocapitalize="off" autocomplete="off" spellcheck="false" title="Enter your search te..." autofocus="" role="combobox" inputmode="search" ...>
Fix all of the following:
- Only title used to generate label for form element
SeriousContent must reflow without two-dimensional scrolling77 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 class="hp_body hp_body_ssrshell ">
<div class="hp_body">
<div style="--hp-cover-opacity: 0;">
<div>
<div class="hpl">
<div class="hpl hp_cont" role="main">
<div class="hpl">
<div class="bottom_row widget msnpeek nomvs" data-priority="2">
<div class="scroll_cont show_all_onerowup" id="scroll_cont">
<div class="vs_cont" id="vs_cont">
Showing first 10 of 77 failing elements.
SeriousText must remain readable when spacing is increased18 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.
Failing Elements
<span>
<a id="heading" class="heading" data-t="{"n":"destination","t&quo..." href="https://www.msn.com/en-nz/news/other/russia-didn-t..." aria-label="Russia didn’t see it coming: Ukraine’s troops pull..." target="_blank"><span class="articleTitle">
<span class="articleTitle">
<a id="heading" class="heading" data-t="{"n":"destination","t&quo..." href="https://www.msn.com/en-nz/entertainment/celebritie..." aria-label="Ellen tried to embarrass Dakota Johnson on live TV..." target="_blank"><a id="heading" class="heading" data-t="{"n":"destination","t&quo..." href="https://www.msn.com/en-nz/news/other/macron-fires-..." aria-label="Macron fires back at Trump: claims that migrants a..." target="_blank"><a part="footer-link" target="_blank" aria-label="See watchlist suggestions" class="footer footer-link blue-cta" data-t="{"n":"seemorelink","t&quo..." href="https://www.msn.com/en-nz/money/watchlist?ocid=Bin..." title="See watchlist suggestions"><div class="price">
<div class="symb-text">
<div class="symb-text">
Showing first 10 of 18 failing elements.
ModerateHeading levels should only increase by one1 element
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Failing Elements
<h3>
Fix any of the following:
- Heading order invalid
ModerateMain landmark should not be contained in another landmark1 element
The main landmark must be at the top level and not nested inside other landmarks. This ensures screen reader users can quickly navigate to the primary content without searching through complex hierarchy, making page navigation simpler and more predictable.
Failing Elements
<div id="waterfallFeedHolder" role="main" class="waterfall-view-feed-root" data-t="{"n":"WaterfallViewFeed","t":8}">Fix any of the following:
- The main landmark is contained in another landmark.
ModerateDocument should not have more than one main landmark1 element
Multiple main landmarks confuse screen reader users about where the primary content is located. Each page should have only one main landmark so users can quickly and predictably navigate to the primary content area.
Failing Elements
<div class="hpl hp_cont" role="main"><div style="display: none;"></div><div class="dimmer cdxShowConv hp_focus_overlay"></div></div>
Fix any of the following:
- Document has more than one main landmark
ModerateLandmarks should have a unique role or role/label/title (i.e. accessible name) combination1 element
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.
Failing Elements
<div class="hpl hp_cont" role="main"><div style="display: none;"></div><div class="dimmer cdxShowConv hp_focus_overlay"></div></div>
Fix any of the following:
- The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
ModerateAll page content should be contained by landmarks5 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
<div id="aitools_island" data-island="aitools" data-priority="2">
Fix any of the following:
- Some page content is not contained by landmarks
<div class="bingwpapptext"><a href="https://go.microsoft.com/fwlink/?linkid=2127455" data-h="ID=HpApp,31826.1" target="_blank" class="bingwpapplink" rel="noopener" tabindex="0"><div>Get the Bing Wallpaper app</div></a></div>
Fix any of the following:
- Some page content is not contained by landmarks
<h3>
Fix any of the following:
- Some page content is not contained by landmarks
<div class="copyright" id="copyright">© Andrey Popov/Getty Images</div>
Fix any of the following:
- Some page content is not contained by landmarks
<h2 class="text" id="headline">Info</h2>
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 id="sb_form_q" class="sb_form_q" name="q" type="search" rows="1" style="width: 843px;" placeholder="Search the web" maxlength="2000" autocapitalize="off" autocomplete="off" spellcheck="false" title="Enter your search te..." autofocus="" role="combobox" inputmode="search" ...>
Fix any of the following:
- ARIA role combobox is not allowed for given element
Passed audits54 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 lang="en" dir="ltr">
<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 lang="en" dir="ltr">
<li> elements must be contained in a <ul> or <ol>28 elements
Lists require proper semantic hierarchy with ul or ol parent elements and li child elements. This structure allows screen readers to announce when users enter a list, how many items it contains, and which item they're currently on, providing essential context for understanding the content.
Audit Elements
<li>
<li class="tile_grp" data-bm="31">
<li class="pntile">
<li class="pntile">
<li class="pntile">
Showing first 5 of 28 audited elements.
<svg> elements with an img or image role must have alternative text1 element
SVG images need text alternatives so their information can be accessed through any sensory modality - visual, auditory, or tactile. Text alternatives enable screen readers to convert visual information into speech or braille, support future translation into sign language, and ensure content is accessible regardless of a user's sensory abilities.
Audit Elements
<svg id="bLogo" role="img" class="logo" viewBox="0 0 24 24" aria-label="Microsoft Logo Image">
<ul> and <ol> must only directly contain <li>, <script> or <template> elements3 elements
Lists must contain only li elements as direct children (besides non-content elements like script or style). When other content elements appear within ul or ol tags, screen readers cannot properly inform users they're listening to list items, breaking the expected list navigation experience.
Audit Elements
<ul class="share">
<ul id="trending_now_tile" class="">
<ul class="items">
All page content should be contained by landmarks1640 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 class="hp_body hp_body_ssrshell ">
<header class="header header-full" id="hdr" data-priority="2">
<div class="head_cont " id="headCont">
<h1 class="logo_cont" aria-labelledby="bLogo">
<svg id="bLogo" role="img" class="logo" viewBox="0 0 24 24" aria-label="Microsoft Logo Image">
Showing first 5 of 1640 audited elements.
All touch targets must be 24px large, or leave sufficient space266 elements
Touch targets must be large enough or spaced far enough apart to be activated without accidentally hitting adjacent controls. This helps users on mobile devices, people with hand tremors or mobility impairments, users in shaking environments like public transit, and anyone using one hand or large fingers to interact with the interface.
Audit Elements
<a class="customIcon" href="/chat?FORM=hpcodx&intent=bing" h="ID=SERP,5057.1">
<a href="/images?FORM=Z9LH" h="ID=SERP,5058.1">Images</a>
<a href="/videos?FORM=Z9LH1" h="ID=SERP,5059.1">Videos</a>
<a href="/maps?FORM=Z9LH2" h="ID=SERP,5060.1">Maps</a>
<a href="/news/search?q=Top+stories&nvaug=%5bNewsVertical+Category%3d%22rt_MaxClass%22%5d&FORM=Z9LH3" h="ID=SERP,5061.1">News</a>
Showing first 5 of 266 audited elements.
Alternative text of images should not be repeated as text79 elements
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 src="data:image/svg+xml,%..." height="16" width="16" alt="" role="presentation" class="rms_img" data-bm="0">
<img src="/th?id=ONUT.bzj5c6LMLts5KutsMKSh3Q&w=186&h=88&c=7&rs=2&qlt=80&pid=PopNow" title="© Sam Chui" alt="© Sam Chui" elementtiming="TTVRCore.TrendingOnBing" data-bm="11">
<img src="/th?id=ONUT.RfOwE9SZfo4aPEjxISTVVw&w=186&h=88&c=7&rs=2&qlt=80&pid=PopNow" title="© Daily Mail" alt="© Daily Mail" data-bm="12">
<img src="/th?id=ONUT.jakSEvspFjkAGIj1DLJ9lg&w=186&h=88&c=7&rs=2&qlt=80&pid=PopNow" title="© Daily Mail" alt="© Daily Mail" data-bm="13">
<img src="/th?id=ONUT.4aZXxYhwT4AbXN-tpnP5bg&w=186&h=88&c=7&rs=2&qlt=80&pid=PopNow" title="© Daily Mail" alt="© Daily Mail" data-bm="14">
Showing first 5 of 79 audited elements.
ARIA attributes must be used as specified for the element's role265 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
<h1 class="logo_cont" aria-labelledby="bLogo">
<svg id="bLogo" role="img" class="logo" viewBox="0 0 24 24" aria-label="Microsoft Logo Image">
<li class="scope " id="codex" role="menuitem" aria-haspopup="false">
<li class="scope " id="images" role="menuitem" aria-haspopup="false"><a href="/images?FORM=Z9LH" h="ID=SERP,5058.1">Images</a></li>
<li class="scope try_exp" id="video" role="menuitem" aria-haspopup="false"><a href="/videos?FORM=Z9LH1" h="ID=SERP,5059.1">Videos</a></li>
Showing first 5 of 265 audited elements.
ARIA attributes must conform to valid names265 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
<h1 class="logo_cont" aria-labelledby="bLogo">
<svg id="bLogo" role="img" class="logo" viewBox="0 0 24 24" aria-label="Microsoft Logo Image">
<li class="scope " id="codex" role="menuitem" aria-haspopup="false">
<li class="scope " id="images" role="menuitem" aria-haspopup="false"><a href="/images?FORM=Z9LH" h="ID=SERP,5058.1">Images</a></li>
<li class="scope try_exp" id="video" role="menuitem" aria-haspopup="false"><a href="/videos?FORM=Z9LH1" h="ID=SERP,5059.1">Videos</a></li>
Showing first 5 of 265 audited elements.
ARIA attributes must conform to valid values259 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
<h1 class="logo_cont" aria-labelledby="bLogo">
<svg id="bLogo" role="img" class="logo" viewBox="0 0 24 24" aria-label="Microsoft Logo Image">
<li class="scope " id="codex" role="menuitem" aria-haspopup="false">
<li class="scope " id="images" role="menuitem" aria-haspopup="false"><a href="/images?FORM=Z9LH" h="ID=SERP,5058.1">Images</a></li>
<li class="scope try_exp" id="video" role="menuitem" aria-haspopup="false"><a href="/videos?FORM=Z9LH1" h="ID=SERP,5059.1">Videos</a></li>
Showing first 5 of 259 audited elements.
ARIA commands must have an accessible name43 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
<li class="scope " id="codex" role="menuitem" aria-haspopup="false">
<li class="scope " id="images" role="menuitem" aria-haspopup="false"><a href="/images?FORM=Z9LH" h="ID=SERP,5058.1">Images</a></li>
<li class="scope try_exp" id="video" role="menuitem" aria-haspopup="false"><a href="/videos?FORM=Z9LH1" h="ID=SERP,5059.1">Videos</a></li>
<li class="scope try_exp" id="local" role="menuitem" aria-haspopup="false"><a href="/maps?FORM=Z9LH2" h="ID=SERP,5060.1">Maps</a></li>
<li class="scope try_exp" id="news" role="menuitem" aria-haspopup="false"><a href="/news/search?q=Top+stories&nvaug=%5bNewsVertical+Category%3d%22rt_MaxClass%22%5d&FORM=Z9LH3" h="ID=SERP,5061.1">News</a></li>
Showing first 5 of 43 audited elements.
ARIA dialog and alertdialog nodes should have an accessible name1 element
Screen reader users cannot identify the purpose of role="dialog" or role="alertdialog" elements without an accessible name. This leaves users confused about what dialog they've encountered and what it contains.
Audit Elements
<div id="qs_searchBoxOuter" role="dialog" aria-label="Quick Search"><a id="qs_searchBox"><div id="qs_selectedText"></div><div id="qs_searchIconOuter"><span id="qs_searchIconInner"></span></div></a></div>
ARIA hidden element must not be focusable or contain focusable elements211 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
<g class="squares" aria-hidden="true"><path class="top_l" d="M0 0h11.35v11.35H0z"></path><path class="top_r" d="M12.53 0h11.35v11.35H12.53z"></path><path class="bom_l" d="M0 12.53h11.35v11.35H0z"></path><path class="bom_r" d="M12.53 12.53h11.35v11.35H12.53z"></path></g>
<div elementtiming="TTVRCore.Logo" aria-hidden="true" style="pointer-events:none;margin-top:-1px;height:1px;width:1px;font-size:1px;position:absolute;top:0;right:0;" tabindex="-1"> </div>
<span aria-hidden="true"><a tabindex="-1" href="/videos?FORM=Z9LH1" h="ID=SERP,5062.1">Videos</a></span>
<span aria-hidden="true"><a tabindex="-1" href="/search?q=Bing+translate&FORM=TTAHP1" h="ID=SERP,5063.1">Translate</a></span>
<span aria-hidden="true"><a tabindex="-1" href="/maps?FORM=Z9LH2" h="ID=SERP,5064.1">Maps</a></span>
Showing first 5 of 211 audited elements.
ARIA role should be appropriate for the element212 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
<svg id="bLogo" role="img" class="logo" viewBox="0 0 24 24" aria-label="Microsoft Logo Image">
<ul class="scopes" role="menubar">
<li class="scope " id="codex" role="menuitem" aria-haspopup="false">
<img src="data:image/svg+xml,%..." height="16" width="16" alt="" role="presentation" class="rms_img" data-bm="0">
<li class="scope " id="images" role="menuitem" aria-haspopup="false"><a href="/images?FORM=Z9LH" h="ID=SERP,5058.1">Images</a></li>
Showing first 5 of 212 audited elements.
ARIA roles used must conform to valid values172 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
<svg id="bLogo" role="img" class="logo" viewBox="0 0 24 24" aria-label="Microsoft Logo Image">
<ul class="scopes" role="menubar">
<li class="scope " id="codex" role="menuitem" aria-haspopup="false">
<img src="data:image/svg+xml,%..." height="16" width="16" alt="" role="presentation" class="rms_img" data-bm="0">
<li class="scope " id="images" role="menuitem" aria-haspopup="false"><a href="/images?FORM=Z9LH" h="ID=SERP,5058.1">Images</a></li>
Showing first 5 of 172 audited elements.
ARIA tab nodes must have an accessible name34 elements
Ensure every ARIA tab node has an accessible name
Audit Elements
<div class="tab" part="tab" slot="tab" role="tab" aria-label="News story" data-t="{"n":"infopanetab","t":11,"b":12,"c.hl":"infopanetab"}" id="tab-0" aria-selected="true" aria-controls="AA2fytQc" tabindex="0" style="grid-column: 1;"><div class="tab" part="tab" slot="tab" role="tab" aria-label="News story" data-t="{"n":"infopanetab","t":11,"b":12,"c.hl":"infopanetab"}" id="tab-1" aria-selected="false" aria-controls="AA1U6YRl" tabindex="-1" style="grid-column: 2;"><div class="tab" part="tab" slot="tab" role="tab" aria-label="News story" data-t="{"n":"infopanetab","t":11,"b":12,"c.hl":"infopanetab"}" id="tab-2" aria-selected="false" aria-controls="AA2g32mG" tabindex="-1" style="grid-column: 3;"><div class="tab" part="tab" slot="tab" role="tab" aria-label="News story" data-t="{"n":"infopanetab","t":11,"b":12,"c.hl":"infopanetab"}" id="tab-3" aria-selected="false" aria-controls="AA2aYcrX" tabindex="-1" style="grid-column: 4;"><div class="tab" part="tab" slot="tab" role="tab" aria-label="News story" data-t="{"n":"infopanetab","t":11,"b":12,"c.hl":"infopanetab"}" id="tab-4" aria-selected="false" aria-controls="AA2atDcr" tabindex="-1" style="grid-column: 5;">Showing first 5 of 34 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>
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 id="sb_form_q" class="sb_form_q" name="q" type="search" rows="1" style="width: 843px;" placeholder="Search the web" maxlength="2000" autocapitalize="off" autocomplete="off" spellcheck="false" title="Enter your search te..." autofocus="" role="combobox" inputmode="search" ...>
Banner landmark should not be contained in another landmark1 element
Banner landmarks must be top-level to effectively designate the header portion of the page. Nested banner landmarks fail to provide the structural information screen reader users need to navigate efficiently through the page layout.
Audit Elements
<header class="header header-full" id="hdr" data-priority="2">
Buttons must have discernible text98 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 id="sb_feedback_floating" class="feedback_button" role="button">
<button part="button-bg upvote" tab-index="0" aria-pressed="false" aria-label="43 Likes" aria-description="More like this" class="icon-button reaction..." data-content="More like this" title="" data-customhandled="true" data-t="{"n":"Upvote","t":11..."><button part="button-bg downvote" tab-index="0" aria-pressed="false" aria-label="Dislike" aria-description="Fewer like this" class="icon-button reaction..." data-content="Fewer like this" title="" data-customhandled="true" data-t="{"n":"Downvote","t":..."><button class="hide-card-button" data-t="{"n":"showFewer","t"..." title="Hide this story" aria-label="Hide this story"><button class="card-actions-button" data-t="{"n":"Card Action El..." title="See more" aria-label="See more">Showing first 5 of 98 audited elements.
Certain ARIA roles must be contained by particular parents43 elements
ARIA roles with missing required parent elements cannot function as intended for assistive technology users. Parent-child relationships convey essential hierarchy and context, like showing where an item sits within a tree structure. Without proper parents, this critical relationship information is lost.
Audit Elements
<li class="scope " id="codex" role="menuitem" aria-haspopup="false">
<li class="scope " id="images" role="menuitem" aria-haspopup="false"><a href="/images?FORM=Z9LH" h="ID=SERP,5058.1">Images</a></li>
<li class="scope try_exp" id="video" role="menuitem" aria-haspopup="false"><a href="/videos?FORM=Z9LH1" h="ID=SERP,5059.1">Videos</a></li>
<li class="scope try_exp" id="local" role="menuitem" aria-haspopup="false"><a href="/maps?FORM=Z9LH2" h="ID=SERP,5060.1">Maps</a></li>
<li class="scope try_exp" id="news" role="menuitem" aria-haspopup="false"><a href="/news/search?q=Top+stories&nvaug=%5bNewsVertical+Category%3d%22rt_MaxClass%22%5d&FORM=Z9LH3" h="ID=SERP,5061.1">News</a></li>
Showing first 5 of 43 audited elements.
Certain ARIA roles must contain particular children7 elements
ARIA roles missing required child elements cannot perform their intended accessibility functions. Children provide essential context, like how a treeitem relates to its parent container and siblings. Without proper children, assistive technologies cannot convey this structural information to users.
Audit Elements
<ul class="scopes" role="menubar">
<ul id="crs_pane" role="list">
<div class="tablist" part="tablist" role="tablist">
<div class="container" role="list" data-t="{"n":"listContent","c.t":1,"c.c":"topstories","ext":{"cid":"4","cid1s":"CanonicalName-topstories","co":4,"col":1,"ct1s":"TopicFeed","height":304,"row":2,"slot":1,"traceIdIndex":0,"width":300}}"><div class="tablist" role="tablist">
Showing first 5 of 7 audited elements.
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
<footer class="footer dynamic_footer" id="footer">
Deprecated ARIA roles must not be used172 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
<svg id="bLogo" role="img" class="logo" viewBox="0 0 24 24" aria-label="Microsoft Logo Image">
<ul class="scopes" role="menubar">
<li class="scope " id="codex" role="menuitem" aria-haspopup="false">
<img src="data:image/svg+xml,%..." height="16" width="16" alt="" role="presentation" class="rms_img" data-bm="0">
<li class="scope " id="images" role="menuitem" aria-haspopup="false"><a href="/images?FORM=Z9LH" h="ID=SERP,5058.1">Images</a></li>
Showing first 5 of 172 audited elements.
Document 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.
Audit Elements
<html lang="en" dir="ltr">
Document should not have more than one banner landmark1 element
Multiple banner landmarks force screen reader users to sort through duplicate options to find header information. Each page should have only one banner landmark to enable quick, predictable navigation to the header without overwhelming users with unnecessary choices.
Audit Elements
<header class="header header-full" id="hdr" data-priority="2">
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
<footer class="footer dynamic_footer" id="footer">
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 lang="en" dir="ltr">
Elements marked as presentational should be consistently ignored22 elements
Elements with role="none" or role="presentation" should be removed from the accessibility tree. Adding global ARIA attributes or making these elements focusable prevents their removal, leaving them accessible to screen readers when they should be ignored, creating unexpected and confusing behavior.
Audit Elements
<img src="data:image/svg+xml,%..." height="16" width="16" alt="" role="presentation" class="rms_img" data-bm="0">
<img alt="" src="https://assets.msn.com/staticsb/statics/latest/icons-wc/icons/dark-mode/detectLocDark.svg">
<img alt="" class="icon-img" src="https://assets.msn.com/staticsb/statics/latest/fluent-icons/chevron_down_12_regular.svg">
<img alt="" class="icon-img" part="more-actions-icon" src="https://assets.msn.com/staticsb/statics/latest/fluent-icons/more_horizontal_16_regular.svg">
<img alt="" src="https://assets.msn.com/staticsb/statics//latest/icons/NtpTopStories.svg">
Showing first 5 of 22 audited elements.
Elements must have their visible text as part of their accessible name52 elements
Interactive widgets that support name from content must have aria-label or aria-labelledby values that match their visible text. Mismatches confuse voice control users who speak the visible label but activate a different function based on the hidden accessible name.
Audit Elements
<a class="id_button tooltip linkBtn" data-priority="2" id="id_rh_w" dir="ltr" aria-label="Microsoft Rewards" aria-expanded="false" aria-controls="rewid-f" aria-haspopup="true" role="button" tabindex="0" href="javascript:void(0)" h="ID=SERP,5019.1">
<a target="_blank" class="tool-item" id="bic" href="/images/create/ai-image-generator?bicsource=hp&FORM=bicbhp" aria-label="Image creator"><div class="icon_area" aria-hidden="true"><div class="icon" role="presentation"></div></div><span>Image creator</span></a>
<a target="_blank" class="tool-item" id="btc" href="/search?q=bing ai writing&FORM=btcbhp" aria-label="Text creator"><div class="icon_area" aria-hidden="true"><div class="icon" role="presentation"></div></div><span>Text creator</span></a>
<a href="/search?q=Jasper+National+Park&form=hpcapt&filters=HpDate:"20261025_0700"+mgzv3configlist:"BingQA_Encyclopedia_Layout"" data-h="ID=HpApp,21421.1" target="_blank" class="title" aria-label="Image of the day: Maligne Lake, Jasper National Park, Alberta, Canada">
<a id="heading" class="heading" data-t="{"n":"destination","..." href="https://www.msn.com/..." aria-label="New poll delivers a ..." target="_blank">Showing first 5 of 52 audited elements.
Elements must meet minimum color contrast ratio thresholds128 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
<input type="submit" name="submit" value="Sign in" aria-label="">
<textarea id="sb_form_q" class="sb_form_q" name="q" type="search" rows="1" style="width: 843px;" placeholder="Search the web" maxlength="2000" autocapitalize="off" autocomplete="off" spellcheck="false" title="Enter your search te..." autofocus="" role="combobox" inputmode="search" ...>
<input id="sb_fileinput" class="fileinput" type="file" accept="image/gif, image/jpeg, image/png, image/webp" multiple="">
<input id="sb_imgpst" class="imgpst" type="text" placeholder="paste image link to search">
<span class="attribution-text">The Daily Digest</span>
Showing first 5 of 128 audited elements.
Elements must only use permitted ARIA attributes264 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
<h1 class="logo_cont" aria-labelledby="bLogo">
<svg id="bLogo" role="img" class="logo" viewBox="0 0 24 24" aria-label="Microsoft Logo Image">
<li class="scope " id="codex" role="menuitem" aria-haspopup="false">
<li class="scope " id="images" role="menuitem" aria-haspopup="false"><a href="/images?FORM=Z9LH" h="ID=SERP,5058.1">Images</a></li>
<li class="scope try_exp" id="video" role="menuitem" aria-haspopup="false"><a href="/videos?FORM=Z9LH1" h="ID=SERP,5059.1">Videos</a></li>
Showing first 5 of 264 audited elements.
Elements must only use supported ARIA attributes265 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
<h1 class="logo_cont" aria-labelledby="bLogo">
<svg id="bLogo" role="img" class="logo" viewBox="0 0 24 24" aria-label="Microsoft Logo Image">
<li class="scope " id="codex" role="menuitem" aria-haspopup="false">
<li class="scope " id="images" role="menuitem" aria-haspopup="false"><a href="/images?FORM=Z9LH" h="ID=SERP,5058.1">Images</a></li>
<li class="scope try_exp" id="video" role="menuitem" aria-haspopup="false"><a href="/videos?FORM=Z9LH1" h="ID=SERP,5059.1">Videos</a></li>
Showing first 5 of 265 audited elements.
Elements should not have tabindex greater than zero96 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
<div class="dots_tab_selection tooltip" tabindex="0" aria-label="More" role="button" aria-expanded="false"></div>
<a class="id_button tooltip linkBtn" data-priority="2" id="id_rh_w" dir="ltr" aria-label="Microsoft Rewards" aria-expanded="false" aria-controls="rewid-f" aria-haspopup="true" role="button" tabindex="0" href="javascript:void(0)" h="ID=SERP,5019.1">
<a id="id_sc" class="idp_ham hphbtop linkBtn" aria-label="Settings and quick links" aria-expanded="false" aria-controls="id_hbfo" aria-haspopup="true" role="button" tabindex="0" href="javascript:void(0)" h="ID=SERP,5029.1"></a>
<div class="b_icon tooltip" role="button" tabindex="0" aria-label="Search using voice" data-sbtipx="Search using voice" data-tooltip="Search using voice" style="height: 100%;">
<div class="b_icon tooltip" role="button" tabindex="0" aria-label="Search using an image" data-sbtipx="Search using an image" data-tooltip="Search using an image">
Showing first 5 of 96 audited elements.
Focused elements must not be entirely hidden by author-created content32 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 class="b_icon tooltip shtip" role="button" tabindex="0" aria-label="Search using voice" data-sbtipx="Search using voice" data-tooltip="Search using voice" style="height: 100%;">
<div class="b_icon tooltip shtip" role="button" tabindex="0" aria-label="Search using an image" data-sbtipx="Search using an image" data-tooltip="Search using an image">
<a target="_blank" class="tool-item" id="bic" href="/images/create/ai-image-generator?bicsource=hp&..." aria-label="Image creator">
<a target="_blank" class="tool-item" id="btc" href="/search?q=bing ai writing&FORM=btcbhp" aria-label="Text creator">
<a href="https://go.microsoft.com/fwlink/?linkid=2127455" data-h="ID=HpApp,31826.1" target="_blank" class="bingwpapplink" rel="noopener" tabindex="0">
Showing first 5 of 32 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 id="sb_form_q" class="sb_form_q" name="q" type="search" rows="1" style="width: 843px;" placeholder="Search the web" maxlength="2000" autocapitalize="off" autocomplete="off" spellcheck="false" title="Enter your search te..." autofocus="" role="combobox" inputmode="search" ...>
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 id="sb_form_q" class="sb_form_q" name="q" type="search" rows="1" style="width: 843px;" placeholder="Search the web" maxlength="2000" autocapitalize="off" autocomplete="off" spellcheck="false" title="Enter your search te..." autofocus="" role="combobox" inputmode="search" ...>
Heading levels should only increase by one26 elements
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Audit Elements
<h1 class="logo_cont" aria-labelledby="bLogo">
<h2 class="text" id="headline">Info</h2>
<h2 title="The last British Airways Boeing 747 flight: An emotional farewell!" class="hp_text overflow"><span>The last British Airways Boeing 747 flight: An emotional farewell!</span></h2>
<h2 title="Wedding venue refused to refund bride's money after fiancée died" class="hp_text overflow"><span>Wedding venue refused to refund bride's money after fiancée died</span></h2>
<h2 title="Scots musician whose famous hit featured in cult Tarantino film left £4million fortune behind" class="hp_text overflow"><span>Scots musician whose famous hit featured in cult Tarantino film left £4million fortune behind</span></h2>
Showing first 5 of 26 audited elements.
Headings should not be empty27 elements
Screen readers announce headings to help users navigate page structure. Empty headings confuse users and prevent them from understanding the page's organization. Headings should only be used to convey structure, not for visual styling, and must contain accessible text that screen readers can announce.
Audit Elements
<h1 class="logo_cont" aria-labelledby="bLogo">
<h3>
<h2 class="text" id="headline">Info</h2>
<h2 title="The last British Airways Boeing 747 flight: An emotional farewell!" class="hp_text overflow"><span>The last British Airways Boeing 747 flight: An emotional farewell!</span></h2>
<h2 title="Wedding venue refused to refund bride's money after fiancée died" class="hp_text overflow"><span>Wedding venue refused to refund bride's money after fiancée died</span></h2>
Showing first 5 of 27 audited elements.
IDs used in ARIA and labels must be unique9 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
<svg id="bLogo" role="img" class="logo" viewBox="0 0 24 24" aria-label="Microsoft Logo Image">
<span id="id_d" _iid="SERP.5031"></span>
<a id="id_sc" class="idp_ham hphbtop linkBtn" aria-label="Settings and quick links" aria-expanded="false" aria-controls="id_hbfo" aria-haspopup="true" role="button" tabindex="0" href="javascript:void(0)" h="ID=SERP,5029.1"></a>
<span id="id_hbfo" _iid="SERP.5030" class="slide_up hpfo hb_hpqexp" tabindex="-1" aria-hidden="true" aria-labelledby="id_sc" role="menu"></span>
<input id="sb_form_go" type="submit" title="Search" name="search" value="" tabindex="-1" aria-hidden="true" class="cdxSearchSubmitIpt">
Showing first 5 of 9 audited elements.
Images must have alternative text79 elements
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 src="data:image/svg+xml,%..." height="16" width="16" alt="" role="presentation" class="rms_img" data-bm="0">
<img src="/th?id=ONUT.bzj5c6LMLts5KutsMKSh3Q&w=186&h=88&c=7&rs=2&qlt=80&pid=PopNow" title="© Sam Chui" alt="© Sam Chui" elementtiming="TTVRCore.TrendingOnBing" data-bm="11">
<img src="/th?id=ONUT.RfOwE9SZfo4aPEjxISTVVw&w=186&h=88&c=7&rs=2&qlt=80&pid=PopNow" title="© Daily Mail" alt="© Daily Mail" data-bm="12">
<img src="/th?id=ONUT.jakSEvspFjkAGIj1DLJ9lg&w=186&h=88&c=7&rs=2&qlt=80&pid=PopNow" title="© Daily Mail" alt="© Daily Mail" data-bm="13">
<img src="/th?id=ONUT.4aZXxYhwT4AbXN-tpnP5bg&w=186&h=88&c=7&rs=2&qlt=80&pid=PopNow" title="© Daily Mail" alt="© Daily Mail" data-bm="14">
Showing first 5 of 79 audited elements.
Inline text spacing must be adjustable with custom stylesheets71 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
<nav class="scope_cont" style="">
<div class="moduleCont" style="background-color: unset;">
<div class="module show five_col feed_bg" style="">
<div class="widget_container" id="widget_container" style="min-height: initial;">
<fluent-design-system-provider style="height: 100%; background: transparent; display: block;" direction="ltr" base-layer-luminance="1" fill-color="#ffffff">
Showing first 5 of 71 audited elements.
Interactive controls must not be nested233 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
<svg id="bLogo" role="img" class="logo" viewBox="0 0 24 24" aria-label="Microsoft Logo Image">
<div class="dots_tab_selection tooltip" tabindex="0" aria-label="More" role="button" aria-expanded="false"></div>
<a class="id_button tooltip linkBtn" data-priority="2" id="id_rh_w" dir="ltr" aria-label="Microsoft Rewards" aria-expanded="false" aria-controls="rewid-f" aria-haspopup="true" role="button" tabindex="0" href="javascript:void(0)" h="ID=SERP,5019.1">
<a id="id_sc" class="idp_ham hphbtop linkBtn" aria-label="Settings and quick links" aria-expanded="false" aria-controls="id_hbfo" aria-haspopup="true" role="button" tabindex="0" href="javascript:void(0)" h="ID=SERP,5029.1"></a>
<div class="b_icon tooltip" role="button" tabindex="0" aria-label="Search using voice" data-sbtipx="Search using voice" data-tooltip="Search using voice" style="height: 100%;">
Showing first 5 of 233 audited elements.
Interactive elements must have a visible focus indicator50 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 class="b_icon tooltip shtip" role="button" tabindex="0" aria-label="Search using voice" data-sbtipx="Search using voice" data-tooltip="Search using voice" style="height: 100%;">
<div class="b_icon tooltip shtip" role="button" tabindex="0" aria-label="Search using an image" data-sbtipx="Search using an image" data-tooltip="Search using an image">
<a target="_blank" class="tool-item" id="bic" href="/images/create/ai-image-generator?bicsource=hp&..." aria-label="Image creator">
<a target="_blank" class="tool-item" id="btc" href="/search?q=bing ai writing&FORM=btcbhp" aria-label="Text creator">
<a href="https://go.microsoft.com/fwlink/?linkid=2127455" data-h="ID=HpApp,31826.1" target="_blank" class="bingwpapplink" rel="noopener" tabindex="0">
Showing first 5 of 50 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination7 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
<header class="header header-full" id="hdr" data-priority="2">
<nav class="scope_cont" style="">
<div id="id_h" class="" role="complementary" aria-label="Account Rewards and Preferences" data-priority="2">
<form action="/search" id="sb_form" class="sb_form hassbi c_show_form fl c_show_c c_show_form_hover2 sb_expanded ssr_cplt hasmic" role="search" data-state="focused" data-as-exp="1" style="position:relative">
<section role="region" aria-label="Trending on Bing" class="carousel show five_col" id="carousel">
Showing first 5 of 7 audited elements.
Links must have discernible text146 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="customIcon" href="/chat?FORM=hpcodx&intent=bing" h="ID=SERP,5057.1">
<a href="/images?FORM=Z9LH" h="ID=SERP,5058.1">Images</a>
<a href="/videos?FORM=Z9LH1" h="ID=SERP,5059.1">Videos</a>
<a href="/maps?FORM=Z9LH2" h="ID=SERP,5060.1">Maps</a>
<a href="/news/search?q=Top+stories&nvaug=%5bNewsVertical+Category%3d%22rt_MaxClass%22%5d&FORM=Z9LH3" h="ID=SERP,5061.1">News</a>
Showing first 5 of 146 audited elements.
Main landmark should not be contained in another landmark1 element
The main landmark must be at the top level and not nested inside other landmarks. This ensures screen reader users can quickly navigate to the primary content without searching through complex hierarchy, making page navigation simpler and more predictable.
Audit Elements
<div class="hpl hp_cont" role="main"><div style="display: none;"></div><div class="dimmer cdxShowConv hp_focus_overlay"></div></div>
Page must have means to bypass repeated blocks1 element
Keyboard-only users must tab through all navigation and header content before reaching the main content, which can take several minutes and cause physical pain for users with motor limitations. Bypass mechanisms like skip links allow these users to jump directly to main content, saving time and reducing fatigue.
Audit Elements
<html lang="en" dir="ltr">
Page 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.
Audit Elements
<html lang="en" dir="ltr">
Required ARIA attributes must be provided172 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
<svg id="bLogo" role="img" class="logo" viewBox="0 0 24 24" aria-label="Microsoft Logo Image">
<ul class="scopes" role="menubar">
<li class="scope " id="codex" role="menuitem" aria-haspopup="false">
<img src="data:image/svg+xml,%..." height="16" width="16" alt="" role="presentation" class="rms_img" data-bm="0">
<li class="scope " id="images" role="menuitem" aria-haspopup="false"><a href="/images?FORM=Z9LH" h="ID=SERP,5058.1">Images</a></li>
Showing first 5 of 172 audited elements.
Scrollable region must have keyboard access2 elements
Scrollable regions must contain focusable elements or be focusable themselves to enable keyboard navigation. Without keyboard access, users cannot scroll to view content that extends beyond the visible area, making that content completely inaccessible to keyboard-only users.
Audit Elements
<html lang="en" dir="ltr">
<ul id="crs_pane" role="list">
Users should be able to zoom and scale the text up to 500%1 element
The user-scalable="no" and restrictive maximum-scale parameters prevent people with low vision from zooming to read content. Users who rely on browser zoom to enlarge text are blocked from accessing content at a readable size, violating their need to scale pages up to 5x zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1.0">
Zooming and scaling must not be disabled1 element
Setting user-scalable="no" or maximum-scale less than 2 prevents people with low vision from zooming to read content. Users who enlarge text in their browsers are blocked from making content readable, violating accessibility guidelines that require supporting at least 200% zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1.0">
How does your site stack up against Bing?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Search Engine