Skip to content
https://pgatour.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) 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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

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

D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 icon(s) detected
Info::
favicon.ico present at site root
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'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
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 PGATOUR.COM - Official Home of Golf and the FedExCup - PGA TOUR ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
B
Lighthouse Accessibility Audits
Score 84/100 — 5 failing, 23 passed
REVIEW
84

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

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div.ScrollableContainer_scrollableContainer__mQpMl > div.ScrollableContainer_scrollableContainerCustomTrack__lpgRS > div.ScrollableContainer_scrollableContainerCustomThumb__X4yAh div > div.ScrollableContainer_scrollableContainer__mQpMl > div.ScrollableContainer_scrollableContainerCustomTrack__lpgRS > div.ScrollableContainer_scrollableContainerCustomThumb__X4yAh
div > div.ScrollableContainer_scrollableContainer__mQpMl > div.ScrollableContainer_scrollableContainerCustomTrack__lpgRS > div.ScrollableContainer_scrollableContainerCustomThumb__X4yAh div > div.ScrollableContainer_scrollableContainer__mQpMl > div.ScrollableContainer_scrollableContainerCustomTrack__lpgRS > div.ScrollableContainer_scrollableContainerCustomThumb__X4yAh

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
NEW blaze-widget-item#blaze-widget-item-1 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-2 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-3 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-4 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-5 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-6 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-7 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-8 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-9 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-10 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-11 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-12 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-13 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-14 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-15 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-16 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-17 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-18 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-19 > blaze-div > blaze-div > blaze-chip
NEW blaze-widget-item#blaze-widget-item-20 > blaze-div > blaze-div > blaze-chip

These are opportunities to improve the legibility of your content.

Best practices

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

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Favorite div.chakra-stack > div.chakra-stack > div.chakra-stack > button.chakra-button
Latest div.LinkBox_container__sbTeW > div.MetaRow_container__YNEN8 > div.MetaRow_large__hkcqy > a.Link_link__FRjoV
Horses for Courses div.LinkBox_container__sbTeW > div.MetaRow_container__YNEN8 > div.MetaRow_large__hkcqy > a.Link_link__FRjoV
Latest div.LinkBox_container__sbTeW > div.MetaRow_container__YNEN8 > div.MetaRow_large__hkcqy > a.Link_link__FRjoV
Interviews div.LinkBox_container__sbTeW > div.MetaRow_container__YNEN8 > div.MetaRow_large__hkcqy > a.Link_link__FRjoV
Interviews div.LinkBox_container__sbTeW > div.MetaRow_container__YNEN8 > div.MetaRow_large__hkcqy > a.Link_link__FRjoV
Interviews div.LinkBox_container__sbTeW > div.MetaRow_container__YNEN8 > div.MetaRow_large__hkcqy > a.Link_link__FRjoV

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
Search div.NavBar_mobileNavBar__T4lCA > header.css-blm0vd > div.css-k0j3re > button.css-wt1w6c
Menu div.NavBar_mobileNavBar__T4lCA > header.css-blm0vd > div.css-k0j3re > button.css-182by4h
WEATHER BY Wind direction SE 13 MPH Humidity 67% Day Partly Cloudy 75°F div.css-186b4kg > div.WeatherBanner_banner__swIbL > div.WeatherBanner_container__perrO > div.WeatherBanner_weatherContent__t3OqH
NEW Five intriguing teams at Zurich Classic blaze-widget-item#blaze-widget-item-1
NEW Ranking teams at Zurich Classic blaze-widget-item#blaze-widget-item-2
NEW First Look: Zurich Classic of New Orleans blaze-widget-item#blaze-widget-item-3
NEW Best shots from Harbour Town blaze-widget-item#blaze-widget-item-4
NEW Round 4 from Harbour Town blaze-widget-item#blaze-widget-item-5
NEW Five takeaways from RBC Heritage blaze-widget-item#blaze-widget-item-6
NEW Top bets that cashed at RBC Heritage blaze-widget-item#blaze-widget-item-7
NEW Round 3 from Harbour Town blaze-widget-item#blaze-widget-item-8
NEW Round 2 at Harbour Town blaze-widget-item#blaze-widget-item-9
NEW Round 1 from RBC Heritage blaze-widget-item#blaze-widget-item-10
NEW Hear what players are saying at RBC Heritage blaze-widget-item#blaze-widget-item-11
NEW The Five: Biggest post-Masters questions blaze-widget-item#blaze-widget-item-12
NEW Check out recent winners at RBC Heritage blaze-widget-item#blaze-widget-item-13
NEW See who tops RBC Heritage field rankings blaze-widget-item#blaze-widget-item-14
NEW Our fantasy picks for RBC Heritage blaze-widget-item#blaze-widget-item-15
NEW Storylines from RBC Heritage blaze-widget-item#blaze-widget-item-16
NEW Round 4: The Masters blaze-widget-item#blaze-widget-item-17
NEW McIlroy's best shots of 2026 blaze-widget-item#blaze-widget-item-18
NEW Top bets that hit at the Masters blaze-widget-item#blaze-widget-item-19
NEW Round 3: The Masters blaze-widget-item#blaze-widget-item-20
○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
●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
●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 have a discernible name
●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
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○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
○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.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A+
Heading Hierarchy
2 headings
PASS
2 headings
Info::
Single H1 present
  • H1 403 ERROR
  • H2 The request could not be satisfied.
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Color Contrast (Screenshot)
6 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.

6 pass
Show all checked elements (6)
ElementRatioRequiredFGBGResult
h1 403 ERROR21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The request could no…21.00:13.0:1
#000000
#FFFFFF
Pass
title ERROR: The request c…21.00:14.5:1
#000000
#FFFFFF
Pass
body Request blocked. We …21.00:14.5:1
#000000
#FFFFFF
Pass
body If you provide conte…21.00:14.5:1
#000000
#FFFFFF
Pass
pre Generated by cloudfr…21.00:14.5: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