Skip to content
https://radaresportivo.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
76
GRADE
C
FIX
7
REVIEW
4
PASS
13
INFO
0
Checks
24
13 PASS 4 REVIEW 7 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

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-mjllkn
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://radaresportivo.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://radaresportivo.com/manifest.json

Manifest contains invalid JSON.

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: #ff8336
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::
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
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

B
Tap Target Adequacy
1 tap target(s) too small or too close together
REVIEW
1 tap target(s) too small or too close together
Info::
1 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.
C
Color Contrast (Screenshot)
Action
1 text elements analyzed, 1 fail WCAG AA
REVIEW

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

0 pass 1 fail WCAG AA
title Radar Esportivo
3.39:1
#000000
on
#616161
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (1)
ElementRatioRequiredFGBGResult
title Radar Esportivo3.39:14.5:1
#000000
#616161
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.

B
Lighthouse Accessibility Audits
Score 84/100 — 4 failing, 24 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.

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.flex-1 > div.flex > div.inline-flex > button.primary div.flex-1 > div.flex > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary

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
nav.flex > div.z-10 > div.flex > a.flex nav.flex > div.z-10 > div.flex > a.flex
div > div > div.feed > a div > div > div.feed > 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.

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
Sign in div.z-10 > div.flex > div.flex > a.font-semibold
Fri div.inline-flex > div > button.flex > div.text-xs
Sat div.inline-flex > div > button.flex > div.text-xs
Sun div.inline-flex > div > button.flex > div.text-xs
5/10 div.inline-flex > div > button.flex > div
Mon div.inline-flex > div > button.flex > div.text-xs
Tue div.inline-flex > div > button.flex > div.text-xs
- 43 matches div.standard > div.rounded-t-lg > div.flex > span.text-ink-400
12:00 AM div.grid > a.col-span-10 > div.col-span-2 > div.place-self-center
EC Bahia div > div.grid > a.col-span-10 > div.col-span-7
Cruzeiro div > div.grid > a.col-span-10 > div.col-span-7
7:00 PM div.grid > a.col-span-10 > div.col-span-2 > div.place-self-center
Clube Do Remo div > div.grid > a.col-span-10 > div.col-span-7
Palmeiras div > div.grid > a.col-span-10 > div.col-span-7
7:00 PM div.grid > a.col-span-10 > div.col-span-2 > div.place-self-center
Atletico Mineiro div > div.grid > a.col-span-10 > div.col-span-7
Botafogo div > div.grid > a.col-span-10 > div.col-span-7
9:30 PM div.grid > a.col-span-10 > div.col-span-2 > div.place-self-center
Mirassol div > div.grid > a.col-span-10 > div.col-span-7
Chapecoense div > div.grid > a.col-span-10 > div.col-span-7
9:30 PM div.grid > a.col-span-10 > div.col-span-2 > div.place-self-center
Corinthians div > div.grid > a.col-span-10 > div.col-span-7
Sao Paulo div > div.grid > a.col-span-10 > div.col-span-7
9:30 PM div.grid > a.col-span-10 > div.col-span-2 > div.place-self-center
Santos div > div.grid > a.col-span-10 > div.col-span-7
Bragantino div > div.grid > a.col-span-10 > div.col-span-7
10:30 PM div.grid > a.col-span-10 > div.col-span-2 > div.place-self-center
Gremio div > div.grid > a.col-span-10 > div.col-span-7
Flamengo div > div.grid > a.col-span-10 > div.col-span-7
Learn more div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label
List of partners. div.fc-dialog-scrollable-content > div.fc-footer > p > a.fc-vendors-list-dialog

These are opportunities to improve the legibility of your content.

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
div.grid > div.grid > div.inline-flex > button.primary div.grid > div.grid > div.inline-flex > button.primary

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
●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
●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
●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
●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
●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
○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>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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 Text Quality
No headings to evaluate -- check is N/A
PASS
No headings to evaluate -- check is N/A
Info::
No headings to evaluate -- check is N/A
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+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
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
Info::
No form controls on this page
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Mobile-Readable Font Sizes
All 14 visible text node(s) render at >= 12 CSS pixels
PASS
All 14 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback