Skip to content
https://informationweek.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Heading Hierarchy
Action
30 headings, 2 skip(s)
FIX
30 headings, 2 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
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 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 TechTarget and Informa Tech’s Digital Business Combine.
  • H4 Related Topics skipped
  • H4 Recent in Leadership
  • H4 Related Topics
  • H4 Recent in Resilience
  • H4 Related Topics
  • H4 Recent in ML & AI
  • H4 Related Topics
  • H4 Recent in Data
  • H4 Related Topics
  • H4 Recent in Sustainability
  • H4 Related Topics
  • H4 Recent in Infrastructure
  • H4 Related Topics
  • H4 Recent in Software
  • H4 Related Topics
  • H4 Recent in More
  • H2 What's Trending
  • H3 The invisible labor crisis inside IT: AI work the org chart can't see
  • H3 CIOs can combat talent scarcity with AI-augmented leadership -- Gartner
  • H3 Who controls the fix? Colorado's repair fight tests CIO power
  • H3 The hidden high cost of training AI on AI
  • H2 Ask the Experts: How CIOs can identify and overcome cultural barriers to innovation
  • H2 Ask the Experts: How CIOs can identify and overcome cultural barriers to innovation
  • H3 Podcasts and Videos
  • H2 How to submit an IT leadership column to InformationWeek
  • H5 Discover More skipped
  • H5 Working With Us
  • H5 Join Us
  • H5 Follow Us

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <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.
B
Landmark Structure
4 landmarks
REVIEW
4 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV "navigation" 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

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
title InformationWeek, News & Analysis Tech Le…
2.98:1
#000000
on
#525A5C
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 TechTarget and Infor…19.60:13.0:1
#000000
#F7F7F7
Pass
h2 What's Trending21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ask the Experts: How…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ask the Experts: How…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 How to submit an IT …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 The invisible labor …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 CIOs can combat tale…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Who controls the fix…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 The hidden high cost…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Podcasts and Videos21.00:13.0:1
#000000
#FFFFFF
Pass
title InformationWeek, New…2.98:14.5:1
#000000
#525A5C
Fail
span TechTarget and Infor…20.29:14.5:1
#000000
#FBFBFB
Pass
span TechTarget and Infor…20.29:14.5:1
#000000
#FBFBFB
Pass
p Together, we power a…20.29:14.5:1
#000000
#FBFBFB
Pass
a InformationWeek Reso…20.29:14.5:1
#000000
#FBFBFB
Pass
a Online Events20.29:14.5:1
#000000
#FBFBFB
Pass
a About20.29:14.5:1
#000000
#FBFBFB
Pass
a Advertise20.29:14.5:1
#000000
#FBFBFB
Pass
span Newsletter Sign-Up20.29:14.5:1
#000000
#FBFBFB
Pass
span Newsletter Sign-Up20.29:14.5:1
#000000
#FBFBFB
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.

A
Alt Text Quality
All 54 images OK
PASS
All 54 images OK
Info::
3 image(s) with alt text over 125 characters
Info::
11 decorative image(s) correctly marked
Info::
40 image(s) with good alt text
54 images 40 good alt text 11 decorative
IssueCount
too long3 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 26 passed
PASS
95

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.

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
Discover More div.Layout > footer.Footer > div.LinkSection > h5.LinkSection-Title

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
IT MANAGEMENT div.TopFeatured-WrapContentPreview > div.ContentPreview > div.ContentPreview-Wrapper > a.Keyword
DATA MANAGEMENT div.HorizontalCard > div.HorizontalCard-ContentWrapper > div.HorizontalCard-KeywordWrapper > a.Keyword
AI INNOVATIONS div.HorizontalCard > div.HorizontalCard-ContentWrapper > div.HorizontalCard-KeywordWrapper > a.Keyword
IT LEADERSHIP div.HorizontalCard > div.HorizontalCard-ContentWrapper > div.HorizontalCard-KeywordWrapper > a.Keyword
CLOUD COMPUTING div.HorizontalCard > div.HorizontalCard-ContentWrapper > div.HorizontalCard-KeywordWrapper > a.Keyword
IT INFRASTRUCTURE div.HorizontalCard > div.HorizontalCard-ContentWrapper > div.HorizontalCard-KeywordWrapper > a.Keyword
MACHINE LEARNING & AI div.HorizontalCard > div.HorizontalCard-ContentWrapper > div.HorizontalCard-KeywordWrapper > a.Keyword
IT LEADERSHIP div.HorizontalCard > div.HorizontalCard-ContentWrapper > div.HorizontalCard-KeywordWrapper > a.Keyword
IT LEADERSHIP div.HorizontalCard > div.HorizontalCard-ContentWrapper > div.HorizontalCard-KeywordWrapper > a.Keyword
MACHINE LEARNING & AI div.ListPreview-Container > div.ListPreview-ContentWrapper > div.ListPreview-KeywordWrapper > a.Keyword
MACHINE LEARNING & AI div.ListPreview-Container > div.ListPreview-ContentWrapper > div.ListPreview-KeywordWrapper > a.Keyword
IT MANAGEMENT div.ListPreview-Container > div.ListPreview-ContentWrapper > div.ListPreview-KeywordWrapper > a.Keyword
DATA MANAGEMENT div.ListPreview-Container > div.ListPreview-ContentWrapper > div.ListPreview-KeywordWrapper > a.Keyword
AI INNOVATIONS div.ListPreview-Container > div.ListPreview-ContentWrapper > div.ListPreview-KeywordWrapper > a.Keyword
IT LEADERSHIP div.HorizontalCard > div.HorizontalCard-ContentWrapper > div.HorizontalCard-KeywordWrapper > a.Keyword
INCIDENT RESPONSE div.HorizontalCard > div.HorizontalCard-ContentWrapper > div.HorizontalCard-KeywordWrapper > a.Keyword
AI INNOVATIONS div.HorizontalCard > div.HorizontalCard-ContentWrapper > div.HorizontalCard-KeywordWrapper > a.Keyword
IT INFRASTRUCTURE div.HorizontalCard > div.HorizontalCard-ContentWrapper > div.HorizontalCard-KeywordWrapper > a.Keyword
MACHINE LEARNING & AI div.HorizontalCard > div.HorizontalCard-ContentWrapper > div.HorizontalCard-KeywordWrapper > a.Keyword
CYBER RESILIENCE div.HorizontalCard > div.HorizontalCard-ContentWrapper > div.HorizontalCard-KeywordWrapper > a.Keyword

These items highlight common accessibility best practices.

○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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<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
○Form elements have associated labels
○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>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback