Yahooyahoo.com
Accessibility Score
Issues Found
Issues Found
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 class="uds-color-mode-light" lang="en-US" style="color-scheme:light" data-hydrated="pass">
Fix all of the following:
- Page must have a level-one heading
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
<article aria-hidden="false" aria-label="Slide 3 of 15" aria-roledescription="slide" class="relative min-w-0 max-md:mr-2 max-md:rounded-lg md:flex-[0_0_100%] flex-[0_0_calc(100%-1rem)] overflow-hidden md:mr-3 md:rounded-xl" role="group" style="transform:translate3d(0, 0, 0)">
Fix any of the following:
- ARIA role group is not allowed for given element
Passed Audits
[role="img"] elements must have alternative text2 elements
Screen readers cannot convert visual images with role="img" into text without an accessible alternative. All users with visual disabilities, from complete blindness to low vision and color blindness, require text alternatives to access the information that images convey.
Audit Elements
<span role="img" aria-label="Image for Taboola Advertising Unit" class="thumbBlock" style="background-image: url("https://images.taboola.com/taboola/image/fetch/h_178%2Cw_320%2Cb_auto,c_pad/https%3A//cdn.taboola.com/libtrc/static/thumbnails/aefb530565968be0e9f375e52c872039.jpg");"><div aria-hidden="false" aria-label="Mostly clear" class="size-[4.5rem] aspect..." role="img" style="--icon-dark: url('ht..."><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 class="uds-color-mode-light" lang="en-US" style="color-scheme:light" data-hydrated="pass">
<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 class="uds-color-mode-light" lang="en-US" style="color-scheme:light" data-hydrated="pass">
<li> elements must be contained in a <ul> or <ol>86 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>
<li>
<li>
<li class="group relative mb-4 flex items-center gap-x-2.5 pb-3 last:mb-0 last:border-0 last:pb-0 sm:border-b sm:border-muted xl:mb-3">
<li class="group relative mb-4 flex items-center gap-x-2.5 pb-3 last:mb-0 last:border-0 last:pb-0 sm:border-b sm:border-muted xl:mb-3">
<li class="group relative mb-4 flex items-center gap-x-2.5 pb-3 last:mb-0 last:border-0 last:pb-0 sm:border-b sm:border-muted xl:mb-3">
<li class="group relative mb-4 flex items-center gap-x-2.5 pb-3 last:mb-0 last:border-0 last:pb-0 sm:border-b sm:border-muted xl:mb-3">
<li class="group relative mb-4 flex items-center gap-x-2.5 pb-3 last:mb-0 last:border-0 last:pb-0 sm:border-b sm:border-muted xl:mb-3">
<li>
Showing first 10 of 86 audited elements.
<svg> elements with an img 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 aria-label="Yahoo" class="fill-uh-purple dark:fill-white h-6" role="img" viewBox="0 0 86 24" xmlns="http://www.w3.org/2000/svg" preserveAspectRatio="xMinYMin meet">
<ul> and <ol> must only directly contain <li>, <script> or <template> elements7 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="absolute left-0 top-0">
<ol>
<ul class="flex h-full flex-col items-start justify-start gap-2">
<ul class="cls-stream-list flex flex-col gap-4 lg:gap-5 sm:rounded-xl sm:bg-primary">
<ul class="mt-5 flex flex-col gap-3 sm:gap-5">
<ul class="mt-3 flex list-none md:mt-1 justify-center">
<ul class="mx-auto flex max-w-[280px] flex-wrap items-center justify-center gap-x-1.5 gap-y-2.5 pt-2 text-xs leading-3 md:mb-0 md:text-[13px]">
All page content should be contained by landmarks1279 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="benji-dashboard-root"></div>
<div class="cls-content-grid grid min-h-dvh grid-cols-1 grid-rows-[auto_1fr_auto] nca-homepage-en-US narrow-page relative z-1 bg-secondary">
<header id="module-uh" data-version="1.7.3" class="font-yahoosans top-0...">
<div class="flex w-full flex-col py-2.5 md:py-[9px] px-5 md:px-6 lg:px-8 gap-2.5 max-w-uh-custom">
<div class="inline-flex items-center justify-around">
<a href="https://www.yahoo.co..." class=" focus-visible:round..." data-ylk="elm:logo;itc:0;sec:y..." data-yga="{"yLinkText":"frontp..." data-rapid_p="2" data-y-link-id="0hl7opn1psyuv810lvxj" data-v9y="1"><svg aria-label="Yahoo" class="fill-uh-purple dark:fill-white h-6" role="img" viewBox="0 0 86 24" xmlns="http://www.w3.org/2000/svg" preserveAspectRatio="xMinYMin meet">
<path d="M24.778 5.86703V7.10...">
<div class="z-10 h-10 w-full caret-purple-700 backdrop-blur-0 md:block md:h-[46px] md:mr-8 lg:mr-10 relative hidden max-w-[702px]">
<form class="gap-1 z-10 h-10 just..." role="search" method="get">
Showing first 10 of 1279 audited elements.
Alternative text of images should not be repeated as text82 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 alt="" width="80" height="80" decoding="async" data-nimg="1" class="chromatic-ignore siz..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" width="80" height="80" decoding="async" data-nimg="1" class="chromatic-ignore siz..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" width="80" height="80" decoding="async" data-nimg="1" class="chromatic-ignore siz..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" width="80" height="80" decoding="async" data-nimg="1" class="chromatic-ignore siz..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" width="80" height="80" decoding="async" data-nimg="1" class="chromatic-ignore siz..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" loading="lazy" width="1104" height="620" decoding="async" data-nimg="1" class="yahoo-ntk-hero-image..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="mr-1.5 inline size-5..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" loading="lazy" width="534" height="304" decoding="async" data-nimg="1" class="relative w-full roun..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="mr-1.5 inline size-5..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" loading="lazy" width="534" height="304" decoding="async" data-nimg="1" class="relative w-full roun..." style="color:transparent" src="https://s.yimg.com/l...">
Showing first 10 of 82 audited elements.
ARIA attributes must be used as specified for the element's role61 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
<svg aria-label="Yahoo" class="fill-uh-purple dark:fill-white h-6" role="img" viewBox="0 0 86 24" xmlns="http://www.w3.org/2000/svg" preserveAspectRatio="xMinYMin meet">
<input aria-autocomplete="both" autocapitalize="off" autocomplete="off" autocorrect="off" class="bg-transparent dark:..." data-lpignore="true" id="uh-sbq" placeholder="Search the web" type="search" value="" data-rapid_p="4" data-v9y="1">
<button class="focus-visible:outlin..." aria-label="Search with Yahoo Sc..." type="button" data-ylk="elm:search;elmt:icon..." data-rapid_p="6" data-y-link-id="05b01hp1qu6kce1mzpkz" data-v9y="1">
<button class="focus-visible:outlin..." aria-label="Search the web" data-ylk="elm:search;elmt:icon..." data-rapid_p="7" data-y-link-id="07i791q1qqpkyq07x5jj" data-v9y="1">
<button class="focus-visible:outlin..." aria-haspopup="menu" aria-expanded="false" id="_R_4pcl6cnqq5bH1_" data-rapid_p="15" data-y-link-id="1ejmscc1ghl1r01gjiav" data-v9y="1">
<a aria-label="Check your mail" class="focus-visible:outlin..." href="https://mail.yahoo.c..." target="_blank" data-ylk="elm:btn;itc:0;sec:yb..." data-rapid_p="16" data-y-link-id="1m4xh6w02ndnw600lh4f" data-v9y="1">
<iframe frameborder="0" src="https://be74ab7750ea..." id="google_ads_iframe_/2..." title="3rd party ad content" name="" scrolling="no" marginwidth="0" marginheight="0" width="970" height="250" data-is-safeframe="true" sandbox="allow-forms allow-po..." allow="private-state-token-..." ...>
<section aria-label="Features bar" class="chromatic-ignore relative mt-3 h-[5.75rem] scroll-mt-[4.75rem]" id="convenience-bar" tabindex="-1">
<select aria-label="Horoscope" class="absolute left-0 top-0 size-full cursor-pointer appearance-none rounded-lg bg-transparent text-transparent outline-none focus-within:ring-2 focus-within:ring-indigo-8">
<select aria-label="Select a league" class="absolute left-0 top-0 size-full cursor-pointer appearance-none rounded-lg bg-transparent text-transparent outline-none focus-within:ring-2 focus-within:ring-indigo-8">
Showing first 10 of 61 audited elements.
ARIA attributes must conform to valid names61 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
<svg aria-label="Yahoo" class="fill-uh-purple dark:fill-white h-6" role="img" viewBox="0 0 86 24" xmlns="http://www.w3.org/2000/svg" preserveAspectRatio="xMinYMin meet">
<input aria-autocomplete="both" autocapitalize="off" autocomplete="off" autocorrect="off" class="bg-transparent dark:..." data-lpignore="true" id="uh-sbq" placeholder="Search the web" type="search" value="" data-rapid_p="4" data-v9y="1">
<button class="focus-visible:outlin..." aria-label="Search with Yahoo Sc..." type="button" data-ylk="elm:search;elmt:icon..." data-rapid_p="6" data-y-link-id="05b01hp1qu6kce1mzpkz" data-v9y="1">
<button class="focus-visible:outlin..." aria-label="Search the web" data-ylk="elm:search;elmt:icon..." data-rapid_p="7" data-y-link-id="07i791q1qqpkyq07x5jj" data-v9y="1">
<button class="focus-visible:outlin..." aria-haspopup="menu" aria-expanded="false" id="_R_4pcl6cnqq5bH1_" data-rapid_p="15" data-y-link-id="1ejmscc1ghl1r01gjiav" data-v9y="1">
<a aria-label="Check your mail" class="focus-visible:outlin..." href="https://mail.yahoo.c..." target="_blank" data-ylk="elm:btn;itc:0;sec:yb..." data-rapid_p="16" data-y-link-id="1m4xh6w02ndnw600lh4f" data-v9y="1">
<iframe frameborder="0" src="https://be74ab7750ea..." id="google_ads_iframe_/2..." title="3rd party ad content" name="" scrolling="no" marginwidth="0" marginheight="0" width="970" height="250" data-is-safeframe="true" sandbox="allow-forms allow-po..." allow="private-state-token-..." ...>
<section aria-label="Features bar" class="chromatic-ignore relative mt-3 h-[5.75rem] scroll-mt-[4.75rem]" id="convenience-bar" tabindex="-1">
<select aria-label="Horoscope" class="absolute left-0 top-0 size-full cursor-pointer appearance-none rounded-lg bg-transparent text-transparent outline-none focus-within:ring-2 focus-within:ring-indigo-8">
<select aria-label="Select a league" class="absolute left-0 top-0 size-full cursor-pointer appearance-none rounded-lg bg-transparent text-transparent outline-none focus-within:ring-2 focus-within:ring-indigo-8">
Showing first 10 of 61 audited elements.
ARIA attributes must conform to valid values60 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
<svg aria-label="Yahoo" class="fill-uh-purple dark:fill-white h-6" role="img" viewBox="0 0 86 24" xmlns="http://www.w3.org/2000/svg" preserveAspectRatio="xMinYMin meet">
<input aria-autocomplete="both" autocapitalize="off" autocomplete="off" autocorrect="off" class="bg-transparent dark:..." data-lpignore="true" id="uh-sbq" placeholder="Search the web" type="search" value="" data-rapid_p="4" data-v9y="1">
<button class="focus-visible:outlin..." aria-label="Search with Yahoo Sc..." type="button" data-ylk="elm:search;elmt:icon..." data-rapid_p="6" data-y-link-id="05b01hp1qu6kce1mzpkz" data-v9y="1">
<button class="focus-visible:outlin..." aria-label="Search the web" data-ylk="elm:search;elmt:icon..." data-rapid_p="7" data-y-link-id="07i791q1qqpkyq07x5jj" data-v9y="1">
<button class="focus-visible:outlin..." aria-haspopup="menu" aria-expanded="false" id="_R_4pcl6cnqq5bH1_" data-rapid_p="15" data-y-link-id="1ejmscc1ghl1r01gjiav" data-v9y="1">
<a aria-label="Check your mail" class="focus-visible:outlin..." href="https://mail.yahoo.c..." target="_blank" data-ylk="elm:btn;itc:0;sec:yb..." data-rapid_p="16" data-y-link-id="1m4xh6w02ndnw600lh4f" data-v9y="1">
<iframe frameborder="0" src="https://be74ab7750ea..." id="google_ads_iframe_/2..." title="3rd party ad content" name="" scrolling="no" marginwidth="0" marginheight="0" width="970" height="250" data-is-safeframe="true" sandbox="allow-forms allow-po..." allow="private-state-token-..." ...>
<section aria-label="Features bar" class="chromatic-ignore relative mt-3 h-[5.75rem] scroll-mt-[4.75rem]" id="convenience-bar" tabindex="-1">
<select aria-label="Horoscope" class="absolute left-0 top-0 size-full cursor-pointer appearance-none rounded-lg bg-transparent text-transparent outline-none focus-within:ring-2 focus-within:ring-indigo-8">
<select aria-label="Select a league" class="absolute left-0 top-0 size-full cursor-pointer appearance-none rounded-lg bg-transparent text-transparent outline-none focus-within:ring-2 focus-within:ring-indigo-8">
Showing first 10 of 60 audited elements.
ARIA commands must have an accessible name2 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
<span role="link" aria-label="Apex Trader Funding in Taboola advertising section" class="branding-inner inline-branding">Apex Trader Funding</span>
<span class="video-label video-title trc_ellipsis" role="link" slot="title" style="-webkit-line-clamp: 2;">Trade at Your Level — Choose Your Account Size with Apex.</span>
ARIA hidden element must not be focusable or contain focusable elements116 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 xmlns="http://www.w3.org/20..." width="24" height="24" viewBox="0 0 24 24" aria-hidden="true" focusable="false" class="flex-none text-prima...">
<svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" fill="none" aria-hidden="true"><path fill="#0F69FF" d="M17.08 9.169H6.104l3.58-3.58A.832.832 0 1 0 8.506 4.41L2.916 10l5.59 5.59a.833.833 0 0 0 1.178-1.18L6.11 10.836H17.08z"></path></svg>
<svg xmlns="http://www.w3.org/2000/svg" width="10" height="10" fill="inherit" aria-hidden="true" class="group-hover:fill-[white] dark:fill-[white]">
<svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 18 18" aria-hidden="true" class="dark:hidden" height="20" width="20">
<svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 18 18" aria-hidden="true" class="hidden dark:block" height="20" width="20">
<div class="absolute left-1/2 z-..." style="bottom:-14px" aria-hidden="true">
<svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="none" viewBox="0 0 16 16" aria-hidden="true" class="fill-white dark:fill-ymp-uh-midnight"><path d="M10.8 7a3.8 3.8 0 1 0-7.6 0 3.8 3.8 0 0 0 7.6 0m-.407 4.949a6 6 0 1 1 1.556-1.556L15.556 14 14 15.556z"></path></svg>
<div class="absolute left-1/2 z-..." style="bottom:-14px" aria-hidden="true">
<svg xmlns="http://www.w3.org/2000/svg" width="12" height="13" fill="none" aria-hidden="true" class="group relative left-1 fill-current group-hover:fill-ymp-uh-grape-jelly dark:group-hover:fill-uds-brand-dark group-hover:top-px top-[0.075rem]">
<svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" viewBox="0 0 16 16" aria-hidden="true" focusable="false" class="flex-none text-primary text-ymp-uh-creator-purple dark:text-uds-brand-dark [&_path]:fill-current">
Showing first 10 of 116 audited elements.
ARIA role should be appropriate for the element43 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 aria-label="Yahoo" class="fill-uh-purple dark:fill-white h-6" role="img" viewBox="0 0 86 24" xmlns="http://www.w3.org/2000/svg" preserveAspectRatio="xMinYMin meet">
<form class="gap-1 z-10 h-10 just..." role="search" method="get">
<svg aria-hidden="false" aria-label="Mostly Clear" focusable="false" height="32" role="img" viewBox="0 0 32 32" width="32" xmlns="http://www.w3.org/2000/svg">
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 138.75 141.25" aria-hidden="false" aria-label="Rotten Tomatoes critic score" height="16" width="16" role="img">
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 106.25 140" aria-hidden="false" aria-label="Rotten Tomatoes audience score" height="16" width="16" role="img">
<svg aria-hidden="true" class="size-6 shrink-0" focusable="false" height="24" role="img" viewBox="0 0 24 24" width="24" xmlns="http://www.w3.org/2000/svg">
<svg aria-hidden="true" class="size-3 animate-trendingArrowUp text-green-6 dark:text-positive" focusable="false" height="16" role="img" viewBox="0 0 16 16" width="16" xmlns="http://www.w3.org/2000/svg">
<section aria-label="Top stories" aria-roledescription="carousel" class="relative" role="group">
<div aria-live="off" class="hidden md:flex bg-always-black/35 h-5 items-center justify-center rounded-2xl px-2 text-[0.8125rem] tracking-[.01625rem] text-always-white md:h-6" role="status"><span class="pr-1 font-bold">3</span><span class="font-normal">of 15</span></div>
<div aria-live="off" class="absolute right-4 top-4 md:hidden bg-always-black/35 h-5 items-center justify-center rounded-2xl px-2 text-[0.8125rem] tracking-[.01625rem] text-always-white md:h-6" role="status"><span class="pr-1 font-bold">1</span><span class="font-normal">of 15</span></div>
Showing first 10 of 43 audited elements.
ARIA roles used must conform to valid values15 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 aria-label="Yahoo" class="fill-uh-purple dark:fill-white h-6" role="img" viewBox="0 0 86 24" xmlns="http://www.w3.org/2000/svg" preserveAspectRatio="xMinYMin meet">
<form class="gap-1 z-10 h-10 just..." role="search" method="get">
<section aria-label="Top stories" aria-roledescription="carousel" class="relative" role="group">
<div aria-live="off" class="hidden md:flex bg-always-black/35 h-5 items-center justify-center rounded-2xl px-2 text-[0.8125rem] tracking-[.01625rem] text-always-white md:h-6" role="status"><span class="pr-1 font-bold">3</span><span class="font-normal">of 15</span></div>
<article aria-hidden="false" aria-label="Slide 3 of 15" aria-roledescription="slide" class="relative min-w-0 max-md:mr-2 max-md:rounded-lg md:flex-[0_0_100%] flex-[0_0_calc(100%-1rem)] overflow-hidden md:mr-3 md:rounded-xl" role="group" style="transform:translate3d(0, 0, 0)">
<div class="flex items-center gap-[0.375rem]" role="group">
<div class="relative h-[2.125rem] w-[6rem] shrink-0 rounded-[1.5rem] bg-tertiary p-[0.1875rem]" role="group">
<button aria-checked="true" aria-label="Small Cards" class="absolute left-[0.1875rem] top-[0.1875rem] z-10 flex h-[1.75rem] w-[2.75rem] items-center justify-center rounded-full bg-transparent transition-colors" role="radio" ...>
<button aria-checked="false" aria-label="Large Cards" class="absolute left-[3.062..." role="radio" data-ylk="elm:large;itc:1;pkgt...">
<div class="chromatic-ignore absolute right-[-7px] top-full z-[19] mt-3 transition-opacity duration-300 opacity-100" role="tooltip" aria-live="polite">
Showing first 10 of 15 audited elements.
ARIA tooltip nodes must have an accessible name1 element
Screen reader users cannot understand the purpose of role="tooltip" elements without an accessible name. The name provides the essential context or help text that the tooltip is meant to convey.
Audit Elements
<div class="chromatic-ignore absolute right-[-7px] top-full z-[19] mt-3 transition-opacity duration-300 opacity-100" role="tooltip" aria-live="polite">
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 class="__variable_ff38b9 __variable_122d00 __variable_d70552 bg-secondary font-yahoosans text-primary" id="news-content-app">
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
<input aria-autocomplete="both" autocapitalize="off" autocomplete="off" autocorrect="off" class="bg-transparent dark:..." data-lpignore="true" id="uh-sbq" placeholder="Search the web" type="search" value="" data-rapid_p="4" data-v9y="1">
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 id="module-uh" data-version="1.7.3" class="font-yahoosans top-0...">
Buttons must have discernible text15 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 class="focus-visible:outlin..." aria-label="Search with Yahoo Sc..." type="button" data-ylk="elm:search;elmt:icon..." data-rapid_p="6" data-y-link-id="05b01hp1qu6kce1mzpkz" data-v9y="1">
<button class="focus-visible:outlin..." aria-label="Search the web" data-ylk="elm:search;elmt:icon..." data-rapid_p="7" data-y-link-id="07i791q1qqpkyq07x5jj" data-v9y="1">
<button class="focus-visible:outlin..." aria-haspopup="menu" aria-expanded="false" id="_R_4pcl6cnqq5bH1_" data-rapid_p="15" data-y-link-id="1ejmscc1ghl1r01gjiav" data-v9y="1">
<button aria-disabled="true" aria-label="Previous" class="flex size-9 items-ce..." data-ylk="elm:arrow;itc:1;ll1:..." data-rapid_p="37" data-v9y="1">
<button aria-disabled="false" aria-label="Next" class="flex size-9 items-ce..." data-ylk="elm:arrow;itc:1;ll1:..." data-rapid_p="38" data-v9y="1">
<button aria-label="Tell us what you thi..." class="flex items-end justi..." data-ylk="cpos:16;slk:feedback..." data-yga="{"yLinkElement":"nav..." data-rapid_p="23" data-y-link-id="0iy7aaj1lrjttw062zmd"><button aria-label="Pause" class="group hidden size-6 ..." data-ylk="pkgt:minintk-heromod..." data-yga="{"yLinkText":"Pause"..." data-rapid_p="1" data-y-link-id="0erg4et0sk8q5r1w7b48" data-v9y="1"><button aria-controls="_R_5qiintr56cnqq5b_" aria-disabled="false" aria-label="Previous slide" class="rapid-noclick-resp g..." data-ylk="" data-yga="{"yLinkElement":"arr..." data-rapid_p="2" data-y-link-id="0rhryt314khoki03154k" data-v9y="1"><button aria-controls="_R_5qiintr56cnqq5b_" aria-disabled="false" aria-label="Next slide" class="rapid-noclick-resp g..." data-ylk="" data-yga="{"yLinkElement":"arr..." data-rapid_p="3" data-y-link-id="13j4r3403m9oef1yv7fj" data-v9y="1"><button aria-checked="true" aria-label="Small Cards" class="absolute left-[0.1875rem] top-[0.1875rem] z-10 flex h-[1.75rem] w-[2.75rem] items-center justify-center rounded-full bg-transparent transition-colors" role="radio" ...>
Showing first 10 of 15 audited elements.
Deprecated ARIA roles must not be used15 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 aria-label="Yahoo" class="fill-uh-purple dark:fill-white h-6" role="img" viewBox="0 0 86 24" xmlns="http://www.w3.org/2000/svg" preserveAspectRatio="xMinYMin meet">
<form class="gap-1 z-10 h-10 just..." role="search" method="get">
<section aria-label="Top stories" aria-roledescription="carousel" class="relative" role="group">
<div aria-live="off" class="hidden md:flex bg-always-black/35 h-5 items-center justify-center rounded-2xl px-2 text-[0.8125rem] tracking-[.01625rem] text-always-white md:h-6" role="status"><span class="pr-1 font-bold">3</span><span class="font-normal">of 15</span></div>
<article aria-hidden="false" aria-label="Slide 3 of 15" aria-roledescription="slide" class="relative min-w-0 max-md:mr-2 max-md:rounded-lg md:flex-[0_0_100%] flex-[0_0_calc(100%-1rem)] overflow-hidden md:mr-3 md:rounded-xl" role="group" style="transform:translate3d(0, 0, 0)">
<div class="flex items-center gap-[0.375rem]" role="group">
<div class="relative h-[2.125rem] w-[6rem] shrink-0 rounded-[1.5rem] bg-tertiary p-[0.1875rem]" role="group">
<button aria-checked="true" aria-label="Small Cards" class="absolute left-[0.1875rem] top-[0.1875rem] z-10 flex h-[1.75rem] w-[2.75rem] items-center justify-center rounded-full bg-transparent transition-colors" role="radio" ...>
<button aria-checked="false" aria-label="Large Cards" class="absolute left-[3.062..." role="radio" data-ylk="elm:large;itc:1;pkgt...">
<div class="chromatic-ignore absolute right-[-7px] top-full z-[19] mt-3 transition-opacity duration-300 opacity-100" role="tooltip" aria-live="polite">
Showing first 10 of 15 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 class="uds-color-mode-light" lang="en-US" style="color-scheme:light" data-hydrated="pass">
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 id="module-uh" data-version="1.7.3" class="font-yahoosans top-0...">
Document 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.
Audit Elements
<main aria-label="Top stories and Stories for you" class="scroll-mt-[9.75rem] rounded-xl will-change-scroll" tabindex="-1">
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 class="uds-color-mode-light" lang="en-US" style="color-scheme:light" data-hydrated="pass">
Elements marked as presentational should be consistently ignored79 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 alt="" width="80" height="80" decoding="async" data-nimg="1" class="chromatic-ignore siz..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" width="80" height="80" decoding="async" data-nimg="1" class="chromatic-ignore siz..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" width="80" height="80" decoding="async" data-nimg="1" class="chromatic-ignore siz..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" width="80" height="80" decoding="async" data-nimg="1" class="chromatic-ignore siz..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" width="80" height="80" decoding="async" data-nimg="1" class="chromatic-ignore siz..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" loading="lazy" width="1104" height="620" decoding="async" data-nimg="1" class="yahoo-ntk-hero-image..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="mr-1.5 inline size-5..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" loading="lazy" width="534" height="304" decoding="async" data-nimg="1" class="relative w-full roun..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="mr-1.5 inline size-5..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" loading="lazy" width="534" height="304" decoding="async" data-nimg="1" class="relative w-full roun..." style="color:transparent" src="https://s.yimg.com/l...">
Showing first 10 of 79 audited elements.
Elements must meet minimum color contrast ratio thresholds264 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 aria-autocomplete="both" autocapitalize="off" autocomplete="off" autocorrect="off" class="bg-transparent dark:..." data-lpignore="true" id="uh-sbq" placeholder="Search the web" type="search" value="" data-rapid_p="4" data-v9y="1">
<a class="hover:text-ymp-uh-gr..." href="https://www.yahoo.co..." data-ylk="elm:navcat;itc:0;pkg..." data-yga="{"yLinkText":"news",..." data-rapid_p="12" data-y-link-id="0iyalrr04lo3ht1vpxz0" data-v9y="1"><a class="hover:text-ymp-uh-gr..." href="https://finance.yaho..." data-ylk="elm:navcat;itc:0;pkg..." data-yga="{"yLinkText":"financ..." data-rapid_p="13" data-y-link-id="1v6r8vy0ju0nc01p3wh8" data-v9y="1"><a class="hover:text-ymp-uh-gr..." href="https://sports.yahoo..." data-ylk="elm:navcat;itc:0;pkg..." data-yga="{"yLinkText":"sports..." data-rapid_p="14" data-y-link-id="0vjbfd91x1w54v1heuk7" data-v9y="1"><button class="focus-visible:outlin..." aria-haspopup="menu" aria-expanded="false" id="_R_4pcl6cnqq5bH1_" data-rapid_p="15" data-y-link-id="1ejmscc1ghl1r01gjiav" data-v9y="1">
<span class="min-w-[26px] whitespace-nowrap leading-tight">Mail</span>
<div class="leading-5">Sign in</div>
<span>Horoscope</span>
<span><span aria-hidden="true" class="px-1">·</span>Leo</span>
<span aria-hidden="true" class="px-1">·</span>
Showing first 10 of 264 audited elements.
Elements must only use permitted ARIA attributes60 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
<svg aria-label="Yahoo" class="fill-uh-purple dark:fill-white h-6" role="img" viewBox="0 0 86 24" xmlns="http://www.w3.org/2000/svg" preserveAspectRatio="xMinYMin meet">
<input aria-autocomplete="both" autocapitalize="off" autocomplete="off" autocorrect="off" class="bg-transparent dark:..." data-lpignore="true" id="uh-sbq" placeholder="Search the web" type="search" value="" data-rapid_p="4" data-v9y="1">
<button class="focus-visible:outlin..." aria-label="Search with Yahoo Sc..." type="button" data-ylk="elm:search;elmt:icon..." data-rapid_p="6" data-y-link-id="05b01hp1qu6kce1mzpkz" data-v9y="1">
<button class="focus-visible:outlin..." aria-label="Search the web" data-ylk="elm:search;elmt:icon..." data-rapid_p="7" data-y-link-id="07i791q1qqpkyq07x5jj" data-v9y="1">
<button class="focus-visible:outlin..." aria-haspopup="menu" aria-expanded="false" id="_R_4pcl6cnqq5bH1_" data-rapid_p="15" data-y-link-id="1ejmscc1ghl1r01gjiav" data-v9y="1">
<a aria-label="Check your mail" class="focus-visible:outlin..." href="https://mail.yahoo.c..." target="_blank" data-ylk="elm:btn;itc:0;sec:yb..." data-rapid_p="16" data-y-link-id="1m4xh6w02ndnw600lh4f" data-v9y="1">
<iframe frameborder="0" src="https://be74ab7750ea..." id="google_ads_iframe_/2..." title="3rd party ad content" name="" scrolling="no" marginwidth="0" marginheight="0" width="970" height="250" data-is-safeframe="true" sandbox="allow-forms allow-po..." allow="private-state-token-..." ...>
<section aria-label="Features bar" class="chromatic-ignore relative mt-3 h-[5.75rem] scroll-mt-[4.75rem]" id="convenience-bar" tabindex="-1">
<select aria-label="Horoscope" class="absolute left-0 top-0 size-full cursor-pointer appearance-none rounded-lg bg-transparent text-transparent outline-none focus-within:ring-2 focus-within:ring-indigo-8">
<select aria-label="Select a league" class="absolute left-0 top-0 size-full cursor-pointer appearance-none rounded-lg bg-transparent text-transparent outline-none focus-within:ring-2 focus-within:ring-indigo-8">
Showing first 10 of 60 audited elements.
Elements must only use supported ARIA attributes61 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
<svg aria-label="Yahoo" class="fill-uh-purple dark:fill-white h-6" role="img" viewBox="0 0 86 24" xmlns="http://www.w3.org/2000/svg" preserveAspectRatio="xMinYMin meet">
<input aria-autocomplete="both" autocapitalize="off" autocomplete="off" autocorrect="off" class="bg-transparent dark:..." data-lpignore="true" id="uh-sbq" placeholder="Search the web" type="search" value="" data-rapid_p="4" data-v9y="1">
<button class="focus-visible:outlin..." aria-label="Search with Yahoo Sc..." type="button" data-ylk="elm:search;elmt:icon..." data-rapid_p="6" data-y-link-id="05b01hp1qu6kce1mzpkz" data-v9y="1">
<button class="focus-visible:outlin..." aria-label="Search the web" data-ylk="elm:search;elmt:icon..." data-rapid_p="7" data-y-link-id="07i791q1qqpkyq07x5jj" data-v9y="1">
<button class="focus-visible:outlin..." aria-haspopup="menu" aria-expanded="false" id="_R_4pcl6cnqq5bH1_" data-rapid_p="15" data-y-link-id="1ejmscc1ghl1r01gjiav" data-v9y="1">
<a aria-label="Check your mail" class="focus-visible:outlin..." href="https://mail.yahoo.c..." target="_blank" data-ylk="elm:btn;itc:0;sec:yb..." data-rapid_p="16" data-y-link-id="1m4xh6w02ndnw600lh4f" data-v9y="1">
<iframe frameborder="0" src="https://be74ab7750ea..." id="google_ads_iframe_/2..." title="3rd party ad content" name="" scrolling="no" marginwidth="0" marginheight="0" width="970" height="250" data-is-safeframe="true" sandbox="allow-forms allow-po..." allow="private-state-token-..." ...>
<section aria-label="Features bar" class="chromatic-ignore relative mt-3 h-[5.75rem] scroll-mt-[4.75rem]" id="convenience-bar" tabindex="-1">
<select aria-label="Horoscope" class="absolute left-0 top-0 size-full cursor-pointer appearance-none rounded-lg bg-transparent text-transparent outline-none focus-within:ring-2 focus-within:ring-indigo-8">
<select aria-label="Select a league" class="absolute left-0 top-0 size-full cursor-pointer appearance-none rounded-lg bg-transparent text-transparent outline-none focus-within:ring-2 focus-within:ring-indigo-8">
Showing first 10 of 61 audited elements.
Elements should not have tabindex greater than zero8 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
<iframe frameborder="0" src="https://be74ab7750ea..." id="google_ads_iframe_/2..." title="3rd party ad content" name="" scrolling="no" marginwidth="0" marginheight="0" width="970" height="250" data-is-safeframe="true" sandbox="allow-forms allow-po..." allow="private-state-token-..." ...>
<section aria-label="Features bar" class="chromatic-ignore relative mt-3 h-[5.75rem] scroll-mt-[4.75rem]" id="convenience-bar" tabindex="-1">
<section aria-label="Trending content" class="hidden xl:grid" id="stacked-list" tabindex="-1">
<main aria-label="Top stories and Stories for you" class="scroll-mt-[9.75rem] rounded-xl will-change-scroll" tabindex="-1">
<a data-ylk="aid:88b8525b-3265-3f..." data-yga="{"yContentCategory":..." aria-hidden="false" class="stretched-box chroma..." tabindex="0" href="/news/science/articl..." data-rapid_p="6" data-y-link-id="1o00eho01r2ldc07j82z" data-v9y="1"><aside aria-label="Weather, games, newsletter sign up, and more" class="hidden scroll-mt-[9.75rem] lg:grid" tabindex="-1">
<a data-ylk="mpos:1;sec:right-rai..." data-yga="{"yLinkElement":"loc..." href="https://weather.yaho..." target="_blank" rel="noopener noreferrer" type="button" class="uds-ring uds-hit-tar..." tabindex="0" data-rapid_p="3" style="column-gap: 0px; tra..." data-y-link-id="1vdaqyl1i7now40f3mcj" ...><iframe frameborder="0" src="https://be74ab7750ea..." id="google_ads_iframe_/2..." title="3rd party ad content" name="" scrolling="no" marginwidth="0" marginheight="0" width="300" height="250" data-is-safeframe="true" sandbox="allow-forms allow-po..." allow="private-state-token-..." ...>
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
<input aria-autocomplete="both" autocapitalize="off" autocomplete="off" autocorrect="off" class="bg-transparent dark:..." data-lpignore="true" id="uh-sbq" placeholder="Search the web" type="search" value="" data-rapid_p="4" data-v9y="1">
Form elements should have a visible label3 elements
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
<input aria-autocomplete="both" autocapitalize="off" autocomplete="off" autocorrect="off" class="bg-transparent dark:..." data-lpignore="true" id="uh-sbq" placeholder="Search the web" type="search" value="" data-rapid_p="4" data-v9y="1">
<select aria-label="Horoscope" class="absolute left-0 top-0 size-full cursor-pointer appearance-none rounded-lg bg-transparent text-transparent outline-none focus-within:ring-2 focus-within:ring-indigo-8">
<select aria-label="Select a league" class="absolute left-0 top-0 size-full cursor-pointer appearance-none rounded-lg bg-transparent text-transparent outline-none focus-within:ring-2 focus-within:ring-indigo-8">
Form field must not have multiple label elements3 elements
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
<input aria-autocomplete="both" autocapitalize="off" autocomplete="off" autocorrect="off" class="bg-transparent dark:..." data-lpignore="true" id="uh-sbq" placeholder="Search the web" type="search" value="" data-rapid_p="4" data-v9y="1">
<select aria-label="Horoscope" class="absolute left-0 top-0 size-full cursor-pointer appearance-none rounded-lg bg-transparent text-transparent outline-none focus-within:ring-2 focus-within:ring-indigo-8">
<select aria-label="Select a league" class="absolute left-0 top-0 size-full cursor-pointer appearance-none rounded-lg bg-transparent text-transparent outline-none focus-within:ring-2 focus-within:ring-indigo-8">
Frames must have an accessible name2 elements
Screen reader users rely on frame titles to understand frame content without exploring each one. Without descriptive, unique titles, users receive unhelpful information like "frame," "JavaScript," or URLs, making navigation through frames difficult and confusing.
Audit Elements
<iframe frameborder="0" src="https://be74ab7750ea..." id="google_ads_iframe_/2..." title="3rd party ad content" name="" scrolling="no" marginwidth="0" marginheight="0" width="970" height="250" data-is-safeframe="true" sandbox="allow-forms allow-po..." allow="private-state-token-..." ...>
<iframe frameborder="0" src="https://be74ab7750ea..." id="google_ads_iframe_/2..." title="3rd party ad content" name="" scrolling="no" marginwidth="0" marginheight="0" width="300" height="250" data-is-safeframe="true" sandbox="allow-forms allow-po..." allow="private-state-token-..." ...>
Heading levels should only increase by one53 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
<h3 class="text-primary display-s-emphasized line-clamp-2">Your love life is expanding and intensifying in all sorts of neat ways, so make sure that you're enjoying it! You may find that at least one person takes a new interest in you, so pay attention! </h3>
<h3 class="text-primary display-s-emphasized line-clamp-1">CrossFit® Games Day 1</h3>
<h3 class="text-primary display-s-emphasized line-clamp-2">How many grams of fiber should I actually be getting per day?</h3>
<h3 class="text-primary display-s-emphasized line-clamp-1">The Odyssey</h3>
<h3 class="text-primary display-s-emphasized line-clamp-2">‘Magnificent Seven’ wins Olympic gold</h3>
<h3 class="text-primary display-s-emphasized line-clamp-1">Yahoo Mini</h3>
<h3 class="text-primary display-s-emphasized line-clamp-1">Kansas City</h3>
<h3 class="text-primary display-s-emphasized line-clamp-1">Detroit</h3>
<h3 class="text-primary display-s-emphasized line-clamp-1">S&P 500</h3>
<h3 class="text-primary display-s-emphasized line-clamp-1">7,408.30</h3>
Showing first 10 of 53 audited elements.
Headings should not be empty53 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
<h3 class="text-primary display-s-emphasized line-clamp-2">Your love life is expanding and intensifying in all sorts of neat ways, so make sure that you're enjoying it! You may find that at least one person takes a new interest in you, so pay attention! </h3>
<h3 class="text-primary display-s-emphasized line-clamp-1">CrossFit® Games Day 1</h3>
<h3 class="text-primary display-s-emphasized line-clamp-2">How many grams of fiber should I actually be getting per day?</h3>
<h3 class="text-primary display-s-emphasized line-clamp-1">The Odyssey</h3>
<h3 class="text-primary display-s-emphasized line-clamp-2">‘Magnificent Seven’ wins Olympic gold</h3>
<h3 class="text-primary display-s-emphasized line-clamp-1">Yahoo Mini</h3>
<h3 class="text-primary display-s-emphasized line-clamp-1">Kansas City</h3>
<h3 class="text-primary display-s-emphasized line-clamp-1">Detroit</h3>
<h3 class="text-primary display-s-emphasized line-clamp-1">S&P 500</h3>
<h3 class="text-primary display-s-emphasized line-clamp-1">7,408.30</h3>
Showing first 10 of 53 audited elements.
IDs used in ARIA and labels must be unique3 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
<input aria-autocomplete="both" autocapitalize="off" autocomplete="off" autocorrect="off" class="bg-transparent dark:..." data-lpignore="true" id="uh-sbq" placeholder="Search the web" type="search" value="" data-rapid_p="4" data-v9y="1">
<h2 class="grow text-primary display-m-emphasized" id="_R_76iintr56cnqq5b_">Explore More</h2>
<div aria-live="off" aria-busy="false" class="flex md:mx-0 mx-4" id="_R_5qiintr56cnqq5b_" style="transform: translate3d(-1128px, 0px, 0px);">
Images must have alternative text82 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 alt="" width="80" height="80" decoding="async" data-nimg="1" class="chromatic-ignore siz..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" width="80" height="80" decoding="async" data-nimg="1" class="chromatic-ignore siz..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" width="80" height="80" decoding="async" data-nimg="1" class="chromatic-ignore siz..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" width="80" height="80" decoding="async" data-nimg="1" class="chromatic-ignore siz..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" width="80" height="80" decoding="async" data-nimg="1" class="chromatic-ignore siz..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" loading="lazy" width="1104" height="620" decoding="async" data-nimg="1" class="yahoo-ntk-hero-image..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="mr-1.5 inline size-5..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" loading="lazy" width="534" height="304" decoding="async" data-nimg="1" class="relative w-full roun..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="mr-1.5 inline size-5..." style="color:transparent" src="https://s.yimg.com/l...">
<img alt="" loading="lazy" width="534" height="304" decoding="async" data-nimg="1" class="relative w-full roun..." style="color:transparent" src="https://s.yimg.com/l...">
Showing first 10 of 82 audited elements.
Inline text spacing must be adjustable with custom stylesheets113 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
<html class="uds-color-mode-light" lang="en-US" style="color-scheme:light" data-hydrated="pass">
<div style="--feature-bar-margin:0">
<div class="relative z-0 items-center justify-center mx-auto my-0 ad-container" id="_R_3j56cnqq5b_" style="height:250px;width:970px">
<div class="flex" id="top_center-frontpage_1024" data-google-query-id="CNKrxt7R6pUDFSavOgUdpIAb5A" style="min-height: 250px;">
<div id="google_ads_iframe_/22888152279/us/yhp/main/dt/us_yhp_main_dt_top_center_0__container__" style="border: 0pt; display: inline-block; width: 970px; height: 250px;">
<iframe frameborder="0" src="https://be74ab7750ea..." id="google_ads_iframe_/2..." title="3rd party ad content" name="" scrolling="no" marginwidth="0" marginheight="0" width="970" height="250" data-is-safeframe="true" sandbox="allow-forms allow-po..." allow="private-state-token-..." ...>
<div class="flex flex-col gap-y-6 md:gap-y-4 lg:grid lg:grid-cols-[minmax(0,1fr)_300px] lg:justify-center lg:gap-x-4 xl:grid-cols-[300px_minmax(0,1fr)_300px]" style="margin-top:var(--feature-bar-margin)">
<img alt="" width="80" height="80" decoding="async" data-nimg="1" class="chromatic-ignore siz..." style="color:transparent" src="https://s.yimg.com/l...">
<div class="absolute left-0 top-0 h-[1.1875rem] w-[1.125rem] rounded-[0.219rem] bg-always-black" style="inset:0">
<img alt="" width="80" height="80" decoding="async" data-nimg="1" class="chromatic-ignore siz..." style="color:transparent" src="https://s.yimg.com/l...">
Showing first 10 of 113 audited elements.
Interactive controls must not be nested47 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 aria-label="Yahoo" class="fill-uh-purple dark:fill-white h-6" role="img" viewBox="0 0 86 24" xmlns="http://www.w3.org/2000/svg" preserveAspectRatio="xMinYMin meet">
<button class="focus-visible:outlin..." aria-label="Search with Yahoo Sc..." type="button" data-ylk="elm:search;elmt:icon..." data-rapid_p="6" data-y-link-id="05b01hp1qu6kce1mzpkz" data-v9y="1">
<button class="focus-visible:outlin..." aria-label="Search the web" data-ylk="elm:search;elmt:icon..." data-rapid_p="7" data-y-link-id="07i791q1qqpkyq07x5jj" data-v9y="1">
<button class="focus-visible:outlin..." aria-haspopup="menu" aria-expanded="false" id="_R_4pcl6cnqq5bH1_" data-rapid_p="15" data-y-link-id="1ejmscc1ghl1r01gjiav" data-v9y="1">
<option value="Capricorn" class="text-primary">Capricorn</option>
<option value="Aquarius" class="text-primary">Aquarius</option>
<option value="Pisces" class="text-primary">Pisces</option>
<option value="Aries" class="text-primary">Aries</option>
<option value="Taurus" class="text-primary">Taurus</option>
<option value="Gemini" class="text-primary">Gemini</option>
Showing first 10 of 47 audited elements.
Interactive elements must have a visible focus indicator29 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
<button class="focus-visible:outline-[rgb(96_1_210/50%)] dark:foc..." aria-label="Search with Yahoo Scout" type="button" data-ylk="elm:search;elmt:icon;itc:0;sec:ybar;slk:scout-btn;..." data-rapid_p="6" data-y-link-id="05b01hp1qu6kce1mzpkz" data-v9y="1">
<button class="focus-visible:outline-[rgb(96_1_210/50%)] dark:foc..." aria-label="Search the web" data-ylk="elm:search;elmt:icon;itc:0;sec:ybar;slk:websrch;su..." data-rapid_p="7" data-y-link-id="07i791q1qqpkyq07x5jj" data-v9y="1">
<a class="focus-visible:outline-[rgb(96_1_210/50%)] dark:foc..." href="#convenience-bar" data-ylk="sec:ybar;" data-rapid_p="8" data-y-link-id="06cixvj141esg70lc929" data-rapidintersecting-timer="884">
<a class="focus-visible:outline-[rgb(96_1_210/50%)] dark:foc..." href="#stacked-list" data-ylk="sec:ybar;" data-rapid_p="9" data-y-link-id="1u9xbno0z7r8zl0igs2c" data-rapidintersecting-timer="886">
<a class="focus-visible:outline-[rgb(96_1_210/50%)] dark:foc..." href="#ntk" data-ylk="sec:ybar;" data-rapid_p="10" data-y-link-id="1395p5o0i49qqw0o2mnt" data-rapidintersecting-timer="892">
<a class="focus-visible:outline-[rgb(96_1_210/50%)] dark:foc..." href="#right-rail" data-ylk="sec:ybar;" data-rapid_p="11" data-y-link-id="1l92vb91vac3bi15h5oo" data-rapidintersecting-timer="894">
<a class="hover:text-ymp-uh-grape-jelly dark:hover:text-uds-..." href="https://www.yahoo.com/" data-ylk="elm:navcat;itc:0;pkgt:top;sec:ybar;slk:news;subsec..." data-yga="{"yLinkText":"news","yLin..." data-rapid_p="12" data-y-link-id="0iyalrr04lo3ht1vpxz0" data-v9y="1"><a class="hover:text-ymp-uh-grape-jelly dark:hover:text-uds-..." href="https://finance.yahoo.com/" data-ylk="elm:navcat;itc:0;pkgt:top;sec:ybar;slk:finance;sub..." data-yga="{"yLinkText":"finance","y..." data-rapid_p="13" data-y-link-id="1v6r8vy0ju0nc01p3wh8" data-v9y="1"><a class="hover:text-ymp-uh-grape-jelly dark:hover:text-uds-..." href="https://sports.yahoo.com/" data-ylk="elm:navcat;itc:0;pkgt:top;sec:ybar;slk:sports;subs..." data-yga="{"yLinkText":"sports","yL..." data-rapid_p="14" data-y-link-id="0vjbfd91x1w54v1heuk7" data-v9y="1"><button class="focus-visible:outline-[rgb(96_1_210/50%)] dark:foc..." aria-haspopup="menu" aria-expanded="false" id="_R_4pcl6cnqq5bH1_" data-rapid_p="15" data-y-link-id="1ejmscc1ghl1r01gjiav" data-v9y="1">
Showing first 10 of 29 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 id="module-uh" data-version="1.7.3" class="font-yahoosans top-0...">
<section aria-label="Features bar" class="chromatic-ignore relative mt-3 h-[5.75rem] scroll-mt-[4.75rem]" id="convenience-bar" tabindex="-1">
<section aria-label="Trending content" class="hidden xl:grid" id="stacked-list" tabindex="-1">
<section aria-labelledby="_R_76iintr56cnqq5b_" class="rounded-xl bg-primary p-4 xl:py-5" id="explore-hub">
<main aria-label="Top stories and Stories for you" class="scroll-mt-[9.75rem] rounded-xl will-change-scroll" tabindex="-1">
<section aria-label="Top stories" aria-roledescription="carousel" class="relative" role="group">
<aside aria-label="Weather, games, newsletter sign up, and more" class="hidden scroll-mt-[9.75rem] lg:grid" tabindex="-1">
Links must have discernible text117 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 href="https://www.yahoo.co..." class=" focus-visible:round..." data-ylk="elm:logo;itc:0;sec:y..." data-yga="{"yLinkText":"frontp..." data-rapid_p="2" data-y-link-id="0hl7opn1psyuv810lvxj" data-v9y="1"><a class="focus-visible:outlin..." href="#convenience-bar" data-ylk="sec:ybar;" data-rapid_p="8" data-y-link-id="06cixvj141esg70lc929">
<a class="focus-visible:outlin..." href="#stacked-list" data-ylk="sec:ybar;" data-rapid_p="9" data-y-link-id="1u9xbno0z7r8zl0igs2c">
<a class="focus-visible:outlin..." href="#ntk" data-ylk="sec:ybar;" data-rapid_p="10" data-y-link-id="1395p5o0i49qqw0o2mnt">
<a class="focus-visible:outlin..." href="#right-rail" data-ylk="sec:ybar;" data-rapid_p="11" data-y-link-id="1l92vb91vac3bi15h5oo">
<a class="hover:text-ymp-uh-gr..." href="https://www.yahoo.co..." data-ylk="elm:navcat;itc:0;pkg..." data-yga="{"yLinkText":"news",..." data-rapid_p="12" data-y-link-id="0iyalrr04lo3ht1vpxz0" data-v9y="1"><a class="hover:text-ymp-uh-gr..." href="https://finance.yaho..." data-ylk="elm:navcat;itc:0;pkg..." data-yga="{"yLinkText":"financ..." data-rapid_p="13" data-y-link-id="1v6r8vy0ju0nc01p3wh8" data-v9y="1"><a class="hover:text-ymp-uh-gr..." href="https://sports.yahoo..." data-ylk="elm:navcat;itc:0;pkg..." data-yga="{"yLinkText":"sports..." data-rapid_p="14" data-y-link-id="0vjbfd91x1w54v1heuk7" data-v9y="1"><a aria-label="Check your mail" class="focus-visible:outlin..." href="https://mail.yahoo.c..." target="_blank" data-ylk="elm:btn;itc:0;sec:yb..." data-rapid_p="16" data-y-link-id="1m4xh6w02ndnw600lh4f" data-v9y="1">
<a href="https://login.yahoo...." class="hover:text-ymp-uh-gr..." data-ylk="elm:signin;itc:0;sec..." data-yga="{"yLinkText":"sign-i..." data-rapid_p="19" data-v9y="1">Showing first 10 of 117 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
<main aria-label="Top stories and Stories for you" class="scroll-mt-[9.75rem] rounded-xl will-change-scroll" tabindex="-1">
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 class="uds-color-mode-light" lang="en-US" style="color-scheme:light" data-hydrated="pass">
Required ARIA attributes must be provided15 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 aria-label="Yahoo" class="fill-uh-purple dark:fill-white h-6" role="img" viewBox="0 0 86 24" xmlns="http://www.w3.org/2000/svg" preserveAspectRatio="xMinYMin meet">
<form class="gap-1 z-10 h-10 just..." role="search" method="get">
<section aria-label="Top stories" aria-roledescription="carousel" class="relative" role="group">
<div aria-live="off" class="hidden md:flex bg-always-black/35 h-5 items-center justify-center rounded-2xl px-2 text-[0.8125rem] tracking-[.01625rem] text-always-white md:h-6" role="status"><span class="pr-1 font-bold">3</span><span class="font-normal">of 15</span></div>
<article aria-hidden="false" aria-label="Slide 3 of 15" aria-roledescription="slide" class="relative min-w-0 max-md:mr-2 max-md:rounded-lg md:flex-[0_0_100%] flex-[0_0_calc(100%-1rem)] overflow-hidden md:mr-3 md:rounded-xl" role="group" style="transform:translate3d(0, 0, 0)">
<div class="flex items-center gap-[0.375rem]" role="group">
<div class="relative h-[2.125rem] w-[6rem] shrink-0 rounded-[1.5rem] bg-tertiary p-[0.1875rem]" role="group">
<button aria-checked="true" aria-label="Small Cards" class="absolute left-[0.1875rem] top-[0.1875rem] z-10 flex h-[1.75rem] w-[2.75rem] items-center justify-center rounded-full bg-transparent transition-colors" role="radio" ...>
<button aria-checked="false" aria-label="Large Cards" class="absolute left-[3.062..." role="radio" data-ylk="elm:large;itc:1;pkgt...">
<div class="chromatic-ignore absolute right-[-7px] top-full z-[19] mt-3 transition-opacity duration-300 opacity-100" role="tooltip" aria-live="polite">
Showing first 10 of 15 audited elements.
Scrollable region must have keyboard access1 element
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
<div class="shimmer_fade-in__HCyIx no-scrollbar flex size-full gap-2 overflow-x-scroll px-4 pb-3 md:px-6 lg:px-0" id="conbar-content">
Select element must have an accessible name2 elements
Screen reader users cannot understand what information a select element requires without a proper label. Labels are essential for identifying form fields even when the purpose seems visually obvious, ensuring all users can complete forms successfully.
Audit Elements
<select aria-label="Horoscope" class="absolute left-0 top-0 size-full cursor-pointer appearance-none rounded-lg bg-transparent text-transparent outline-none focus-within:ring-2 focus-within:ring-indigo-8">
<select aria-label="Select a league" class="absolute left-0 top-0 size-full cursor-pointer appearance-none rounded-lg bg-transparent text-transparent outline-none focus-within:ring-2 focus-within:ring-indigo-8">
The skip-link target should exist and be focusable4 elements
Skip links allow keyboard users to bypass repetitive navigation and jump directly to main content. Without skip links, users must tab through potentially hundreds of navigation links on every page, which is time-consuming and can cause physical pain for users with motor limitations.
Audit Elements
<a class="focus-visible:outlin..." href="#convenience-bar" data-ylk="sec:ybar;" data-rapid_p="8" data-y-link-id="06cixvj141esg70lc929">
<a class="focus-visible:outlin..." href="#stacked-list" data-ylk="sec:ybar;" data-rapid_p="9" data-y-link-id="1u9xbno0z7r8zl0igs2c">
<a class="focus-visible:outlin..." href="#ntk" data-ylk="sec:ybar;" data-rapid_p="10" data-y-link-id="1395p5o0i49qqw0o2mnt">
<a class="focus-visible:outlin..." href="#right-rail" data-ylk="sec:ybar;" data-rapid_p="11" data-y-link-id="1l92vb91vac3bi15h5oo">
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">
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">