Skip to content
https://g1.globo.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
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::
1 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 1 <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
Alt Text Quality
2 of 11 images have issues
REVIEW
2 of 11 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
9 decorative image(s) correctly marked
11 images 9 decorative 2 missing
IssueCount
missing2 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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
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 ✓Page Title Globo.com - Desculpe-nos, página não encontrada ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
11 icon(s) detected
REVIEW
11 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 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.

19 pass 1 fail WCAG AA
span MENU
3.48:1
#000000
on
#C4170C
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
title g1 - O portal de not…21.00:14.5:1
#000000
#FFFFFF
Pass
a Pular para o conteú…10.06:14.5:1
#000000
#E7A29E
Pass
span MENU3.48:14.5:1
#000000
#C4170C
Fail
button buscar19.26:14.5:1
#000000
#F5F5F5
Pass
div Entrar com Conta Glo…21.00:14.5:1
#000000
#FFFFFF
Pass
p Usuário deslogado21.00:14.5:1
#000000
#FFFFFF
Pass
span MENU21.00:14.5:1
#000000
#FFFFFF
Pass
div Entrar com Conta Glo…20.65:14.5:1
#000000
#FDFDFD
Pass
p Usuário deslogado21.00:14.5:1
#000000
#FFFFFF
Pass
p Foragido da Justiça…21.00:14.5:1
#000000
#FFFFFF
Pass
span Há 13 minutos21.00:14.5:1
#000000
#FFFFFF
Pass
span Mundo21.00:14.5:1
#000000
#FFFFFF
Pass
span Lei de Diretrizes Or…21.00:14.5:1
#000000
#FFFFFF
Pass
p Governo propõe sal…21.00:14.5:1
#000000
#FFFFFF
Pass
p Valor é 5,92% maior…21.00:14.5:1
#000000
#FFFFFF
Pass
span Há 3 horas19.77:14.5:1
#000000
#F8F8F8
Pass
span Economia21.00:14.5:1
#000000
#FFFFFF
Pass
p Meta fiscal em 2027 …21.00:14.5:1
#000000
#FFFFFF
Pass
p Proposta de LDO prev…21.00:14.5:1
#000000
#FFFFFF
Pass
span Há 2 horas21.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.

A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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

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

A+
Heading Hierarchy
10 headings
PASS
10 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H2 Foragido da Justiça brasileira, Ramagem ficou 2 dias preso antes de ser liberado
  • H2 Governo propõe salário mínimo de R$ 1.717 em 2027
  • H2 Meta fiscal em 2027 prevê superávit de 0,5% do PIB, projeta governo
  • H2 Dólar cai pelo 6º dia seguido e segue abaixo de R$ 5
  • H2 Gilmar pede que PGR investigue relator de CPI por possível abuso de autoridade
  • H2 Escala 6x1: o que muda entre a proposta do governo e o texto que avança no Congresso
  • H2 Megaoperação da PF que prendeu os MCs Ryan e Poze teve 39 alvos; detalhes
  • H2 Grupo ligado a Ryan lavou dinheiro do tráfico de 3 toneladas de cocaína, diz PF
  • H2 8 das 10 músicas mais ouvidas no Brasil têm artistas de produtoras alvos da PF

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#busca-camposearchbuscararia-label
A
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 24 passed
PASS
92

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

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#a6c1eefe-b68a-4a72-8f88-1c68969e5045 > div.feed-post-body > div.feed-media-wrapper > a.feed-post-figure-link div#a6c1eefe-b68a-4a72-8f88-1c68969e5045 > div.feed-post-body > div.feed-media-wrapper > a.feed-post-figure-link
div#8d05f0c9-bafc-4ae7-adae-4ecc39e6e4ca > div.feed-post-body > div.feed-media-wrapper > a.feed-post-figure-link div#8d05f0c9-bafc-4ae7-adae-4ecc39e6e4ca > div.feed-post-body > div.feed-media-wrapper > a.feed-post-figure-link
div#ca86e434-7503-4645-bf2d-b917d28a25f1 > div.feed-post-body > div.feed-media-wrapper > a.feed-post-figure-link div#ca86e434-7503-4645-bf2d-b917d28a25f1 > div.feed-post-body > div.feed-media-wrapper > a.feed-post-figure-link
div#14b7a13e-8ac2-48e5-97b9-c3b05b6b625d > div.feed-post-body > div.feed-media-wrapper > a.feed-post-figure-link div#14b7a13e-8ac2-48e5-97b9-c3b05b6b625d > div.feed-post-body > div.feed-media-wrapper > a.feed-post-figure-link
div#49dd0f73-8b61-4531-a222-f529ae902e37 > div.feed-post-body > div.feed-media-wrapper > a.feed-post-figure-link div#49dd0f73-8b61-4531-a222-f529ae902e37 > div.feed-post-body > div.feed-media-wrapper > a.feed-post-figure-link
div.diretorio__esquerda > div.diretorio__logos > div.diretorio__logos__logo > a div.diretorio__esquerda > div.diretorio__logos > div.diretorio__logos__logo > 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
body.bs-home > div.searchV2 > div.searchV2__suggest > ul.searchV2__suggest__items body.bs-home > div.searchV2 > div.searchV2__suggest > ul.searchV2__suggest__items

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

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
ge div.base-container > ul.container-list-item > li.list-item-product > a.link-logo
gshow div.base-container > ul.container-list-item > li.list-item-product > a.link-logo
○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
●Buttons have an accessible name
●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.
●`[accesskey]` values are unique
●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
●Background and foreground colors have a sufficient contrast ratio
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●All heading elements contain content.
●Identical links have the same purpose.
○`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 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
○`<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
○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>`.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback