Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 2 REVIEW 9 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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

Document Language

Action

Missing <html lang> attribute (WCAG 3.1.1)

FIX

Missing <html lang> attribute (WCAG 3.1.1)

Without `<html lang="...">`, screen readers default to the user's system language even when reading content in a different one -- words get pronounced wrong (English text read with French phonetics, etc.). Add a BCP-47 language tag to the <html> root element.

Tap Target Adequacy

Action

28 tap target(s) too small or too close together

FIX

28 tap target(s) too small or too close together

28 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

404 Error Page

Action

HTTP 429, bare page

FIX

HTTP 429, bare page

Unexpected status code: HTTP 429

Expected HTTP 404 but received 429. This may confuse search engine crawlers.

Got: HTTP 429

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 ✗

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Color Contrast (Screenshot)

Action

8 text elements analyzed, 4 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

4 pass 4 fail WCAG AA 3 pass AA only

p Your IP address has been blocked from ac…

4.48:1

#000000

#6C68CB

needs 4.5:1 (normal text)

16px · top of page (header area)

p Access denied

4.05:1

#000000

#6861BF

needs 4.5:1 (normal text)

16px · above the fold

div If you believe this is an error, please …

3.81:1

#000000

#665DB7

needs 4.5:1 (normal text)

16px · above the fold

a kj@fantasyteamadvice.com

3.67:1

#000000

#655AB4

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (8)

Element	Ratio	Required	FG	BG	Result
h1 Access Denied	4.59:1	3.0:1	#000000	#6C6ACE	Pass
title Access Denied	4.74:1	4.5:1	#000000	#6B6DD2	Pass
div 🚫	4.68:1	4.5:1	#000000	#6B6CD0	Pass
p Your IP address has …	4.48:1	4.5:1	#000000	#6C68CB	Fail
strong Reason:	4.30:1	3.0:1	#000000	#6B65C6	Pass
p Access denied	4.05:1	4.5:1	#000000	#6861BF	Fail
div If you believe this …	3.81:1	4.5:1	#000000	#665DB7	Fail
a kj@fantasyteamadvice…	3.67:1	4.5:1	#000000	#655AB4	Fail

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.

Lighthouse Accessibility Audits

Score 86/100 — 4 failing, 21 passed

REVIEW

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
We use cookies to improve your experience. By clicking "Accept", you agree to o… `body.w-full > div.fixed`

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
Log In `body.w-full > div.site-header > div.flex > a.btn`
Crush daily MLB DFS contests with our advanced lineup optimizer. Get pitcher/hi… `div.py-8 > div.container > div.max-w-4xl > p.text-base`
Six premium tools that give FTA+ members an edge on player props, PrizePicks en… `div.container > div.max-w-6xl > div.text-center > p.text-lg`
Today's best +EV NBA player props ranked by edge. Per-minute projections compar… `div.max-w-6xl > div.grid > div.bg-white/5 > p.text-on-surface-subtle`
Daily NBA MORE/LESS picks with confidence ratings and transparent hit rate trac… `div.max-w-6xl > div.grid > div.bg-white/5 > p.text-on-surface-subtle`
Proprietary EFF, HV, and PROD ratings across L1 through season windows. Compare… `div.max-w-6xl > div.grid > div.bg-white/5 > p.text-on-surface-subtle`
See how every NBA defense performs against each position. Color-coded matchup g… `div.max-w-6xl > div.grid > div.bg-white/5 > p.text-on-surface-subtle`
Complete player pages with per-minute stat projections, live prop lines from 4 … `div.max-w-6xl > div.grid > div.bg-white/5 > p.text-on-surface-subtle`
Projected pace, pace boosts, offensive/defensive ratings, and calculated target… `div.max-w-6xl > div.grid > div.bg-white/5 > p.text-on-surface-subtle`

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
DFS Lineup Optimizer for DraftKings, FanDuel & Yahoo `div.space-y-6 > div.flex > div > h4.text-base`
Weekly — $9.99/week `div.bg-white/5 > div.space-y-4 > div > h4.text-lg`
Site Links `body.w-full > div.footer > div.link-container > h4`

These are opportunities to improve keyboard navigation in your application.

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
Homepage `div.footer > div.link-container > div > a`
Contact Us `div.footer > div.link-container > div > a`
Mock Draft `div.footer > div.link-container > div > a`
MLB Props Today `div.footer > div.link-container > div > a`
MLB Top Stacks Today `div.footer > div.link-container > div > a`
MLB DFS Hub `div.footer > div.link-container > div > a`
MLB DFS Picks `div.footer > div.link-container > div > a`
DraftKings MLB Picks `div.footer > div.link-container > div > a`
FanDuel MLB Picks `div.footer > div.link-container > div > a`
DraftKings MLB Props `div.footer > div.link-container > div > a`
FanDuel MLB Props `div.footer > div.link-container > div > a`
BetMGM MLB Props `div.footer > div.link-container > div > a`
Caesars MLB Props `div.footer > div.link-container > div > a`
MLB Park Factors `div.footer > div.link-container > div > a`
Batter vs Pitcher `div.footer > div.link-container > div > a`
MLB Batting Splits `div.footer > div.link-container > div > a`
MLB Stat Leaders `div.footer > div.link-container > div > a`
MLB Pitcher Matchups `div.footer > div.link-container > div > a`
MLB Player Comparison `div.footer > div.link-container > div > a`
MLB Fantasy Calculator `div.footer > div.link-container > div > a`
MLB Hot & Cold Players `div.footer > div.link-container > div > a`
NHL Optimizer `div.footer > div.link-container > div > a`
NHL Player Search `div.footer > div.link-container > div > a`
Popular NHL Players `div.footer > div.link-container > div > a`
NHL Ownerships `div.footer > div.link-container > div > a`
NHL Starting Lineups `div.footer > div.link-container > div > a`
DraftKings NHL Picks `div.footer > div.link-container > div > a`
FanDuel NHL Picks `div.footer > div.link-container > div > a`

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

●`[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

●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

●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

○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

○Form elements have associated labels

○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.

○No element has a `[tabindex]` value greater than 0

○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+

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

H1 Access Denied

A+

Heading Text Quality

All 1 heading(s) have substantive, well-formed text

PASS

All 1 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

1 links, 0 buttons — all OK

PASS

1 links, 0 buttons — all OK

1 link(s) with descriptive text

1 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

1 links and buttons have descriptive text

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

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

No form controls on this page

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Mobile-Readable Font Sizes

All 7 visible text node(s) render at >= 12 CSS pixels

PASS

All 7 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.