Skip to content
https://ibge.gov.br

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
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-7rvxdr
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
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://ibge.gov.br/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://ibge.gov.br/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: #00427e
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::
2 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 2 <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
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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 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

B
Form Accessibility
2 of 4 controls have issues
REVIEW
2 of 4 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="c" id="nomeAreaTerritorialHome">; <input type="text">
Info::
2 control(s) properly labeled
4 controls
2 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#mod-search-searchwordsearchBuscarfor/id
#mod-search-searchwordsearchBuscarfor/id
#nomeAreaTerritorialHomeselect(none)none
inputtext(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select name="c" id="nomeAreaTerritorialHome">; <input type="text">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

B
Favicon & Branding
14 icon(s) detected
REVIEW
14 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
title IBGE | Portal do IBGE | IBGE
1.26:1
#000000
on
#071D41
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Instituto Brasileiro…18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Instituto Brasileiro…18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Comunicados18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Cidades e Estados18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Nossos sites18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Próximas divulgaç…18.43:13.0:1
#000000
#F0F0F0
Pass
h2 IBGE Esclarece18.43:13.0:1
#000000
#F0F0F0
Pass
h2 IBGE Explica18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Erramos18.43:13.0:1
#000000
#F0F0F0
Pass
h3 Nomes no Brasil18.43:13.0:1
#000000
#F0F0F0
Pass
h3 Panorama Censo 202218.43:13.0:1
#000000
#F0F0F0
Pass
h3 CPNU18.43:13.0:1
#000000
#F0F0F0
Pass
h3 Casa Brasil IBGE18.43:13.0:1
#000000
#F0F0F0
Pass
h3 IBGE promove oficina…18.43:13.0:1
#000000
#F0F0F0
Pass
h3 IBGE disponibiliza A…18.43:13.0:1
#000000
#F0F0F0
Pass
h3 IBGE 90 anos: Presid…18.43:13.0:1
#000000
#F0F0F0
Pass
h3 IBGE celebra 90 anos…18.43:13.0:1
#000000
#F0F0F0
Pass
h3 TARDE - Assista ao v…18.43:13.0:1
#000000
#F0F0F0
Pass
h3 MANHÃ - Assista ao …18.43:13.0:1
#000000
#F0F0F0
Pass
title IBGE | Portal do IBG…1.26:14.5:1
#000000
#071D41
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 78/100 — 6 failing, 20 passed
REVIEW
78

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Recife div > div#section_quickfacts > div.largura-maxima > div.imagem

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
213.421.037 div > a.popclock-home > div.indicador-info > p.indicador-value
0,88% div.id7060 > a > div#nome-7060 > p#ultimo_valor_dado-7060
2,3% div.id5932 > a > div#nome-5932 > p#ultimo_valor_dado-5932
5,1% div.id4094 > a > div#nome-4094 > p#ultimo_valor_dado-4094

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Selecione... Acre - 12 Rio Branco ( AC ) - 1200401 Alagoas - 27 Maceió ( AL ) -… div.container-informacao > form.quick-facts-formulario > div#divInputMunicipios > select#nomeAreaTerritorialHome

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#section_bannerstopo > div.banner-topo > div > iframe div#section_bannerstopo > div.banner-topo > div > iframe

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.largura-maxima > div.content-esclarece > div.quadro-esclarece > a div.largura-maxima > div.content-esclarece > div.quadro-esclarece > 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.

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
População Estimativas da População 2025 div > a.popclock-home > div.indicador-info > h6.indicador-title

These are opportunities to improve keyboard navigation in your application.

○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
●`[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
●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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●ARIA IDs are unique
●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
○No form fields have multiple labels
○`<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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○Elements with visible text labels have matching accessible names.
○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
33 headings, 1 skip(s)
PASS
33 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Instituto Brasileiro de Geografia e Estatística
  • H2 Instituto Brasileiro de Geografia e Estatística
  • H6 PopulaçãoEstimativas da População 2025 skipped
  • H6 InflaçãoIPCAMensal
  • H6 PIBSCNTAcumulado 4 trimestres
  • H6 DesempregoPNAD Contínua
  • H6 InflaçãoINPC
  • H6 InflaçãoIPCA-15
  • H6 Preços - ProdutorIPP
  • H6 InflaçãoIPCAAcumulado 12 meses
  • H6 IndústriaPIM-PF
  • H6 ComércioPMC
  • H6 ServiçosPMS
  • H6 ConstruçãoSINAPI
  • H3 Nomes no Brasil
  • H3 Panorama Censo 2022
  • H3 CPNU
  • H3 Casa Brasil IBGE
  • H3 AGÊNCIA DE NOTÍCIAS
  • H3 IBGE promove oficina para comunicadores sobre o 12º Censo Agropecuário, Florestal e Aquícola
  • H3 IBGE disponibiliza Agenda semanal com programações para os dias 20 a 24 de abril
  • H3 IBGE 90 anos: Presidências do IBGE e do TSE se reúnem em Brasília para fortalecer a democracia
  • H3 IBGE celebra 90 anos com evento no Itamaraty e lançamento de publicações inéditas
  • H3 IBGE Digital
  • H3 TARDE - Assista ao vivo nesta quarta-feira (15) às 14h o 3º dia do Workshop de Experiências de Censos de População em Situação de Rua
  • H3 MANHÃ - Assista ao vivo nesta quarta-feira (15) às 08h30 o 3º dia do Workshop de Experiências de Censos de População em Situação de Rua
  • H2 Comunicados
  • H2 Cidades e Estados
  • H2 Nossos sites
  • H2 Próximas divulgações
  • H2 IBGE Esclarece
  • H2 IBGE Explica
  • H2 Erramos

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A
Alt Text Quality
1 of 233 images have issues
PASS
1 of 233 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
7 decorative image(s) correctly marked
Info::
225 image(s) with good alt text
233 images 225 good alt text 7 decorative 1 missing
IssueCount
missing1 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

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

Send Feedback