Skip to content
https://Lojadasbateriaspe.com.br

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
4
REVIEW
9
PASS
11
INFO
0
Checks
24
11 PASS 9 REVIEW 4 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
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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Heading Hierarchy
Action
39 headings, 2 skip(s)
REVIEW
39 headings, 2 skip(s)
Warning::
Multiple H1 headings (29 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H6 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 SOLICITE
  • H1 ORÇAMENTO duplicate H1
  • H1 Muito duplicate H1
  • H1 mais duplicate H1
  • H1 bateria duplicate H1
  • H6 ZONA SUL skipped
  • H6 (81) 99479-4610
  • H6 ZONA NORTE
  • H6 (81) 98954-9028
  • H6 OLINDA
  • H6 (81) 98954-9028
  • H6 JABOATÃO
  • H6 (81) 99256-4044
  • H1 ESCOLHA SUA BATERIA duplicate H1
  • H1 Ligue e entregamos em até 40 minutos duplicate H1
  • H1 LINHA AUTOMOTIVA duplicate H1
  • H1 ENERGIA BRASILEIRA PRESENTE NAS MAIORES MONTADORAS DO MUNDO. duplicate H1
  • H1 LINHA PESADA duplicate H1
  • H1 LINHA NÁUTICA duplicate H1
  • H1 A MAIS RESISTENTE A LONGAS JORNADAS DE TRABALHO E VIBRAÇÕES. duplicate H1
  • H1 TRANQUILIDADE PARA VOCÊ, SEGURANÇA PARA SUA EMBARCAÇÃO. duplicate H1
  • H1 LINHA MOTO duplicate H1
  • H1 SEGURANÇA E QUALIDADE QUE SUA MOTO PRECISA. duplicate H1
  • H1 LINHA NOBREAK duplicate H1
  • H1 A ENERGIA DA SUA EMPRESA NÃO PODE PARAR. duplicate H1
  • H5 Receba os melhores descontos! skipped
  • H1 QUEM SOMOS duplicate H1
  • H1 VANTAGENS duplicate H1
  • H1 Aceitamos todos os cartões em até 10x sem juros duplicate H1
  • H1 ​ duplicate H1
  • H1 Entrega rápida e instalação grátis, em até 40 minutos duplicate H1
  • H1 ​ duplicate H1
  • H1 Baterias Moura com até 24 meses de garantia duplicate H1
  • H1 ​ duplicate H1
  • H1 Excelência em atendimento duplicate H1
  • H1 DEPOIMENTOS duplicate H1
  • H1 Entrega duplicate H1
  • H1 Rápida duplicate H1
  • H2 (81) 3204.1092 / (81) 99479.4610

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

B
Alt Text Quality
21 of 23 images have issues
REVIEW
21 of 23 images have issues
Warning::
21 image(s) with filename as alt text
Info::
2 image(s) with good alt text
23 images 2 good alt text 21 generic
IssueCount
filename21 image(s)
B
Form Accessibility
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="nome" id="input_comp-ki4txgit1">; <input type="email" name="email" id="input_comp-ki4txgj21">; <input type="tel" name="phone" id="input_comp-ki4txgj5">
3 controls
0 labeled
3 placeholder only
0 unlabeled
ControlTypeLabelMethod
#input_comp-ki4txgit1text(Nome)placeholder only
#input_comp-ki4txgj21email(Email)placeholder only
#input_comp-ki4txgj5tel(Telefone)placeholder only

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

<input type="text" name="nome" id="input_comp-ki4txgit1">; <input type="email" name="email" id="input_comp-ki4txgj21">; <input type="tel" name="phone" id="input_comp-ki4txgj5">

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

C
Mobile Keyboard & Autofill
Action
2/3 eligible field(s) missing autocomplete or inputmode
REVIEW
2/3 eligible field(s) missing autocomplete or inputmode
Warning::
2 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email, tel.
Got: <input type="email" name="email" id="input_comp-ki4txgj21">, <input type="tel" name="phone" id="input_comp-ki4txgj5">
C
Mobile-Readable Font Sizes
Action
87% of visible text renders at >= 12 CSS px (7 below threshold)
REVIEW
87% of visible text renders at >= 12 CSS px (7 below threshold)
Warning::
7 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> 6.0px ("BATERIAS ENTREGA RÁPIDA LOJA DAS BATERIA..."); <span> 10.0px ("ENERGIA BRASILEIRA PRESENTE NAS MAIORES ..."); <span> 10.0px ("A MAIS RESISTENTE A LONGAS JORNADAS DE T..."); <span> 10.0px ("TRANQUILIDADE PARA VOCÊ, SEGURANÇA PARA ..."); <span> 10.0px ("SEGURANÇA E QUALIDADE QUE SUA MOTO PRECI...").
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Error: Page Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
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
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
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
title Loja das Baterias | Recife | Baterias Mo…
1.99:1
#000000
on
#243E6E
needs 4.5:1 (normal text)
16px · top of page (header area)
span top of page
1.99:1
#000000
on
#243E6E
needs 4.5:1 (normal text)
16px · top of page (header area)
p INÍCIO
1.99:1
#000000
on
#243E6E
needs 4.5:1 (normal text)
16px · top of page (header area)
p CONTATO
1.99:1
#000000
on
#243E6E
needs 4.5:1 (normal text)
16px · top of page (header area)
p BATERIAS
1.99:1
#000000
on
#243E6E
needs 4.5:1 (normal text)
16px · above the fold
span ZONA SUL
1.06:1
#FAFAFA
on
#F3F4F3
needs 4.5:1 (normal text)
16px · mid-page
span ZONA NORTE
4.35:1
#FAFAFA
on
#767676
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
span OLINDA
3.48:1
#FAFAFA
on
#968465
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

2 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)
ElementRatioRequiredFGBGResult
title Loja das Baterias | …1.99:14.5:1
#000000
#243E6E
Fail
span top of page1.99:14.5:1
#000000
#243E6E
Fail
p INÍCIO1.99:14.5:1
#000000
#243E6E
Fail
p CONTATO1.99:14.5:1
#000000
#243E6E
Fail
p BATERIAS1.99:14.5:1
#000000
#243E6E
Fail
p More17.20:14.5:1
#000000
#E5E9EC
Pass
div Use tab to navigate …16.32:14.5:1
#000000
#E0E3E8
Pass
span SOLICITE16.63:14.5:1
#000000
#E2E5EA
Pass
span ORÇAMENTO17.68:14.5:1
#000000
#E8ECEF
Pass
span Início6.94:14.5:1
#000000
#3D98EF
Pass
span Muito7.44:14.5:1
#000000
#2AA3E2
Pass
span mais19.60:14.5:1
#000000
#F7F7F7
Pass
span bateria19.43:14.5:1
#000000
#F6F6F6
Pass
span ZONA SUL1.06:14.5:1
#FAFAFA
#F3F4F3
Fail
span (81) 99479-461018.59:14.5:1
#000000
#F1F1F1
Pass
span ZONA NORTE4.35:14.5:1
#FAFAFA
#767676
Fail
span (81) 98954-902815.21:14.5:1
#000000
#F0DA9B
Pass
span Contato12.02:14.5:1
#000000
#F5BB29
Pass
span OLINDA3.48:14.5:1
#FAFAFA
#968465
Fail
span (81) 98954-90287.02:14.5:1
#000000
#929695
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
Landmark Structure
14 landmarks
PASS
14 landmarks
Info::
<main> landmark present
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 "Site" MAIN CONTENTINFO footer

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

A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Info::
3 heading(s) are too short (≤2 characters) to convey meaning
Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H1: "\u200b" - H1: "\u200b" - H1: "\u200b"
Got: 3 ≤2-char heading(s)
Info::
20 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 20 all-caps heading(s)
A+
Form Input Types
3 form control(s) checked, no type mismatches
PASS
3 form control(s) checked, no type mismatches
Info::
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
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "pt"
PASS
Lang attribute set to "pt"
Info::
<html lang="pt"> is set and valid
Got: pt
A+
Tabindex Anti-Patterns
22 explicit tabindex attribute(s) checked, no anti-patterns
PASS
22 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
All 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 mobile-depth signal(s) detected
Info::
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.
Info::
iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)
The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.
A
Lighthouse Accessibility Audits
Score 90/100 — 3 failing, 24 passed
PASS
90

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 > div > nav#TINY_MENU > button.G0pJvJ div > div > nav#TINY_MENU > button.G0pJvJ

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 > div > div#comp-kl9xuu7n > a.AVxir3 div > div > div#comp-kl9xuu7n > a.AVxir3
div > div > div#comp-kl9xvw5b > a.AVxir3 div > div > div#comp-kl9xvw5b > a.AVxir3
div > div > div#comp-ksaqciq5 > a.AVxir3 div > div > div#comp-ksaqciq5 > a.AVxir3
div > div > div#comp-kyxttnb3 > a.AVxir3 div > div > div#comp-kyxttnb3 > a.AVxir3
div > div > div#comp-msmi9eey > a.AVxir3 div > div > div#comp-msmi9eey > a.AVxir3
div > div > div#comp-msmi6tqw > a.AVxir3 div > div > div#comp-msmi6tqw > a.AVxir3
div > div > div#comp-kljtskbm > a.AVxir3 div > div > div#comp-kljtskbm > a.AVxir3
div > div > div#comp-kotyrkuq > a.AVxir3 div > div > div#comp-kotyrkuq > a.AVxir3
div > div > div#comp-kotytizd > a.AVxir3 div > div > div#comp-kotytizd > a.AVxir3

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.

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
ZONA NORTE div > div > div#comp-kkicjt29 > h6.font_6
Receba os melhores descontos! div > div > div#comp-ki4txgip > h5.font_5

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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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.
●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
●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
●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 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
○Links are distinguishable without relying on color.
○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