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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 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
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: #00a300
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::
6 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 6 <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
9 landmarks
REVIEW
9 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
3 of 6 <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 "Acesso rápido" 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 6 controls have issues
REVIEW
2 of 6 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input name="monthpicker" id="dp1776897976378">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" id="searchtext-input">
Info::
4 control(s) properly labeled
6 controls
4 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#check-allcheckboxSelecionar tudoaria-label
#check-group-0checkboxDesselecionar toda classearia-label
#check-group-1checkboxSelecionar toda classearia-label
#check-group-2checkboxSelecionar toda classearia-label
#searchtext-inputsearch(O que você procura?)placeholder only
#dp1776897976378input(none)none

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

<input name="monthpicker" id="dp1776897976378">

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

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

<input type="search" id="searchtext-input">

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Estado - Imprensa Nacional ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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, 20 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 20 fail WCAG AA
h1 Home
1.44:1
#000000
on
#192945
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Serviços da IN
1.44:1
#000000
on
#192945
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Notícias
1.44:1
#000000
on
#192945
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Agenda do Diretor-Geral
1.44:1
#000000
on
#192945
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Acesso à Informação
1.44:1
#000000
on
#192945
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Centrais de Conteúdo
1.44:1
#000000
on
#192945
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Atendimento ao Cidadão
1.44:1
#000000
on
#192945
needs 3.0:1 (large text)
24px · bottom of viewport
title Home — Imprensa Nacional
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · top of page (header area)
span Ir para o
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · top of page (header area)
a Conteúdo
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · top of page (header area)
span Ir para a
3.60:1
#000000
on
#656565
needs 4.5:1 (normal text)
16px · top of page (header area)
a Página Inicial
3.60:1
#000000
on
#656565
needs 4.5:1 (normal text)
16px · above the fold
span Ir para o menu de
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
a Navegação
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
span Ir para a
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
a Busca
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
span Ir para o
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
a Mapa do site
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
span Abrir menu principal de navegação
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
a Imprensa Nacional
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Home1.44:13.0:1
#000000
#192945
Fail
h2 Serviços da IN1.44:13.0:1
#000000
#192945
Fail
h2 Notícias1.44:13.0:1
#000000
#192945
Fail
h2 Agenda do Diretor-Ge…1.44:13.0:1
#000000
#192945
Fail
h2 Acesso à Informaç…1.44:13.0:1
#000000
#192945
Fail
h2 Centrais de Conteúd…1.44:13.0:1
#000000
#192945
Fail
h2 Atendimento ao Cidad…1.44:13.0:1
#000000
#192945
Fail
title Home — Imprensa Na…3.66:14.5:1
#000000
#666666
Fail
span Ir para o3.66:14.5:1
#000000
#666666
Fail
a Conteúdo3.66:14.5:1
#000000
#666666
Fail
span Ir para a3.60:14.5:1
#000000
#656565
Fail
a Página Inicial3.60:14.5:1
#000000
#656565
Fail
span Ir para o menu de3.66:14.5:1
#000000
#666666
Fail
a Navegação3.66:14.5:1
#000000
#666666
Fail
span Ir para a3.66:14.5:1
#000000
#666666
Fail
a Busca3.66:14.5:1
#000000
#666666
Fail
span Ir para o3.66:14.5:1
#000000
#666666
Fail
a Mapa do site3.66:14.5:1
#000000
#666666
Fail
span Abrir menu principal…3.66:14.5:1
#000000
#666666
Fail
a Imprensa Nacional3.66:14.5:1
#000000
#666666
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 85/100 — 4 failing, 29 passed
REVIEW
85

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.wrapper-login > div.header-sign-in > div.cta-wrapper > button.br-sign-in div.wrapper-login > div.header-sign-in > div.cta-wrapper > button.br-sign-in

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.monthpicker-stroke-wrapper > div.monthpicker-wrapper > div.monthpicker > input#dp1776897932981 div.monthpicker-stroke-wrapper > div.monthpicker-wrapper > div.monthpicker > input#dp1776897932981

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.column > div#daecaf65-4fc6-4b9b-aa98-2dc7f7e46c48 > div.cover-embed-tile > iframe#buscadou-iframe div.column > div#daecaf65-4fc6-4b9b-aa98-2dc7f7e46c48 > div.cover-embed-tile > iframe#buscadou-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.nitf-basic-tile > p.tile-subtitle > div.social-links > a.toggle-social-links div.nitf-basic-tile > p.tile-subtitle > div.social-links > a.toggle-social-links
div.nitf-basic-tile > p.tile-subtitle > div.social-links > a.toggle-social-links div.nitf-basic-tile > p.tile-subtitle > div.social-links > a.toggle-social-links
div.nitf-basic-tile > p.tile-subtitle > div.social-links > a.toggle-social-links div.nitf-basic-tile > p.tile-subtitle > div.social-links > a.toggle-social-links

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.

○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
●`[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
●`button`, `link`, and `menuitem` elements have accessible names
●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.
●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
●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.
●Skip links are focusable.
●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.
○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
○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
○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.
○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
9 headings
PASS
9 headings
Info::
Single H1 present
  • H1 Home
  • H2 Serviços da IN
  • H2 Notícias
  • H2 Recebimento de matérias do DOU terá horário reduzido nas vésperas de Natal e Ano Novo
  • H2 Novas aquisições de equipamentos de impressão e acabamento estão em operação no parque gráfico da IN
  • H2 Agenda do Diretor-Geral
  • H2 Acesso à Informação
  • H2 Centrais de Conteúdo
  • H2 Atendimento ao Cidadão
A+
Alt Text Quality
All 5 images OK
PASS
All 5 images OK
Info::
1 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
5 images 4 good alt text 1 decorative
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback