Skip to content
https://mlb.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
D
Alt Text Quality
Action
9 of 298 images have issues
FIX
9 of 298 images have issues
Critical::
9 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
42 decorative image(s) correctly marked
Info::
247 image(s) with good alt text
298 images 247 good alt text 42 decorative 9 missing
IssueCount
missing9 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
404 Error Page
Action
HTTP 404, custom page
FIX
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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::
4 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 4 <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
17 landmarks
REVIEW
17 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
3 of 4 <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
Heading Hierarchy
56 headings
REVIEW
56 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 The Rivalry is back. Here's everything you need to know
  • H2 Latest News
  • H2 ABS Challenge System
  • H2 Suggested Follows
  • H2 Popular
  • H2 Latest Highlights
  • H2 Vladimir Guerrero Jr.'s two-run homer (2)
  • H2 Dalton Rushing's two-homer game against Rockies
  • H2 Max Muncy's two-homer game
  • H2 Real Fast: Monday's best in 60 seconds
  • H2 Dylan Cease strikes out 12 for first win with Blue Ja
  • H2 Leody Taveras' grand slam (2)
  • H2 Cal Raleigh's solo home run (3)
  • H2 Dansby Swanson's three-run homer (5)
  • H2 FastCast: Monday's best in < 15 minutes
  • H2 4/20/26: Top 5 Plays of the Day
  • H2 Elly De La Cruz dives, throws out Caminero at first
  • H2 Matt Olson's two-run home run (6)
  • H2 Standings
  • H3 AL East
  • H3 AL Central
  • H3 AL West
  • H3 NL East
  • H3 NL Central
  • H3 NL West
  • H2 J-Ram no stranger to Player of Week nods, but Hoerner gets his first
  • H2 It's all glove between these two young Dominican stars
  • H2 MLB swings big for kids with MLB Clubhouse
  • H2 Star Watch
  • H2 Blue Jays hit the road for a 5-plus hour ... bus ride?
  • H2 The latest quiz from Sporcle and MLB
  • H2 Hug tugs at the heartstrings after toss into the stands
  • H2 This on-field ballpark proposal hit a little different
  • H2 1 early-season development each team can believe in
  • H2 Prospects
  • H2 The dog days are here and it's not even summer yet
  • H2 You won't believe how this 21-inning college game ended
  • H2 Injury blow for Dodgers; time to believe in Braves
  • H2 ICYMI
  • H2 Is this one of the best rookie classes ever? We rank ROY contenders
  • H2 Can these early stats leaders stay ahead of the field?
  • H2 Trading homers – and history!
  • H2 Latest News
  • H2 ABS Challenge System
  • H2 Privacy Preference Center
  • H3 Your Privacy
  • H3 Strictly Necessary Cookies
  • H3 Functional Cookies
  • H3 Performance Cookies
  • H3 Targeting Cookies
  • H4 Your Privacy
  • H4 Strictly Necessary Cookies
  • H4 Functional Cookies
  • H4 Performance Cookies
  • H4 Targeting Cookies
  • H3 Cookie List

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

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 74/100 — 8 failing, 24 passed
REVIEW
74

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
Monday's highlight reel Back-to-back home runs from 2026 Creatures on the loo… div.l-grid__col > div.l-grid__content > div.styles__TabsContainer-sc-158k888-0 > div#tabpanel_popular
This Sal Stewart kid can MASH Judge is back doing what he does best ... Trout… div.l-grid__col > div.l-grid__content > div.styles__TabsContainer-sc-158k888-0 > div#tabpanel_star_watch
Prospect Team of the Week: April 2-12 MLB's No. 1 prospect is here This trio … div.l-grid__col > div.l-grid__content > div.styles__TabsContainer-sc-158k888-0 > div#tabpanel_prospects
Slam season is in full bloom Too early to crown a HR robbery king? Fresh face… div.l-grid__col > div.l-grid__content > div.styles__TabsContainer-sc-158k888-0 > div#tabpanel_icymi

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
NEWS li.styles__StyledNavItem-sc-87c9f2fb-3 > div.styles__StyledNavItemInner-sc-87c9f2fb-0 > a.styles__StyledNavItemLink-sc-87c9f2fb-1 > span.styles__StyledNavItemText-sc-87c9f2fb-2
SCORES li.styles__StyledNavItem-sc-87c9f2fb-3 > div.styles__StyledNavItemInner-sc-87c9f2fb-0 > a.styles__StyledNavItemLink-sc-87c9f2fb-1 > span.styles__StyledNavItemText-sc-87c9f2fb-2
SCHEDULE li.styles__StyledNavItem-sc-87c9f2fb-3 > div.styles__StyledNavItemInner-sc-87c9f2fb-0 > a.styles__StyledNavItemLink-sc-87c9f2fb-1 > span.styles__StyledNavItemText-sc-87c9f2fb-2
STATS li.styles__StyledNavItem-sc-87c9f2fb-3 > div.styles__StyledNavItemInner-sc-87c9f2fb-0 > a.styles__StyledNavItemLink-sc-87c9f2fb-1 > span.styles__StyledNavItemText-sc-87c9f2fb-2
MLB Privacy Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a
Terms of Use Agreement div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a
Cookies Settings div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-pc-btn-handler

These are opportunities to improve the legibility of your content.

Names and labels

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.p-image > div.p-image__image > a > img.lazyload div.p-image > div.p-image__image > a > img.lazyload
div#w7e-clipping-2-1 > div > div#w7e-platform-21-1 > img div#w7e-clipping-2-1 > div > div#w7e-platform-21-1 > img
div#google_ads_iframe_/2605/mlb.mlb/xhomepage/phone/android_1__container__ > div#w7e-platform-2-1 > div#w7e-platform-116-1 > img div#google_ads_iframe_/2605/mlb.mlb/xhomepage/phone/android_1__container__ > div#w7e-platform-2-1 > div#w7e-platform-116-1 > img

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
body#forge-pagebuilder_index > iframe#Spotible_creative.spotible.com body#forge-pagebuilder_index > iframe#Spotible_creative.spotible.com

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.l-grid__content > div.p-image > div.p-image__image > a div.l-grid__content > div.p-image > div.p-image__image > 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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
© 2026 MLB Advanced Media, LP. All rights reserved. Terms of Use Privacy Policy… footer#react-footer > section.styles__StyledMainContent-sc-1d2dd0c0-1 > div.styles__StyledLegalLinks-sc-348155a5-0 > ul.styles__StyledLegalLinksList-sc-348155a5-1

These are opportunities to improve the experience of reading tabular or list data using 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
Apple TV div.StatusLayerstyle__StatusLayerWrapper-sc-mdqr4z-0 > div.GameInfoLayerstyle__GameInfoLayerWrapper-sc-1f4mugx-0 > div.GameInfoLayerstyle__PromotionLabelWrapper-sc-1f4mugx-1 > a.linkstyle__AnchorElement-sc-5g3tf0-0
Apple TV div.StatusLayerstyle__StatusLayerWrapper-sc-mdqr4z-0 > div.GameInfoLayerstyle__GameInfoLayerWrapper-sc-1f4mugx-0 > div.GameInfoLayerstyle__PromotionLabelWrapper-sc-1f4mugx-1 > a.linkstyle__AnchorElement-sc-5g3tf0-0

These items highlight common accessibility best practices.

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
APR 20 div.MiniScoreboardGridstyle__CarouselWrapper-sc-n9p1yy-8 > div.MiniScoreboardGridstyle__OverflowViewportRow-sc-n9p1yy-0 > div.MiniScoreboardStickyDatestyle__StickyDateWrapper-sc-1mgbvud-0 > a.ClickthroughWrapper-sc-12my6di-0
APR 21 div.MiniScoreboardGridstyle__CarouselWrapper-sc-n9p1yy-8 > div.MiniScoreboardGridstyle__OverflowViewportRow-sc-n9p1yy-0 > div.MiniScoreboardStickyDatestyle__StickyDateWrapper-sc-1mgbvud-0 > a.ClickthroughWrapper-sc-12my6di-0
APR 22 div.MiniScoreboardGridstyle__CarouselWrapper-sc-n9p1yy-8 > div.MiniScoreboardGridstyle__OverflowViewportRow-sc-n9p1yy-0 > div.MiniScoreboardStickyDatestyle__StickyDateWrapper-sc-1mgbvud-0 > a.ClickthroughWrapper-sc-12my6di-0
APR 23 div.MiniScoreboardGridstyle__CarouselWrapper-sc-n9p1yy-8 > div.MiniScoreboardGridstyle__OverflowViewportRow-sc-n9p1yy-0 > div.MiniScoreboardStickyDatestyle__StickyDateWrapper-sc-1mgbvud-0 > a.ClickthroughWrapper-sc-12my6di-0
APR 24 div.MiniScoreboardGridstyle__CarouselWrapper-sc-n9p1yy-8 > div.MiniScoreboardGridstyle__OverflowViewportRow-sc-n9p1yy-0 > div.MiniScoreboardStickyDatestyle__StickyDateWrapper-sc-1mgbvud-0 > a.ClickthroughWrapper-sc-12my6di-0
○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
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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.
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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 9 controls have issues
PASS
1 of 9 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
8 control(s) properly labeled
9 controls
8 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#chkbox-idcheckboxcheckbox labelfor/id
#g-recaptcha-response-100000textarea(none)none

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

<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

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 The Rivalry is back.…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Latest News21.00:13.0:1
#000000
#FFFFFF
Pass
h2 ABS Challenge System21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Suggested Follows21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Latest Highlights21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Vladimir Guerrero Jr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Dalton Rushing's two…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Max Muncy's two-home…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Real Fast: Monday's …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Dylan Cease strikes …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Leody Taveras' grand…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Cal Raleigh's solo h…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Dansby Swanson's thr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 FastCast: Monday's b…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 4/20/26: Top 5 Plays…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Elly De La Cruz dive…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Matt Olson's two-run…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Standings21.00:13.0:1
#000000
#FFFFFF
Pass
h2 J-Ram no stranger to…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 It's all glove betwe…21.00:13.0:1
#000000
#FFFFFF
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