Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 4 REVIEW 6 FIX

Tabindex Anti-Patterns

Action

0 positive, 71 -1-on-focusable

FIX

0 positive, 71 -1-on-focusable

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" on naturally-focusable <button id="slick-slide-control01">

tabindex="-1" on naturally-focusable <button id="slick-slide-control02">

tabindex="-1" on naturally-focusable <button id="slick-slide-control03">

tabindex="-1" on naturally-focusable <button id="slick-slide-control04">

tabindex="-1" on naturally-focusable <button id="slick-slide-control05">

tabindex="-1" on naturally-focusable <button id="slick-slide-control06">

tabindex="-1" on naturally-focusable <button id="slick-slide-control07">

tabindex="-1" on naturally-focusable <button id="slick-slide-control08">

tabindex="-1" on naturally-focusable <button id="slick-slide-control09">

tabindex="-1" on naturally-focusable <button id="slick-slide-control010">

tabindex="-1" on naturally-focusable <button id="slick-slide-control011">

tabindex="-1" on naturally-focusable <button id="slick-slide-control012">

tabindex="-1" on naturally-focusable <button id="slick-slide-control013">

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Landmark Structure

Action

2 landmarks

REVIEW

2 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

No banner (header) landmark

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

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

Heading Hierarchy

13 headings

REVIEW

13 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 Institucional
H2 Atendimento
H2 Produtos para Você
H2 Serviços para Você
H2 Benefícios do Trabalhador
H2 Programas Sociais
H2 Produtos para sua Empresa
H2 Serviços para sua Empresa
H2 Produtos para o Poder Público
H2 Serviços para o Poder Público
H2 Benefícios do Trabalhador>
H2 Programas Sociais>
H2 Serviços>

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA 1 pass AA only

h2 Atendimento

2.76:1

#000000

#186113

needs 3.0:1 (large text)

24px · mid-page

title CAIXA

3.10:1

#000000

#005CA9

needs 4.5:1 (normal text)

16px · top of page (header area)

a Acesso à informação

2.52:1

#000000

#155752

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Aviso de privacidade

2.63:1

#000000

#265C1E

needs 4.5:1 (normal text)

16px · top of page (header area)

a CAIXA Notícias

2.53:1

#000000

#1D5A1B

needs 4.5:1 (normal text)

16px · above the fold

a Downloads

2.37:1

#000000

#115617

needs 4.5:1 (normal text)

16px · above the fold

a Educação Financeira

2.62:1

#000000

#185D1E

needs 4.5:1 (normal text)

16px · above the fold

a Governança corporativa

2.59:1

#000000

#195C1C

needs 4.5:1 (normal text)

16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Institucional	3.10:1	3.0:1	#000000	#005CA9	Pass
h2 Atendimento	2.76:1	3.0:1	#000000	#186113	Fail
h2 Produtos para Você	15.45:1	3.0:1	#000000	#D0E0E3	Pass
h2 Serviços para Você	15.45:1	3.0:1	#000000	#D0E0E3	Pass
h2 Benefícios do Traba…	15.45:1	3.0:1	#000000	#D0E0E3	Pass
h2 Programas Sociais	15.45:1	3.0:1	#000000	#D0E0E3	Pass
h2 Produtos para sua Em…	15.45:1	3.0:1	#000000	#D0E0E3	Pass
h2 Serviços para sua E…	15.45:1	3.0:1	#000000	#D0E0E3	Pass
h2 Produtos para o Pode…	15.45:1	3.0:1	#000000	#D0E0E3	Pass
h2 Serviços para o Pod…	15.45:1	3.0:1	#000000	#D0E0E3	Pass
h2 Benefícios do Traba…	15.45:1	3.0:1	#000000	#D0E0E3	Pass
h2 Programas Sociais	15.45:1	3.0:1	#000000	#D0E0E3	Pass
h2 Serviços	15.45:1	3.0:1	#000000	#D0E0E3	Pass
title CAIXA	3.10:1	4.5:1	#000000	#005CA9	Fail
a Acesso à informaç�…	2.52:1	4.5:1	#000000	#155752	Fail
a Aviso de privacidade	2.63:1	4.5:1	#000000	#265C1E	Fail
a CAIXA Notícias	2.53:1	4.5:1	#000000	#1D5A1B	Fail
a Downloads	2.37:1	4.5:1	#000000	#115617	Fail
a Educação Financeir…	2.62:1	4.5:1	#000000	#185D1E	Fail
a Governança corporat…	2.59:1	4.5:1	#000000	#195C1C	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.

A+

Heading Text Quality

All 13 heading(s) have substantive, well-formed text

PASS

All 13 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

Alt Text Quality

All 62 images OK

PASS

All 62 images OK

10 image(s) with alt text over 125 characters

22 decorative image(s) correctly marked

30 image(s) with good alt text

62 images 30 good alt text 22 decorative

Issue	Count
too long	10 image(s)

Form Accessibility

1 of 3 controls have issues

PASS

1 of 3 controls have issues

1 control(s) without accessible label

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

Got: <select name="ctl00$ctl57$g_297c5981_717e_42db_820d_ad6d2449ff62$dropDownModalidades" id="dropDownModalidades">

2 control(s) properly labeled

3 controls

2 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#pesquisaHeader	text	Campo para realizar a busca.	for/id
#pesquisaHeaderMobile	text	Campo para realizar a busca.	for/id
#dropDownModalidades	select	(none)	none

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

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

Link & Button Quality

1 issue(s) across 317 links and 50 buttons

PASS

1 issue(s) across 317 links and 50 buttons

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button#tituloHeaderMenu0

317 link(s) with descriptive text

317 links

0 empty

0 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
<button>	(empty)	empty	Add button text or aria-label

366 links and buttons have descriptive text

Icon-only buttons need an aria-label so screen readers can announce them.

button#tituloHeaderMenu0

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

A+

Form Input Types

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

3 form control(s) checked, no input-semantic issues

PASS

3 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "pt-BR"

PASS

Lang attribute set to "pt-BR"

<html lang="pt-BR"> is set and valid

Got: pt-BR

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 69 visible text node(s) render at >= 12 CSS pixels

PASS

All 69 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 30 passed

PASS

100

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.

○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

●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.

●Select elements have associated label elements.

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[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 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

●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.

○`[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

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○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.