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

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title Banco do Brasil... ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

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 ✗

Landmark Structure

Action

1 landmarks

REVIEW

1 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) 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

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

No headings

REVIEW

No headings

No headings found

Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

Mobile-Readable Font Sizes

Action

86% of visible text renders at >= 12 CSS px (24 below threshold)

REVIEW

86% of visible text renders at >= 12 CSS px (24 below threshold)

24 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.0px ("Soluções Digitais"); <span> 11.0px ("Badge Soluções Digitais"); <span> 11.0px ("Produtos"); <span> 11.0px ("Badge Produtos"); <span> 11.0px ("Produtos").

Lighthouse Accessibility Audits

Score 88/100 — 4 failing, 26 passed

REVIEW

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
div.swiper-container-wrapper > bb-swiper > div.bb-swiper > div.swiper-pagination `div.swiper-container-wrapper > bb-swiper > div.bb-swiper > div.swiper-pagination`
div.swiper-container-wrapper > bb-swiper > div.bb-swiper > div.swiper-pagination `div.swiper-container-wrapper > bb-swiper > div.bb-swiper > div.swiper-pagination`
div.swiper-container-wrapper > bb-swiper > div.bb-swiper > div.swiper-pagination `div.swiper-container-wrapper > bb-swiper > div.bb-swiper > div.swiper-pagination`

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
Pra Você `section.sbm-items > ul.sbm-items__level-1 > li#menu-lateral-id-0 > div.sbm-items__level-1__label`
Pro Seu Negócio `section.sbm-items > ul.sbm-items__level-1 > li#menu-lateral-id-1 > div.sbm-items__level-1__label`
Agronegócios `section.sbm-items > ul.sbm-items__level-1 > li#menu-lateral-id-2 > div.sbm-items__level-1__label`
Setor Público `section.sbm-items > ul.sbm-items__level-1 > li#menu-lateral-id-3 > div.sbm-items__level-1__label`
Acesse sua conta `section.sbm-items > ul.sbm-items__level-1 > li#menu-lateral-id-4 > div.sbm-items__level-1__label`
Segurança `section.sbm-items > ul.sbm-items__level-1 > li#menu-lateral-id-0 > div.sbm-items__level-1__label`
Atendimento `section.sbm-items > ul.sbm-items__level-1 > li#menu-lateral-id-1 > div.sbm-items__level-1__label`
Soluções Digitais `section.sbm-items > ul.sbm-items__level-1 > li#menu-lateral-id-2 > div.sbm-items__level-1__label`
Open Finance `section.sbm-items > ul.sbm-items__level-1 > li#menu-lateral-id-3 > div.sbm-items__level-1__label`
O BB `section.sbm-items > ul.sbm-items__level-1 > li#menu-lateral-id-0 > div.sbm-items__level-1__label`
Blog BB `section.sbm-items > ul.sbm-items__level-1 > li#menu-lateral-id-1 > div.sbm-items__level-1__label`
BB nas redes sociais `section.sbm-items > ul.sbm-items__level-1 > li#menu-lateral-id-2 > div.sbm-items__level-1__label`
Coligadas `section.sbm-items > ul.sbm-items__level-1 > li#menu-lateral-id-3 > div.sbm-items__level-1__label`
Acesso a informação `section.sbm-items > ul.sbm-items__level-1 > li#menu-lateral-id-4 > div.sbm-items__level-1__label`
Transparência `section.sbm-items > ul.sbm-items__level-1 > li#menu-lateral-id-5 > div.sbm-items__level-1__label`
Declaração de Acessibilidade `section.sbm-items > ul.sbm-items__level-1 > li#menu-lateral-id-6 > div.sbm-items__level-1__label`

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
ABRA SUA CONTA `div.col-16 > div.row > div.col-16 > button.bb-button`
VEM SER CLIENTE `div.bb-card-image--content > div > div.group-buttons > button.button`
PEÇA JÁ O SEU `div.bb-card-image--content > div > div.group-buttons > button.button`
SIMULE AQUI `div.bb-card-image--content > div > div.group-buttons > button.button`
SAIBA MAIS `div.bb-card-image--content > div > div.group-buttons > button.button`
ACESSE O SHOPPING BB `div.bb-card-image--content > div > div.group-buttons > button.button`
Educação e Carreira `ul.qtd-items-5 > li.navigation > button.active > span.name`
SAIBA MAIS `a.item-context > div.card-text > div.label-link > span`

These are opportunities to improve the legibility of your content.

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
Crédito do Trabalhador é no BB! `div.col-16 > div.text-content > div > h3.bb-header-xlarge`
Cliente + Premiado `div.col-16 > div.text-content > div > h3.bb-header-xlarge`

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

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

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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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

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

○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

○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 Text Quality

No headings to evaluate -- check is N/A

PASS

No headings to evaluate -- check is N/A

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

2 links, 0 buttons — all OK

PASS

2 links, 0 buttons — all OK

2 link(s) with descriptive text

2 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

2 links and buttons have descriptive text

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

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+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

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+

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+

Color Contrast (Screenshot)

5 text elements analyzed, 0 fail WCAG AA

PASS

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

5 pass

Show all checked elements (5)

Element	Ratio	Required	FG	BG	Result
title Pra Você \| Banco do…	19.11:1	4.5:1	#000000	#FCFC30	Pass
a Ir para o conteúdo …	14.30:1	4.5:1	#000000	#D8DC59	Pass
span Pra você	19.14:1	4.5:1	#000000	#FDFC30	Pass
a Ignorar menu lateral	19.14:1	4.5:1	#000000	#FDFC30	Pass
div Conteúdo após menu…	19.14:1	4.5:1	#000000	#FDFC30	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.

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