Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 2 REVIEW 5 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-r3t96g

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://feedly.com/site.webmanifest contains invalid JSON. Browsers cannot parse it.

Got: https://feedly.com/site.webmanifest

Manifest contains invalid JSON.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #ffffff

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

4 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 4 <nav> element(s)

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.

Heading Hierarchy

7 headings

REVIEW

7 headings

No H1 heading found

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

H2 ThreatIntelligence
H2 MarketIntelligence
H2 NewsReader
H2 Products
H2 Resources
H2 Downloads
H2 Learn More

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

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

4 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

A+

Alt Text Quality

All 38 images OK

PASS

All 38 images OK

1 image(s) with alt text over 125 characters

37 image(s) with good alt text

38 images 37 good alt text

Issue	Count
too long	1 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

3 issue(s) across 47 links and 2 buttons

PASS

3 issue(s) across 47 links and 2 buttons

3 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /threat-intelligence ("Learn More"); /market-intelligence ("Learn More"); /news-reader ("Learn More")

44 link(s) with descriptive text

47 links

0 empty

3 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/threat-intelligence	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Threat Intelligence
/market-intelligence	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Market Intelligence
/news-reader	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: News Reader

46 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/threat-intelligence ("Learn More"); /market-intelligence ("Learn More"); /news-reader ("Learn More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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)

Element	Ratio	Required	FG	BG	Result
h2 Threat	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Intelligence	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Market	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h2 Intelligence	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h2 News	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h2 Reader	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h2 Products	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h2 Resources	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h2 Downloads	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h2 Learn More	18.43:1	3.0:1	#000000	#F0F0F0	Pass
title Feedly: Track the to…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Threat Intelligence	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Market Intelligence	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span News Reader	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Threat Intelligence	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Market Intelligence	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span News Reader	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Log in	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Log in	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Log in	21.00:1	4.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+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 25 passed

PASS

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
Find, synthesize, and share industry and competitive intelligence faster `div.Flex_flex___mzvZ > div.Flex_flex___mzvZ > div.Flex_flex___mzvZ > p.Tile_description__NV9Re`
Stay ahead of the curve `div.BaseFooter_container__g4K3d > div.Flex_flex___mzvZ > div > p.MarketingFooter_subTitle__Ms_Y7`
Market Intelligence `nav.FooterLinkGroup_nav__RxRQ6 > ul.Flex_flex___mzvZ > li.Text_text__4F9CK > a.Link_link__0RTCn`
Threat Intelligence `nav.FooterLinkGroup_nav__RxRQ6 > ul.Flex_flex___mzvZ > li.Text_text__4F9CK > a.Link_link__0RTCn`
News Reader `nav.FooterLinkGroup_nav__RxRQ6 > ul.Flex_flex___mzvZ > li.Text_text__4F9CK > a.Link_link__0RTCn`
Changelog `nav.FooterLinkGroup_nav__RxRQ6 > ul.Flex_flex___mzvZ > li.Text_text__4F9CK > a.Link_link__0RTCn`
AI Library `nav.FooterLinkGroup_nav__RxRQ6 > ul.Flex_flex___mzvZ > li.Text_text__4F9CK > a.Link_link__0RTCn`
Case Studies `nav.FooterLinkGroup_nav__RxRQ6 > ul.Flex_flex___mzvZ > li.Text_text__4F9CK > a.Link_link__0RTCn`
CVE Insights Cards `nav.FooterLinkGroup_nav__RxRQ6 > ul.Flex_flex___mzvZ > li.Text_text__4F9CK > a.Link_link__0RTCn`
TI Essentials `nav.FooterLinkGroup_nav__RxRQ6 > ul.Flex_flex___mzvZ > li.Text_text__4F9CK > a.Link_link__0RTCn`
Blog `nav.FooterLinkGroup_nav__RxRQ6 > ul.Flex_flex___mzvZ > li.Text_text__4F9CK > a.Link_link__0RTCn`
Documentation `nav.FooterLinkGroup_nav__RxRQ6 > ul.Flex_flex___mzvZ > li.Text_text__4F9CK > a.Link_link__0RTCn`
Slack Community `nav.FooterLinkGroup_nav__RxRQ6 > ul.Flex_flex___mzvZ > li.Text_text__4F9CK > a.Link_link__0RTCn`
iOS `nav.FooterLinkGroup_nav__RxRQ6 > ul.Flex_flex___mzvZ > li.Text_text__4F9CK > a.Link_link__0RTCn`
Android `nav.FooterLinkGroup_nav__RxRQ6 > ul.Flex_flex___mzvZ > li.Text_text__4F9CK > a.Link_link__0RTCn`
Chrome extension `nav.FooterLinkGroup_nav__RxRQ6 > ul.Flex_flex___mzvZ > li.Text_text__4F9CK > a.Link_link__0RTCn`
Firefox extension `nav.FooterLinkGroup_nav__RxRQ6 > ul.Flex_flex___mzvZ > li.Text_text__4F9CK > a.Link_link__0RTCn`
Advertise on Feedly `nav.FooterLinkGroup_nav__RxRQ6 > ul.Flex_flex___mzvZ > li.Text_text__4F9CK > a.Link_link__0RTCn`
Discover Top Blogs `nav.FooterLinkGroup_nav__RxRQ6 > ul.Flex_flex___mzvZ > li.Text_text__4F9CK > a.Link_link__0RTCn`
© 2026 `div.BaseFooter_container__g4K3d > div.Flex_flex___mzvZ > div.Flex_flex___mzvZ > p.Text_text__4F9CK`
Privacy `div.Flex_flex___mzvZ > div.Flex_flex___mzvZ > a.Link_link__0RTCn > p.Text_text__4F9CK`
Terms `div.Flex_flex___mzvZ > div.Flex_flex___mzvZ > a.Link_link__0RTCn > p.Text_text__4F9CK`

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

●`[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

●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

○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

○Links are distinguishable without relying on color.

○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.