Skip to content
https://pcpclaim-uk.co.uk

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
82
GRADE
B
FIX
3
REVIEW
8
PASS
13
INFO
0
Checks
24
13 PASS 8 REVIEW 3 FIX
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: #234977
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 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.

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::
3 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 3 <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
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
2 of 3 <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

C
Heading Hierarchy
Action
64 headings, 3 skip(s)
REVIEW
64 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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.
  • H1 PCP Claims: Get Specialist Advice & Compensation
  • H3 No Win, No Fee Read more skipped
  • H3 The Claims Experts
  • H3 Knowledgeable Handlers
  • H3 Around-the-Clock Support
  • H3 If ANY of the below apply, you may be due compensation:
  • H3 Step 1.
  • H3 Step 2.
  • H3 Step 3.
  • H3 Step 4.
  • H3 PCP Finance Claims
  • H3 HP Finance Claims
  • H3 Mass Redress Scheme is Confirmed
  • H3 We Understand Your Rights
  • H3 A Dedicated and Experienced Team
  • H3 Check Your Eligibility for Free
  • H2 How Have I Been Mis-Sold on My Finance Agreement?
  • H3 Check if you’re eligible to claim in minutes
  • H2 Frequently Asked Questions
  • H4 Can I claim on my own? skipped
  • H4 I had multiple cars, can I claim for them all?
  • H4 How much will I get?
  • H4 What documentation do I need to provide?
  • H4 Which dealers/introducers/banks have been mis-selling?
  • H4 What does No Win, No Fee mean?
  • H4 How can I tell if I’m eligible?
  • H2 Key Milestones of PCP Claims So Far
  • H5 Early Mis-Selling and Ombudsman Limitations skipped
  • H5 Consumer Concerns Begin
  • H5 Financial Conduct Authority (FCA) Investigation
  • H5 FCA Changes Commission Rules
  • H5 FCA Launches Comprehensive Investigation
  • H5 Lloyds Prepares Compensation Fund
  • H5 FCA Delays Investigation Conclusion
  • H5 Landmark Court of Appeal Ruling
  • H5 FCA Extends Deadline for All Commission Complaints
  • H5 Supreme Court Rejects Chancellor’s Intervention in Appeal Case
  • H5 More Lenders Set Aside Money for Potential Compensation
  • H5 UK Supreme Court Hears Appeal in Landmark Case
  • H5 Ford Sets Aside £61M to Cover Potential Costs
  • H5 Santander Considers Reshaping Car Finance Division
  • H5 FCA Provides Update on Potential Redress Scheme
  • H5 Supreme Court Partially Overturns Court of Appeal Ruling
  • H5 The FCA Is Seeking to Consult on a Redress Scheme
  • H5 The FCA Launches the Consultation of a Redress Scheme
  • H5 Lenders Boost Their Compensation Funds
  • H5 The FCA Provides an Update on the Consultation
  • H5 The FCA Closes Consultation on a Redress Scheme
  • H5 The FCA Will Lift Complaint Response Deadline on 31 May 2026
  • H5 Santander UK Raises Redress Provision to £461m
  • H5 In-House Lenders Could Be Exempt From Redress Scheme
  • H5 FCA Confirms Mass Redress Scheme
  • H5 MotoNovo Finance Owner Seeks to Exit UK Market
  • H5 Close Brothers Says £320m Costs Can Be 'Comfortably Absorbed'
  • H5 Lloyds Won’t Launch a Legal Challenge
  • H2 Latest News
  • H3 Car Finance Compensation: What the Legal Challenge Means for You
  • H3 The Wait Is Over: UK’s Final Car Finance Compensation Scheme Has Been Confirmed
  • H3 FCA Outlines How Proposed Motor Finance Compensation Scheme Could Work
  • H3 The Economic Case for Full Car Finance Redress in the UK
  • H3 FCA Pushes Motor Finance Deadline as Work on Redress Scheme Picks Up Pace
  • H3 Banks Push Back Against the FCA’s Car Finance Redress — But Can They Really Stop It?
  • H3 Lloyds’ Profits Slide as Car Finance Costs Catch Up with the Bank
  • H3 Barclays Near-Quadruples the Money It Has Set Aside for Motor Finance Repayments

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

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

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
C
Favicon & Branding
Action
5 icon(s) detected
REVIEW
5 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: PCP Claim UK
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name PCP Claim UK 192×192 icon 512×512 icon Start URL Display Mode standalone
Name PCP Claim UK Display Mode standalone Theme Color #665D8C Background Color #ffffff Icons 2 icon(s)
B
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 20 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 PCP Claims: Get Spec…3.51:13.0:1
#000000
#665D8C
Pass
h2 How Have I Been Mis-…3.27:13.0:1
#000000
#605986
Pass
h2 Frequently Asked Que…3.27:13.0:1
#000000
#605986
Pass
h2 Key Milestones of PC…3.27:13.0:1
#000000
#605986
Pass
h2 Latest News3.27:13.0:1
#000000
#605986
Pass
h3 No Win, No Fee3.29:13.0:1
#000000
#615987
Pass
h3 The Claims Experts3.27:13.0:1
#000000
#605986
Pass
h3 Knowledgeable Handle…3.27:13.0:1
#000000
#605986
Pass
h3 Around-the-Clock Sup…3.27:13.0:1
#000000
#605986
Pass
h3 of the below apply, …3.27:13.0:1
#000000
#605986
Pass
h3 Step 1.3.27:13.0:1
#000000
#605986
Pass
h3 Step 2.3.27:13.0:1
#000000
#605986
Pass
h3 Step 3.3.27:13.0:1
#000000
#605986
Pass
h3 Step 4.3.27:13.0:1
#000000
#605986
Pass
h3 PCP Finance Claims3.27:13.0:1
#000000
#605986
Pass
h3 HP Finance Claims3.27:13.0:1
#000000
#605986
Pass
h3 Mass Redress Scheme …3.27:13.0:1
#000000
#605986
Pass
h3 We Understand Your R…3.27:13.0:1
#000000
#605986
Pass
h3 A Dedicated and Expe…3.27:13.0:1
#000000
#605986
Pass
h3 Check Your Eligibili…3.27:13.0:1
#000000
#605986
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 5 failing, 24 passed
REVIEW
85

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

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
High Interest Rates div.col-lg-9 > div#v-pills-tabContent > div#v-pills-high-interest-rates > div#v-collapse-heading-high-interest-rates
Unfair Commission Fees div.col-lg-9 > div#v-pills-tabContent > div#v-pills-unfair-commission-fees > div#v-collapse-heading-unfair-commission-fees
Lack of Affordability Checks div.col-lg-9 > div#v-pills-tabContent > div#v-pills-lack-of-affordability-checks > div#v-collapse-heading-lack-of-affordability-checks
Not Disclosing Relationships div.col-lg-9 > div#v-pills-tabContent > div#v-pills-not-disclosing-relationships > div#v-collapse-heading-not-disclosing-relationships

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
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot
div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot
div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot
div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot
div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot
div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot
div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot
div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot
div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot div.owl-wrap > div#newsCarousel > div.owl-dots > button.owl-dot

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
CHECK NOW div.container > div.row > div.content-col > a.cta
CHECK NOW div.point > div.content-col > div.in > a.cta
car finance claims div.in > p > a > strong
CHECK NOW div.point > div.content-col > div.in > a.cta
confirmed div.in > p > a > strong
CHECK NOW div.point > div.content-col > div.in > a.cta
Unfair Commission Fees div#v-pills-tabContent > div#v-pills-unfair-commission-fees > div#v-collapse-heading-unfair-commission-fees > a
Lack of Affordability Checks div#v-pills-tabContent > div#v-pills-lack-of-affordability-checks > div#v-collapse-heading-lack-of-affordability-checks > a
Not Disclosing Relationships div#v-pills-tabContent > div#v-pills-not-disclosing-relationships > div#v-collapse-heading-not-disclosing-relationships > a
Check if you’re eligible to claim in minutes section.missold > div.container > div.missold__ctawrap > h3.headline
PCP Claim UK is a trading style of AM1 Claims Management Limited (AM1); this si… div.container > div.footer__whitebox > div.footer__disclaimer > p
AM1 Claims Management Limited uses Elmwood Law Limited (ELL) to fulfil claims s… div.container > div.footer__whitebox > div.footer__disclaimer > p
You can claim for free without using a claims management company by contacting … div.container > div.footer__whitebox > div.footer__disclaimer > p
For more information on the FCA's car finance investigation, click here. div.container > div.footer__whitebox > div.footer__disclaimer > p
AM1 Claims Management Limited does not charge customers for its free eligibilit… div.container > div.footer__whitebox > div.footer__disclaimer > p
AM1 Claims Management may refer your claim to a third party, such as a law firm… div.container > div.footer__whitebox > div.footer__disclaimer > p
*In successful cases, Elmwood Law Limited charges fees of 18% to 36% (including… div.container > div.footer__whitebox > div.footer__disclaimer > p

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
No Win, No Fee Read More div.owl-item > div.usp > div.top > h3
Can I claim on my own? div.col-xl-8 > div.faq-loop > div.faq-card > h4.--header
Early Mis-Selling And Ombudsman Limitations div.col-md-10 > div.timeline > div.timeline-item > h5.my20

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Read More body.home > main.page-wrap > div.section-timeline > button.readmore-toggle
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
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 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
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
`[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.
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.
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
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 Text Quality
All 64 heading(s) have substantive, well-formed text
PASS
All 64 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 26 images OK
PASS
All 26 images OK
Info::
5 decorative image(s) correctly marked
Info::
21 image(s) with good alt text
26 images 21 good alt text 5 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
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
Info::
No form controls on this page
A+
Document Language
Lang attribute set to "en-GB"
PASS
Lang attribute set to "en-GB"
Info::
<html lang="en-GB"> is set and valid
Got: en-GB
A+
Tabindex Anti-Patterns
2 explicit tabindex attribute(s) checked, no anti-patterns
PASS
2 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 253 visible text node(s) render at >= 12 CSS pixels
PASS
All 253 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback