Relatório de acessibilidade de playstation.com

Auditoria de acessibilidade de playstation.com — verificado em Feb 20, 2026

Technology
0 /100
F Problemas Críticos

10 problemas encontrados em 2 categorias

4 Crítico 6 Importante

Visão geral de conformidade WCAG

Percetível 3 problemas
Operável 4 problemas
Compreensível 0 problemas
Robusto 3 problemas

Problemas encontrados

Images missing alt text

Crítico

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

WCAG 1.1.1
14 elemento(s) afetado(s)
  • <img src="https://gmedia.playstation.com/is/image/SIEPDC/nba-2k26-S5-logo-desktop-01-en-09">
  • <img src="https://gmedia.playstation.com/is/image/SIEPDC/nba-2k26-S5-logo-desktop-01-en-09">
  • <img src="https://gmedia.playstation.com/is/image/SIEPDC/Battlefield-6-Season2-Logo-01-en-">
  • <img src="https://gmedia.playstation.com/is/image/SIEPDC/Battlefield-6-Season2-Logo-01-en-">
  • <img src="https://gmedia.playstation.com/is/image/SIEPDC/god-of-war-sons-of-sparta-logo-01">
Como corrigir

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

Links missing accessible name

Crítico

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

WCAG 2.4.4
6 elemento(s) afetado(s)
  • <a href="http://facebook.com/playstationfrance">
  • <a href="http://twitter.com/playstationfr">
  • <a href="http://instagram.com/playstationfr">
  • <a href="https://www.youtube.com/user/playstationfrance">
  • <a href="(no href)">
Como corrigir

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

Buttons missing accessible name

Crítico

Buttons must have discernible text for screen reader users.

WCAG 4.1.2
1 elemento(s) afetado(s)
  • <button>
Como corrigir

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

Videos missing captions

Crítico

Video content must have captions for deaf and hard-of-hearing users.

WCAG 1.2.2
4 elemento(s) afetado(s)
  • <video> "(inline)"
  • <video> "(inline)"
  • <video> "(inline)"
  • <video> "(inline)"
Como corrigir

Add closed captions or subtitles to all video content.

Heading levels skip order

Importante

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

WCAG 1.3.1
4 elemento(s) afetado(s)
  • <h3> "PlayStation Plus Premium" (after h1)
  • <h5> "Nouveautés" (after h1)
  • <h4> "Rager apportera le rythme au PlayStation VR2 le 5 " (after h2)
  • <h5> "SENSITIVE_CONTENT" (after h3)
Como corrigir

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

Frames missing title

Importante

Iframes must have title attributes describing their content.

WCAG 2.4.1
3 elemento(s) afetado(s)
  • <iframe src="(no src)">
  • <iframe src="(no src)">
  • <iframe src="//s.thebrighttag.com/iframe?c=O14oOQO">
Como corrigir

Add descriptive title attributes to all <iframe> elements.

Duplicate element IDs

Importante

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

WCAG 4.1.1
18 elemento(s) afetado(s)
  • id="fig-caption-84b5cada-9ec6-382c-8747-871521748cce"
  • id="icon-badges-ps4-ps5-a"
  • id="icon-badges-ps4-ps5-c"
  • id="icon-badges-ps4-ps5-b"
  • id="icon-badges-ps4-ps5-d"
Como corrigir

Make each id attribute value unique within the page.

Positive tabindex values

Importante

Elements with tabindex > 0 disrupt natural tab order and confuse keyboard users.

WCAG 2.4.3
6 elemento(s) afetado(s)
  • <a tabindex="1">
  • <a tabindex="1">
  • <a tabindex="1">
  • <a tabindex="1">
  • <div tabindex="1">
Como corrigir

Remove positive tabindex values. Use tabindex="0" or tabindex="-1" only.

No skip navigation link

Importante

Pages should have a mechanism to bypass repeated navigation blocks.

WCAG 2.4.1
1 elemento(s) afetado(s)
  • No skip navigation link found
Como corrigir

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

Invalid ARIA attributes

Importante

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

WCAG 4.1.2
6 elemento(s) afetado(s)
  • <figure aria-labelledby="fig-caption-03aa89ce-8aff-31d4-8411-261ca1f29f16"> (missing ref)
  • <figure aria-labelledby="fig-caption-77f8f603-2cfa-3265-9d33-eec5152566b6"> (missing ref)
  • <figure aria-labelledby="fig-caption-64de76ea-7c75-3d9d-a071-9d874b79b4fd"> (missing ref)
  • <figure aria-labelledby="fig-caption-fd1c0f12-e198-3c00-a0d4-82a210368d98"> (missing ref)
  • <figure aria-labelledby="fig-caption-bd2ea070-17ba-3e52-8f4e-616f54f387da"> (missing ref)
Como corrigir

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

Correções prioritárias

Aqui estão as mudanças mais impactantes que playstation.com deveria fazer:

  1. #1
    Images missing alt text Crítico

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

  2. #2
    Links missing accessible name Crítico

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

  3. #3
    Videos missing captions Crítico

    Add closed captions or subtitles to all video content.

Perguntas frequentes

playstation.com é acessível?

playstation.com obteve 0/100 (nota F) em nossa auditoria. Esta pontuação reflete verificações automáticas segundo WCAG 2.1 nível AA.

playstation.com é conforme com WCAG?

Nosso scan encontrou 10 problemas de acessibilidade em playstation.com. A conformidade WCAG completa requer resolver todos os problemas críticos e maiores.

playstation.com é conforme com a EAA?

A Lei Europeia de Acessibilidade exige que os sites cumpram WCAG 2.1 AA. Consulte o relatório detalhado acima para o estado de conformidade de playstation.com.

Quais problemas de acessibilidade tem playstation.com?

Consulte a lista completa de problemas acima com níveis de gravidade, elementos afetados e correções recomendadas para playstation.com.

Verifique seu próprio site

Obtenha um relatório de acessibilidade gratuito em segundos.