Skip to content
https://techrepublic.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
F
Heading Hierarchy
Action
134 headings, 13 skip(s)
FIX
134 headings, 13 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
6 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 TechRepublic
  • H1 Welcome to TechRepublic
  • H2 Most Recent
  • H4 Apple skipped
  • H3 MacBook Neo Cheat Sheet: Everything to Know About Apple’s Budget Mac
  • H4 Hardware
  • H3 Intel Handheld Gaming Chip Core G3: Can It Challenge AMD in 2026?
  • H4 Applications
  • H3 Meta Tests Paid WhatsApp Features With New ‘Plus’ Tier
  • H4 Hardware
  • H3 Galaxy S27 Could Debut Samsung’s Biggest Battery Upgrade in Years
  • H4 APAC
  • H3 China Deploys Robot Dogs, Drones, and Humanoids to Run a ‘Full-Space’ Metro System
  • H2 Featured
  • H4 (empty)
  • H3 2026’s Breach List So Far: FBI Hacked, 1B Androids at Risk, 270M iPhones Vulnerable
  • H2 Editor's Picks
  • H4 (empty)
  • H3 Meta Plans Up to 8,000 Job Cuts in New Round of Layoffs
  • H4 (empty)
  • H3 Amazon Debuts ‘Slimmest Ever’ Fire TV Stick HD Starting at $34.99
  • H2 Articles by Topic
  • H3 MacBook Neo Cheat Sheet: Everything to Know About Apple’s Budget Mac
  • H6 Aminu Abdullahi skipped
  • H6 Apr 21, 2026
  • H3 China Deploys Robot Dogs, Drones, and Humanoids to Run a ‘Full-Space’ Metro System
  • H6 Aminu Abdullahi skipped
  • H6 Apr 21, 2026
  • H3 Google Photos Rolls Out New AI-Powered Portrait Editing Features
  • H6 Madeline Clarke skipped
  • H6 Apr 21, 2026
  • H3 Google’s AI Overviews Produce Hundreds of Millions of Inaccurate Answers Every Day, Analysis Suggests
  • H6 Simon Chandler skipped
  • H6 Apr 21, 2026
  • H2 Join TechRepublic Premium Today
  • H2 Latest from Premium
  • H4 (empty)
  • H3 SMB Compliance & Protection Without the Guesswork
  • H4 (empty)
  • H3 Your AI Governance Can’t Wait. Here’s Where to Start.
  • H4 (empty)
  • H3 Quick Glossary: Drones
  • H2 Meet our Experts
  • H3 Justin Meyers
  • H3 Llanor Alleyne
  • H3 Joseph Ofonagoro
  • H3 Ken Underhill
  • H3 Hanna Sillo
  • H3 Kezia Jungco
  • H3 Sasha Menon
  • H3 Liz Ticong
  • H3 Aminu Abdullahi
  • H3 Luis Millares
  • H3 Fiona Jackson
  • H3 Megan Crouse
  • H3 Esther Shein
  • H3 Andy Wolber
  • H3 Erik Eckel
  • H3 Jack Wallen
  • H3 Drew Robb
  • H3 Kara Sherrer
  • H3 Nicole Rennolds
  • H3 Franklin Okeke
  • H3 Agatha Aviso
  • H3 Madeline Clarke
  • H3 Cory Bohon
  • H3 Robi Mansueto
  • H3 Patrick Murray
  • H3 Jenna Phipps
  • H3 Bianca Caballero
  • H3 Brittany Brooks
  • H3 Sunny Yadav
  • H3 Allison Francis
  • H3 Rayanne Harmon
  • H3 J.R. Johnivan
  • H3 Jameli Jimenez
  • H3 Faithe Day
  • H3 Liz Smith
  • H3 Eric Gerard Ruiz
  • H3 Corey Noles
  • H3 Grant Harvey
  • H3 Justin Meyers
  • H3 Llanor Alleyne
  • H3 Joseph Ofonagoro
  • H3 Ken Underhill
  • H3 Hanna Sillo
  • H3 Kezia Jungco
  • H3 Sasha Menon
  • H3 Liz Ticong
  • H3 Aminu Abdullahi
  • H3 Luis Millares
  • H3 Fiona Jackson
  • H3 Megan Crouse
  • H2 Videos
  • H6 View All skipped
  • H4 Payroll
  • H3 Zoho People 2024: A Complete Breakdown
  • H6 Watch Video skipped
  • H4 Latest Videos
  • H3 Heating Up Productivity: Top 5 Features of Fireberry Revealed
  • H6 Watch Video skipped
  • H3 Mastering Data: Exploring the Top 5 Data Management Platforms
  • H6 Watch Video skipped
  • H2 Latest Articles
  • H4 Apple skipped
  • H3 MacBook Neo Cheat Sheet: Everything to Know About Apple’s Budget Mac
  • H4 Hardware
  • H3 Intel Handheld Gaming Chip Core G3: Can It Challenge AMD in 2026?
  • H4 Applications
  • H3 Meta Tests Paid WhatsApp Features With New ‘Plus’ Tier
  • H4 Hardware
  • H3 Galaxy S27 Could Debut Samsung’s Biggest Battery Upgrade in Years
  • H4 APAC
  • H3 China Deploys Robot Dogs, Drones, and Humanoids to Run a ‘Full-Space’ Metro System
  • H4 Apple
  • H3 Apple May Drop iOS 27 Support for Four iPhones, Leaving Millions Behind
  • H4 APAC
  • H3 Huawei Just Beat Apple and Samsung to a New Foldable Format in China
  • H4 Android
  • H3 Google Photos Rolls Out New AI-Powered Portrait Editing Features
  • H4 Google
  • H3 Leak Points to Google’s ‘Fitbit Air’ as a Screen-Free Wearable for Health Tracking
  • H4 Artificial Intelligence
  • H3 Google’s AI Overviews Produce Hundreds of Millions of Inaccurate Answers Every Day, Analysis Suggests
  • H3 Daily Tech Insider
  • H3 If you can only read one tech story a day, this is it.
  • H3 Daily Tech Insider
  • H3 If you can only read one tech story a day, this is it.
  • H3 Create a TechRepublic Account
  • H3 Sign in to TechRepublic
  • H3 Reset Password
  • H3 Welcome. Tell us a little bit about you.
  • H3 Want to receive more TechRepublic news?
  • H3 You're All Set

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F
Form Accessibility
Action
28 of 36 controls have issues
FIX
28 of 36 controls have issues
Critical::
19 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="search-trigger">; <select name="company_size_uuid">; <select name="industry_uuid">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox"> (+9 more)
Warning::
9 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="email">; <input type="password" name="password" id="sign-up_password">; <input type="text" name="email">; <input type="password" name="password">; <input type="email" name="email">; <input type="text" name="first_name">; <input type="text" name="last_name">; <input type="text" name="title">; <input type="text" name="company">
Info::
8 control(s) properly labeled
36 controls
8 labeled
9 placeholder only
19 unlabeled
ControlTypeLabelMethod
#nav-site-searchsearchSearchfor/id
#email-69e7d6434eaaaemailEmail Addressfor/id
#opt-in-69e7d6434eaaacheckboxI agree to the Terms of Use and Privacy Policy. I understand I will receive a subscription to TechRepublic's Daily Tech Insider newsletter. You can opt out at any time.for/id
#email-69e7d6434fe05emailEmail Addressfor/id
#opt-in-69e7d6434fe05checkboxI agree to the Terms of Use and Privacy Policy. I understand I will receive a subscription to TechRepublic's Daily Tech Insider newsletter. You can opt out at any time.for/id
#countryselectCountryfor/id
termscheckboxnone
#remember-mecheckboxnone
#sign-up_passwordpassword(Password *)placeholder only
emailtext(Email)placeholder only
passwordpassword(Password)placeholder only
emailtext(Email *)placeholder only
emailemail(Email)placeholder only
first_nametext(First Name)placeholder only
last_nametext(Last Name)placeholder only
titletext(Job Title)placeholder only
companytext(Company Name)placeholder only
#search-triggercheckbox(none)none
company_size_uuidselect(none)none
industry_uuidselect(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="checkbox" id="search-trigger">; <select name="company_size_uuid">; <select name="industry_uuid">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox"> (+9 more)

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="email">; <input type="password" name="password" id="sign-up_password">; <input type="text" name="email">; <input type="password" name="password">; <input type="email" name="email">; <input type="text" name="first_name">; <input type="text" name="last_name">; <input type="text" name="title">; <input type="text" name="company">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #3289c8
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - TechRepublic ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
7 icon(s) detected
REVIEW
7 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 29 passed
REVIEW
88

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Hanna Sillo div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-clone01
Kezia Jungco div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-clone02
Liz Ticong div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide02
Aminu Abdullahi div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide03
Luis Millares div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide04
Fiona Jackson div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide05
Megan Crouse div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide06
Esther Shein div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide07
Andy Wolber div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide08
Erik Eckel div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide09
Jack Wallen div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide10
Drew Robb div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide11
Kara Sherrer Staff Writer div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide12
Nicole Rennolds div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide13
Franklin Okeke div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide14
Agatha Aviso div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide15
Madeline Clarke div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide16
Cory Bohon div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide17
Robi Mansueto div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide18
Patrick Murray div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide19
Jenna Phipps div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide20
Bianca Caballero div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide21
Brittany Brooks div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide22
Sunny Yadav div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide23
Allison Francis div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide24
Rayanne Harmon div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide25
J.R. Johnivan div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide26
Jameli Jimenez div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide27
Faithe Day div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide28
Liz Smith div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide29
Eric Gerard Ruiz Staff Writer div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide30
Corey Noles div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide31
Grant Harvey Contributing Writer div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide32
Justin Meyers div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide33
Llanor Alleyne div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide34
Joseph Ofonagoro div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide35
Ken Underhill div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide36
Hanna Sillo div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide37
Kezia Jungco div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-slide38
Sasha Menon div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-clone03
Liz Ticong div#splide01 > div#splide01-track > ul#splide01-list > a#splide01-clone04

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
By Aminu Abdullahi div.group > footer > div.byline > span
Apr 21, 2026 footer > div.byline > span.date-published > time
By TechRepublic Staff div.group > footer > div.byline > span
Apr 21, 2026 footer > div.byline > span.date-published > time
By Kezia Jungco div.group > footer > div.byline > span
Apr 21, 2026 footer > div.byline > span.date-published > time
By Joseph Ofonagoro div.group > footer > div.byline > span
Apr 21, 2026 footer > div.byline > span.date-published > time
By Aminu Abdullahi div.group > footer > div.byline > span
Apr 21, 2026 footer > div.byline > span.date-published > time
By Joseph Ofonagoro div.group > footer > div.byline > span
Apr 21, 2026 footer > div.byline > span.date-published > time
By Aminu Abdullahi div.group > footer > div.byline > span
Apr 21, 2026 footer > div.byline > span.date-published > time
By Madeline Clarke div.group > footer > div.byline > span
Apr 21, 2026 footer > div.byline > span.date-published > time
By Aminu Abdullahi div.group > footer > div.byline > span
Apr 21, 2026 footer > div.byline > span.date-published > time
By Simon Chandler div.group > footer > div.byline > span
Apr 21, 2026 footer > div.byline > span.date-published > time
I agree to the Terms of Use and Privacy Policy. I understand I will receive a s… form.ta-campaign-widget__form > div.ta-campaign-widget__checkbox > div.flex > label.ta-campaign-widget__checkbox__label
I agree to the Terms of Use and Privacy Policy. I understand I will receive a s… form.ta-campaign-widget__form > div.ta-campaign-widget__checkbox > div.flex > label.ta-campaign-widget__checkbox__label

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Terms of Use div.ta-campaign-widget__checkbox > div.flex > label.ta-campaign-widget__checkbox__label > a
Privacy Policy div.ta-campaign-widget__checkbox > div.flex > label.ta-campaign-widget__checkbox__label > a
Terms of Use div.ta-campaign-widget__checkbox > div.flex > label.ta-campaign-widget__checkbox__label > a
Privacy Policy div.ta-campaign-widget__checkbox > div.flex > label.ta-campaign-widget__checkbox__label > a
Do Not Sell My Data div.col-1 > div.inmobi-consent > div#choice-footer-msg > a

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Aminu Abdullahi div.abt-posts-container__card > a.abt-posts-container__card--link > div.abt-posts-container__card--content-container > h6.abt-posts-container__card--author
Aminu Abdullahi div.abt-posts-container__card > a.abt-posts-container__card--link > div.abt-posts-container__card--content-container > h6.abt-posts-container__card--author
Madeline Clarke div.abt-posts-container__card > a.abt-posts-container__card--link > div.abt-posts-container__card--content-container > h6.abt-posts-container__card--author
Simon Chandler div.abt-posts-container__card > a.abt-posts-container__card--link > div.abt-posts-container__card--content-container > h6.abt-posts-container__card--author
article.is-premium > div.group > header > h4.category-title article.is-premium > div.group > header > h4.category-title
View All div.video-component > div.layout > a > h6.video-component__view-all
Watch Video div.layout > div.video-component__featured > div.video-component__featured--content > h6.video-component__featured--content-link
Watch Video div.video-component__latest-videos > div.video-component__latest-videos--video > div.video-component__latest-videos--video-content > h6.video-component__latest-videos--video-content-link
Watch Video div.video-component__latest-videos > div.video-component__latest-videos--video > div.video-component__latest-videos--video-content > h6.video-component__latest-videos--video-content-link

These are opportunities to improve keyboard navigation in your application.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A
Landmark Structure
50 landmarks
PASS
50 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
1 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A
Alt Text Quality
1 of 82 images have issues
PASS
1 of 82 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
2 decorative image(s) correctly marked
Info::
79 image(s) with good alt text
82 images 79 good alt text 2 decorative 1 missing
IssueCount
missing1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

A
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: TechRepublic
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name TechRepublic ✓192×192 icon ✓512×512 icon ✗Start URL https://techrepublic.com ✓Display Mode standalone ✓
Name TechRepublic Display Mode standalone Theme Color #3289c8 Background Color #3289c8 Icons 2 icon(s)
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: https://www.techrepublic.com/wp-content/themes/techrepublic-theme/print.css?ver=1.34.1
Print Stylesheet ✓ Print Optimized
Print stylesheet https://www.techrepublic.com/wp-content/themes/techrepublic-theme/print.css?ver=1.34.1 ✓Inline @media print Not detected ✗
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 TechRepublic18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Articles by Topic18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Latest from Premium18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Meet our Experts18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Videos18.26:13.0:1
#000000
#EFEFEF
Pass
h3 MacBook Neo Cheat Sh…18.26:13.0:1
#000000
#EFEFEF
Pass
h3 China Deploys Robot …18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Google Photos Rolls …18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Google’s AI Overvi…18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Justin Meyers18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Llanor Alleyne18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Joseph Ofonagoro18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Ken Underhill18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Hanna Sillo18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Kezia Jungco18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Sasha Menon18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Liz Ticong18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Aminu Abdullahi18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Luis Millares18.26:13.0:1
#000000
#EFEFEF
Pass
h3 Fiona Jackson18.26:13.0:1
#000000
#EFEFEF
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback