Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 33 -1-on-focusable

FIX

0 positive, 33 -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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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" 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.)

D

Iframe Accessibility

Action

6/7 iframe(s) missing title; 0 placeholder(s)

FIX

6/7 iframe(s) missing title; 0 placeholder(s)

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.

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.

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.

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.

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.

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.

D

Favicon & Branding

Action

2 icon(s) detected

FIX

2 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'>.

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

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.

D

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.

D

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 ✗

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

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.

B

Link & Button Quality

31 issue(s) across 132 links and 0 buttons

REVIEW

31 issue(s) across 132 links and 0 buttons

31 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://www.conectadum.com/starlink-e-kddi-lancam-roaming-via-satelite-entre-…; https://www.conectadum.com/starlink-x-internet-vivo-fibra-e-5g-qual-compensa; https://www.conectadum.com/starlink-precos-planos-e-comparativo-completo-com-…; https://www.conectadum.com/plano-mais-barato-da-starlink; https://www.conectadum.com/cadastrar-starlink; https://www.conectadum.com/plano-familia-starlink-conecte-duas-casas-por-r-35…; https://www.conectadum.com/starlink-direct-to-cell-explode-em-2026-spacex-adi…; https://www.conectadum.com/starlink-no-celular-em-2027-da-spacex-quer-alcanca…; https://www.conectadum.com/starlink-site-oficial-ou-mercado-livre-onde-comprar; https://www.conectadum.com/transformei-o-starlink-mini-na-solucao-perfeita-de… (+21 more)

101 link(s) with descriptive text

132 links

31 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.conectadum.com/starlink-e-kd…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/starlink-x-in…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/starlink-prec…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/plano-mais-ba…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/cadastrar-sta…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/plano-familia…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/starlink-dire…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/starlink-no-c…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/starlink-site…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/transformei-o…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/starlink-de-e…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/5-motivos-que…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/amazon-kuiper…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/amazon-renome…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/amazon-lanca-…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/amazon-lanca-…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/plano-mais-ba…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/cadastrar-sta…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/plano-familia…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/starlink-e-kd…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/spacex-corta-…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/china-acelera…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/spacex-planej…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/starlink-dire…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/starlink-no-c…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/spacex-quer-l…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/spacex-se-pre…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/starlink-x-in…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/starlink-prec…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/starlink-dest…	(empty)	empty	Add link text or aria-label
https://www.conectadum.com/starlink-plan…	(empty)	empty	Add link text or aria-label

101 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://www.conectadum.com/starlink-e-kddi-lancam-roaming-via-satelite-entre-…; https://www.conectadum.com/starlink-x-internet-vivo-fibra-e-5g-qual-compensa; https://www.conectadum.com/starlink-precos-planos-e-comparativo-completo-com-…; https://www.conectadum.com/plano-mais-barato-da-starlink; https://www.conectadum.com/cadastrar-starlink; https://www.conectadum.com/plano-familia-starlink-conecte-duas-casas-por-r-35…; https://www.conectadum.com/starlink-direct-to-cell-explode-em-2026-spacex-adi…; https://www.conectadum.com/starlink-no-celular-em-2027-da-spacex-quer-alcanca…; https://www.conectadum.com/starlink-site-oficial-ou-mercado-livre-onde-comprar; https://www.conectadum.com/transformei-o-starlink-mini-na-solucao-perfeita-de… (+21 more)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

C

Mobile-Readable Font Sizes

Action

81% of visible text renders at >= 12 CSS px (35 below threshold)

REVIEW

81% of visible text renders at >= 12 CSS px (35 below threshold)

35 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.5px ("Ferramenta"); <a> 11.8px ("Starlink"); <a> 11.8px ("Notícias"); <a> 11.8px ("Dicas"); <a> 11.8px ("Dicas").

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 10 fail WCAG AA

REVIEW

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

10 pass 10 fail WCAG AA

h1 Starlink e internet via satélite, sem e…

1.77:1

#000000

on

#11366C

needs 3.0:1 (large text)

32px · above the fold

title Conectadum — Starlink, internet via sa…

1.23:1

#000000

on

#0B1B3A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Pular para o conteúdo

1.23:1

#000000

on

#0B1B3A

needs 4.5:1 (normal text)

16px · top of page (header area)

span Conecta

1.23:1

#000000

on

#0B1B3A

needs 4.5:1 (normal text)

16px · top of page (header area)

strong dum

1.23:1

#000000

on

#0B1B3A

needs 3.0:1 (large text)

16px · top of page (header area)

a Starlink

1.23:1

#000000

on

#0B1B3A

needs 4.5:1 (normal text)

16px · above the fold

a Internet via Satélite

1.34:1

#000000

on

#0D2247

needs 4.5:1 (normal text)

16px · above the fold

a Planos

1.55:1

#000000

on

#0F2D5B

needs 4.5:1 (normal text)

16px · above the fold

a Notícias

1.57:1

#000000

on

#0F2E5E

needs 4.5:1 (normal text)

16px · above the fold

a SpaceX

1.62:1

#000000

on

#0F3061

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Starlink e internet …	1.77:1	3.0:1	#000000	#11366C	Fail
h2 Últimas publicaçõ…	19.75:1	3.0:1	#000000	#F6F8FC	Pass
h2 Starlink	19.75:1	3.0:1	#000000	#F6F8FC	Pass
h2 Internet via Satéli…	19.75:1	3.0:1	#000000	#F6F8FC	Pass
h2 Planos	19.75:1	3.0:1	#000000	#F6F8FC	Pass
h2 Notícias	19.75:1	3.0:1	#000000	#F6F8FC	Pass
h2 SpaceX	19.75:1	3.0:1	#000000	#F6F8FC	Pass
h2 Dicas	19.75:1	3.0:1	#000000	#F6F8FC	Pass
h2 Assuntos	19.75:1	3.0:1	#000000	#F6F8FC	Pass
h2 Ferramentas	19.75:1	3.0:1	#000000	#F6F8FC	Pass
h2 Institucional	19.75:1	3.0:1	#000000	#F6F8FC	Pass
title Conectadum — Starl…	1.23:1	4.5:1	#000000	#0B1B3A	Fail
a Pular para o conteú…	1.23:1	4.5:1	#000000	#0B1B3A	Fail
span Conecta	1.23:1	4.5:1	#000000	#0B1B3A	Fail
strong dum	1.23:1	3.0:1	#000000	#0B1B3A	Fail
a Starlink	1.23:1	4.5:1	#000000	#0B1B3A	Fail
a Internet via Satéli…	1.34:1	4.5:1	#000000	#0D2247	Fail
a Planos	1.55:1	4.5:1	#000000	#0F2D5B	Fail
a Notícias	1.57:1	4.5:1	#000000	#0F2E5E	Fail
a SpaceX	1.62:1	4.5:1	#000000	#0F3061	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

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

A+

Heading Hierarchy

45 headings

PASS

45 headings

Single H1 present

H1 Starlink e internet via satélite, sem enrolação
H2 Starlink: comprar no site oficial ou no Mercado Livre? O que vale mais a pena
H2 Últimas publicações
H3 Starlink e KDDI lançam roaming via satélite entre países e ampliam o fim das áreas sem sinal
H3 Starlink x Internet Vivo Fibra e 5G: Qual Compensa Mais em 2026?
H3 Starlink: Preços, Planos e Comparativo Completo com outras operadoras de Internet Fibra
H3 Plano Mais Barato da Starlink no Brasil em 2026: Preços, Como Funciona e se Vale a Pena
H3 Como cadastrar na Starlink e ativar planos de internet via satélite em 2026
H3 Plano Família Starlink: Conecte Duas Casas por R$ 354/mês com Kit Mini Grátis no Brasil
H3 Plano de R$36 da Starlink: Como Funciona e Como Ativar?
H3 Starlink Direct to Cell explode em 2026: SpaceX adiciona mais de 18 mil usuários por dia e chega a 13 milhões de conexões
H3 Starlink no celular em 2027 da SpaceX quer alcançar velocidades de até 150 Mbps por usuário
H2 Starlink
H3 Starlink: comprar no site oficial ou no Mercado Livre? O que vale mais a pena
H3 Transformei o Starlink Mini na Solução Perfeita de Internet Off-Grid – Veja Como!
H3 Starlink de Elon Musk revoluciona a internet global — mas os riscos valem a pena?
H3 5 Motivos que Fazem a Internet via Satélite da Starlink Superar os Provedores Tradicionais
H2 Internet via Satélite
H3 Amazon Kuiper chega à Nigéria, mas não quer disputar os clientes da Starlink
H3 Amazon renomeia seu concorrente do Starlink para Amazon Leo e reforça aposta na internet via satélite
H3 Amazon Lança Internet Via Satélite com Mais de 150 Satélites e Encerra Monopólio da Starlink
H3 Amazon Lança Antena de Satélite Mais Rápida e Aumenta Disputa com a Starlink
H2 Planos
H3 Plano Mais Barato da Starlink no Brasil em 2026: Preços, Como Funciona e se Vale a Pena
H3 Como cadastrar na Starlink e ativar planos de internet via satélite em 2026
H3 Plano Família Starlink: Conecte Duas Casas por R$ 354/mês com Kit Mini Grátis no Brasil
H3 Plano de R$36 da Starlink: Como Funciona e Como Ativar?
H2 Notícias
H3 Starlink e KDDI lançam roaming via satélite entre países e ampliam o fim das áreas sem sinal
H3 SpaceX corta acesso não autorizado da Rússia aos satélites Starlink usados em ataques à Ucrânia, confirma Elon Musk
H3 China acelera programa espacial com turismo espacial, constelações de satélites e avanço em energia solar orbital até 2030
H3 SpaceX planeja lançar 1 milhão de satélites Starlink para revolucionar a infraestrutura de IA global com tecnologia inovadora
H2 SpaceX
H3 Starlink Direct to Cell explode em 2026: SpaceX adiciona mais de 18 mil usuários por dia e chega a 13 milhões de conexões
H3 Starlink no celular em 2027 da SpaceX quer alcançar velocidades de até 150 Mbps por usuário
H3 SpaceX quer levar a computação de IA para a órbita da Terra
H3 SpaceX se Prepara para Lançar Segunda Geração do Sistema Celular Starlink em 2027
H2 Dicas
H3 Starlink x Internet Vivo Fibra e 5G: Qual Compensa Mais em 2026?
H3 Starlink: Preços, Planos e Comparativo Completo com outras operadoras de Internet Fibra
H3 Starlink destaca o alinhamento da antena, mas usuários apontam o fator que realmente faz diferença no Wi-Fi
H3 Starlink planos: Qual é o ideal para sua necessidade?
H2 Assuntos
H2 Ferramentas
H2 Institucional

A

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

3 heading(s) are over 120 characters -- likely a misformatted paragraph

Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H3: 121 chars - H3: 122 chars - H3: 125 chars

Got: 3 >120-char heading(s)

A+

Alt Text Quality

All 32 images OK

PASS

All 32 images OK

31 decorative image(s) correctly marked

1 image(s) with good alt text

32 images 1 good alt text 31 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#hq	search	Buscar	for/id

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

1 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+

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

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Página não encontrada | Conectadum ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

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 96/100 — 1 failing, 25 passed

PASS

96

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
C1 `header.site-header > div.wrap > a.logo > span.logo-mark`
Comparador de planos `header.site-header > div.wrap > nav.main-nav > a.nav-tool`
C1 `div.grid > article.card > a.card-img > span.card-img-empty`
C1 `div.grid > article.card > a.card-img > span.card-img-empty`
C1 `div.wrap > div > a.logo > span.logo-mark`

These are opportunities to improve the legibility of your content.

○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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●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

○Buttons have an accessible name

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

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

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