Australian Governmentaustralia.gov.au
Accessibility Score
Issues Found
Issues Found
CriticalElements must only use supported ARIA attributes1 element
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.
Failing Elements
<div class="login-container" aria-expanded="false"><button type="button" id="user-banner" class="sign-in sign-in--unauth"><div class="sign-in-btn" title="Not signed in"><span>Sign in</span></div></button></div>
Fix all of the following:
- ARIA attribute is not allowed: aria-expanded="false"
CriticalCertain ARIA roles must contain particular children3 elements
ARIA roles missing required child elements cannot perform their intended accessibility functions. Children provide essential context, like how a treeitem relates to its parent container and siblings. Without proper children, assistive technologies cannot convey this structural information to users.
Failing Elements
<div part="container" role="list"><slot></slot></div>
Fix any of the following:
- Element has children which are not allowed: button[tabindex]
<gui-tile-list class="cmp-list-gui hydrated" id="list-e830ad2bac" data-cmp-data-layer="{"list-e830ad2bac":{"@type":"mygov-common/components/core/list","repo:modifyDate":"2023-03-03T00:27:08Z"}}" variant="3up" role="list">Fix any of the following:
- Element has children which are not allowed: a[tabindex]
<div part="container" role="list"><slot></slot></div>
Fix any of the following:
- Element has children which are not allowed: [role=tooltip]
CriticalCertain ARIA roles must be contained by particular parents2 elements
ARIA roles with missing required parent elements cannot function as intended for assistive technology users. Parent-child relationships convey essential hierarchy and context, like showing where an item sits within a tree structure. Without proper parents, this critical relationship information is lost.
Failing Elements
<gui-nav-item href="https://x.com/mygovau" anchor-aria-label="X" icon-only-name="logo_x" role="listitem" class="hydrated"></gui-nav-item>
Fix any of the following:
- Required ARIA parent role not present: list
<gui-nav-item href="https://www.youtube.com/user/mygovau" anchor-aria-label="YouTube" icon-only-name="logo_you_tube" role="listitem" class="hydrated"></gui-nav-item>
Fix any of the following:
- Required ARIA parent role not present: list
ModerateZooming 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.
Failing Elements
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=0">
Fix any of the following:
- user-scalable on <meta> tag disables zooming on mobile devices
Passed Audits
<html> element must have a lang attribute1 element
Screen readers need language information to switch between pronunciation libraries. Without a specified language, screen readers default to the user's preferred language, resulting in incorrect pronunciation that sounds like a strange accent and makes content difficult or impossible to understand.
Audit Elements
<html lang="en">
<html> element must have a valid value for the lang attribute1 element
Screen readers use language-specific sound libraries for proper pronunciation. Invalid language attributes cause screen readers to use the wrong library, making text sound like a confusing accent or completely unintelligible, especially for multilingual users who access content in multiple languages.
Audit Elements
<html lang="en">
<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 xmlns="http://www.w3.org/2000/svg" data-name="Layer 1" viewBox="0 0 350.86 76.18" height="100%" width="100%" display="block" fill="currentColor" part="icon" role="img">
All page content should be contained by landmarks253 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Audit Elements
<div class="cmp-page__skiptomaincontent">
<a class="cmp-page__skiptomaincontent-link" href="#main">Skip to main content</a>
</div><a class="cmp-page__skiptomaincontent-link" href="#main">Skip to main content</a>
<div class="root container responsivegrid">
<div id="container-f3f77ec7ec" class="cmp-container root responsivegrid">
<div class="aem-Grid aem-Grid--12 aem-Grid--default--12 ">
<div class="global-banners aem-GridColumn aem-GridColumn--default--12"><div data-habitat="C1"></div>
</div><div data-habitat="C1"></div>
<div class="header aem-GridColumn aem-GridColumn--default--12">
<gui-header class="mygov-header hydrated" responsive-breakpoint="63.99875em" side-nav-close-text="Close" side-nav-menu-text="Menu">
<header part="header"><slot></slot><div part="side-nav-trigger-button-container"><button part="side-nav-trigger-button"><span>Menu</span><gui-icon exportparts="icon: icon-menu" name="menu" library="default" class="hydrated"></gui-icon></button></div></header>
Showing first 10 of 253 audited elements.
Alternative text of images should not be repeated as text7 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 class="mygov-header-show-lg-above" src="/content/dam/mygov/public/images/brand/myGov-logo-cobranded-black.svg" alt="Australian Government and myGov logo">
<img src="/en/services/raising..." srcset="/en/services/raising..." loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="1920" height="1080" alt="" title="Mother and toddler">
<img src="/en/services/living-..." srcset="/en/services/living-..." loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="800" height="533" alt="Person contemplating..." title="Living arrangements ...">
<img src="/en/services/ageing/..." srcset="/en/services/ageing/..." loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="1920" height="1080" alt="" title="Woman and man using ...">
<img src="/en/services/work/_j..." srcset="/en/services/work/_j..." loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="800" height="533" alt="A young person with ..." title="Work category">
<img src="/en/services/educati..." srcset="/en/services/educati..." loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="800" height="533" alt="Three young children..." title="Education category">
<img src="/en/services/health-..." srcset="/en/services/health-..." loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="800" height="533" alt="A young person in a ..." title="Health and disabilit...">
ARIA attributes must be used as specified for the element's role19 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
<gui-nav-bar class="mygov-nav-bar-header hydrated" aria-label="top level" role="navigation">
<div class="login-container" aria-expanded="false"><button type="button" id="user-banner" class="sign-in sign-in--unauth"><div class="sign-in-btn" title="Not signed in"><span>Sign in</span></div></button></div>
<gui-nav-bar class="mygov-nav-bar mygov-header-show-lg-above hydrated" aria-label="Menu" role="navigation">
<a aria-current="false" href="/en/services/raising-kids">Raising kids</a>
<a aria-current="false" href="/en/services/living-arrangements">Living arrangements</a>
<a aria-current="false" href="/en/services/ageing">Ageing</a>
<a aria-current="false" href="/en/services/work">Work</a>
<a aria-current="false" href="/en/services/education">Education</a>
<a aria-current="false" href="/en/services/health-and-disability">Health and disability</a>
<div class="assistant-panel-closed" role="region" aria-label="Digital Assistant" aria-expanded="false">
Showing first 10 of 19 audited elements.
ARIA attributes must conform to valid names19 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
<gui-nav-bar class="mygov-nav-bar-header hydrated" aria-label="top level" role="navigation">
<div class="login-container" aria-expanded="false"><button type="button" id="user-banner" class="sign-in sign-in--unauth"><div class="sign-in-btn" title="Not signed in"><span>Sign in</span></div></button></div>
<gui-nav-bar class="mygov-nav-bar mygov-header-show-lg-above hydrated" aria-label="Menu" role="navigation">
<a aria-current="false" href="/en/services/raising-kids">Raising kids</a>
<a aria-current="false" href="/en/services/living-arrangements">Living arrangements</a>
<a aria-current="false" href="/en/services/ageing">Ageing</a>
<a aria-current="false" href="/en/services/work">Work</a>
<a aria-current="false" href="/en/services/education">Education</a>
<a aria-current="false" href="/en/services/health-and-disability">Health and disability</a>
<div class="assistant-panel-closed" role="region" aria-label="Digital Assistant" aria-expanded="false">
Showing first 10 of 19 audited elements.
ARIA attributes must conform to valid values19 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
<gui-nav-bar class="mygov-nav-bar-header hydrated" aria-label="top level" role="navigation">
<div class="login-container" aria-expanded="false"><button type="button" id="user-banner" class="sign-in sign-in--unauth"><div class="sign-in-btn" title="Not signed in"><span>Sign in</span></div></button></div>
<gui-nav-bar class="mygov-nav-bar mygov-header-show-lg-above hydrated" aria-label="Menu" role="navigation">
<a aria-current="false" href="/en/services/raising-kids">Raising kids</a>
<a aria-current="false" href="/en/services/living-arrangements">Living arrangements</a>
<a aria-current="false" href="/en/services/ageing">Ageing</a>
<a aria-current="false" href="/en/services/work">Work</a>
<a aria-current="false" href="/en/services/education">Education</a>
<a aria-current="false" href="/en/services/health-and-disability">Health and disability</a>
<div class="assistant-panel-closed" role="region" aria-label="Digital Assistant" aria-expanded="false">
Showing first 10 of 19 audited elements.
ARIA role should be appropriate for the element50 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
<gui-nav-bar class="mygov-nav-bar-header hydrated" aria-label="top level" role="navigation">
<div part="container" role="list"><slot></slot></div>
<gui-nav-item class="mygov-header-show-lg-above hydrated" role="listitem">
<a href="/content/mygov/en">Home</a>
</gui-nav-item><gui-nav-item class="mygov-header-show-lg-above hydrated" role="listitem">
<a class="active" href="/en/services"><span>Browse</span></a>
</gui-nav-item><gui-nav-item class="mygov-header-show-lg-above hydrated" role="listitem">
<a href="/en/search">
<span>Search</span>
<gui-icon name="search" library="default" class="hydrated"></gui-icon>
</a>
</gui-nav-item><div class="toast__message is-information" id="" role="alert"><i class="toast__icon"></i><button class="btn close" type="button" aria-label="Close" title="Close"></button></div>
<gui-nav-bar class="mygov-nav-bar mygov-header-show-lg-above hydrated" aria-label="Menu" role="navigation">
<div part="container" role="list"><slot></slot></div>
<gui-nav-item role="listitem" class="hydrated">
<a aria-current="false" href="/en/services/raising-kids">Raising kids</a>
</gui-nav-item><gui-nav-item role="listitem" class="hydrated">
<a aria-current="false" href="/en/services/living-arrangements">Living arrangements</a>
</gui-nav-item>Showing first 10 of 50 audited elements.
ARIA roles used must conform to valid values49 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
<gui-nav-bar class="mygov-nav-bar-header hydrated" aria-label="top level" role="navigation">
<div part="container" role="list"><slot></slot></div>
<gui-nav-item class="mygov-header-show-lg-above hydrated" role="listitem">
<a href="/content/mygov/en">Home</a>
</gui-nav-item><gui-nav-item class="mygov-header-show-lg-above hydrated" role="listitem">
<a class="active" href="/en/services"><span>Browse</span></a>
</gui-nav-item><gui-nav-item class="mygov-header-show-lg-above hydrated" role="listitem">
<a href="/en/search">
<span>Search</span>
<gui-icon name="search" library="default" class="hydrated"></gui-icon>
</a>
</gui-nav-item><gui-nav-bar class="mygov-nav-bar mygov-header-show-lg-above hydrated" aria-label="Menu" role="navigation">
<div part="container" role="list"><slot></slot></div>
<gui-nav-item role="listitem" class="hydrated">
<a aria-current="false" href="/en/services/raising-kids">Raising kids</a>
</gui-nav-item><gui-nav-item role="listitem" class="hydrated">
<a aria-current="false" href="/en/services/living-arrangements">Living arrangements</a>
</gui-nav-item><gui-nav-item role="listitem" class="hydrated">
<a aria-current="false" href="/en/services/ageing">Ageing</a>
</gui-nav-item>Showing first 10 of 49 audited elements.
ARIA tooltip nodes must have an accessible name2 elements
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
<gui-popover role="tooltip" arrow-hidden="false" popover-content-width="fit-content" exportparts="popover-content, popover-arrow, popover-trigger" type="tooltip" placement="bottom" offset="6" close-on-focus-out="" class="hydrated">
<gui-popover role="tooltip" arrow-hidden="false" popover-content-width="fit-content" exportparts="popover-content, popover-arrow, popover-trigger" type="tooltip" placement="bottom" offset="6" close-on-focus-out="" class="hydrated">
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="landing-page base-page page basicpage page-mygov-landing assistant-body" id="landing-page-61a06bc315" data-cmp-link-accessibility-enabled="" data-cmp-link-accessibility-text="opens in a new tab" data-cmp-data-layer-enabled="" data-cmp-data-layer-name="adobeDataLayer">
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 part="header"><slot></slot><div part="side-nav-trigger-button-container"><button part="side-nav-trigger-button"><span>Menu</span><gui-icon exportparts="icon: icon-menu" name="menu" library="default" class="hydrated"></gui-icon></button></div></header>
Buttons must have discernible text2 elements
Screen reader users cannot determine the purpose of buttons without an accessible name. Without a name, users don't know what action the button will perform when activated.
Audit Elements
<button type="button" id="user-banner" class="sign-in sign-in--unauth"><div class="sign-in-btn" title="Not signed in"><span>Sign in</span></div></button>
<button class="assistant-btn-dsk" data-layer="bot" aria-label="Assistant" aria-expanded="false">
Certain ARIA roles must be contained by particular parents26 elements
ARIA roles with missing required parent elements cannot function as intended for assistive technology users. Parent-child relationships convey essential hierarchy and context, like showing where an item sits within a tree structure. Without proper parents, this critical relationship information is lost.
Audit Elements
<gui-nav-item class="mygov-header-show-lg-above hydrated" role="listitem">
<a href="/content/mygov/en">Home</a>
</gui-nav-item><gui-nav-item class="mygov-header-show-lg-above hydrated" role="listitem">
<a class="active" href="/en/services"><span>Browse</span></a>
</gui-nav-item><gui-nav-item class="mygov-header-show-lg-above hydrated" role="listitem">
<a href="/en/search">
<span>Search</span>
<gui-icon name="search" library="default" class="hydrated"></gui-icon>
</a>
</gui-nav-item><gui-nav-item role="listitem" class="hydrated">
<a aria-current="false" href="/en/services/raising-kids">Raising kids</a>
</gui-nav-item><gui-nav-item role="listitem" class="hydrated">
<a aria-current="false" href="/en/services/living-arrangements">Living arrangements</a>
</gui-nav-item><gui-nav-item role="listitem" class="hydrated">
<a aria-current="false" href="/en/services/ageing">Ageing</a>
</gui-nav-item><gui-nav-item role="listitem" class="hydrated">
<a aria-current="false" href="/en/services/work">Work</a>
</gui-nav-item><gui-nav-item role="listitem" class="hydrated">
<a aria-current="false" href="/en/services/education">Education</a>
</gui-nav-item><gui-nav-item role="listitem" class="hydrated">
<a aria-current="false" href="/en/services/health-and-disability">Health and disability</a>
</gui-nav-item><gui-breadcrumb anchor-aria-current="false" data-cmp-data-layer="{"Landing-page-item-..." itemprop="itemListElement" itemscope="" itemtype="https://schema.org/L..." role="listitem" class="hydrated">Showing first 10 of 26 audited elements.
Certain ARIA roles must contain particular children5 elements
ARIA roles missing required child elements cannot perform their intended accessibility functions. Children provide essential context, like how a treeitem relates to its parent container and siblings. Without proper children, assistive technologies cannot convey this structural information to users.
Audit Elements
<div part="container" role="list"><slot></slot></div>
<div part="container" role="list"><slot></slot></div>
<div part="slot-container" role="list"><slot></slot></div>
<div part="slot-container" role="list"><slot></slot></div>
<div part="container" role="list"><slot></slot></div>
Contentinfo landmark should not be contained in another landmark1 element
The contentinfo landmark must be at the top level to help screen reader users quickly navigate to footer information. When nested inside another landmark, it becomes harder to find, defeating its purpose of providing quick access to content information.
Audit Elements
<footer style="padding-bottom: 40px;">
Deprecated ARIA roles must not be used49 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
<gui-nav-bar class="mygov-nav-bar-header hydrated" aria-label="top level" role="navigation">
<div part="container" role="list"><slot></slot></div>
<gui-nav-item class="mygov-header-show-lg-above hydrated" role="listitem">
<a href="/content/mygov/en">Home</a>
</gui-nav-item><gui-nav-item class="mygov-header-show-lg-above hydrated" role="listitem">
<a class="active" href="/en/services"><span>Browse</span></a>
</gui-nav-item><gui-nav-item class="mygov-header-show-lg-above hydrated" role="listitem">
<a href="/en/search">
<span>Search</span>
<gui-icon name="search" library="default" class="hydrated"></gui-icon>
</a>
</gui-nav-item><gui-nav-bar class="mygov-nav-bar mygov-header-show-lg-above hydrated" aria-label="Menu" role="navigation">
<div part="container" role="list"><slot></slot></div>
<gui-nav-item role="listitem" class="hydrated">
<a aria-current="false" href="/en/services/raising-kids">Raising kids</a>
</gui-nav-item><gui-nav-item role="listitem" class="hydrated">
<a aria-current="false" href="/en/services/living-arrangements">Living arrangements</a>
</gui-nav-item><gui-nav-item role="listitem" class="hydrated">
<a aria-current="false" href="/en/services/ageing">Ageing</a>
</gui-nav-item>Showing first 10 of 49 audited elements.
Document should have one main landmark1 element
Every page should have exactly one main landmark that identifies the primary content. Without a main landmark, screen reader users must navigate through all content linearly to find what they're looking for, making page navigation difficult and time-consuming.
Audit Elements
<html lang="en">
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 part="header"><slot></slot><div part="side-nav-trigger-button-container"><button part="side-nav-trigger-button"><span>Menu</span><gui-icon exportparts="icon: icon-menu" name="menu" library="default" class="hydrated"></gui-icon></button></div></header>
Document should not have more than one contentinfo landmark1 element
Multiple contentinfo landmarks force screen reader users to sort through extra options to find footer information. Each page should have only one content info landmark to enable quick, predictable navigation without overwhelming users with duplicate structural markers.
Audit Elements
<footer style="padding-bottom: 40px;">
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 id="main" class="cmp-container root responsivegrid" role="main" data-section="content">
Documents must have <title> element to aid in navigation1 element
The page title is the first thing screen reader users hear when loading a page. Without a descriptive, unique title, users must read through the entire page to understand its contents and purpose, wasting valuable time on every page visit.
Audit Elements
<html lang="en">
Elements marked as presentational should be consistently ignored2 elements
Elements with role="none" or role="presentation" should be removed from the accessibility tree. Adding global ARIA attributes or making these elements focusable prevents their removal, leaving them accessible to screen readers when they should be ignored, creating unexpected and confusing behavior.
Audit Elements
<img src="/en/services/raising..." srcset="/en/services/raising..." loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="1920" height="1080" alt="" title="Mother and toddler">
<img src="/en/services/ageing/..." srcset="/en/services/ageing/..." loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="1920" height="1080" alt="" title="Woman and man using ...">
Elements must meet minimum color contrast ratio thresholds47 elements
People with low vision or color blindness cannot read text that lacks sufficient contrast with its background. With nearly three times more people having low vision than total blindness, and 8% of men and 0.4% of women having color deficiencies, adequate contrast is essential for making text readable to millions of users.
Audit Elements
<a href="/content/mygov/en">Home</a>
<span>Browse</span>
<span>Search</span>
<span>Sign in</span>
<a href="/en/create-account">Create account</a>
<a href="/en/about/help">Help</a>
<a aria-current="false" href="/en/services/raising-kids">Raising kids</a>
<a aria-current="false" href="/en/services/living-arrangements">Living arrangements</a>
<a aria-current="false" href="/en/services/ageing">Ageing</a>
<a aria-current="false" href="/en/services/work">Work</a>
Showing first 10 of 47 audited elements.
Elements must only use permitted ARIA attributes19 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
<gui-nav-bar class="mygov-nav-bar-header hydrated" aria-label="top level" role="navigation">
<div class="login-container" aria-expanded="false"><button type="button" id="user-banner" class="sign-in sign-in--unauth"><div class="sign-in-btn" title="Not signed in"><span>Sign in</span></div></button></div>
<gui-nav-bar class="mygov-nav-bar mygov-header-show-lg-above hydrated" aria-label="Menu" role="navigation">
<a aria-current="false" href="/en/services/raising-kids">Raising kids</a>
<a aria-current="false" href="/en/services/living-arrangements">Living arrangements</a>
<a aria-current="false" href="/en/services/ageing">Ageing</a>
<a aria-current="false" href="/en/services/work">Work</a>
<a aria-current="false" href="/en/services/education">Education</a>
<a aria-current="false" href="/en/services/health-and-disability">Health and disability</a>
<div class="assistant-panel-closed" role="region" aria-label="Digital Assistant" aria-expanded="false">
Showing first 10 of 19 audited elements.
Elements must only use supported ARIA attributes18 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
<gui-nav-bar class="mygov-nav-bar-header hydrated" aria-label="top level" role="navigation">
<gui-nav-bar class="mygov-nav-bar mygov-header-show-lg-above hydrated" aria-label="Menu" role="navigation">
<a aria-current="false" href="/en/services/raising-kids">Raising kids</a>
<a aria-current="false" href="/en/services/living-arrangements">Living arrangements</a>
<a aria-current="false" href="/en/services/ageing">Ageing</a>
<a aria-current="false" href="/en/services/work">Work</a>
<a aria-current="false" href="/en/services/education">Education</a>
<a aria-current="false" href="/en/services/health-and-disability">Health and disability</a>
<div class="assistant-panel-closed" role="region" aria-label="Digital Assistant" aria-expanded="false">
<button class="assistant-btn-dsk" data-layer="bot" aria-label="Assistant" aria-expanded="false">
Showing first 10 of 18 audited elements.
Heading levels should only increase by one10 elements
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Audit Elements
<h1 class="cmp-title__text">Find government payments and services</h1>
<h2 part="heading">Raising kids</h2>
<h2 part="heading">Living arrangements</h2>
<h2 part="heading">Ageing</h2>
<h2 part="heading">Work</h2>
<h2 part="heading">Education</h2>
<h2 part="heading">Health and disability</h2>
<h3 part="heading-text">About this site</h3>
<h3 part="heading-text">Browse</h3>
<h3 part="heading">Follow us</h3>
Headings should not be empty10 elements
Screen readers announce headings to help users navigate page structure. Empty headings confuse users and prevent them from understanding the page's organization. Headings should only be used to convey structure, not for visual styling, and must contain accessible text that screen readers can announce.
Audit Elements
<h1 class="cmp-title__text">Find government payments and services</h1>
<h2 part="heading">Raising kids</h2>
<h2 part="heading">Living arrangements</h2>
<h2 part="heading">Ageing</h2>
<h2 part="heading">Work</h2>
<h2 part="heading">Education</h2>
<h2 part="heading">Health and disability</h2>
<h3 part="heading-text">About this site</h3>
<h3 part="heading-text">Browse</h3>
<h3 part="heading">Follow us</h3>
Images must have alternative text7 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 class="mygov-header-show-lg-above" src="/content/dam/mygov/public/images/brand/myGov-logo-cobranded-black.svg" alt="Australian Government and myGov logo">
<img src="/en/services/raising..." srcset="/en/services/raising..." loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="1920" height="1080" alt="" title="Mother and toddler">
<img src="/en/services/living-..." srcset="/en/services/living-..." loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="800" height="533" alt="Person contemplating..." title="Living arrangements ...">
<img src="/en/services/ageing/..." srcset="/en/services/ageing/..." loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="1920" height="1080" alt="" title="Woman and man using ...">
<img src="/en/services/work/_j..." srcset="/en/services/work/_j..." loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="800" height="533" alt="A young person with ..." title="Work category">
<img src="/en/services/educati..." srcset="/en/services/educati..." loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="800" height="533" alt="Three young children..." title="Education category">
<img src="/en/services/health-..." srcset="/en/services/health-..." loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="800" height="533" alt="A young person in a ..." title="Health and disabilit...">
Inline text spacing must be adjustable with custom stylesheets3 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
<footer style="padding-bottom: 40px;">
<div part="heading" style="display: block;"><slot name="heading"><h3 part="heading-text">About this site</h3></slot></div>
<div part="heading" style="display: block;"><slot name="heading"><h3 part="heading-text">Browse</h3></slot></div>
Interactive controls must not be nested8 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
<img class="mygov-header-show-lg-above" src="/content/dam/mygov/public/images/brand/myGov-logo-cobranded-black.svg" alt="Australian Government and myGov logo">
<button type="button" id="user-banner" class="sign-in sign-in--unauth"><div class="sign-in-btn" title="Not signed in"><span>Sign in</span></div></button>
<button class="assistant-btn-dsk" data-layer="bot" aria-label="Assistant" aria-expanded="false">
<img src="/en/services/living-..." srcset="/en/services/living-..." loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="800" height="533" alt="Person contemplating..." title="Living arrangements ...">
<img src="/en/services/work/_j..." srcset="/en/services/work/_j..." loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="800" height="533" alt="A young person with ..." title="Work category">
<img src="/en/services/educati..." srcset="/en/services/educati..." loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="800" height="533" alt="Three young children..." title="Education category">
<img src="/en/services/health-..." srcset="/en/services/health-..." loading="lazy" class="cmp-image__image" itemprop="contentUrl" width="800" height="533" alt="A young person in a ..." title="Health and disabilit...">
<svg xmlns="http://www.w3.org/2000/svg" data-name="Layer 1" viewBox="0 0 350.86 76.18" height="100%" width="100%" display="block" fill="currentColor" part="icon" role="img">
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination11 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 part="header"><slot></slot><div part="side-nav-trigger-button-container"><button part="side-nav-trigger-button"><span>Menu</span><gui-icon exportparts="icon: icon-menu" name="menu" library="default" class="hydrated"></gui-icon></button></div></header>
<gui-nav-bar class="mygov-nav-bar-header hydrated" aria-label="top level" role="navigation">
<gui-nav-bar class="mygov-nav-bar mygov-header-show-lg-above hydrated" aria-label="Menu" role="navigation">
<main id="main" class="cmp-container root responsivegrid" role="main" data-section="content">
<div class="assistant-panel-closed" role="region" aria-label="Digital Assistant" aria-expanded="false">
<gui-breadcrumbs id="Landing-page" class="mygov-breadcrumbs-re..." aria-label="Breadcrumb" data-cmp-data-layer="{"Landing-page":{"@t..." itemscope="" itemtype="http://schema.org/Br..." role="navigation"><footer style="padding-bottom: 40px;">
<gui-nav-list class="mygov-nav-list-support-links hydrated" aria-label="About this site" heading-text="About this site" responsive-breakpoint="47.99875em" role="navigation" density="default">
<gui-nav-list class="mygov-nav-list-support-links hydrated" aria-label="Browse" heading-text="Browse" responsive-breakpoint="47.99875em" role="navigation" density="default">
<gui-nav-bar aria-label="support links" class="mygov-nav-bar-support-links hydrated" role="navigation">
Showing first 10 of 11 audited elements.
Links must have discernible text39 elements
Keyboard users and screen reader users can only interact with links that have accessible names and can receive focus. Without proper names, users don't know where links lead. Without keyboard focus, users who cannot use a mouse cannot activate the links at all.
Audit Elements
<a class="cmp-page__skiptomaincontent-link" href="#main">Skip to main content</a>
<a class="mygov-header-logo" href="/en">
<a href="/content/mygov/en">Home</a>
<a class="active" href="/en/services"><span>Browse</span></a>
<a href="/en/search">
<span>Search</span>
<gui-icon name="search" library="default" class="hydrated"></gui-icon>
</a><a href="/en/create-account">Create account</a>
<a href="/en/about/help">Help</a>
<a aria-current="false" href="/en/services/raising-kids">Raising kids</a>
<a aria-current="false" href="/en/services/living-arrangements">Living arrangements</a>
<a aria-current="false" href="/en/services/ageing">Ageing</a>
Showing first 10 of 39 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 id="main" class="cmp-container root responsivegrid" role="main" data-section="content">
Page must have means to bypass repeated blocks1 element
Keyboard-only users must tab through all navigation and header content before reaching the main content, which can take several minutes and cause physical pain for users with motor limitations. Bypass mechanisms like skip links allow these users to jump directly to main content, saving time and reducing fatigue.
Audit Elements
<html lang="en">
Page should contain a level-one heading1 element
Screen reader users use keyboard shortcuts to jump directly to the first h1, expecting to land at the main content. Without an h1 or with a misplaced one, users must listen to more of the page to understand its structure, wasting valuable time on every page visit.
Audit Elements
<html lang="en">
Required ARIA attributes must be provided49 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
<gui-nav-bar class="mygov-nav-bar-header hydrated" aria-label="top level" role="navigation">
<div part="container" role="list"><slot></slot></div>
<gui-nav-item class="mygov-header-show-lg-above hydrated" role="listitem">
<a href="/content/mygov/en">Home</a>
</gui-nav-item><gui-nav-item class="mygov-header-show-lg-above hydrated" role="listitem">
<a class="active" href="/en/services"><span>Browse</span></a>
</gui-nav-item><gui-nav-item class="mygov-header-show-lg-above hydrated" role="listitem">
<a href="/en/search">
<span>Search</span>
<gui-icon name="search" library="default" class="hydrated"></gui-icon>
</a>
</gui-nav-item><gui-nav-bar class="mygov-nav-bar mygov-header-show-lg-above hydrated" aria-label="Menu" role="navigation">
<div part="container" role="list"><slot></slot></div>
<gui-nav-item role="listitem" class="hydrated">
<a aria-current="false" href="/en/services/raising-kids">Raising kids</a>
</gui-nav-item><gui-nav-item role="listitem" class="hydrated">
<a aria-current="false" href="/en/services/living-arrangements">Living arrangements</a>
</gui-nav-item><gui-nav-item role="listitem" class="hydrated">
<a aria-current="false" href="/en/services/ageing">Ageing</a>
</gui-nav-item>Showing first 10 of 49 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
<html lang="en">
The skip-link target should exist and be focusable1 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 class="cmp-page__skiptomaincontent-link" href="#main">Skip to main content</a>
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, user-scalable=0">