Skip to content
https://esteticdoctorpoa.com/index3.php

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
71
GRADE
C
FIX
7
REVIEW
6
PASS
11
INFO
0
Checks
24
11 PASS 6 REVIEW 7 FIX
D
Mobile Keyboard & Autofill
Action
2/2 eligible field(s) missing autocomplete or inputmode
FIX
2/2 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: tel.
Got: <input type="tel" id="fTel">
Warning::
1 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: tel.
Got: <input type="tel" id="fTel">
D
Mobile-Readable Font Sizes
Action
45% of visible text renders at >= 12 CSS px (210 below threshold)
FIX
45% of visible text renders at >= 12 CSS px (210 below threshold)
Warning::
210 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: <p> 9.0px ("Estética Regenerativa · Porto Alegre"); <a> 11.0px ("Agendar Consulta"); <a> 11.0px ("Ver Procedimentos"); <span> 9.0px ("★ Google"); <span> 9.0px ("Avaliações").
F
Favicon & Branding
Action
No icons detected
FIX
No icons 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::
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ 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.

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
Landmark Structure
Action
2 landmarks
REVIEW
2 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
Info::
No banner (header) landmark
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 (missing!) 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

B
Heading Hierarchy
11 headings, 1 skip(s)
REVIEW
11 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (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.
  • H1 Rejuvenesçasem perdersua identidade.
  • H2 A equipe Estetic Doctor
  • H2 Um ambiente pensado para você
  • H2 Nossos Procedimentos
  • H2 Antes & Depois
  • H2 Avaliações Reais
  • H2 Agende suaConsulta
  • H4 Navegação skipped
  • H4 Procedimentos
  • H4 Redes Sociais
  • H3 (empty)

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
Form Accessibility
Action
4 of 4 controls have issues
REVIEW
4 of 4 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select id="fProc">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="fNome">; <input type="tel" id="fTel">; <textarea id="fMsg">
4 controls
0 labeled
3 placeholder only
1 unlabeled
ControlTypeLabelMethod
#fNometext(Como podemos te chamar?)placeholder only
#fTeltel((51) 9 9999-9999)placeholder only
#fMsgtextarea(Conte um pouco sobre o que você gostaria de melhorar...)placeholder only
#fProcselect(none)none

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

<select id="fProc">

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" id="fNome">; <input type="tel" id="fTel">; <textarea id="fMsg">

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
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 This Page Does Not Exist ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Lighthouse Accessibility Audits
Score 81/100 — 5 failing, 19 passed
REVIEW
81

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
5,0 body > div.trust-bar > div.trust-item > span.trust-num
★ GOOGLE body > div.trust-bar > div.trust-item > span.trust-lbl
44 body > div.trust-bar > div.trust-item > span.trust-num
AVALIAÇÕES body > div.trust-bar > div.trust-item > span.trust-lbl
CRBM body > div.trust-bar > div.trust-item > span.trust-num
6102 · REGISTRO body > div.trust-bar > div.trust-item > span.trust-lbl
PORTO ALEGRE · RS div.faixa > div.faixa-inner > div.faixa-track > span.faixa-item
DRA. ANDRESSA BERNARDO div.faixa > div.faixa-inner > div.faixa-track > span.faixa-item
O QUE OFERECEMOS section#procedimentos > div.proc-header > div > p.sec-tag
Ciência regenerativa a serviço da sua beleza natural. section#procedimentos > div.proc-header > div > p.sec-sub
01 section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-num
SAIBA MAIS section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-link
02 section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-num
SAIBA MAIS section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-link
03 section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-num
SAIBA MAIS section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-link
04 section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-num
SAIBA MAIS section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-link
05 section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-num
SAIBA MAIS section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-link
06 section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-num
SAIBA MAIS section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-link
07 section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-num
SAIBA MAIS section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-link
08 section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-num
SAIBA MAIS section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-link
09 section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-num
SAIBA MAIS section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-link
010 section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-num
SAIBA MAIS section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-link
011 section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-num
SAIBA MAIS section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-link
012 section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-num
SAIBA MAIS section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-link
013 section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-num
SAIBA MAIS section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-link
014 section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-num
SAIBA MAIS section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-link
015 section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-num
SAIBA MAIS section#procedimentos > div#procGrid > div.proc-card-clean > div.proc-link
ESTÉTICA REGENERATIVA · PORTO ALEGRE footer > div.footer-top > div > span.footer-tag
NAVEGAÇÃO footer > div.footer-top > div.footer-col > h4
Home div.footer-col > ul > li > a
Sobre div.footer-col > ul > li > a
Procedimentos div.footer-col > ul > li > a
Resultados div.footer-col > ul > li > a
Avaliações div.footer-col > ul > li > a
Blog div.footer-col > ul > li > a
PROCEDIMENTOS footer > div.footer-top > div.footer-col > h4
Bio Botox div.footer-col > ul > li > a
Harmonização Facial div.footer-col > ul > li > a
Skin Glass Coreano div.footer-col > ul > li > a
Tratamento de Melasma div.footer-col > ul > li > a
Ver todos → div.footer-col > ul > li > a
REDES SOCIAIS div.footer-top > div > div.footer-col > h4
© 2026 Estetic Doctor. Todos os direitos reservados. body > footer > div.footer-bot > p.footer-copy
Desenvolvido por Infinite Ads body > footer > div.footer-bot > p.footer-credit
Infinite Ads footer > div.footer-bot > p.footer-credit > a

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Selecione um procedimento... Bio Botox Blefaro Regenerativa Botox Botox Regener… div.contato-grid > div.fade-in > div.form-group > select#fProc

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div.mapa-wrap > iframe body > div.mapa-wrap > iframe

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
body > a.wa-float body > a.wa-float

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
NAVEGAÇÃO footer > div.footer-top > div.footer-col > h4

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>`
●`[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.
●ARIA attributes are used as specified for the element's role
●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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●All heading elements contain content.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○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
○`<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
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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
○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.
○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
All 11 heading(s) have substantive, well-formed text
PASS
All 11 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 11 images OK
PASS
All 11 images OK
Info::
1 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
11 images 10 good alt text 1 decorative
All images have appropriate alt text.
A+
Form Input Types
4 form control(s) checked, no type mismatches
PASS
4 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
4 form control(s) checked, no input-semantic issues
PASS
4 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "pt-BR"
PASS
Lang attribute set to "pt-BR"
Info::
<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
Info::
No explicit tabindex attributes found
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d3454.4!2d-51.196!3d-30.02…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
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
1 mobile-depth signal(s) detected
PASS
1 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.
A+
Color Contrast (Screenshot)
20 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.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Rejuvenesça17.40:13.0:1
#000000
#F4E8DA
Pass
h1 sem perder17.72:13.0:1
#000000
#F6EADC
Pass
h2 A equipe17.70:13.0:1
#000000
#F5EADD
Pass
h2 Um ambiente17.70:13.0:1
#000000
#F5EADD
Pass
h2 para você17.70:13.0:1
#000000
#F5EADD
Pass
h2 Nossos17.70:13.0:1
#000000
#F5EADD
Pass
h2 Antes &17.70:13.0:1
#000000
#F5EADD
Pass
h2 Avaliações17.70:13.0:1
#000000
#F5EADD
Pass
h2 Agende sua17.70:13.0:1
#000000
#F5EADD
Pass
title Estetic Doctor | Est…11.24:14.5:1
#000000
#D1BAA0
Pass
a Home11.24:14.5:1
#000000
#D1BAA0
Pass
a Sobre11.24:14.5:1
#000000
#D1BAA0
Pass
a Procedimentos11.37:14.5:1
#000000
#D2BBA2
Pass
a Resultados11.24:14.5:1
#000000
#D1BAA0
Pass
a Avaliações11.35:14.5:1
#000000
#D1BBA3
Pass
a Blog11.43:14.5:1
#000000
#D1BCA3
Pass
a Contato11.56:14.5:1
#000000
#D2BDA4
Pass
button ✕11.47:14.5:1
#000000
#D2BCA4
Pass
a Home11.47:14.5:1
#000000
#D2BCA4
Pass
a Sobre11.56:14.5:1
#000000
#D2BDA4
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.

Send Feedback