Skip to content
https://ebc.com.br

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Warning::
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 403 ✗Page Title Access Denied ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
7 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 7 <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.
B
Landmark Structure
19 landmarks
REVIEW
19 landmarks
Info::
<main> landmark present
Info::
7 <nav> landmark(s) found
Warning::
7 of 7 <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 ASIDE 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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA 1 pass AA only
title EBC - Empresa Brasil de Comunicação
2.27:1
#000000
on
#424758
needs 4.5:1 (normal text)
16px · top of page (header area)
span agência
3.00:1
#000000
on
#52596B
needs 4.5:1 (normal text)
16px · top of page (header area)
a rádio gov
2.73:1
#000000
on
#724939
needs 4.5:1 (normal text)
16px · above the fold
a radioagência nacional
2.58:1
#000000
on
#704530
needs 4.5:1 (normal text)
16px · mid-page
a RNCP
2.56:1
#000000
on
#70442F
needs 4.5:1 (normal text)
16px · mid-page
a tvbrasil internacional
2.38:1
#000000
on
#6A402C
needs 4.5:1 (normal text)
16px · mid-page
a canalgov
2.28:1
#000000
on
#653E2C
needs 4.5:1 (normal text)
16px · mid-page
a tvBrasil
2.03:1
#000000
on
#5A3825
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 STF tem 2 votos para…19.95:13.0:1
#000000
#F9F9F9
Pass
h2 Fique por dentro das…19.95:13.0:1
#000000
#F9F9F9
Pass
title EBC - Empresa Brasil…2.27:14.5:1
#000000
#424758
Fail
span agência3.00:14.5:1
#000000
#52596B
Fail
b Brasil8.84:13.0:1
#000000
#A8A8A9
Pass
span rádio14.03:14.5:1
#000000
#D3D3D3
Pass
b MEC21.00:13.0:1
#000000
#FFFFFF
Pass
span rádio11.75:14.5:1
#000000
#C4C1C1
Pass
b Nacional11.77:13.0:1
#000000
#BFC0DA
Pass
b Brasil9.56:13.0:1
#000000
#96ADF2
Pass
span canal7.08:14.5:1
#000000
#5095FF
Pass
b gov9.07:13.0:1
#000000
#7DAAFF
Pass
button mais8.58:14.5:1
#000000
#96A1EA
Pass
a agência gov4.63:14.5:1
#000000
#846F8B
Pass
a rádio gov2.73:14.5:1
#000000
#724939
Fail
a radioagência nacion…2.58:14.5:1
#000000
#704530
Fail
a RNCP2.56:14.5:1
#000000
#70442F
Fail
a tvbrasil internacion…2.38:14.5:1
#000000
#6A402C
Fail
a canalgov2.28:14.5:1
#000000
#653E2C
Fail
a tvBrasil2.03:14.5:1
#000000
#5A3825
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.

C
Lighthouse Accessibility Audits
Action
Score 74/100 — 7 failing, 19 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.

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.container-header-ebc > div.content-center > div.container-btns-mob > button#pesquisa-btn div.container-header-ebc > div.content-center > div.container-btns-mob > button#pesquisa-btn
article#content > section.slider > div.buttons > button#prev-button article#content > section.slider > div.buttons > button#prev-button
article#content > section.slider > div.buttons > button#next-button article#content > section.slider > div.buttons > button#next-button

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.coluna-dois > div#containerPlayersRadios > div.content-player-box > iframe#myAudio div.coluna-dois > div#containerPlayersRadios > div.content-player-box > iframe#myAudio

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.content-center > div.redes-sociais-footer > nav.redes-sociais-ebc > a div.content-center > div.redes-sociais-footer > nav.redes-sociais-ebc > a
div.content-center > div.redes-sociais-footer > nav.redes-sociais-ebc > a div.content-center > div.redes-sociais-footer > nav.redes-sociais-ebc > a
div.content-center > div.redes-sociais-footer > nav.redes-sociais-ebc > a div.content-center > div.redes-sociais-footer > nav.redes-sociais-ebc > a
div.content-center > div.redes-sociais-footer > nav.redes-sociais-ebc > a div.content-center > div.redes-sociais-footer > nav.redes-sociais-ebc > a
div.content-center > div.redes-sociais-footer > nav.redes-sociais-ebc > a div.content-center > div.redes-sociais-footer > nav.redes-sociais-ebc > 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
--- Escolha uma rádio abaixo --- div.coluna-dois > div#containerPlayersRadios > div.content-player-box > div.titulo-escolha-radio
Rádio MEC FM div.content-player-box > div#listaRadiosMEC > div#radioMECFM > div.name-radio
Rádio MEC AM div.content-player-box > div#listaRadiosMEC > div#radioMECAM > div.name-radio

These are opportunities to improve the legibility of your content.

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
Últimas Notícias Festa do Disco, da Rádio Nacional, celebra álbum icônico de Do… div.content-center > div.rowflex > div.container-noticias-imprensa > ul.ultimas-noticias-destaques-ebc
Institucional Ações e Programas Participação Social Auditorias Convênios e Tran… div.content-center > div.paginas-internas > nav > ul.options

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
playpause div.container-video > div > div#player-tvbr > div

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
LGPD div.rights-ebc > div.content-center > div.final-info > a
○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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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
●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.
●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
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Document has a main landmark.
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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
○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.
○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
2 headings
PASS
2 headings
Info::
Single H1 present
  • H1 STF tem 2 votos para manter preso ex-presidente do BRB no caso Master
  • H2 Fique por dentro das principais notícias do governo federal
A+
Alt Text Quality
1 of 74 images have issues
PASS
1 of 74 images have issues
Warning::
1 image(s) with generic alt text
Info::
73 image(s) with good alt text
74 images 73 good alt text 1 generic
IssueCount
generic1 image(s)
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 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" name="SearchableText" id="busca-ebc">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#busca-ebctext(O que você está procurando?)placeholder only

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

<input type="text" name="SearchableText" id="busca-ebc">

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

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

Send Feedback