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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
45
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
D
Alt Text Quality
Action
2 of 76 images have issues
FIX
2 of 76 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
37 decorative image(s) correctly marked
Info::
37 image(s) with good alt text
76 images 37 good alt text 37 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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-1um4ob
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.

D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 icon(s) detected
Info::
favicon.ico present at site root
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 Present
PNG Icons Present
Apple Touch Missing
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://sp.gov.br/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://sp.gov.br/manifest.json

Manifest contains invalid JSON.

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
Landmark Structure
31 landmarks
REVIEW
31 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (4 found)
A page should have only one <main> landmark.
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 "Portal Application" MAIN CONTENTINFO footer

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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
Heading Hierarchy
Action
60 headings, 2 skip(s)
REVIEW
60 headings, 2 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Web Content Viewer
  • H1 VIVA SP
  • H2 Web Content Viewer
  • H2 Web Content Viewer
  • H3 O QUE VOCÊ PROCURA?
  • H2 Web Content Viewer
  • H3 (empty)
  • H2 Web Content Viewer
  • H2 Web Content Viewer
  • H3 Serviços por Categoria
  • H2 Web Content Viewer
  • H1 Conheça SP duplicate H1
  • H2 Web Content Viewer
  • H3 ÓRGÃOS E ENTIDADES
  • H5 FUNDAÇÕES skipped
  • H5 OUTROS ÓRGÃOS
  • H5 PREFEITURAS
  • H5 GOVERNADOR
  • H5 FUNDO SOCIAL
  • H5 SECRETARIAS
  • H5 EMPRESAS
  • H5 AUTARQUIAS
  • H5 FUNDAÇÕES
  • H5 OUTROS ÓRGÃOS
  • H5 PREFEITURAS
  • H5 GOVERNADOR
  • H5 FUNDO SOCIAL
  • H5 SECRETARIAS
  • H5 EMPRESAS
  • H5 AUTARQUIAS
  • H5 FUNDAÇÕES
  • H5 OUTROS ÓRGÃOS
  • H5 PREFEITURAS
  • H2 Web Content Viewer
  • H1 Campanhas duplicate H1
  • H2 Web Content Viewer
  • H3 Nossas redes sociais
  • H2 Web Content Viewer
  • H3 Ouvidoria e Acesso à Informação
  • H2 Web Content Viewer
  • H5 RECLAMAÇÕES skipped
  • H5 DENÚNCIAS
  • H5 INFORMAÇÕES
  • H5 ELOGIOS
  • H5 SUGESTÕES
  • H5 SOLICITAÇÕES
  • H5 RECLAMAÇÕES
  • H5 DENÚNCIAS
  • H5 INFORMAÇÕES
  • H5 ELOGIOS
  • H5 SUGESTÕES
  • H5 SOLICITAÇÕES
  • H5 RECLAMAÇÕES
  • H5 DENÚNCIAS
  • H5 INFORMAÇÕES
  • H4 Fala SP
  • H4 Transparência
  • H4 Termo de Uso
  • H4 Política de Privacidade
  • H2 Sua sessão está prestes a expirar. Deseja continuar conectado?

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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

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

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 saopaulo
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 VIVA SP21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Conheça SP21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Campanhas21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Sua sessão está pr…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 O QUE VOCÊ PROCURA?21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Serviços por Catego…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ÓRGÃOS E ENTIDADES21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Nossas redes sociais21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Ouvidoria e Acesso …21.00:13.0:1
#000000
#FFFFFF
Pass
title saopaulo1.00:14.5:1
#000000
#000000
Fail
a Início21.00:14.5:1
#000000
#FFFFFF
Pass
a Institucional21.00:14.5:1
#000000
#FFFFFF
Pass
span Estrutura21.00:14.5:1
#000000
#FFFFFF
Pass
span Agenda do governador21.00:14.5:1
#000000
#FFFFFF
Pass
span Mapa do Site21.00:14.5:1
#000000
#FFFFFF
Pass
span Cartilha de projetos…21.00:14.5:1
#000000
#FFFFFF
Pass
span Serviços21.00:14.5:1
#000000
#FFFFFF
Pass
span Conheça SP21.00:14.5:1
#000000
#FFFFFF
Pass
a Canais de Comunicaç…21.00:14.5:1
#000000
#FFFFFF
Pass
span Fala SP21.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.

B
Lighthouse Accessibility Audits
Score 84/100 — 5 failing, 28 passed
REVIEW
84

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Este site utiliza apenas cookies essenciais para garantir seu funcionamento e m… body.toolbar-closed > div#lgpdModal

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.

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
ÓRGÃOS E ENTIDADES div.wpthemeControlBody > section#IDAcessoRapidocffea980-09ad-4181-ab95-1fcc43069d19 > div.container > h3#ÓRGÃOS E ENTIDADES
FUNDO SOCIAL a > div.card > div.card-body > h5
NOSSAS REDES SOCIAIS section > div.container > section#redes-home > h3.tit-area
SUGESTÕES a > div.card > div.card-body > h5

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-lg-6 > div.noticia > a > img.img-fluid div.col-lg-6 > div.noticia > a > img.img-fluid
footer > div#barraAcessibilidade > a#btnAcessibilidade > img footer > div#barraAcessibilidade > a#btnAcessibilidade > img

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.container > div.row > div.col-md > a#linkLogo div.container > div.row > div.col-md > a#linkLogo
div.row > div.col-lg-6 > div.painel-item > a div.row > div.col-lg-6 > div.painel-item > a
div.row > div.col-lg-6 > div.painel-item > a div.row > div.col-lg-6 > div.painel-item > a
div.col-lg-6 > ul.list-inline > li.list-inline-item > a div.col-lg-6 > ul.list-inline > li.list-inline-item > a
div.col-lg-6 > ul.list-inline > li.list-inline-item > a div.col-lg-6 > ul.list-inline > li.list-inline-item > a
div.col-lg-6 > ul.list-inline > li.list-inline-item > a div.col-lg-6 > ul.list-inline > li.list-inline-item > a
div.col-lg-6 > ul.list-inline > li.list-inline-item > a div.col-lg-6 > ul.list-inline > li.list-inline-item > a
div.col-lg-6 > ul.list-inline > li.list-inline-item > a div.col-lg-6 > ul.list-inline > li.list-inline-item > a
div.col-lg-6 > ul.list-inline > li.list-inline-item > a div.col-lg-6 > ul.list-inline > li.list-inline-item > a
div.col-lg-6 > ul.list-inline > li.list-inline-item > a div.col-lg-6 > ul.list-inline > li.list-inline-item > a
div.col-lg-6 > ul.list-inline > li.list-inline-item > a div.col-lg-6 > ul.list-inline > li.list-inline-item > a
div.col-12 > ul.list-inline > li.list-inline-item > a div.col-12 > ul.list-inline > li.list-inline-item > a
div.col-12 > ul.list-inline > li.list-inline-item > a div.col-12 > ul.list-inline > li.list-inline-item > a
div.col-12 > ul.list-inline > li.list-inline-item > a div.col-12 > ul.list-inline > li.list-inline-item > a
div.col-12 > ul.list-inline > li.list-inline-item > a div.col-12 > ul.list-inline > li.list-inline-item > a
div.col-12 > ul.list-inline > li.list-inline-item > a div.col-12 > ul.list-inline > li.list-inline-item > a
div.col-12 > ul.list-inline > li.list-inline-item > a div.col-12 > ul.list-inline > li.list-inline-item > a
div.col-12 > ul.list-inline > li.list-inline-item > a div.col-12 > ul.list-inline > li.list-inline-item > a
div.col-12 > ul.list-inline > li.list-inline-item > a div.col-12 > ul.list-inline > li.list-inline-item > a
div.col-12 > ul.list-inline > li.list-inline-item > a div.col-12 > ul.list-inline > li.list-inline-item > a
body.toolbar-closed > footer > div#barraAcessibilidade > a#btnAcessibilidade body.toolbar-closed > footer > div#barraAcessibilidade > a#btnAcessibilidade

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Form elements have associated labels
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.
Document has a main landmark.
Deprecated ARIA roles were not used
All heading elements contain content.
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
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
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
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="search_query" id="input-search-large">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#input-search-largetext(Busque pela informação desejada)placeholder only

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

<input type="text" name="search_query" id="input-search-large">

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