Skip to content
https://tampabay.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
D
Landmark Structure
Action
3 landmarks
FIX
3 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::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
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 (missing!) NAV MAIN (missing!) 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

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

F
Alt Text Quality
Action
5 of 74 images have issues
FIX
5 of 74 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
1 image(s) with filename as alt text
Warning::
1 image(s) with generic alt text
Info::
22 image(s) with alt text over 125 characters
Info::
47 image(s) with good alt text
74 images 47 good alt text 2 generic 3 missing
IssueCount
missing3 image(s)
filename1 image(s)
generic1 image(s)
too long22 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

D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: App
Info::
192x192 icon present
PWA Install Criteria Not Installable
Name App ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗
Name App Icons 6 icon(s)
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: #228877
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::
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.
C
Heading Hierarchy
Action
32 headings, 1 skip(s)
REVIEW
32 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
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::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Featured
  • H2 Regions
  • H2 Topics
  • H2 (empty)
  • H4 Regions skipped
  • H4 Topics
  • H4 Pro
  • H4 College
  • H4 Other
  • H2 SPORTS
  • H2 VIEWPOINTS
  • H2 POLITICS
  • H2 LATEST
  • H2 BAY MAGAZINE
  • H3 Read the e-Newspaper
  • H3 Read the e-Newspaper Subscribers only
  • H3 Most Read
  • H3 Around the Web
  • H4 Access Low-interest HELOC Funds for Your Home Renovation
  • H4 Take on a Challenge: Make Pasta Al Limone at Home
  • H4 Get Personalized Mortgage Advice Close to Home
  • H4 How Much Money Should You Have Before Hiring a Financial Advisor?
  • H2 DIVE IN
  • H2 Keep up with Tampa Bay’s top headlines
  • H2 You’re all signed up!
  • H2 Contact
  • H2 Account
  • H2 About
  • H2 Advertise
  • H2 Shop
  • H2 More
  • H2 ONLY AVAILABLE FOR SUBSCRIBERS

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

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

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 LinkedIn ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
21 icon(s) detected
REVIEW
21 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Lighthouse Accessibility Audits
Action
Score 77/100 — 7 failing, 25 passed
REVIEW
77

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.

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.nsu__sign-up--visible > div.newsletters-subscribe-form > div > button.button div.nsu__sign-up--visible > div.newsletters-subscribe-form > div > button.button

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.paper-preview-fp__left > div.paper-preview-fp__left-graphic > a > img#paper-preview-fp__i div.paper-preview-fp__left > div.paper-preview-fp__left-graphic > a > img#paper-preview-fp__i
div.footer__segment > div.footer__segment-links > a.footer__florida-public-notices-verified > img div.footer__segment > div.footer__segment-links > a.footer__florida-public-notices-verified > img
body.panelClosed > img#06db9294 body.panelClosed > img#06db9294

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.layout--lg > div > div.raw-html > iframe div.layout--lg > div > div.raw-html > iframe

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.paper-preview-fp__wrapper > div.paper-preview-fp__left > div.paper-preview-fp__left-graphic > a div.paper-preview-fp__wrapper > div.paper-preview-fp__left > div.paper-preview-fp__left-graphic > a
div.footer__links > div.footer__segment > div.footer__segment-links > a.footer__florida-public-notices-verified div.footer__links > div.footer__segment > div.footer__segment-links > a.footer__florida-public-notices-verified

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
Menu div.nav-bar > div#hamburger > button.button > div.hamburger__menu-button
SUBSCRIBE only $3 FOR 3 MONTHS div#sticky-subscribe-banner > a.subscribe-cta > div.banner-inner > span.subscribe-text
SUBSCRIBE a.subscribe-cta > div.banner-inner > span.subscribe-text > span.highlight
$3 FOR 3 MONTHS a.subscribe-cta > div.banner-inner > span.subscribe-text > span.highlight
Search div.mobile-right-rail > div.mrr__button > div.mrr__button__content > div.mrr__button__label
Featured div.mobile-right-rail > div.mrr__button > div.mrr__button__content > div.mrr__button__label
Latest News div.mobile-right-rail > div.mrr__button > div.mrr__button__content > div.mrr__button__label
Most Read div.mobile-right-rail > div.mrr__button > div.mrr__button__content > div.mrr__button__label
ADVERTISEMENT div.vert__header-vert > div.layout--lg > div.vert > span.vert__slug
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

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Menu Close div#top > nav > div.nav-bar > div#hamburger

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
Menu Close div#top > nav > div.nav-bar > div#hamburger
Games & Puzzles div.side-scroller--interior > ul.masthead__list > li.masthead__list-item--tertiary > a.nav__link--gamespuzzles
○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
●`[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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●All heading elements contain content.
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○Uses ARIA roles only on compatible elements
○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
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
qtextsearch queryaria-label
inputtext(Enter email)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text">

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

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 Featured20.48:13.0:1
#000000
#FCFCFD
Pass
h2 Regions18.96:13.0:1
#000000
#EDF4FD
Pass
h2 Topics18.96:13.0:1
#000000
#EDF4FD
Pass
h2 SPORTS18.96:13.0:1
#000000
#EDF4FD
Pass
h2 VIEWPOINTS18.96:13.0:1
#000000
#EDF4FD
Pass
h2 POLITICS18.96:13.0:1
#000000
#EDF4FD
Pass
h2 LATEST18.96:13.0:1
#000000
#EDF4FD
Pass
h2 BAY MAGAZINE18.96:13.0:1
#000000
#EDF4FD
Pass
h2 DIVE IN18.96:13.0:1
#000000
#EDF4FD
Pass
h2 Keep up with Tampa B…18.96:13.0:1
#000000
#EDF4FD
Pass
h2 You’re all signed…18.96:13.0:1
#000000
#EDF4FD
Pass
h2 Contact18.96:13.0:1
#000000
#EDF4FD
Pass
h2 Account18.96:13.0:1
#000000
#EDF4FD
Pass
h2 About18.96:13.0:1
#000000
#EDF4FD
Pass
h2 Advertise18.96:13.0:1
#000000
#EDF4FD
Pass
h2 Shop18.96:13.0:1
#000000
#EDF4FD
Pass
h2 More18.96:13.0:1
#000000
#EDF4FD
Pass
h2 ONLY AVAILABLE FOR S…18.96:13.0:1
#000000
#EDF4FD
Pass
h3 Most Read18.96:13.0:1
#000000
#EDF4FD
Pass
h3 Around the Web18.96:13.0:1
#000000
#EDF4FD
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