LinkedInlinkedin.com
Accessibility Score
Issues Found
Issues Found
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">
<li> elements must be contained in a <ul> or <ol>92 elements
Lists require proper semantic hierarchy with ul or ol parent elements and li child elements. This structure allows screen readers to announce when users enter a list, how many items it contains, and which item they're currently on, providing essential context for understanding the content.
Audit Elements
<li class="">
<li class="">
<li class="">
<li class="">
<li class="">
<li class="explore-top-content__pill">
<li class="explore-top-content__pill">
<li class="explore-top-content__pill">
<li class="explore-top-content__pill">
<li class="explore-top-content__pill">
Showing first 10 of 92 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements12 elements
Lists must contain only li elements as direct children (besides non-content elements like script or style). When other content elements appear within ul or ol tags, screen readers cannot properly inform users they're listening to list items, breaking the expected list navigation experience.
Audit Elements
<ul class="top-nav-menu flex items-center babybear:w-full babybear:justify-between babybear:pt-1 justify-start w-max pt-0 overflow-x-auto
after:papamamabear:up-down-divider after:papamamabear:!h-[37px]
nav__menu babybear:order-last order-3 ml-auto"><ul class="show-more-less__list show-more-less__list--no-hidden-elems etta-show-more-less" data-impression-id="homepage-basic_explore-top-content_pill-list-module_etta-show-more-less_show-more-less">
<ul data-max-num-to-show="10" class="show-more-less__list show-more-less__list--hide-after-10" data-impression-id="homepage-basic_pill-list-module_etta-show-more-less_show-more-less">
<ul class="show-more-less__list show-more-less__list--no-hidden-elems etta-show-more-less" data-impression-id="homepage-basic_discover_products_pill-list-module_etta-show-more-less_show-more-less">
<ul class="show-more-less__list show-more-less__list--no-hidden-elems etta-show-more-less" data-impression-id="homepage-basic_discover_games_pill-list-module_etta-show-more-less_show-more-less">
<ul class="slide-list__list items-stretch flex list-none transition-all duration-slow ease-standard " style="transform: translate3d(0px, 0px, 0px);">
<ul>
<ul>
<ul>
<ul>
Showing first 10 of 12 audited elements.
All page content should be contained by landmarks322 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
<a href="#main-content" class="skip-link btn-md btn-primary absolute z-11 -top-[100vh] focus:top-0">
Skip to main content
</a><div class="guest-upsells">
<form class="google-auth base-google-auth" action="https://www.linkedin.com/uas/login-submit" method="post">
<form class="microsoft-auth" action="https://www.linkedin.com/uas/login-submit" method="post">
<div class="sticky top-0 z-[900] bg-white">
<nav class="nav pt-1.5 pb-2 flex items-center justify-between relative flex-nowrap babymamabear:py-1.5
babybear:flex-wrap " aria-label="Primary"><a href="/?trk=guest_homepage..." class="nav__logo-link link-..." data-tracking-contro...="guest_homepage-basic..." data-tracking-will-n...="">
<span class="sr-only">LinkedIn</span>
<icon class="block text-color-brand w-[102px] h-[26px] babybear:hidden order-1" data-test-id="nav-logo"></icon>
<ul class="top-nav-menu flex items-center babybear:w-full babybear:justify-between babybear:pt-1 justify-start w-max pt-0 overflow-x-auto
after:papamamabear:up-down-divider after:papamamabear:!h-[37px]
nav__menu babybear:order-last order-3 ml-auto">Showing first 10 of 322 audited elements.
Alternative text of images should not be repeated as text5 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="flip-rtl block -z-1 relative flex-shrink babybear:static w-[700px] h-[560px] babybear:w-[374px] babybear:h-[214px]" alt="Welcome to your professional community" data-test-id="hero__illustration" src="https://static.licdn.com/aero-v1/sc/h/dxf91zhqd2z6b0bwg85ktm5s4">
<img class="w-[450px] rounded-[50%] mamabear:max-w-[50vw] babybear:h-[300px] babybear:w-[300px] babybear:mt-2 babybear:mx-auto" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/dbvmk0tsk0o0hd59fi64z3own" alt="">
<img class="flex-shrink-0 xs:mr-[72px] mb-2 h-32 w-32" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/43h6n82li4xu0q23s8jqizk6j" alt="">
<img class="flex-shrink-0 xs:mr-[72px] mb-2 h-32 w-32" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/1dhh8rr3wohexkaya6jhn2y8j" alt="">
<img class="h-[840px] self-center ml-12 flip-rtl babybear:hidden" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/292yd0en6qdvkbezeuj71yu4y" alt="Who is LinkedIn for?">
ARIA attributes must be used as specified for the element's role10 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
<nav class="nav pt-1.5 pb-2 flex items-center justify-between relative flex-nowrap babymamabear:py-1.5
babybear:flex-wrap " aria-label="Primary"><div class="google-auth-button__placeholder mx-auto
" data-theme="filled_blue" data-logo-alignment="center" data-locale="en_US" role="button" aria-label="Continue with google" data-safe-to-skip-tnc-redirect=""></div><a class="btn-md babybear:btn-sm mb-1.5 mr-1 flex items-center w-fit float-left btn-secondary-emphasis" data-tracking-control-name="homepage-basic_explore--top-content_topic-pill" data-tracking-will-navigate="" href="https://www.linkedin.com/top-content/" aria-label="Show all top content">
<button class="show-more-less__button show-more-less__more-button show-more-less-button
" aria-expanded="false" data-tracking-control-name="homepage-basic_pill-list-module_etta-show-more-less_show_more"><a class="btn-md babybear:btn-..." data-tracking-contro...="homepage-basic_top-p..." data-tracking-will-n...="" href="https://www.linkedin..." aria-label="Show all softwares a...">
<div class="relative overflow-hidden slide-list__container " aria-live="polite" tabindex="0">
<button data-tracking-control-name="homepage-basic_testimonials_slide_list_next_button" class="slide-list__nav-button rounded-xl px-1.5 py-1 btn-overlay cursor-pointer disabled:hidden" aria-label="Next Slide" data-direction="next">
<button class="dropdown-to-modal__b..." aria-expanded="false" data-tracking-contro...="homepage-basic_learn...">
<a class="btn-md babybear:btn-sm mb-1.5 mr-1 flex items-center w-fit float-left btn-primary" data-tracking-control-name="homepage-basic_join-cta" data-tracking-will-navigate="" href="https://www.linkedin.com/signup?trk=homepage-basic_join-cta" aria-describedby="bottom-cta-section__header">
<button class="language-selector__b..." aria-expanded="false" data-tracking-contro...="footer-lang-dropdown...">
ARIA attributes must conform to valid names10 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
<nav class="nav pt-1.5 pb-2 flex items-center justify-between relative flex-nowrap babymamabear:py-1.5
babybear:flex-wrap " aria-label="Primary"><div class="google-auth-button__placeholder mx-auto
" data-theme="filled_blue" data-logo-alignment="center" data-locale="en_US" role="button" aria-label="Continue with google" data-safe-to-skip-tnc-redirect=""></div><a class="btn-md babybear:btn-sm mb-1.5 mr-1 flex items-center w-fit float-left btn-secondary-emphasis" data-tracking-control-name="homepage-basic_explore--top-content_topic-pill" data-tracking-will-navigate="" href="https://www.linkedin.com/top-content/" aria-label="Show all top content">
<button class="show-more-less__button show-more-less__more-button show-more-less-button
" aria-expanded="false" data-tracking-control-name="homepage-basic_pill-list-module_etta-show-more-less_show_more"><a class="btn-md babybear:btn-..." data-tracking-contro...="homepage-basic_top-p..." data-tracking-will-n...="" href="https://www.linkedin..." aria-label="Show all softwares a...">
<div class="relative overflow-hidden slide-list__container " aria-live="polite" tabindex="0">
<button data-tracking-control-name="homepage-basic_testimonials_slide_list_next_button" class="slide-list__nav-button rounded-xl px-1.5 py-1 btn-overlay cursor-pointer disabled:hidden" aria-label="Next Slide" data-direction="next">
<button class="dropdown-to-modal__b..." aria-expanded="false" data-tracking-contro...="homepage-basic_learn...">
<a class="btn-md babybear:btn-sm mb-1.5 mr-1 flex items-center w-fit float-left btn-primary" data-tracking-control-name="homepage-basic_join-cta" data-tracking-will-navigate="" href="https://www.linkedin.com/signup?trk=homepage-basic_join-cta" aria-describedby="bottom-cta-section__header">
<button class="language-selector__b..." aria-expanded="false" data-tracking-contro...="footer-lang-dropdown...">
ARIA attributes must conform to valid values10 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
<nav class="nav pt-1.5 pb-2 flex items-center justify-between relative flex-nowrap babymamabear:py-1.5
babybear:flex-wrap " aria-label="Primary"><div class="google-auth-button__placeholder mx-auto
" data-theme="filled_blue" data-logo-alignment="center" data-locale="en_US" role="button" aria-label="Continue with google" data-safe-to-skip-tnc-redirect=""></div><a class="btn-md babybear:btn-sm mb-1.5 mr-1 flex items-center w-fit float-left btn-secondary-emphasis" data-tracking-control-name="homepage-basic_explore--top-content_topic-pill" data-tracking-will-navigate="" href="https://www.linkedin.com/top-content/" aria-label="Show all top content">
<button class="show-more-less__button show-more-less__more-button show-more-less-button
" aria-expanded="false" data-tracking-control-name="homepage-basic_pill-list-module_etta-show-more-less_show_more"><a class="btn-md babybear:btn-..." data-tracking-contro...="homepage-basic_top-p..." data-tracking-will-n...="" href="https://www.linkedin..." aria-label="Show all softwares a...">
<div class="relative overflow-hidden slide-list__container " aria-live="polite" tabindex="0">
<button data-tracking-control-name="homepage-basic_testimonials_slide_list_next_button" class="slide-list__nav-button rounded-xl px-1.5 py-1 btn-overlay cursor-pointer disabled:hidden" aria-label="Next Slide" data-direction="next">
<button class="dropdown-to-modal__b..." aria-expanded="false" data-tracking-contro...="homepage-basic_learn...">
<a class="btn-md babybear:btn-sm mb-1.5 mr-1 flex items-center w-fit float-left btn-primary" data-tracking-control-name="homepage-basic_join-cta" data-tracking-will-navigate="" href="https://www.linkedin.com/signup?trk=homepage-basic_join-cta" aria-describedby="bottom-cta-section__header">
<button class="language-selector__b..." aria-expanded="false" data-tracking-contro...="footer-lang-dropdown...">
ARIA commands must have an accessible name1 element
Screen reader users cannot determine the purpose of interactive elements with role="link", role="button", or role="menuitem" that lack an accessible name. Without a name, these controls are essentially invisible to assistive technology users.
Audit Elements
<div class="google-auth-button__placeholder mx-auto
" data-theme="filled_blue" data-logo-alignment="center" data-locale="en_US" role="button" aria-label="Continue with google" data-safe-to-skip-tnc-redirect=""></div>ARIA hidden element must not be focusable or contain focusable elements6 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
<li class="flex justify-between relative items-center mr-12 w-full babybear:flex babybear:flex-wrap-reverse babybear:mr-2" data-test-id="testimonial" aria-hidden="true">
<li class="flex justify-between relative items-center mr-12 w-full babybear:flex babybear:flex-wrap-reverse babybear:mr-2" data-test-id="testimonial" aria-hidden="true">
<icon aria-hidden="true" class="w-3 h-3 ml-1" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/7asbl4deqijhoy3z2ivveispv"></icon>
<icon aria-hidden="true" class="ml-2 flip-rtl" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/3l4csbmaa6sv4gtsledhbu9lq"></icon>
<icon aria-hidden="true" class="ml-2 flip-rtl" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/3l4csbmaa6sv4gtsledhbu9lq"></icon>
<icon aria-hidden="true" class="ml-2 flip-rtl" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/3l4csbmaa6sv4gtsledhbu9lq"></icon>
ARIA role should be appropriate for the element115 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
<main class="flex flex-col items-center overflow-hidden min-h-[calc(100vh-76px-50px)]" role="main" id="main-content">
<div class="google-auth-button__placeholder mx-auto
" data-theme="filled_blue" data-logo-alignment="center" data-locale="en_US" role="button" aria-label="Continue with google" data-safe-to-skip-tnc-redirect=""></div><div class="previous-slide-list__a11y-notification sr-only hidden" role="alert">
No more previous content
</div><div class="next-slide-list__a11y-notification sr-only hidden" role="alert">
No more next content
</div><li aria-label="Artificial Intelligence for Business 1,040+ course" class="mt-2 mr-1 mb-0 ml-2" role="menuitem">
<li aria-label="Business Analysis and Strategy 2,030+ courses" class="mt-2 mr-1 mb-0 ml-2" role="menuitem">
<li aria-label="Business Software and Tools 3,480+ courses" class="mt-2 mr-1 mb-0 ml-2" role="menuitem">
<li aria-label="Career Development 720+ courses" class="mt-2 mr-1 mb-0 ml-2" role="menuitem">
<li aria-label="Customer Service 320+ courses" class="mt-2 mr-1 mb-0 ml-2" role="menuitem">
<li aria-label="Diversity, Equity, and Inclusion (DEI) 340+ courses" class="mt-2 mr-1 mb-0 ml-2" role="menuitem">
Showing first 10 of 115 audited elements.
ARIA roles used must conform to valid values2 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
<main class="flex flex-col items-center overflow-hidden min-h-[calc(100vh-76px-50px)]" role="main" id="main-content">
<div class="google-auth-button__placeholder mx-auto
" data-theme="filled_blue" data-logo-alignment="center" data-locale="en_US" role="button" aria-label="Continue with google" data-safe-to-skip-tnc-redirect=""></div>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 dir="ltr">
Buttons must have discernible text4 elements
Screen reader users cannot determine the purpose of buttons without an accessible name. Without a name, users don't know what action the button will perform when activated.
Audit Elements
<button class="show-more-less__button show-more-less__more-button show-more-less-button
" aria-expanded="false" data-tracking-control-name="homepage-basic_pill-list-module_etta-show-more-less_show_more"><button data-tracking-control-name="homepage-basic_testimonials_slide_list_next_button" class="slide-list__nav-button rounded-xl px-1.5 py-1 btn-overlay cursor-pointer disabled:hidden" aria-label="Next Slide" data-direction="next">
<button class="dropdown-to-modal__b..." aria-expanded="false" data-tracking-contro...="homepage-basic_learn...">
<button class="language-selector__b..." aria-expanded="false" data-tracking-contro...="footer-lang-dropdown...">
Contentinfo landmark should not be contained in another landmark1 element
The contentinfo landmark must be at the top level to help screen reader users quickly navigate to footer information. When nested inside another landmark, it becomes harder to find, defeating its purpose of providing quick access to content information.
Audit Elements
<footer class="li-footer bg-transparent w-full ">
Deprecated ARIA roles must not be used2 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
<main class="flex flex-col items-center overflow-hidden min-h-[calc(100vh-76px-50px)]" role="main" id="main-content">
<div class="google-auth-button__placeholder mx-auto
" data-theme="filled_blue" data-logo-alignment="center" data-locale="en_US" role="button" aria-label="Continue with google" data-safe-to-skip-tnc-redirect=""></div>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 class="slide-list__header mb-1.5"> <!----> </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 class="li-footer bg-transparent w-full ">
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 class="flex flex-col items-center overflow-hidden min-h-[calc(100vh-76px-50px)]" role="main" id="main-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 ignored3 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 class="w-[450px] rounded-[50%] mamabear:max-w-[50vw] babybear:h-[300px] babybear:w-[300px] babybear:mt-2 babybear:mx-auto" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/dbvmk0tsk0o0hd59fi64z3own" alt="">
<img class="flex-shrink-0 xs:mr-[72px] mb-2 h-32 w-32" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/43h6n82li4xu0q23s8jqizk6j" alt="">
<img class="flex-shrink-0 xs:mr-[72px] mb-2 h-32 w-32" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/1dhh8rr3wohexkaya6jhn2y8j" alt="">
Elements must meet minimum color contrast ratio thresholds64 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
<span class="top-nav-link__label-text font-sans text-xs leading-regular text-center
font-regular whitespace-nowrap">
Top Content
</span><span class="top-nav-link__label-text font-sans text-xs leading-regular text-center
font-regular whitespace-nowrap">
People
</span><span class="top-nav-link__label-text font-sans text-xs leading-regular text-center
font-regular whitespace-nowrap">
Learning
</span><span class="top-nav-link__label-text font-sans text-xs leading-regular text-center
font-regular whitespace-nowrap">
Jobs
</span><span class="top-nav-link__label-text font-sans text-xs leading-regular text-center
font-regular whitespace-nowrap">
Games
</span><a class="nav__button-secondary btn-secondary-emphasis ml-3 btn-md" href="https://www.linkedin.com/login?fromSignIn=true&trk=guest_homepage-basic_nav-header-signin" data-tracking-control-name="guest_homepage-basic_nav-header-signin" data-tracking-will-navigate="" data-tracking-client-ingraph="">
<a class="nav__button-tertiary btn-primary btn-md" href="https://www.linkedin.com/signup?trk=guest_homepage-basic_nav-header-join" data-tracking-control-name="guest_homepage-basic_nav-header-join" data-test-live-nav-primary-cta="" data-tracking-will-navigate="" data-tracking-client-ingraph="">
<h1 class="font-sans babybear:pb-3 font-regular leading-regular text-display-lg text-color-text babybear:text-display-md babybear:text-center" data-test-id="hero__headline">
Welcome to your professional community
</h1><a class="sign-in-form__sign-i..." href="https://www.linkedin..." data-test-id="home-hero-sign-in-ct..." data-tracking-contro...="homepage-basic_home-..." data-tracking-will-n...="" data-tracking-client...="">
<p class="linkedin-tc__text text-color-text-low-emphasis text-xs pb-2 text-center mt-3" data-impression-id="linkedin-tc__button-skip-tc-text">
Showing first 10 of 64 audited elements.
Elements must only use permitted ARIA attributes10 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
<nav class="nav pt-1.5 pb-2 flex items-center justify-between relative flex-nowrap babymamabear:py-1.5
babybear:flex-wrap " aria-label="Primary"><div class="google-auth-button__placeholder mx-auto
" data-theme="filled_blue" data-logo-alignment="center" data-locale="en_US" role="button" aria-label="Continue with google" data-safe-to-skip-tnc-redirect=""></div><a class="btn-md babybear:btn-sm mb-1.5 mr-1 flex items-center w-fit float-left btn-secondary-emphasis" data-tracking-control-name="homepage-basic_explore--top-content_topic-pill" data-tracking-will-navigate="" href="https://www.linkedin.com/top-content/" aria-label="Show all top content">
<button class="show-more-less__button show-more-less__more-button show-more-less-button
" aria-expanded="false" data-tracking-control-name="homepage-basic_pill-list-module_etta-show-more-less_show_more"><a class="btn-md babybear:btn-..." data-tracking-contro...="homepage-basic_top-p..." data-tracking-will-n...="" href="https://www.linkedin..." aria-label="Show all softwares a...">
<div class="relative overflow-hidden slide-list__container " aria-live="polite" tabindex="0">
<button data-tracking-control-name="homepage-basic_testimonials_slide_list_next_button" class="slide-list__nav-button rounded-xl px-1.5 py-1 btn-overlay cursor-pointer disabled:hidden" aria-label="Next Slide" data-direction="next">
<button class="dropdown-to-modal__b..." aria-expanded="false" data-tracking-contro...="homepage-basic_learn...">
<a class="btn-md babybear:btn-sm mb-1.5 mr-1 flex items-center w-fit float-left btn-primary" data-tracking-control-name="homepage-basic_join-cta" data-tracking-will-navigate="" href="https://www.linkedin.com/signup?trk=homepage-basic_join-cta" aria-describedby="bottom-cta-section__header">
<button class="language-selector__b..." aria-expanded="false" data-tracking-contro...="footer-lang-dropdown...">
Elements must only use supported ARIA attributes10 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
<nav class="nav pt-1.5 pb-2 flex items-center justify-between relative flex-nowrap babymamabear:py-1.5
babybear:flex-wrap " aria-label="Primary"><div class="google-auth-button__placeholder mx-auto
" data-theme="filled_blue" data-logo-alignment="center" data-locale="en_US" role="button" aria-label="Continue with google" data-safe-to-skip-tnc-redirect=""></div><a class="btn-md babybear:btn-sm mb-1.5 mr-1 flex items-center w-fit float-left btn-secondary-emphasis" data-tracking-control-name="homepage-basic_explore--top-content_topic-pill" data-tracking-will-navigate="" href="https://www.linkedin.com/top-content/" aria-label="Show all top content">
<button class="show-more-less__button show-more-less__more-button show-more-less-button
" aria-expanded="false" data-tracking-control-name="homepage-basic_pill-list-module_etta-show-more-less_show_more"><a class="btn-md babybear:btn-..." data-tracking-contro...="homepage-basic_top-p..." data-tracking-will-n...="" href="https://www.linkedin..." aria-label="Show all softwares a...">
<div class="relative overflow-hidden slide-list__container " aria-live="polite" tabindex="0">
<button data-tracking-control-name="homepage-basic_testimonials_slide_list_next_button" class="slide-list__nav-button rounded-xl px-1.5 py-1 btn-overlay cursor-pointer disabled:hidden" aria-label="Next Slide" data-direction="next">
<button class="dropdown-to-modal__b..." aria-expanded="false" data-tracking-contro...="homepage-basic_learn...">
<a class="btn-md babybear:btn-sm mb-1.5 mr-1 flex items-center w-fit float-left btn-primary" data-tracking-control-name="homepage-basic_join-cta" data-tracking-will-navigate="" href="https://www.linkedin.com/signup?trk=homepage-basic_join-cta" aria-describedby="bottom-cta-section__header">
<button class="language-selector__b..." aria-expanded="false" data-tracking-contro...="footer-lang-dropdown...">
Elements should not have tabindex greater than zero1 element
Using tabindex values greater than 0 creates unexpected tab orders that disorient users. It makes elements appear to be skipped when users tab past them, requires setting tabindex on every element to maintain order, and forces all tabindex items to be visited before any normal elements, breaking natural navigation flow.
Audit Elements
<div class="relative overflow-hidden slide-list__container " aria-live="polite" tabindex="0">
Heading levels should only increase by one15 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="font-sans babybear:pb-3 font-regular leading-regular text-display-lg text-color-text babybear:text-display-md babybear:text-center" data-test-id="hero__headline">
Welcome to your professional community
</h1><h2 class="header">
Explore top LinkedIn content
</h2><h2 class="header">
Find the right job or internship for you
</h2><h2 class="header !text-warm-red-70 text-center pb-4 babybear:mb-3">
Post your job for millions of people to see
</h2><h2 class="header">
Discover the best software tools
</h2><h2 class="header">
Keep your mind sharp with games
</h2><h2 class="header !text-warm-red-70">
Let the right people know you’re open to work
</h2><h2 class="header">
Connect with people who can help
</h2><h2 class="header">
Learn the skills you need to succeed
</h2><h2 class="header !text-warm-red-70 mb-1">
Who is LinkedIn for?
</h2>Showing first 10 of 15 audited elements.
Headings should not be empty15 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="font-sans babybear:pb-3 font-regular leading-regular text-display-lg text-color-text babybear:text-display-md babybear:text-center" data-test-id="hero__headline">
Welcome to your professional community
</h1><h2 class="header">
Explore top LinkedIn content
</h2><h2 class="header">
Find the right job or internship for you
</h2><h2 class="header !text-warm-red-70 text-center pb-4 babybear:mb-3">
Post your job for millions of people to see
</h2><h2 class="header">
Discover the best software tools
</h2><h2 class="header">
Keep your mind sharp with games
</h2><h2 class="header !text-warm-red-70">
Let the right people know you’re open to work
</h2><h2 class="header">
Connect with people who can help
</h2><h2 class="header">
Learn the skills you need to succeed
</h2><h2 class="header !text-warm-red-70 mb-1">
Who is LinkedIn for?
</h2>Showing first 10 of 15 audited elements.
IDs used in ARIA and labels must be unique1 element
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
<h2 class="header papabear:!text-display-lg mt-6 mb-2 keep-all babybear:mt-0 babybear:mb-3" id="bottom-cta-section__header">
Join your colleagues, classmates, and friends on LinkedIn
</h2>Images must have alternative text5 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="flip-rtl block -z-1 relative flex-shrink babybear:static w-[700px] h-[560px] babybear:w-[374px] babybear:h-[214px]" alt="Welcome to your professional community" data-test-id="hero__illustration" src="https://static.licdn.com/aero-v1/sc/h/dxf91zhqd2z6b0bwg85ktm5s4">
<img class="w-[450px] rounded-[50%] mamabear:max-w-[50vw] babybear:h-[300px] babybear:w-[300px] babybear:mt-2 babybear:mx-auto" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/dbvmk0tsk0o0hd59fi64z3own" alt="">
<img class="flex-shrink-0 xs:mr-[72px] mb-2 h-32 w-32" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/43h6n82li4xu0q23s8jqizk6j" alt="">
<img class="flex-shrink-0 xs:mr-[72px] mb-2 h-32 w-32" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/1dhh8rr3wohexkaya6jhn2y8j" alt="">
<img class="h-[840px] self-center ml-12 flip-rtl babybear:hidden" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/292yd0en6qdvkbezeuj71yu4y" alt="Who is LinkedIn for?">
Inline text spacing must be adjustable with custom stylesheets1 element
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
<ul class="slide-list__list items-stretch flex list-none transition-all duration-slow ease-standard " style="transform: translate3d(0px, 0px, 0px);">
Interactive controls must not be nested7 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
<div class="google-auth-button__placeholder mx-auto
" data-theme="filled_blue" data-logo-alignment="center" data-locale="en_US" role="button" aria-label="Continue with google" data-safe-to-skip-tnc-redirect=""></div><img class="flip-rtl block -z-1 relative flex-shrink babybear:static w-[700px] h-[560px] babybear:w-[374px] babybear:h-[214px]" alt="Welcome to your professional community" data-test-id="hero__illustration" src="https://static.licdn.com/aero-v1/sc/h/dxf91zhqd2z6b0bwg85ktm5s4">
<button class="show-more-less__button show-more-less__more-button show-more-less-button
" aria-expanded="false" data-tracking-control-name="homepage-basic_pill-list-module_etta-show-more-less_show_more"><button data-tracking-control-name="homepage-basic_testimonials_slide_list_next_button" class="slide-list__nav-button rounded-xl px-1.5 py-1 btn-overlay cursor-pointer disabled:hidden" aria-label="Next Slide" data-direction="next">
<button class="dropdown-to-modal__b..." aria-expanded="false" data-tracking-contro...="homepage-basic_learn...">
<img class="h-[840px] self-center ml-12 flip-rtl babybear:hidden" data-delayed-url="https://static.licdn.com/aero-v1/sc/h/292yd0en6qdvkbezeuj71yu4y" alt="Who is LinkedIn for?">
<button class="language-selector__b..." aria-expanded="false" data-tracking-contro...="footer-lang-dropdown...">
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination3 elements
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Audit Elements
<nav class="nav pt-1.5 pb-2 flex items-center justify-between relative flex-nowrap babymamabear:py-1.5
babybear:flex-wrap " aria-label="Primary"><main class="flex flex-col items-center overflow-hidden min-h-[calc(100vh-76px-50px)]" role="main" id="main-content">
<footer class="li-footer bg-transparent w-full ">
Links must be distinguishable without relying on color4 elements
People with low vision or color blindness cannot visually distinguish links from surrounding text without sufficient color contrast (3:1 ratio minimum). When link colors are too similar to regular text, users with visual impairments cannot identify which text is clickable.
Audit Elements
<a href="/legal/user-agreement?trk=linkedin-tc_auth-button_user-agreement" target="_blank" data-tracking-control-name="linkedin-tc_auth-button_user-agreement" data-tracking-will-navigate="true">User Agreement</a>
<a href="/legal/privacy-policy?trk=linkedin-tc_auth-button_privacy-policy" target="_blank" data-tracking-control-name="linkedin-tc_auth-button_privacy-policy" data-tracking-will-navigate="true">Privacy Policy</a>
<a href="/legal/cookie-policy?trk=linkedin-tc_auth-button_cookie-policy" target="_blank" data-tracking-control-name="linkedin-tc_auth-button_cookie-policy" data-tracking-will-navigate="true">Cookie Policy</a>
<a href="https://www.linkedin.com/signup" class="sign-in-form__join-cta link link-no-visited-state" data-test-id="sign-in-join-cta" data-tracking-client-ingraph="true" data-tracking-control-name="homepage-basic_sign-in-form_inline-join-cta" data-tracking-will-navigate="true">Join now</a>
Links must have discernible text101 elements
Keyboard users and screen reader users can only interact with links that have accessible names and can receive focus. Without proper names, users don't know where links lead. Without keyboard focus, users who cannot use a mouse cannot activate the links at all.
Audit Elements
<a href="#main-content" class="skip-link btn-md btn-primary absolute z-11 -top-[100vh] focus:top-0">
Skip to main content
</a><a href="/?trk=guest_homepage..." class="nav__logo-link link-..." data-tracking-contro...="guest_homepage-basic..." data-tracking-will-n...="">
<a href="https://www.linkedin..." data-tracking-contro...="guest_homepage-basic..." data-tracking-will-n...="" class="top-nav-link flex ju...">
<a href="https://www.linkedin..." data-tracking-contro...="guest_homepage-basic..." data-tracking-will-n...="" class="top-nav-link flex ju...">
<a href="https://www.linkedin..." data-tracking-contro...="guest_homepage-basic..." data-tracking-will-n...="" class="top-nav-link flex ju...">
<a href="https://www.linkedin..." data-tracking-contro...="guest_homepage-basic..." data-tracking-will-n...="" class="top-nav-link flex ju...">
<a href="https://www.linkedin..." data-tracking-contro...="guest_homepage-basic..." data-tracking-will-n...="" class="top-nav-link flex ju...">
<a class="nav__button-secondary btn-secondary-emphasis ml-3 btn-md" href="https://www.linkedin.com/login?fromSignIn=true&trk=guest_homepage-basic_nav-header-signin" data-tracking-control-name="guest_homepage-basic_nav-header-signin" data-tracking-will-navigate="" data-tracking-client-ingraph="">
<a class="nav__button-tertiary btn-primary btn-md" href="https://www.linkedin.com/signup?trk=guest_homepage-basic_nav-header-join" data-tracking-control-name="guest_homepage-basic_nav-header-join" data-test-live-nav-primary-cta="" data-tracking-will-navigate="" data-tracking-client-ingraph="">
<a class="sign-in-form__sign-i..." href="https://www.linkedin..." data-test-id="home-hero-sign-in-ct..." data-tracking-contro...="homepage-basic_home-..." data-tracking-will-n...="" data-tracking-client...="">
Showing first 10 of 101 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 class="flex flex-col items-center overflow-hidden min-h-[calc(100vh-76px-50px)]" role="main" id="main-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 provided2 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
<main class="flex flex-col items-center overflow-hidden min-h-[calc(100vh-76px-50px)]" role="main" id="main-content">
<div class="google-auth-button__placeholder mx-auto
" data-theme="filled_blue" data-logo-alignment="center" data-locale="en_US" role="button" aria-label="Continue with google" data-safe-to-skip-tnc-redirect=""></div>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 href="#main-content" class="skip-link btn-md btn-primary absolute z-11 -top-[100vh] focus:top-0">
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">
Zooming and scaling must not be disabled1 element
Setting user-scalable="no" or maximum-scale less than 2 prevents people with low vision from zooming to read content. Users who enlarge text in their browsers are blocked from making content readable, violating accessibility guidelines that require supporting at least 200% zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1">