Skip to content
https://sfexaminer.com

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
D
Form Accessibility
Action
7 of 9 controls have issues
FIX
7 of 9 controls have issues
Critical::
6 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit" name="logout">; <input type="submit">; <input type="submit" name="logout">; <input type="submit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q">
Info::
2 control(s) properly labeled
9 controls
2 labeled
1 placeholder only
6 unlabeled
ControlTypeLabelMethod
#site-search-2535100-termtextSite searchfor/id
#site-search-2535082-termtextSite searchfor/id
qtext(Search...)placeholder only
inputsubmit(none)none
inputsubmit(none)none
logoutsubmit(none)none
logoutsubmit(none)none
inputsubmit(none)none
#g-recaptcha-response-100000textarea(none)none

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

<input type="submit">; <input type="submit" name="logout">; <input type="submit">; <input type="submit" name="logout">; <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="q">

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

F
404 Error Page
Action
HTTP 429, bare page
FIX
HTTP 429, bare page
Warning::
Unexpected status code: HTTP 429
Expected HTTP 404 but received 429. This may confuse search engine crawlers.
Got: HTTP 429
Warning::
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 429 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Landmark Structure
Action
8 landmarks
REVIEW
8 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) ASIDE "Left Main Menu" CONTENTINFO footer

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

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

B
Heading Hierarchy
87 headings, 2 skip(s)
REVIEW
87 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H4 Log In Using Your Account
  • H2 Local startup offers promise of clean power for SF
  • H5 Troy Wolverton skipped
  • H4 Services for SF seniors, disabled people could face budget cuts
  • H5 Natalia Gurevich
  • H4 'Hamnet' gets Royal Shakespeare Company treatment in SF
  • H4 SF tech millionaire's spending laps that of opponents in race for Congress
  • H5 Patrick Hoge
  • H4 Proposed cuts to health programs spur community outrage
  • H5 Natalia Gurevich
  • H4 From stage to street: An elite opera singer's addiction struggle in The City
  • H4 Why every San Franciscan should know the name Luis Valdez
  • H5 OUR PARTNERS
  • H4 A Weekend in Luxury: Mother’s Day Brunch at Hotel Nikko
  • H4 Foes of changes to Overpaid Executive Tax add $2 million to fight it
  • H5 Patrick Hoge
  • H4 SF hands reins of street outreach teams to different agency
  • H5 Natalia Gurevich
  • H4 New state bill aims to cancel medical debt for low-income Californians
  • H5 Natalia Gurevich
  • H3 From the New York Times
  • H4 Virginia passes new map, lifting Democrats' midterm chances
  • H4 Rare tornado reported near Fresno as storm moves through California
  • H4 Tim Cook will step down as Apple CEO
  • H3 FORUM
  • H3 Arbitrary vetoes of new housing create a true moral crisis
  • H3 Our Partners
  • H4 A Weekend in Luxury: Mother’s Day Brunch at Hotel Nikko
  • H4 Making Progress on Energy Costs Without Compromising Safety
  • H4 How Luxury Senior Communities Are Redefining What Comes Next
  • H4 A Full-service Health Plan to Empower Seniors’ Independence
  • H3 Inspiring Women
  • H3 Mary Furlong
  • H3 Denise Hale
  • H3 Lisa Presta
  • H3 Jennifer Murphy-Ellamar
  • H3 Public Health
  • H4 SF hands reins of street outreach teams to different agency
  • H5 Natalia Gurevich
  • H4 New state bill aims to cancel medical debt for low-income Californians
  • H5 Natalia Gurevich
  • H4 San Francisco reports first infant measles case in 7 years
  • H5 Natalia Gurevich
  • H4 State abortion fund for low-income patients to run out of money this year
  • H5 Natalia Gurevich
  • H3 Reporter At Large
  • H3 In The City with Patrick Hoge
  • H4 Foes of changes to Overpaid Executive Tax add $2 million to fight it
  • H4 SF tech millionaire's spending laps that of opponents in race for Congress
  • H4 Coalition unveils a $25 million fund to fill downtown vacancies
  • H3 Marketplace
  • H4 Craig Fontaine Ashton: Northern California Personal Injury Lawyer and Podcaster
  • H4 Best Dispensaries in Sacramento: 10 Top Picks
  • H4 Combating the 2026 Burnout Epidemic: Strategies for San Francisco Professionals
  • H4 Critical Training Solution Explains the Training Mindset: Preparation, Clarity, and Controlled Response
  • H3 Technology
  • H2 Troy Wolverton
  • H3 Local startup offers promise of clean power for SF
  • H4 New East Bay nonprofit aims to jump-start battery manufacturing in state
  • H4 OpenAI, Anthropic and SpaceX’s IPOs could be a balm for state’s budget woes
  • H3 Latest e-Edition
  • H4 San Francisco
  • H3 Local Events
  • H3 CULTURE
  • H1 From stage to street: An elite opera singer's addiction struggle in The City
  • H4 Why every San Franciscan should know the name Luis Valdez skipped
  • H4 'Hamnet' gets Royal Shakespeare Company treatment in SF
  • H4 Grateful Dead's vault recordings find new online home
  • H3 SIPS IN THE CITY
  • H4 With Natalia Gurevich
  • H4 The Valley Club is where you can be ‘the star of your own movie’
  • H4 Bix continues to ‘throw a party every night’
  • H3 The Social Set
  • H4 YBCA exhibitions spotlight identity, history and community in San Francisco
  • H3 Around the Web
  • H4 How Long Does $1 Million Last After 60?
  • H4 Should You Buy an Electric Car?
  • H4 Test Your Hearing From The Comfort of Your Home
  • H4 We've Got Your Eyes Covered - Find Your Perfect Pair!
  • H4 Get Personalized Mortgage Advice Close to Home
  • H4 Take on a Challenge: Make Pasta Al Limone at Home
  • H4 Is My Space a Good Fit for Airbnb?
  • H4 Look for Any High School Yearbook, It's Free!
  • H4 8 Reasons Your Car Insurance Rate Changes
  • H4 Sections
  • H4 Services
  • H4 Browser Compatibility

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
Lighthouse Accessibility Audits
Score 85/100 — 5 failing, 25 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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search div.navbar-header > ul.hidden-md > li.search-form-dropdown > a.dropdown-toggle

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.

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
OUR PARTNERS div.clearfix > div.block-overline > div.block-overline-inner > h5
Accept all div.Card-buoy__sc-1s2p2gv-0 > div.Card__CardHeader-buoy__sc-1s2p2gv-1 > div.Frame-buoy__sc-1d4hofp-0 > button.Button__StyledButton-buoy__sc-a1qza5-0
PURPOSES div.Card-buoy__sc-1s2p2gv-0 > div.Frame-buoy__sc-1d4hofp-0 > div.Pills__StyledPills-buoy__sc-pti2cl-0 > button.Pills__StyledPill-buoy__sc-pti2cl-1
1725 PARTNERS div.Card-buoy__sc-1s2p2gv-0 > div.Frame-buoy__sc-1d4hofp-0 > div.Pills__StyledPills-buoy__sc-pti2cl-0 > button.Pills__StyledPill-buoy__sc-pti2cl-1

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
Troy Wolverton div.media-list > div.media > div.media-body > h5.media-heading
Why every San Franciscan should know the name Luis Valdez div.card-container > div.card-body > div.card-headline > h4.tnt-headline

These are opportunities to improve keyboard navigation in your application.

Names and labels

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#tncms-block-2565382 > section#block-2565382 > div.block > a div#tncms-block-2565382 > section#block-2565382 > div.block > a

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Technology div.card-body > div.card-labels > div.card-label-section > a.tnt-section-tag
The City div.card-body > div.card-labels > div.card-label-section > a.tnt-section-tag
Natalia Gurevich div.media > div.media-body > h5.media-heading > a.tnt-user-profile-link
Culture div.card-body > div.card-labels > div.card-label-section > a.tnt-section-tag
Politics div.card-body > div.card-labels > div.card-label-section > a.tnt-section-tag
Patrick Hoge div.media > div.media-body > h5.media-heading > a.tnt-user-profile-link
San Francisco News div.card-body > div.card-labels > div.card-label-section > a.tnt-section-tag
Culture div.card-body > div.card-labels > div.card-label-section > a.tnt-section-tag
Culture div.card-body > div.card-labels > div.card-label-section > a.tnt-section-tag
Politics div.card-body > div.card-labels > div.card-label-section > a.tnt-section-tag
Patrick Hoge div.media > div.media-body > h5.media-heading > a.tnt-user-profile-link
Public Health div.card-body > div.card-labels > div.card-label-section > a.tnt-section-tag
Public Health div.card-body > div.card-labels > div.card-label-section > a.tnt-section-tag
Natalia Gurevich div.media > div.media-body > h5.media-heading > a.tnt-user-profile-link
Natalia Gurevich div.media > div.media-body > h5.media-heading > a.tnt-user-profile-link
Natalia Gurevich div.media > div.media-body > h5.media-heading > a.tnt-user-profile-link
Natalia Gurevich div.media > div.media-body > h5.media-heading > a.tnt-user-profile-link
Culture div.card-body > div.card-labels > div.card-label-section > a.tnt-section-tag
Culture div.card-body > div.card-labels > div.card-label-section > a.tnt-section-tag
Pop music div.card-body > div.card-labels > div.card-label-section > a.tnt-section-tag
Politics div#tncms-region-nav-footer-col-one-nav > ul#footer-col-one-nav_menu > li > a.nav-link
Technology div#tncms-region-nav-footer-col-one-nav > ul#footer-col-one-nav_menu > li > a.nav-link
Climate div#tncms-region-nav-footer-col-one-nav > ul#footer-col-one-nav_menu > li > a.nav-link
Housing div#tncms-region-nav-footer-col-one-nav > ul#footer-col-one-nav_menu > li > a.nav-link
Transit div#tncms-region-nav-footer-col-one-nav > ul#footer-col-one-nav_menu > li > a.nav-link
Education div#tncms-region-nav-footer-col-one-nav > ul#footer-col-one-nav_menu > li > a.nav-link
Forum div#tncms-region-nav-footer-col-one-nav > ul#footer-col-one-nav_menu > li > a.nav-link
Sports div#tncms-region-nav-footer-col-one-nav > ul#footer-col-one-nav_menu > li > a.nav-link
Culture div#tncms-region-nav-footer-col-one-nav > ul#footer-col-one-nav_menu > li > a.nav-link
Real Estate div#tncms-region-nav-footer-col-one-nav > ul#footer-col-one-nav_menu > li > a.nav-link
Contact Us div#tncms-region-nav-footer-col-two-nav > ul#footer-col-two-nav_menu > li > a.nav-link
Careers div#tncms-region-nav-footer-col-two-nav > ul#footer-col-two-nav_menu > li > a.nav-link
Advertise div#tncms-region-nav-footer-col-two-nav > ul#footer-col-two-nav_menu > li > a.nav-link
Archives div#tncms-region-nav-footer-col-two-nav > ul#footer-col-two-nav_menu > li > a.nav-link
Events div#tncms-region-nav-footer-col-two-nav > ul#footer-col-two-nav_menu > li > a.nav-link
Newsletters div#tncms-region-nav-footer-col-two-nav > ul#footer-col-two-nav_menu > li > a.nav-link
Our Partners div#tncms-region-nav-footer-col-two-nav > ul#footer-col-two-nav_menu > li > a.nav-link
Search div#tncms-region-nav-footer-col-two-nav > ul#footer-col-two-nav_menu > li > a.nav-link
Weather div#tncms-region-nav-footer-col-two-nav > ul#footer-col-two-nav_menu > li > a.nav-link

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
●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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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
○`<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.
○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.
○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+
Alt Text Quality
1 of 111 images have issues
PASS
1 of 111 images have issues
Warning::
1 image(s) with generic alt text
Info::
48 decorative image(s) correctly marked
Info::
62 image(s) with good alt text
111 images 62 good alt text 48 decorative 1 generic
IssueCount
generic1 image(s)
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
h3 From the New York Ti…18.96:13.0:1
#000000
#EDF4FD
Pass
h3 Around the Web18.96:13.0:1
#000000
#EDF4FD
Pass
title San Francisco Examin…15.48:14.5:1
#000000
#D1DFEC
Pass
a Skip to main content15.48:14.5:1
#000000
#D1DFEC
Pass
label Site search15.48:14.5:1
#000000
#D1DFEC
Pass
span Search15.48:14.5:1
#000000
#D1DFEC
Pass
a Sign Up15.48:14.5:1
#000000
#D1DFEC
Pass
a Log In12.57:14.5:1
#000000
#BCCAD7
Pass
a Dashboard15.48:14.5:1
#000000
#D1DFEC
Pass
a Logout12.57:14.5:1
#000000
#BCCAD7
Pass
li My Account17.41:14.5:1
#000000
#E2EBF3
Pass
a Dashboard20.48:14.5:1
#000000
#FCFCFD
Pass
a Profile20.48:14.5:1
#000000
#FCFCFD
Pass
a Saved items20.48:14.5:1
#000000
#FCFCFD
Pass
a Logout20.48:14.5:1
#000000
#FCFCFD
Pass
span Facebook20.48:14.5:1
#000000
#FCFCFD
Pass
span Twitter20.48:14.5:1
#000000
#FCFCFD
Pass
span Instagram20.48:14.5:1
#000000
#FCFCFD
Pass
a News20.48:14.5:1
#000000
#FCFCFD
Pass
a Business20.48:14.5:1
#000000
#FCFCFD
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