Skip to content
https://eweek.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) 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!) MAIN (missing!) ASIDE CONTENTINFO (missing!)

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
7 headings
REVIEW
7 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Latest News
  • H2 Artificial Intelligence
  • H2 Video Highlights
  • H3 Get the Free Newsletter!
  • H2 Events
  • H3 Company
  • H3 Categories

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

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 ✓Page Title X ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
9 icon(s) detected
REVIEW
9 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA
title eWeek: Technology News for IT Profession…
2.33:1
#000000
on
#314C5E
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span We value your privacy
3.19:1
#000000
on
#565E66
needs 4.5:1 (normal text)
16px · top of page (header area)
div We and our
3.20:1
#000000
on
#575E66
needs 4.5:1 (normal text)
16px · top of page (header area)
a partners
3.26:1
#000000
on
#595F67
needs 4.5:1 (normal text)
16px · top of page (header area)
div store and/or access information on a dev…
3.26:1
#000000
on
#595F67
needs 4.5:1 (normal text)
16px · above the fold
div Please note that this website/app uses o…
3.26:1
#000000
on
#595F67
needs 4.5:1 (normal text)
16px · above the fold
span MORE OPTIONS
3.26:1
#000000
on
#595F67
needs 4.5:1 (normal text)
16px · above the fold
span AGREE
3.26:1
#000000
on
#595F67
needs 4.5:1 (normal text)
16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Latest News21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Artificial Intellige…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Video Highlights21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Events21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Get the Free Newslet…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Company21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Categories21.00:13.0:1
#000000
#FFFFFF
Pass
title eWeek: Technology Ne…2.33:14.5:1
#000000
#314C5E
Fail
span We value your privac…3.19:14.5:1
#000000
#565E66
Fail
div We and our3.20:14.5:1
#000000
#575E66
Fail
a partners3.26:14.5:1
#000000
#595F67
Fail
div store and/or access …3.26:14.5:1
#000000
#595F67
Fail
div Please note that thi…3.26:14.5:1
#000000
#595F67
Fail
span MORE OPTIONS3.26:14.5:1
#000000
#595F67
Fail
span AGREE3.26:14.5:1
#000000
#595F67
Fail
a ___21.00:14.5:1
#000000
#FFFFFF
Pass
button Latest News21.00:14.5:1
#000000
#FFFFFF
Pass
button Resources21.00:14.5:1
#000000
#FFFFFF
Pass
button Artificial Intellige…21.00:14.5:1
#000000
#FFFFFF
Pass
button Video21.00:14.5:1
#000000
#FFFFFF
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
1 of 49 images have issues
PASS
1 of 49 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
20 decorative image(s) correctly marked
Info::
28 image(s) with good alt text
49 images 28 good alt text 20 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
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#subscription-email-8042emailENTER YOUR EMAILfor/id
emailemail(enter your email)placeholder only

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

<input type="email" name="email">

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

A
Lighthouse Accessibility Audits
Score 93/100 — 2 failing, 26 passed
PASS
93

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.

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
partners div.qc-cmp2-publisher-logo-container > div.qc-cmp2-summary-info > div > a
LATEST NEWS a.bg-primary > astro-island > div.ticker-container > span.w-full
LATEST NEWS a.bg-primary > astro-island > div.ticker-container > span.w-full
LATEST NEWS a.bg-primary > astro-island > div.ticker-container > span.w-full
LATEST NEWS a.bg-primary > astro-island > div.ticker-container > span.w-full
LATEST NEWS a.bg-primary > astro-island > div.ticker-container > span.w-full
LATEST NEWS a.bg-primary > astro-island > div.ticker-container > span.w-full
LATEST NEWS a.bg-primary > astro-island > div.ticker-container > span.w-full
LATEST NEWS a.bg-primary > astro-island > div.ticker-container > span.w-full
LATEST NEWS a.bg-primary > astro-island > div.ticker-container > span.w-full
VIEW ALL div.flex > div.justify-center > a > button.button
ARTIFICIAL INTELLIGENCE a.bg-primary > astro-island > div.ticker-container > span.w-full
ARTIFICIAL INTELLIGENCE a.bg-primary > astro-island > div.ticker-container > span.w-full
ARTIFICIAL INTELLIGENCE a.bg-primary > astro-island > div.ticker-container > span.w-full
VIDEO li.glide__slide > div.flex > div.grow > a.font-mono
VIEW ALL div.flex > div.justify-center > a > button.button
Terms div.pt-[20px] > form.space-y-4 > div.text-sm > a
Privacy Policy div.pt-[20px] > form.space-y-4 > div.text-sm > a
eWeek has the latest technology news and analysis, buying guides, and product r… div.wrapper > div.flex > div.space-y-[24px] > p.leading-6
COMPANY div.flex > div.flex > div.space-y-[24px] > h3.h3
About us div.flex > div.space-y-[24px] > div.grid > a.text-primary-foreground
Contact us div.flex > div.space-y-[24px] > div.grid > a.text-primary-foreground
Advertise with us div.flex > div.space-y-[24px] > div.grid > a.text-primary-foreground
CATEGORIES div.flex > div.flex > div.space-y-[24px] > h3.h3
Latest News div.flex > div.space-y-[24px] > div.grid > a.text-primary-foreground
Resources div.flex > div.space-y-[24px] > div.grid > a.text-primary-foreground
Artificial Intelligence div.flex > div.space-y-[24px] > div.grid > a.text-primary-foreground
Video div.flex > div.space-y-[24px] > div.grid > a.text-primary-foreground
Big Data & Analytics div.flex > div.space-y-[24px] > div.grid > a.text-primary-foreground
Cloud div.flex > div.space-y-[24px] > div.grid > a.text-primary-foreground
Networking div.flex > div.space-y-[24px] > div.grid > a.text-primary-foreground
Do Not Sell My Data div.flex > div.flex > div#choice-footer-msg > a

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 div.pt-[20px] > form.space-y-4 > div.text-sm > a
Privacy Policy div.pt-[20px] > form.space-y-4 > div.text-sm > a

These are opportunities to improve the legibility of your content.

○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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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.
○Elements with visible text labels have matching accessible names.
○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