Skip to content
https://screamingfrog.co.uk

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
47
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
F
Alt Text Quality
Action
26 of 37 images have issues
FIX
26 of 37 images have issues
Critical::
26 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
12 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
37 images 10 good alt text 1 decorative 26 missing
IssueCount
missing26 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Form Accessibility
Action
12 of 16 controls have issues
FIX
12 of 16 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>; <select>; <input type="submit">; <input type="submit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Warning::
7 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s">; <input type="text" name="your-name">; <input type="email" name="your-email">; <textarea name="your-message">; <input type="text" name="your-name">; <input type="email" name="your-email">; <textarea name="your-message" id="message-support">
Info::
4 control(s) properly labeled
16 controls
4 labeled
7 placeholder only
5 unlabeled
ControlTypeLabelMethod
file-12filenone
_wpcf7_ak_hp_textareatextareaΔnone
file-12filenone
_wpcf7_ak_hp_textareatextareaΔnone
stext(Looking for something?)placeholder only
your-nametext(Your Name)placeholder only
your-nametext(Your Name)placeholder only
your-emailemail(Email Address)placeholder only
#message-supporttextarea(Your message - Please include as much details as possible.)placeholder only
your-emailemail(Email Address)placeholder only
your-messagetextarea(Your message - Please include as much details as possible.)placeholder only
selectselect(none)none
selectselect(none)none
inputsubmit(none)none
inputsubmit(none)none
#g-recaptcha-response-100000textarea(none)none

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

<select>; <select>; <input type="submit">; <input type="submit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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="s">; <input type="text" name="your-name">; <input type="email" name="your-email">; <textarea name="your-message">; <input type="text" name="your-name">; <input type="email" name="your-email">; <textarea name="your-message" id="message-support">

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
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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 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

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found - Screaming Frog ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Lighthouse Accessibility Audits
Action
Score 73/100 — 7 failing, 20 passed
REVIEW
73

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
16 April, 2026 by Mark Porter Et al. Green SEO: Leveraging Screaming Frog for … div#sf-carousel__items-mw > div#sf-carousel__items-iw > div#sf-carousel__items > div#sf-carousel__items-item1
13 April, 2026 by Chloe Meek Out of Site, Out of Mind: Best Practices for Crea… div#sf-carousel__items-mw > div#sf-carousel__items-iw > div#sf-carousel__items > div#sf-carousel__items-item2
26 February, 2026 by Danny Sturrock Et al. Design Trends That Are Shaping 2026… div#sf-carousel__items-mw > div#sf-carousel__items-iw > div#sf-carousel__items > div#sf-carousel__items-item3
20 February, 2026 by Arash Seyfi Analysing and Reconstructing Site Architectur… div#sf-carousel__items-mw > div#sf-carousel__items-iw > div#sf-carousel__items > div#sf-carousel__items-item4
12 January, 2026 by Liam Lesani Data-Driven Content Pruning at Scale Using API… div#sf-carousel__items-mw > div#sf-carousel__items-iw > div#sf-carousel__items > div#sf-carousel__items-item5
5 December, 2025 by Oliver Brett Screaming Frog & Good Travel Management Take … div#sf-carousel__items-mw > div#sf-carousel__items-iw > div#sf-carousel__items > div#sf-carousel__items-item6
21 October, 2025 by Mark Porter The brightonSEO Crawling Clinic October ’25 I… div#sf-carousel__items-mw > div#sf-carousel__items-iw > div#sf-carousel__items > div#sf-carousel__items-item7
20 October, 2025 by Dan Sharp Screaming Frog SEO Spider Update – Version 23.0 … div#sf-carousel__items-mw > div#sf-carousel__items-iw > div#sf-carousel__items > div#sf-carousel__items-item8
6 October, 2025 by Adriano Maggi Flying Blind: Measuring Keyword Coverage on a… div#sf-carousel__items-mw > div#sf-carousel__items-iw > div#sf-carousel__items > div#sf-carousel__items-item9

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body#js-app > header.sf-header > div.sf-header__content > button.sf-header__mobile-nav-control body#js-app > header.sf-header > div.sf-header__content > button.sf-header__mobile-nav-control
main.page-content > div#sf-carousel > div.sf-carousel__control > button#sf-carousel__control-btn--prev main.page-content > div#sf-carousel > div.sf-carousel__control > button#sf-carousel__control-btn--prev
main.page-content > div#sf-carousel > div.sf-carousel__control > button#sf-carousel__control-btn--next main.page-content > div#sf-carousel > div.sf-carousel__control > button#sf-carousel__control-btn--next

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.sf-wrap > div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > img.sf-homepage-services-nav__icon div.sf-wrap > div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > img.sf-homepage-services-nav__icon
div.sf-wrap > div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > img.sf-homepage-services-nav__icon div.sf-wrap > div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > img.sf-homepage-services-nav__icon
div.sf-wrap > div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > img.sf-homepage-services-nav__icon div.sf-wrap > div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > img.sf-homepage-services-nav__icon
div.sf-wrap > div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > img.sf-homepage-services-nav__icon div.sf-wrap > div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > img.sf-homepage-services-nav__icon
div.sf-wrap > div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > img.sf-homepage-services-nav__icon div.sf-wrap > div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > img.sf-homepage-services-nav__icon
div.sf-wrap > div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > img.sf-homepage-services-nav__icon div.sf-wrap > div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > img.sf-homepage-services-nav__icon
div.sf-software-overview > div.sf-software-overview__operating-systems > div.sf-operating-system > img div.sf-software-overview > div.sf-software-overview__operating-systems > div.sf-operating-system > img
div.sf-software-overview > div.sf-software-overview__operating-systems > div.sf-operating-system > img div.sf-software-overview > div.sf-software-overview__operating-systems > div.sf-operating-system > img
div.sf-software-overview > div.sf-software-overview__operating-systems > div.sf-operating-system > img div.sf-software-overview > div.sf-software-overview__operating-systems > div.sf-operating-system > img
div.sf-bg > div.sf-wrap > div.sf-agency-overview > img.x2 div.sf-bg > div.sf-wrap > div.sf-agency-overview > img.x2

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#sf-carousel__items-item0 > div.sf-post-preview > div.sf-post-preview__hero > a.sf-post-preview__hero-img div#sf-carousel__items-item0 > div.sf-post-preview > div.sf-post-preview__hero > a.sf-post-preview__hero-img

These are opportunities to improve the semantics of the controls in your application. This 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
Agency Services div.sf-homepage-hero > div.sf-wrap > div.sf-homepage-hero__btns > a
SEO Spider Tool div.sf-homepage-hero > div.sf-wrap > div.sf-homepage-hero__btns > a
Search Engine div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > h2.sf-homepage-services-nav__text > span
Marketing div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > h2.sf-homepage-services-nav__text > span
Search Engine div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > h2.sf-homepage-services-nav__text > span
Optimisation div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > h2.sf-homepage-services-nav__text > span
Pay Per Click div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > h2.sf-homepage-services-nav__text > span
Management div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > h2.sf-homepage-services-nav__text > span
Social Media div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > h2.sf-homepage-services-nav__text > span
Marketing div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > h2.sf-homepage-services-nav__text > span
Content div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > h2.sf-homepage-services-nav__text > span
Marketing div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > h2.sf-homepage-services-nav__text > span
Link div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > h2.sf-homepage-services-nav__text > span
Building div.sf-homepage-services-nav__grid > a.sf-homepage-services-nav__item > h2.sf-homepage-services-nav__text > span
View All Services main.page-content > div#sf-homepage-services-nav > div.sf-wrap > button#sf-homepage-services-nav__show-all
Frog div.sf-software-overview__text > p > strong > span.sf-color
Features div.sf-software-overview > div.sf-software-overview__text > div.sf-software-overview__cta > a.sf-software-overview__cta-btn
Download div.sf-software-overview > div.sf-software-overview__text > div.sf-software-overview__cta > a.sf-software-overview__cta-btn
Get in touch div.sf-agency-overview > div.sf-agency-overview__text > p > a
Simon Goble, Dogbuddy div.sf-quotation > div.sf-quotation__source > div.sf-quotation__source-details > p.sf-quotation__source-name
More from the blog div#sf-carousel > div.sf-wrap > div.sf-carousel__header > a
 Continue Reading div.sf-post-preview > div.sf-post-preview__content > p.sf-post-preview__cta > a.sf-arrow-link
0 Comments div.sf-post-preview > div.sf-post-preview__content > p.sf-post-preview__cta > a.sf-marg

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
Available On div.sf-wrap > div.sf-software-overview > div.sf-software-overview__operating-systems > h4

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
●Form elements have associated labels
●ARIA attributes are used as specified for the element's role
●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 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
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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
○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
○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.
A
Heading Hierarchy
40 headings, 1 skip(s)
PASS
40 headings, 1 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.
  • H1 We are a UK based SEO agency and the creators of the famous website crawler and log file analyser tools.
  • H2 Search Engine Marketing
  • H2 Search Engine Optimisation
  • H2 Pay Per Click Management
  • H2 Social Media Marketing
  • H2 Content Marketing
  • H2 Link Building
  • H2 Google Ads Audits
  • H2 Analytics Consultancy
  • H2 Technical SEO
  • H2 Digital Copywriting
  • H2 Digital PR
  • H2 Reactive PR
  • H2 SEO Spider Tool
  • H4 Available On skipped
  • H2 We're an agency that develops search strategies for large brands to small and medium sized enterprises.
  • H2 Latest from the blog
  • H2 Using the Screaming Frog SEO Spider to Generate Markdown at Scale
  • H2 Green SEO: Leveraging Screaming Frog for a Sustainable Web
  • H2 Out of Site, Out of Mind: Best Practices for Creating Valuable On-Site Campaign Content
  • H2 Design Trends That Are Shaping 2026
  • H2 Analysing and Reconstructing Site Architecture Using Breadcrumbs: A Practical SEO Guide
  • H2 Data-Driven Content Pruning at Scale Using APIs and the Screaming Frog SEO Spider
  • H2 Screaming Frog & Good Travel Management Take Flight With UK Search Awards Win
  • H2 The brightonSEO Crawling Clinic October ’25
  • H2 Screaming Frog SEO Spider Update – Version 23.0
  • H2 Flying Blind: Measuring Keyword Coverage on a Cluster Without First-Party Tools
  • H3 Services
  • H3 Latest Posts
  • H3 Latest Guides
  • H3 Contact Us
  • H3 About Us
  • H2 SEO Spider v.23.3
  • H2 SEO Spider v.23.3
  • H2 SEO Spider v.23.3
  • H2 Log File Analyser v.6.4
  • H2 Log File Analyser v.6.4
  • H2 Log File Analyser v.6.4
  • H2 Support Ticket
  • H2 Support Ticket

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+
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
h2 SEO Spider Tool8.32:13.0:1
#000000
#75B42D
Pass
h2 We're an agency that…8.32:13.0:1
#000000
#75B42D
Pass
h2 Latest from the blog8.32:13.0:1
#000000
#75B42D
Pass
h2 SEO Spider v.23.38.32:13.0:1
#000000
#75B42D
Pass
h2 SEO Spider v.23.38.32:13.0:1
#000000
#75B42D
Pass
h2 SEO Spider v.23.38.32:13.0:1
#000000
#75B42D
Pass
h2 Log File Analyser v.…8.32:13.0:1
#000000
#75B42D
Pass
h2 Log File Analyser v.…8.32:13.0:1
#000000
#75B42D
Pass
h2 Log File Analyser v.…8.32:13.0:1
#000000
#75B42D
Pass
h2 Support Ticket8.32:13.0:1
#000000
#75B42D
Pass
h2 Support Ticket8.32:13.0:1
#000000
#75B42D
Pass
h3 Services8.32:13.0:1
#000000
#75B42D
Pass
h3 Latest Posts8.32:13.0:1
#000000
#75B42D
Pass
h3 Latest Guides8.32:13.0:1
#000000
#75B42D
Pass
h3 Contact Us8.32:13.0:1
#000000
#75B42D
Pass
h3 About Us8.32:13.0:1
#000000
#75B42D
Pass
title SEO Agency - Screami…21.00:14.5:1
#000000
#FFFFFF
Pass
a About21.00:14.5:1
#000000
#FFFFFF
Pass
a Team12.29:14.5:1
#000000
#ACD281
Pass
a Our Story8.31:14.5:1
#000000
#74B42C
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