Yahoo yahoo.com

Screenshot of the Yahoo home page

Accessibility score

Poor+15 vs September

League position

4thof 9

Issues found

5

Audits passed

50

Accessibility score over time

weekly scans · last 6 months

Good · 90+
Needs improvement · 70–89
Poor · Below 70

This month's scan

Issues found

2Serious3Moderate

Serious

Elements must have their visible text as part of their accessible name

1 element

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

.w-auto

<a aria-label="Check your emails" class="focus-visible:outlin..." href="https://nz.mail.yaho..." target="_blank" data-ylk="elm:btn;itc:0;sec:yb..." data-y-link-id="16jqfti152dl9z1knvwp" data-rapid_p="14" data-v9y="1">

Fix any of the following:

Text inside the element is not included in the accessible name

Serious

Text must remain readable when spacing is increased

8 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

div.leading-5

<div class="leading-5">

a[href="/news/desperate-maga-candidate-vivek-ramaswamy-022028950.html"]

<a data-ylk="ccode:type_modeled__recall_trendingscorealloydb;cp..." data-yga="{&quot;yContentCategory&quot;:&quot;&quot;,&quot;y..." class="stretched-box chromatic-ignore text-primary headli..." href="/news/desperate-maga-candidate-vivek-ramaswamy-022..." data-y-link-id="1efnc7r0it1kbb0qn1j2" data-r...

li.cls-card-story:nth-of-type(7)>div.last\:border-none>div.gap-1\.5>h3>a.stretched-box

<a data-ylk="ccode:type_modeled__recall_trendingscorealloydb;cn..." data-yga="{&quot;yContentCategory&quot;:&quot;News&quot;,&qu..." class="stretched-box chromatic-ignore text-primary headli..." href="/news/aussie-serves-up-one-of-nations-worst-invasi..." data-y-link-id="0pwpxdg1w37o7z06ouof" data-r...

a[href="/news/donald-trump-knifes-son-donald-053301989.html"]

<a data-ylk="ccode:type_modeled__recall_trendingscorealloydb;cp..." data-yga="{&quot;yContentCategory&quot;:&quot;&quot;,&quot;y..." class="stretched-box chromatic-ignore text-primary headli..." href="/news/donald-trump-knifes-son-donald-053301989.htm..." data-y-link-id="0vrdg2w1nvy2v10rb85c" data-r...

a[href="/news/scott-jennings-trump-decision-defend-015157209.html"]

<a data-ylk="ccode:type_nonpersonalized__recall_popqual;cpos:22..." data-yga="{&quot;yContentCategory&quot;:&quot;&quot;,&quot;y..." class="stretched-box chromatic-ignore text-primary headli..." href="/news/scott-jennings-trump-decision-defend-0151572..." data-y-link-id="0irfzcj14bjbs40e16qu" data-r...

a[href="/news/ice-barbie-kristi-noem-busted-032030766.html"]

<a data-ylk="ccode:type_modeled__recall_trendingscorealloydb;cp..." data-yga="{&quot;yContentCategory&quot;:&quot;&quot;,&quot;y..." class="stretched-box chromatic-ignore text-primary headli..." href="/news/ice-barbie-kristi-noem-busted-032030766.html" data-y-link-id="12tlrdy1719jyt0wx31w" data-rapi...

a[href="/news/british-airways-plane-encounters-drone-180856664.html"]

<a data-ylk="ccode:type_modeled__recall_trendingscorealloydb;cp..." data-yga="{&quot;yContentCategory&quot;:&quot;&quot;,&quot;y..." class="stretched-box chromatic-ignore text-primary headli..." href="/news/british-airways-plane-encounters-drone-18085..." data-y-link-id="1i6hubz1keqvgr05b1cp" data-r...

a[href="/news/mom-36-drowned-trying-save-191845645.html"]

<a data-ylk="ccode:type_modeled__recall_trendingscorealloydb;cp..." data-yga="{&quot;yContentCategory&quot;:&quot;&quot;,&quot;y..." class="stretched-box chromatic-ignore text-primary headli..." href="/news/mom-36-drowned-trying-save-191845645.html" data-y-link-id="1rd3n7f0bnueon0pd0yi" data-rapid_p...

Moderate

Page should contain a level-one heading

1 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

<html class="uds-color-mode-light" lang="en-NZ" style="color-scheme:light" data-hydrated="pass">

Fix all of the following:

Page must have a level-one heading

Moderate

All page content should be contained by landmarks

1 element

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

#_R_7656iusq5b_ > .leading-3.bg-accent\/2.text-center

<div class="flex size-full items-center justify-center text-center leading-3 bg-accent/2" style="height:90px;width:728px">Advertisement</div>

Fix any of the following:

Some page content is not contained by landmarks

Moderate

The skip-link target should exist and be focusable

2 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.

Failing Elements

a[href$="#convenience-bar"]

<a class="focus-visible:outlin..." href="#convenience-bar" data-ylk="sec:ybar;" data-y-link-id="0fqebka0ylib9u066bka" data-rapid_p="7">

Fix any of the following:

No skip link target

a[href$="#ntk"]

<a class="focus-visible:outlin..." href="#ntk" data-ylk="sec:ybar;" data-y-link-id="1o6wxi91szmo3o12o0lo" data-rapid_p="9">

Fix any of the following:

No skip link target

Passed audits50 across 1 page

<html> element must have a lang attribute

1 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

<html class="uds-color-mode-light" lang="en-NZ" style="color-scheme:light" data-hydrated="pass">

<html> element must have a valid value for the lang attribute

1 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

<html class="uds-color-mode-light" lang="en-NZ" style="color-scheme:light" data-hydrated="pass">

<li> elements must be contained in a <ul> or <ol>

47 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

.left-0.top-0 > li:nth-child(1)

<li>

.left-0.top-0 > li:nth-child(2)

<li>

.left-0.top-0 > li:nth-child(3)

<li>

.left-0.top-0 > li:nth-child(4)

<li>

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(1)

<li class="cls-card-story list-none [contain-intrinsic-size:auto_var(--feed-card-intrinsic-h,130px)] [content-visibility:auto]">

Showing first 5 of 47 audited elements.

<svg> elements with an img or image role must have alternative text

2 elements

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

.fill-uh-purple

<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">

.size-8

<svg aria-hidden="false" aria-label="Partly cloudy" class="size-8" focusable="false" height="32" role="img" viewBox="0 0 32 32" width="32" xmlns="http://www.w3.org/2000/svg">

<ul> and <ol> must only directly contain <li>, <script> or <template> elements

6 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

.left-0.top-0

<ul class="absolute left-0 top-0">

.cls-stream-list

<ul class="cls-stream-list flex flex-col gap-4 lg:gap-5">

.mt-5

<ul class="mt-5 flex flex-col gap-3 sm:gap-5">

section[aria-labelledby="_R_9fktlfrm56iusq5b_"] > .h-full

<ul class="flex h-full flex-col items-start justify-start gap-2">

.top-\[92px\] > .lg\:sticky.lg\:top-\[720px\].xl\:max-w-\[300px\] > .grow-0.md\:ml-auto.md\:w-full > .mb-1 > .mt-3.md\:mt-1

<ul class="mt-3 flex list-none md:mt-1 justify-center">

Showing first 5 of 6 audited elements.

All page content should be contained by landmarks

431 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

#benji-dashboard-root

<div id="benji-dashboard-root"></div>

#privacy-banner-container

<div id="privacy-banner-container" class="w-full [&amp;&gt;iframe]:block"></div>

.cls-content-grid

<div class="cls-content-grid grid min-h-dvh grid-cols-1 grid-rows-[auto_1fr_auto] nca-homepage-en-NZ relative z-1 bg-secondary">

#module-uh

<header id="module-uh" data-version="1.20.2" class="focus-visible:outlin...">

.py-2\.5

<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">

Showing first 5 of 431 audited elements.

All touch targets must be 24px large, or leave sufficient space

47 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

.focus-visible\:outline-offset-8

<a href="https://nz.yahoo.com..." class=" focus-visible:round..." data-ylk="elm:logo;itc:0;sec:y..." data-yga="{"yLinkText":"frontp..." data-y-link-id="0qpw3yk16035951l6o2w" data-rapid_p="2" data-v9y="1">

#uh-sbq

<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">

.rapid-noclick-resp

<button class="focus-visible:outlin..." aria-label="Search query for Sea..." data-ylk="elm:search;elmt:icon..." data-y-link-id="0wgkexl0wd6mgb0nxvsq" data-rapid_p="6" data-v9y="1">

a[href$="#convenience-bar"]

<a class="focus-visible:outlin..." href="#convenience-bar" data-ylk="sec:ybar;" data-y-link-id="0fqebka0ylib9u066bka" data-rapid_p="7">

a[href$="#stacked-list"]

<a class="focus-visible:outlin..." href="#stacked-list" data-ylk="sec:ybar;" data-y-link-id="0tsjqiu1mmf0ei1bz7w5" data-rapid_p="8">

Showing first 5 of 47 audited elements.

Alternative text of images should not be repeated as text

30 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

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(1) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .pointer-events-none.chromatic-ignore.relative > .object-cover.sm\:block[width="520"]

<img alt="" loading="lazy" width="520" height="286" decoding="async" data-nimg="1" class="relative hidden size..." style="color:transparent" src="https://s.yimg.com/l...">

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(1) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .gap-1\.5.flex-1.items-start > .flex-row.w-full.items-center > .flex-row.min-w-0.items-center > .inline.rounded-full.mr-1\.5

<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...">

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(3) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .pointer-events-none.chromatic-ignore.relative > .object-cover.sm\:block[width="520"]

<img alt="" loading="lazy" width="520" height="286" decoding="async" data-nimg="1" class="relative hidden size..." src="https://s.yimg.com/l..." style="color: transparent;">

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(3) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .gap-1\.5.flex-1.items-start > .flex-row.w-full.items-center > .flex-row.min-w-0.items-center > .inline.rounded-full.mr-1\.5

<img alt="" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="mr-1.5 inline size-5..." src="https://s.yimg.com/l..." style="color: transparent;">

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(4) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .pointer-events-none.chromatic-ignore.relative > .object-cover.sm\:block[width="520"]

<img alt="" loading="lazy" width="520" height="286" decoding="async" data-nimg="1" class="relative hidden size..." src="https://s.yimg.com/l..." style="color: transparent;">

Showing first 5 of 30 audited elements.

ARIA attributes must be used as specified for the element's role

16 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

.fill-uh-purple

<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">

#uh-sbq

<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">

.rapid-noclick-resp

<button class="focus-visible:outlin..." aria-label="Search query for Sea..." data-ylk="elm:search;elmt:icon..." data-y-link-id="0wgkexl0wd6mgb0nxvsq" data-rapid_p="6" data-v9y="1">

#_R_9qp56iusq5bH1_

<button class="focus-visible:outlin..." aria-label="More menu" aria-expanded="false" id="_R_9qp56iusq5bH1_" data-y-link-id="1g0yvno1vidfjv02xte9" data-rapid_p="13" data-v9y="1">

.w-auto

<a aria-label="Check your emails" class="focus-visible:outlin..." href="https://nz.mail.yaho..." target="_blank" data-ylk="elm:btn;itc:0;sec:yb..." data-y-link-id="16jqfti152dl9z1knvwp" data-rapid_p="14" data-v9y="1">

Showing first 5 of 16 audited elements.

ARIA attributes must conform to valid names

16 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

.fill-uh-purple

<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">

#uh-sbq

<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">

.rapid-noclick-resp

<button class="focus-visible:outlin..." aria-label="Search query for Sea..." data-ylk="elm:search;elmt:icon..." data-y-link-id="0wgkexl0wd6mgb0nxvsq" data-rapid_p="6" data-v9y="1">

#_R_9qp56iusq5bH1_

<button class="focus-visible:outlin..." aria-label="More menu" aria-expanded="false" id="_R_9qp56iusq5bH1_" data-y-link-id="1g0yvno1vidfjv02xte9" data-rapid_p="13" data-v9y="1">

.w-auto

<a aria-label="Check your emails" class="focus-visible:outlin..." href="https://nz.mail.yaho..." target="_blank" data-ylk="elm:btn;itc:0;sec:yb..." data-y-link-id="16jqfti152dl9z1knvwp" data-rapid_p="14" data-v9y="1">

Showing first 5 of 16 audited elements.

ARIA attributes must conform to valid values

16 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

.fill-uh-purple

<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">

#uh-sbq

<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">

.rapid-noclick-resp

<button class="focus-visible:outlin..." aria-label="Search query for Sea..." data-ylk="elm:search;elmt:icon..." data-y-link-id="0wgkexl0wd6mgb0nxvsq" data-rapid_p="6" data-v9y="1">

#_R_9qp56iusq5bH1_

<button class="focus-visible:outlin..." aria-label="More menu" aria-expanded="false" id="_R_9qp56iusq5bH1_" data-y-link-id="1g0yvno1vidfjv02xte9" data-rapid_p="13" data-v9y="1">

.w-auto

<a aria-label="Check your emails" class="focus-visible:outlin..." href="https://nz.mail.yaho..." target="_blank" data-ylk="elm:btn;itc:0;sec:yb..." data-y-link-id="16jqfti152dl9z1knvwp" data-rapid_p="14" data-v9y="1">

Showing first 5 of 16 audited elements.

ARIA hidden element must not be focusable or contain focusable elements

34 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

.\!shrink

<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[fill="none"][width="20"][height="20"]

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

.group-hover\:fill-\[white\]

<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]">

.fill-white

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

.top-full

<span class="absolute inset-x-0 top-full z-10 hidden group-hover:block group-focus-visible:block" style="height:9px" aria-hidden="true"></span>

Showing first 5 of 34 audited elements.

ARIA role should be appropriate for the element

4 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

.fill-uh-purple

<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

<form class="gap-2.5 z-10 h-10 ju..." role="search" method="get">

.size-8

<svg aria-hidden="false" aria-label="Partly cloudy" class="size-8" focusable="false" height="32" role="img" viewBox="0 0 32 32" width="32" xmlns="http://www.w3.org/2000/svg">

next-route-announcer,#__next-route-announcer__

<div aria-live="assertive" id="__next-route-announcer__" role="alert" style="position: absolute; border: 0px; height: 1px; margin: -1px; padding: 0px; width: 1px; clip: rect(0px, 0px, 0px, 0px); overflow: hidden; white-space: nowrap; overflow-wrap: normal;"></div>

ARIA roles used must conform to valid values

4 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

.fill-uh-purple

<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

<form class="gap-2.5 z-10 h-10 ju..." role="search" method="get">

.size-8

<svg aria-hidden="false" aria-label="Partly cloudy" class="size-8" focusable="false" height="32" role="img" viewBox="0 0 32 32" width="32" xmlns="http://www.w3.org/2000/svg">

next-route-announcer,#__next-route-announcer__

<div aria-live="assertive" id="__next-route-announcer__" role="alert" style="position: absolute; border: 0px; height: 1px; margin: -1px; padding: 0px; width: 1px; clip: rect(0px, 0px, 0px, 0px); overflow: hidden; white-space: nowrap; overflow-wrap: normal;"></div>

aria-hidden="true" must not be present on the document body

1 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

#news-content-app

<body class="__variable_bf21da __variable_b835f1 __variable_fc858e bg-secondary font-yahoosans text-primary" id="news-content-app">

autocomplete attribute must be used correctly

1 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

#uh-sbq

<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 landmark

1 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

#module-uh

<header id="module-uh" data-version="1.20.2" class="focus-visible:outlin...">

Buttons must have discernible text

3 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

.rapid-noclick-resp

<button class="focus-visible:outlin..." aria-label="Search query for Sea..." data-ylk="elm:search;elmt:icon..." data-y-link-id="0wgkexl0wd6mgb0nxvsq" data-rapid_p="6" data-v9y="1">

#_R_9qp56iusq5bH1_

<button class="focus-visible:outlin..." aria-label="More menu" aria-expanded="false" id="_R_9qp56iusq5bH1_" data-y-link-id="1g0yvno1vidfjv02xte9" data-rapid_p="13" data-v9y="1">

button[data-y-link-id="16xm5dm0c1hvl81hjwjd"]

<button class="group flex shrink-0 ..." data-ylk="mpos:1;sec:right-rai..." data-yga="{"yLinkElement":"loc..." data-y-link-id="16xm5dm0c1hvl81hjwjd" data-rapid_p="1" data-v9y="1">

Content must reflow without two-dimensional scrolling

0 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.

Deprecated ARIA roles must not be used

4 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

.fill-uh-purple

<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

<form class="gap-2.5 z-10 h-10 ju..." role="search" method="get">

.size-8

<svg aria-hidden="false" aria-label="Partly cloudy" class="size-8" focusable="false" height="32" role="img" viewBox="0 0 32 32" width="32" xmlns="http://www.w3.org/2000/svg">

next-route-announcer,#__next-route-announcer__

<div aria-live="assertive" id="__next-route-announcer__" role="alert" style="position: absolute; border: 0px; height: 1px; margin: -1px; padding: 0px; width: 1px; clip: rect(0px, 0px, 0px, 0px); overflow: hidden; white-space: nowrap; overflow-wrap: normal;"></div>

Document should have one main landmark

1 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

<html class="uds-color-mode-light" lang="en-NZ" style="color-scheme:light" data-hydrated="pass">

Document should not have more than one banner landmark

1 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

#module-uh

<header id="module-uh" data-version="1.20.2" class="focus-visible:outlin...">

Document should not have more than one main landmark

1 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

<main aria-label="Top stories and Stories for you" class="scroll-mt-[9.75rem] rounded-xl will-change-scroll md:bg-primary" tabindex="-1">

Documents must have <title> element to aid in navigation

1 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

<html class="uds-color-mode-light" lang="en-NZ" style="color-scheme:light" data-hydrated="pass">

Elements marked as presentational should be consistently ignored

30 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

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(1) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .pointer-events-none.chromatic-ignore.relative > .object-cover.sm\:block[width="520"]

<img alt="" loading="lazy" width="520" height="286" decoding="async" data-nimg="1" class="relative hidden size..." style="color:transparent" src="https://s.yimg.com/l...">

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(1) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .gap-1\.5.flex-1.items-start > .flex-row.w-full.items-center > .flex-row.min-w-0.items-center > .inline.rounded-full.mr-1\.5

<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...">

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(3) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .pointer-events-none.chromatic-ignore.relative > .object-cover.sm\:block[width="520"]

<img alt="" loading="lazy" width="520" height="286" decoding="async" data-nimg="1" class="relative hidden size..." src="https://s.yimg.com/l..." style="color: transparent;">

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(3) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .gap-1\.5.flex-1.items-start > .flex-row.w-full.items-center > .flex-row.min-w-0.items-center > .inline.rounded-full.mr-1\.5

<img alt="" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="mr-1.5 inline size-5..." src="https://s.yimg.com/l..." style="color: transparent;">

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(4) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .pointer-events-none.chromatic-ignore.relative > .object-cover.sm\:block[width="520"]

<img alt="" loading="lazy" width="520" height="286" decoding="async" data-nimg="1" class="relative hidden size..." src="https://s.yimg.com/l..." style="color: transparent;">

Showing first 5 of 30 audited elements.

Elements must have their visible text as part of their accessible name

1 element

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

#_R_9qp56iusq5bH1_

<button class="focus-visible:outlin..." aria-label="More menu" aria-expanded="false" id="_R_9qp56iusq5bH1_" data-y-link-id="1g0yvno1vidfjv02xte9" data-rapid_p="13" data-v9y="1">

Elements must meet minimum color contrast ratio thresholds

78 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

#uh-sbq

<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">

.font-bold

<a class="hover:text-ymp-uh-gr..." href="https://nz.yahoo.com..." data-ylk="elm:navcat;itc:0;pkg..." data-yga="{"yLinkText":"news",..." data-y-link-id="1wrueda1mp4ehp1yi3ws" data-rapid_p="11" data-v9y="1">

a[data-y-link-id="1212kf516xn73x1ikee0"]

<a class="hover:text-ymp-uh-gr..." href="https://nz.finance.y..." data-ylk="elm:navcat;itc:0;pkg..." data-yga="{"yLinkText":"financ..." data-y-link-id="1212kf516xn73x1ikee0" data-rapid_p="12" data-v9y="1">

#_R_9qp56iusq5bH1_

<button class="focus-visible:outlin..." aria-label="More menu" aria-expanded="false" id="_R_9qp56iusq5bH1_" data-y-link-id="1g0yvno1vidfjv02xte9" data-rapid_p="13" data-v9y="1">

.min-w-\[26px\]

<span class="min-w-[26px] whitespace-nowrap leading-tight">Mail</span>

Showing first 5 of 78 audited elements.

Elements must only use permitted ARIA attributes

16 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

.fill-uh-purple

<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">

#uh-sbq

<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">

.rapid-noclick-resp

<button class="focus-visible:outlin..." aria-label="Search query for Sea..." data-ylk="elm:search;elmt:icon..." data-y-link-id="0wgkexl0wd6mgb0nxvsq" data-rapid_p="6" data-v9y="1">

#_R_9qp56iusq5bH1_

<button class="focus-visible:outlin..." aria-label="More menu" aria-expanded="false" id="_R_9qp56iusq5bH1_" data-y-link-id="1g0yvno1vidfjv02xte9" data-rapid_p="13" data-v9y="1">

.w-auto

<a aria-label="Check your emails" class="focus-visible:outlin..." href="https://nz.mail.yaho..." target="_blank" data-ylk="elm:btn;itc:0;sec:yb..." data-y-link-id="16jqfti152dl9z1knvwp" data-rapid_p="14" data-v9y="1">

Showing first 5 of 16 audited elements.

Elements must only use supported ARIA attributes

16 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

.fill-uh-purple

<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">

#uh-sbq

<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">

.rapid-noclick-resp

<button class="focus-visible:outlin..." aria-label="Search query for Sea..." data-ylk="elm:search;elmt:icon..." data-y-link-id="0wgkexl0wd6mgb0nxvsq" data-rapid_p="6" data-v9y="1">

#_R_9qp56iusq5bH1_

<button class="focus-visible:outlin..." aria-label="More menu" aria-expanded="false" id="_R_9qp56iusq5bH1_" data-y-link-id="1g0yvno1vidfjv02xte9" data-rapid_p="13" data-v9y="1">

.w-auto

<a aria-label="Check your emails" class="focus-visible:outlin..." href="https://nz.mail.yaho..." target="_blank" data-ylk="elm:btn;itc:0;sec:yb..." data-y-link-id="16jqfti152dl9z1knvwp" data-rapid_p="14" data-v9y="1">

Showing first 5 of 16 audited elements.

Elements should not have tabindex greater than zero

2 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

main

<main aria-label="Top stories and Stories for you" class="scroll-mt-[9.75rem] rounded-xl will-change-scroll md:bg-primary" tabindex="-1">

aside

<aside aria-label="Weather, games, newsletter sign-up and more" class="hidden scroll-mt-[9.75rem] lg:grid" tabindex="-1">

Focused elements must not be entirely hidden by author-created content

45 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

button.rapid-noclick-resp

<button class="focus-visible:outline-[rgb(96_1_210/80%)] dark:foc..." aria-label="Search query for Search the web" data-ylk="elm:search;elmt:icon;itc:0;sec:ybar;slk:websrch;su..." data-y-link-id="0wgkexl0wd6mgb0nxvsq" data-rapid_p="6" data-v9y="1">

a[href="#convenience-bar"]

<a class="focus-visible:outline-[rgb(96_1_210/80%)] dark:foc..." href="#convenience-bar" data-ylk="sec:ybar;" data-y-link-id="0fqebka0ylib9u066bka" data-rapid_p="7" data-rapidintersecting-timer="802">

a[href="#stacked-list"]

<a class="focus-visible:outline-[rgb(96_1_210/80%)] dark:foc..." href="#stacked-list" data-ylk="sec:ybar;" data-y-link-id="0tsjqiu1mmf0ei1bz7w5" data-rapid_p="8" data-rapidintersecting-timer="804">

a[href="#ntk"]

<a class="focus-visible:outline-[rgb(96_1_210/80%)] dark:foc..." href="#ntk" data-ylk="sec:ybar;" data-y-link-id="1o6wxi91szmo3o12o0lo" data-rapid_p="9" data-rapidintersecting-timer="806">

a[href="#right-rail"]

<a class="focus-visible:outline-[rgb(96_1_210/80%)] dark:foc..." href="#right-rail" data-ylk="sec:ybar;" data-y-link-id="0u1zr5m0hs44061t1d0l" data-rapid_p="10" data-rapidintersecting-timer="808">

Showing first 5 of 45 audited elements.

Form elements must have labels

1 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

#uh-sbq

<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 label

1 element

The title and aria-describedby attributes provide supplementary hints, not labels. Screen readers treat these as advisory information rather than true labels, which prevents them from properly conveying the form element's purpose. Form fields need proper labels that can be programmatically determined.

Audit Elements

#uh-sbq

<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 field must not have multiple label elements

1 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

#uh-sbq

<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">

Heading levels should only increase by one

17 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

.inline-block

<h2 class="inline-block text-primary display-m-emphasized">For You</h2>

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(1) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .gap-1\.5.flex-1.items-start > h3

<h3>

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(3) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .gap-1\.5.flex-1.items-start > h3

<h3>

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(4) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .gap-1\.5.flex-1.items-start > h3

<h3>

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(5) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .gap-1\.5.flex-1.items-start > h3

<h3>

Showing first 5 of 17 audited elements.

Headings should not be empty

17 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

.inline-block

<h2 class="inline-block text-primary display-m-emphasized">For You</h2>

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(1) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .gap-1\.5.flex-1.items-start > h3

<h3>

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(3) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .gap-1\.5.flex-1.items-start > h3

<h3>

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(4) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .gap-1\.5.flex-1.items-start > h3

<h3>

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(5) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .gap-1\.5.flex-1.items-start > h3

<h3>

Showing first 5 of 17 audited elements.

IDs used in ARIA and labels must be unique

3 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

#uh-sbq

<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">

#_R_59ktlfrm56iusq5b_

<h2 class="grow text-primary display-m-emphasized" id="_R_59ktlfrm56iusq5b_">Explore more</h2>

#_R_9fktlfrm56iusq5b_

<h2 class="grow text-primary display-m-emphasized" id="_R_9fktlfrm56iusq5b_">Explore more</h2>

Images must have alternative text

30 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

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(1) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .pointer-events-none.chromatic-ignore.relative > .object-cover.sm\:block[width="520"]

<img alt="" loading="lazy" width="520" height="286" decoding="async" data-nimg="1" class="relative hidden size..." style="color:transparent" src="https://s.yimg.com/l...">

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(1) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .gap-1\.5.flex-1.items-start > .flex-row.w-full.items-center > .flex-row.min-w-0.items-center > .inline.rounded-full.mr-1\.5

<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...">

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(3) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .pointer-events-none.chromatic-ignore.relative > .object-cover.sm\:block[width="520"]

<img alt="" loading="lazy" width="520" height="286" decoding="async" data-nimg="1" class="relative hidden size..." src="https://s.yimg.com/l..." style="color: transparent;">

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(3) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .gap-1\.5.flex-1.items-start > .flex-row.w-full.items-center > .flex-row.min-w-0.items-center > .inline.rounded-full.mr-1\.5

<img alt="" loading="lazy" width="20" height="20" decoding="async" data-nimg="1" class="mr-1.5 inline size-5..." src="https://s.yimg.com/l..." style="color: transparent;">

.cls-card-story.\[contain-intrinsic-size\:auto_var\(--feed-card-intrinsic-h\,130px\)\].\[content-visibility\:auto\]:nth-child(4) > .last\:border-none.lg\:last\:pb-0.xl\:pr-5 > .pointer-events-none.chromatic-ignore.relative > .object-cover.sm\:block[width="520"]

<img alt="" loading="lazy" width="520" height="286" decoding="async" data-nimg="1" class="relative hidden size..." src="https://s.yimg.com/l..." style="color: transparent;">

Showing first 5 of 30 audited elements.

Inline text spacing must be adjustable with custom stylesheets

6 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

<html class="uds-color-mode-light" lang="en-NZ" style="color-scheme:light" data-hydrated="pass">

.cls-content-grid > div > div:nth-child(1)

<div style="--feature-bar-margin:0">

#_R_7656iusq5b_

<div class="relative z-0 items-center justify-center mx-auto my-0 ad-container" id="_R_7656iusq5b_" style="height:250px;width:970px">

#_R_7656iusq5b_ > .leading-3.bg-accent\/2.text-center

<div class="flex size-full items-center justify-center text-center leading-3 bg-accent/2" style="height:90px;width:728px">Advertisement</div>

.gap-y-6

<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-[680px_300px]" style="margin-top:var(--feature-bar-margin)">

Showing first 5 of 6 audited elements.

Interactive controls must not be nested

5 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

.fill-uh-purple

<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">

.rapid-noclick-resp

<button class="focus-visible:outlin..." aria-label="Search query for Sea..." data-ylk="elm:search;elmt:icon..." data-y-link-id="0wgkexl0wd6mgb0nxvsq" data-rapid_p="6" data-v9y="1">

#_R_9qp56iusq5bH1_

<button class="focus-visible:outlin..." aria-label="More menu" aria-expanded="false" id="_R_9qp56iusq5bH1_" data-y-link-id="1g0yvno1vidfjv02xte9" data-rapid_p="13" data-v9y="1">

button[data-y-link-id="16xm5dm0c1hvl81hjwjd"]

<button class="group flex shrink-0 ..." data-ylk="mpos:1;sec:right-rai..." data-yga="{"yLinkElement":"loc..." data-y-link-id="16xm5dm0c1hvl81hjwjd" data-rapid_p="1" data-v9y="1">

.size-8

<svg aria-hidden="false" aria-label="Partly cloudy" class="size-8" focusable="false" height="32" role="img" viewBox="0 0 32 32" width="32" xmlns="http://www.w3.org/2000/svg">

Interactive elements must have a visible focus indicator

47 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.rapid-noclick-resp

<button class="focus-visible:outline-[rgb(96_1_210/80%)] dark:foc..." aria-label="Search query for Search the web" data-ylk="elm:search;elmt:icon;itc:0;sec:ybar;slk:websrch;su..." data-y-link-id="0wgkexl0wd6mgb0nxvsq" data-rapid_p="6" data-v9y="1">

a[href="#convenience-bar"]

<a class="focus-visible:outline-[rgb(96_1_210/80%)] dark:foc..." href="#convenience-bar" data-ylk="sec:ybar;" data-y-link-id="0fqebka0ylib9u066bka" data-rapid_p="7" data-rapidintersecting-timer="802">

a[href="#stacked-list"]

<a class="focus-visible:outline-[rgb(96_1_210/80%)] dark:foc..." href="#stacked-list" data-ylk="sec:ybar;" data-y-link-id="0tsjqiu1mmf0ei1bz7w5" data-rapid_p="8" data-rapidintersecting-timer="804">

a[href="#ntk"]

<a class="focus-visible:outline-[rgb(96_1_210/80%)] dark:foc..." href="#ntk" data-ylk="sec:ybar;" data-y-link-id="1o6wxi91szmo3o12o0lo" data-rapid_p="9" data-rapidintersecting-timer="806">

a[href="#right-rail"]

<a class="focus-visible:outline-[rgb(96_1_210/80%)] dark:foc..." href="#right-rail" data-ylk="sec:ybar;" data-y-link-id="0u1zr5m0hs44061t1d0l" data-rapid_p="10" data-rapidintersecting-timer="808">

Showing first 5 of 47 audited elements.

Keyboard focus must be able to leave every component it can enter

0 elements

Keyboard users move through a page with Tab, Shift+Tab, arrow keys and Escape. When focus enters a component and none of those keys lets it leave, the rest of the page becomes unreachable and the only way out is to reload or abandon it.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination

5 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

#module-uh

<header id="module-uh" data-version="1.20.2" class="focus-visible:outlin...">

form

<form class="gap-2.5 z-10 h-10 ju..." role="search" method="get">

main

<main aria-label="Top stories and Stories for you" class="scroll-mt-[9.75rem] rounded-xl will-change-scroll md:bg-primary" tabindex="-1">

aside

<aside aria-label="Weather, games, newsletter sign-up and more" class="hidden scroll-mt-[9.75rem] lg:grid" tabindex="-1">

section[aria-labelledby="_R_9fktlfrm56iusq5b_"]

<section aria-labelledby="_R_9fktlfrm56iusq5b_" class="rounded-xl bg-primary p-4 xl:py-5" id="explore-hub">

Links must have discernible text

45 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

.focus-visible\:outline-offset-8

<a href="https://nz.yahoo.com..." class=" focus-visible:round..." data-ylk="elm:logo;itc:0;sec:y..." data-yga="{"yLinkText":"frontp..." data-y-link-id="0qpw3yk16035951l6o2w" data-rapid_p="2" data-v9y="1">

a[href$="#convenience-bar"]

<a class="focus-visible:outlin..." href="#convenience-bar" data-ylk="sec:ybar;" data-y-link-id="0fqebka0ylib9u066bka" data-rapid_p="7">

a[href$="#stacked-list"]

<a class="focus-visible:outlin..." href="#stacked-list" data-ylk="sec:ybar;" data-y-link-id="0tsjqiu1mmf0ei1bz7w5" data-rapid_p="8">

a[href$="#ntk"]

<a class="focus-visible:outlin..." href="#ntk" data-ylk="sec:ybar;" data-y-link-id="1o6wxi91szmo3o12o0lo" data-rapid_p="9">

a[href$="#right-rail"]

<a class="focus-visible:outlin..." href="#right-rail" data-ylk="sec:ybar;" data-y-link-id="0u1zr5m0hs44061t1d0l" data-rapid_p="10">

Showing first 5 of 45 audited elements.

Main landmark should not be contained in another landmark

1 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

<main aria-label="Top stories and Stories for you" class="scroll-mt-[9.75rem] rounded-xl will-change-scroll md:bg-primary" tabindex="-1">

Page must have means to bypass repeated blocks

1 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

<html class="uds-color-mode-light" lang="en-NZ" style="color-scheme:light" data-hydrated="pass">

Required ARIA attributes must be provided

4 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

.fill-uh-purple

<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

<form class="gap-2.5 z-10 h-10 ju..." role="search" method="get">

.size-8

<svg aria-hidden="false" aria-label="Partly cloudy" class="size-8" focusable="false" height="32" role="img" viewBox="0 0 32 32" width="32" xmlns="http://www.w3.org/2000/svg">

next-route-announcer,#__next-route-announcer__

<div aria-live="assertive" id="__next-route-announcer__" role="alert" style="position: absolute; border: 0px; height: 1px; margin: -1px; padding: 0px; width: 1px; clip: rect(0px, 0px, 0px, 0px); overflow: hidden; white-space: nowrap; overflow-wrap: normal;"></div>

The skip-link target should exist and be focusable

1 element

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[href$="#right-rail"]

<a class="focus-visible:outlin..." href="#right-rail" data-ylk="sec:ybar;" data-y-link-id="0u1zr5m0hs44061t1d0l" data-rapid_p="10">

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"]

<meta name="viewport" content="width=device-width, initial-scale=1">

Zooming and scaling must not be disabled

1 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"]

<meta name="viewport" content="width=device-width, initial-scale=1">

How does your site stack up against Yahoo?

Run the same automated WCAG 2.2 checks we run on the scoreboard.

More in Search Engine