Toegankelijkheidsrapport van playstation.com

Toegankelijkheidsaudit van playstation.com — gescand op Feb 20, 2026

Technology
0 /100
F Kritieke Problemen

10 problemen gevonden in 2 categorieën

4 Kritiek 6 Belangrijk

WCAG-conformiteitsoverzicht

Waarneembaar 3 problemen
Bedienbaar 4 problemen
Begrijpelijk 0 problemen
Robuust 3 problemen

Gevonden problemen

Images missing alt text

Kritiek

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

WCAG 1.1.1
14 element(en) getroffen
  • <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">
Hoe te repareren

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

Links missing accessible name

Kritiek

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

WCAG 2.4.4
6 element(en) getroffen
  • <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)">
Hoe te repareren

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

Buttons missing accessible name

Kritiek

Buttons must have discernible text for screen reader users.

WCAG 4.1.2
1 element(en) getroffen
  • <button>
Hoe te repareren

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

Videos missing captions

Kritiek

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

WCAG 1.2.2
4 element(en) getroffen
  • <video> "(inline)"
  • <video> "(inline)"
  • <video> "(inline)"
  • <video> "(inline)"
Hoe te repareren

Add closed captions or subtitles to all video content.

Heading levels skip order

Belangrijk

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

WCAG 1.3.1
4 element(en) getroffen
  • <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)
Hoe te repareren

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

Frames missing title

Belangrijk

Iframes must have title attributes describing their content.

WCAG 2.4.1
3 element(en) getroffen
  • <iframe src="(no src)">
  • <iframe src="(no src)">
  • <iframe src="//s.thebrighttag.com/iframe?c=O14oOQO">
Hoe te repareren

Add descriptive title attributes to all <iframe> elements.

Duplicate element IDs

Belangrijk

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

WCAG 4.1.1
18 element(en) getroffen
  • 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"
Hoe te repareren

Make each id attribute value unique within the page.

Positive tabindex values

Belangrijk

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

WCAG 2.4.3
6 element(en) getroffen
  • <a tabindex="1">
  • <a tabindex="1">
  • <a tabindex="1">
  • <a tabindex="1">
  • <div tabindex="1">
Hoe te repareren

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

No skip navigation link

Belangrijk

Pages should have a mechanism to bypass repeated navigation blocks.

WCAG 2.4.1
1 element(en) getroffen
  • No skip navigation link found
Hoe te repareren

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

Invalid ARIA attributes

Belangrijk

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

WCAG 4.1.2
6 element(en) getroffen
  • <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)
Hoe te repareren

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

Prioritaire oplossingen

Dit zijn de meest impactvolle wijzigingen die playstation.com zou moeten doorvoeren:

  1. #1
    Images missing alt text Kritiek

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

  2. #2
    Links missing accessible name Kritiek

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

  3. #3
    Videos missing captions Kritiek

    Add closed captions or subtitles to all video content.

Veelgestelde vragen

Is playstation.com toegankelijk?

playstation.com scoorde 0/100 (cijfer F) in onze audit. Deze score weerspiegelt geautomatiseerde controles volgens WCAG 2.1 Level AA.

Is playstation.com WCAG-conform?

Onze scan vond 10 toegankelijkheidsproblemen op playstation.com. Volledige WCAG-conformiteit vereist het oplossen van alle kritieke en grote problemen.

Is playstation.com EAA-conform?

De Europese Toegankelijkheidswet vereist dat websites voldoen aan WCAG 2.1 AA. Bekijk het rapport hierboven voor de conformiteitsstatus van playstation.com.

Welke toegankelijkheidsproblemen heeft playstation.com?

Bekijk de volledige probleemlijst hierboven met ernst, getroffen elementen en aanbevolen oplossingen voor playstation.com.

Scan uw eigen website

Ontvang in seconden een gratis toegankelijkheidsrapport.