Report di accessibilità di no-ip.com

Audit di accessibilità di no-ip.com — scansionato il Feb 20, 2026

Technology
0 /100
F Problemi Critici

11 problemi rilevati in 3 categorie

4 Critico 6 Maggiore 1 Minore

Panoramica conformità WCAG

Percepibile 4 problemi
Operabile 4 problemi
Comprensibile 0 problemi
Robusto 3 problemi

Problemi trovati

Images missing alt text

Critico

Images must have alternative text to convey their meaning to screen reader users.

WCAG 1.1.1
5 elemento/i interessato/i
  • <img src="//d2qr50rz2oof04.cloudfront.net/assets/img/navigation/managed-dns.svg">
  • <img src="//d2qr50rz2oof04.cloudfront.net/assets/img/navigation/managed-dns.svg">
  • <img src="//d2qr50rz2oof04.cloudfront.net/assets/img/navigation/managed-dns.svg">
  • <img src="//d2qr50rz2oof04.cloudfront.net/assets/img/navigation/managed-dns.svg">
  • <img src="//d2qr50rz2oof04.cloudfront.net/assets/img/navigation/managed-dns.svg">
Come correggere

Add descriptive alt attributes to all <img> elements. Use alt="" for decorative images.

Links missing accessible name

Critico

Links must have discernible text so screen reader users understand their purpose.

WCAG 2.4.4
3 elemento/i interessato/i
  • <a href="#">
  • <a href="https://www.noip.com/support/">
  • <a href="#">
Come correggere

Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

Viewport blocks user scaling

Critico

Users must be able to zoom and scale the page. Blocking zoom prevents low-vision users from enlarging content.

WCAG 1.4.4
1 elemento/i interessato/i
  • <meta name="viewport" content="width=device-width, initial-scale=1, minimum-scale=1, user-scalable=no">
Come correggere

Remove maximum-scale=1 and user-scalable=no from the viewport meta tag.

Buttons missing accessible name

Critico

Buttons must have discernible text for screen reader users.

WCAG 4.1.2
2 elemento/i interessato/i
  • <button>
  • <button>
Come correggere

Add text content, aria-label, or title to all <button> elements.

Heading levels skip order

Maggiore

Headings should follow a logical order (h1 → h2 → h3) without skipping levels.

WCAG 1.3.1
3 elemento/i interessato/i
  • <h4> "Create Your Free Hostname Now" (after h1)
  • <h5> "Seamlessly Integrated with Your Favorite Tools" (after h3)
  • <h5> "Join Our Mailing List" (after h2)
Come correggere

Restructure headings to follow sequential order. Don't skip from h1 to h3.

Frames missing title

Maggiore

Iframes must have title attributes describing their content.

WCAG 2.4.1
1 elemento/i interessato/i
  • <iframe src="//www.googletagmanager.com/ns.html?id=GTM-VFGB">
Come correggere

Add descriptive title attributes to all <iframe> elements.

Duplicate element IDs

Maggiore

Element IDs must be unique to ensure correct assistive technology behavior.

WCAG 4.1.1
7 elemento/i interessato/i
  • id="three-icon-loading"
  • id="userDropdown"
  • id="solutionsDrop"
  • id="cartCsrfToken"
Come correggere

Make each id attribute value unique within the page.

No skip navigation link

Maggiore

Pages should have a mechanism to bypass repeated navigation blocks.

WCAG 2.4.1
1 elemento/i interessato/i
  • No skip navigation link found
Come correggere

Add a 'Skip to main content' link as the first focusable element on the page.

Invalid ARIA attributes

Maggiore

ARIA attributes must be valid and used correctly to work with assistive technologies.

WCAG 4.1.2
4 elemento/i interessato/i
  • <button aria-hidden="true"> (focusable)
  • <ul aria-labelledby="resourcesDrop"> (missing ref)
Come correggere

Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.

Generic link text

Maggiore

Links must have descriptive text that indicates their purpose. Generic text like 'click here' or 'read more' does not help screen reader users understand where the link goes.

WCAG 2.4.4
8 elemento/i interessato/i
  • <a href="https://www.noip.com/solutions/enterprise-dns-solutions">learn more</a>
  • <a href="https://www.noip.com/solutions/managed-dns-system-admins">learn more</a>
  • <a href="https://www.noip.com/solutions/msp">learn more</a>
  • <a href="https://www.noip.com/solutions/dynamic-dns-home-network">learn more</a>
  • <a href="https://www.noip.com/remote-access/security-camera">learn more</a>
Come correggere

Replace generic link text with descriptive text, e.g., 'Read our accessibility guide' instead of 'Read more'.

Incorrect list structure

Minore

List items must be contained within <ul>, <ol>, or <dl> elements.

WCAG 1.3.1
2 elemento/i interessato/i
  • <li> inside <template>
Come correggere

Ensure <li> elements are direct children of <ul> or <ol>.

Correzioni prioritarie

Ecco le modifiche più importanti che no-ip.com dovrebbe apportare:

  1. #1
    Images missing alt text Critico

    Add descriptive alt attributes to all <img> elements. Use alt="" for decorative images.

  2. #2
    Links missing accessible name Critico

    Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

  3. #3
    Buttons missing accessible name Critico

    Add text content, aria-label, or title to all <button> elements.

Domande frequenti

no-ip.com è accessibile?

no-ip.com ha ottenuto 0/100 (voto F) nel nostro audit. Questo punteggio riflette controlli automatizzati secondo WCAG 2.1 livello AA.

no-ip.com è conforme WCAG?

La nostra scansione ha trovato 11 problemi di accessibilità su no-ip.com. La piena conformità WCAG richiede la risoluzione di tutti i problemi critici e maggiori.

no-ip.com è conforme all'EAA?

La Legge Europea sull'Accessibilità richiede che i siti web rispettino gli standard WCAG 2.1 AA. Controlla il report dettagliato sopra per lo stato di conformità di no-ip.com.

Quali problemi di accessibilità ha no-ip.com?

Consulta l'elenco completo dei problemi sopra con livelli di gravità, elementi interessati e correzioni consigliate per no-ip.com.

Scansiona il tuo sito web

Ottieni un report di accessibilità gratuito in pochi secondi.

Scansione gratuita Vedi i prezzi