Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 3 REVIEW 5 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title The brand data platform - Brandfetch ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

4 icon(s) detected

FIX

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

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

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

Mobile-Readable Font Sizes

Action

76% of visible text renders at >= 12 CSS px (59 below threshold)

REVIEW

76% of visible text renders at >= 12 CSS px (59 below threshold)

59 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.0px ("\"id\""); <span> 10.0px ("\"idZA7HYRWK\""); <span> 10.0px ("\"name\""); <span> 10.0px ("\"Attio\""); <span> 10.0px ("\"domain\"").

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 14 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 The brand data platf…	6.08:1	3.0:1	#000000	#8A8A8A	Pass
h2 Explore brands	6.08:1	3.0:1	#000000	#8A8A8A	Pass
h2 Give your brand a	6.25:1	3.0:1	#000000	#8C8C8C	Pass
h2 home on the internet	6.25:1	3.0:1	#000000	#8C8C8C	Pass
h3 Build with brand dat…	6.25:1	3.0:1	#000000	#8C8C8C	Pass
h3 Search the world's b…	6.25:1	3.0:1	#000000	#8C8C8C	Pass
title The brand data platf…	6.25:1	4.5:1	#000000	#8C8C8C	Pass
p Type a brand name or…	6.25:1	4.5:1	#000000	#8C8C8C	Pass
p For Brands	6.25:1	4.5:1	#000000	#8C8C8C	Pass
p For Developers	6.08:1	4.5:1	#000000	#8A8A8A	Pass
p Plugins	6.08:1	4.5:1	#000000	#8A8A8A	Pass
p Blog	6.08:1	4.5:1	#000000	#8A8A8A	Pass
p Sign in	6.08:1	4.5:1	#000000	#8A8A8A	Pass
span Join Brandfetch	6.08:1	4.5:1	#000000	#8A8A8A	Pass
p Tap into the most co…	6.08:1	4.5:1	#000000	#8A8A8A	Pass
p Search from millions…	6.08:1	4.5:1	#000000	#8A8A8A	Pass
p Type a brand name or…	6.08:1	4.5:1	#000000	#8A8A8A	Pass
p Figma	6.08:1	4.5:1	#000000	#8A8A8A	Pass
p Stripe	6.08:1	4.5:1	#000000	#8A8A8A	Pass
p Reddit	6.08:1	4.5:1	#000000	#8A8A8A	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.

Landmark Structure

11 landmarks

PASS

11 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

Heading Hierarchy

27 headings, 1 skip(s)

PASS

27 headings, 1 skip(s)

Single H1 present

Heading level skipped: H3 → H5 (missing H4)

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

H1 The brand data platform
H2 Explore brands
H3 Build with brand data
H5 Add your brand on Brandfetch skipped
H6 Naver
H6 Dell
H6 LongHorn Steakhouse
H6 Hugging Face
H6 Fendi
H6 Nintendo
H6 Discovery+
H6 Coach
H6 Tencent
H6 Pearl Abyss
H6 LendingClub
H6 Ecco
H6 PhonePe
H6 Tidal
H6 Blizzard
H6 Viber
H6 Lululemon
H6 Huawei
H6 Chili's
H6 Payoneer
H2 Your questions, answered
H3 Search the world's brands
H2 Give your brand a home on the internet

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

A+

Heading Text Quality

All 27 heading(s) have substantive, well-formed text

PASS

All 27 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

Alt Text Quality

2 of 83 images have issues

PASS

2 of 83 images have issues

2 image(s) with generic alt text

81 image(s) with good alt text

83 images 81 good alt text 2 generic

Issue	Count
generic	2 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

87 links, 6 buttons — all OK

PASS

87 links, 6 buttons — all OK

10 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://docs.brandfetch.com/guides/logo-fair-use; https://docs.brandfetch.com/mcp/overview; https://status.brandfetch.io; https://trust.brandfetch.com; https://docs.brandfetch.com/get-started; /llms.txt; /auth.md; https://x.com/brandfetch; https://linkedin.com/company/brandfetch; https://instagram.com/brandfetch

77 link(s) with descriptive text

87 links

0 empty

0 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://docs.brandfetch.com/guides/logo-…	logo fair use guide	new tab	Add '(opens in new tab)' to text
https://docs.brandfetch.com/mcp/overview	MCP docs	new tab	Add '(opens in new tab)' to text
https://status.brandfetch.io	All services online	new tab	Add '(opens in new tab)' to text
https://trust.brandfetch.com	SOC2	new tab	Add '(opens in new tab)' to text
https://docs.brandfetch.com/get-started	Docs	new tab	Add '(opens in new tab)' to text
/llms.txt	LLMS	new tab	Add '(opens in new tab)' to text
/auth.md	auth.md	new tab	Add '(opens in new tab)' to text
https://x.com/brandfetch	X	new tab	Add '(opens in new tab)' to text
https://linkedin.com/company/brandfetch	Linkedin	new tab	Add '(opens in new tab)' to text
https://instagram.com/brandfetch	Instagram	new tab	Add '(opens in new tab)' to text

83 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://docs.brandfetch.com/guides/logo-fair-use; https://docs.brandfetch.com/mcp/overview; https://status.brandfetch.io; https://trust.brandfetch.com; https://docs.brandfetch.com/get-started; /llms.txt; /auth.md; https://x.com/brandfetch; https://linkedin.com/company/brandfetch; https://instagram.com/brandfetch

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

tabindex="-1" on naturally-focusable <select>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

Lighthouse Accessibility Audits

Score 94/100 — 2 failing, 22 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
Start for free `div.index-module-scss-module__1vxd5W__flex > a.index-module-scss-module__5HxASG__width-xs-full > button.index-module-scss-module__43-cmG__button > span`

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
Add your brand on Brandfetch `div.index-module__dy3LwW__item > div.index-module-scss-module__1vxd5W__flex > div.index-module-scss-module__jz34vW__box > h5.index-module-scss-module__WznaLG__level-5`

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

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

●ARIA input fields have accessible names

●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

●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

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` 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.

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

○Identical links have the same purpose.

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