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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
D
Form Accessibility
Action
6 of 7 controls have issues
FIX
6 of 7 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="barra-estado__toggle">; <select name="department">
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="palavraschave">; <input type="text" name="name">; <input type="email" name="email">; <input type="text" name="cpf">
Info::
1 control(s) properly labeled
7 controls
1 labeled
4 placeholder only
2 unlabeled
ControlTypeLabelMethod
#buscageralTextBoxtextO que você procura?for/id
nametext(Nome)placeholder only
emailemail(Email)placeholder only
cpftext(CPF)placeholder only
palavraschavetext(O que você procura?)placeholder only
#barra-estado__togglecheckbox(none)none
departmentselect(none)none

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

<input type="checkbox" id="barra-estado__toggle">; <select name="department">

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="text" name="palavraschave">; <input type="text" name="name">; <input type="email" name="email">; <input type="text" name="cpf">

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

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.

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.
C
Landmark Structure
Action
4 landmarks
REVIEW
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (missing!) CONTENTINFO footer

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

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

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

17 pass 3 fail WCAG AA
title RS.GOV.BR - Portal de Serviços Digitais
2.56:1
#000000
on
#4F4F4F
needs 4.5:1 (normal text)
16px · top of page (header area)
a Ir para o conteúdo
4.07:1
#000000
on
#D12839
needs 4.5:1 (normal text)
16px · top of page (header area)
a Ir para o menu
4.07:1
#000000
on
#D12839
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 RS.GOV.BR - Portal d…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Jornadas21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Serviços por catego…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 você pode:21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Indicadores21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Canais de Atendiment…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Acesso à Informaç…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Denúncia21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Manifestações21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Descomplica RS21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ouvindo...21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Ainda tem alguma dú…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Tire suas dúvidas21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Guia de serviços21.00:13.0:1
#000000
#FFFFFF
Pass
title RS.GOV.BR - Portal d…2.56:14.5:1
#000000
#4F4F4F
Fail
a Ir para o conteúdo4.07:14.5:1
#000000
#D12839
Fail
a Ir para o menu4.07:14.5:1
#000000
#D12839
Fail
a Ir para a busca13.09:14.5:1
#000000
#FBC501
Pass
span Estado13.44:14.5:1
#000000
#FDC803
Pass
a Notícias13.38:14.5:1
#000000
#FEC703
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+
Heading Hierarchy
24 headings
PASS
24 headings
Info::
Single H1 present
  • H1 RS.GOV.BR - Portal de Serviços Digitais
  • H2 Jornadas
  • H3 Jornada do Produtor Rural
  • H3 Jornada do Aluno
  • H3 Jornada do Empreendedor
  • H2 Serviços por categoria
  • H3 Ainda tem alguma dúvida?
  • H3 Tire suas dúvidas
  • H3 Guia de serviços
  • H2 No RS.GOV.BR você pode:
  • H2 Encontrar serviços públicos do RS e do país
  • H2 Agendar atendimento de forma fácil e rápida
  • H2 Conhecer os aplicativos do Governo do Estado
  • H2 Indicadores
  • H3 758
  • H3 77%
  • H3 96%
  • H3 89%
  • H2 Canais de Atendimento
  • H2 Acesso à Informação
  • H2 Denúncia
  • H2 Manifestações
  • H2 Descomplica RS
  • H2 Ouvindo...
A+
Alt Text Quality
All 34 images OK
PASS
All 34 images OK
Info::
34 image(s) with good alt text
34 images 34 good alt text
All images have appropriate alt text.
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Página não encontrada - RS.GOV.BR - Portal de Serviços Digitais ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /themes/rsgov2025/css/print.css?2.1.5.157.1+8
Print Stylesheet ✓ Print Optimized
Print stylesheet /themes/rsgov2025/css/print.css?2.1.5.157.1+8 ✓Inline @media print Not detected ✗
A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 27 passed
PASS
95

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.

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
Serviços estaduais section.panel > div.panel-body > div.lista-publicacoes-modular__item > p.lista-publicacoes-modular__descricao
Serviços digitais avançados section.panel > div.panel-body > div.lista-publicacoes-modular__item > p.lista-publicacoes-modular__descricao
Serviços digitais section.panel > div.panel-body > div.lista-publicacoes-modular__item > p.lista-publicacoes-modular__descricao
Satisfação do Usuário section.panel > div.panel-body > div.lista-publicacoes-modular__item > p.lista-publicacoes-modular__descricao
Atualizado em: 12/2025 div.container > div.row > div.col-xs-12 > div.indicadores__data-atualizacao
ACEITAR TODOS div#matriz2-cookie-confirmation > div#matriz2-cookie-confirmation-inner > div#matriz2-cookie-confirmation-buttons-area > a#matriz2-cookie-confirmation-button
ACEITAR NECESSÁRIOS div#matriz2-cookie-confirmation > div#matriz2-cookie-confirmation-inner > div#matriz2-cookie-confirmation-buttons-area > a#matriz2-cookie-confirmation-basic-button

These are opportunities to improve the legibility of your content.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●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
●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.
●Links have a discernible name
●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
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`button`, `link`, and `menuitem` elements have 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
○`<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>`.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback