Skip to content
https://ea.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
6
REVIEW
6
PASS
1
INFO
0
Checks
13
1 PASS 6 REVIEW 6 FIX
D
Alt Text Quality
Action
2 of 13 images have issues
FIX
2 of 13 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with alt text over 125 characters
Info::
6 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
13 images 4 good alt text 6 decorative 2 missing
IssueCount
missing2 image(s)
too long1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) 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::
HTML icon links detected
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'>.
favicon.ico Missing
PNG Icons Present
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark 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!) MAIN ASIDE "Open Cookie Preferences Modal" CONTENTINFO footer

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

C
Heading Hierarchy
Action
8 headings
REVIEW
8 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
3 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 [[ eyebrowText ]][[ eyebrowSecondaryText ]]
  • H3 (empty)
  • H2 [[ eyebrowSecondaryText ]]
  • H3 (empty)
  • H3 (empty)
  • H3 Featured Games
  • H3 Latest Updates
  • H2 Unlock a world of thrill

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title 404 - Official EA Site Custom Styling Navigation Homepage Link Search Form
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA 1 pass AA only
h2 Unlock a world of thrill
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Featured Games
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Latest Updates
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
title Electronic Arts Home Page - Official EA …
1.16:1
#000000
on
#161616
needs 4.5:1 (normal text)
16px · top of page (header area)
a EA Originals
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a Games Library
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a EA app Deals
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a PlayStation
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Unlock a world of th…1.00:13.0:1
#000000
#000000
Fail
h3 Featured Games1.00:13.0:1
#000000
#000000
Fail
h3 Latest Updates1.00:13.0:1
#000000
#000000
Fail
title Electronic Arts Home…1.16:14.5:1
#000000
#161616
Fail
a EA Play8.23:14.5:1
#000000
#A2A2A2
Pass
a FIFA 2321.00:14.5:1
#000000
#FFFFFF
Pass
a F1™ 2218.26:14.5:1
#000000
#D7F4FE
Pass
a Madden NFL 2317.52:14.5:1
#000000
#CEF0FE
Pass
a Apex Legends17.46:14.5:1
#000000
#CCF0FE
Pass
a Battlefield™ 204217.32:14.5:1
#000000
#CBEFFE
Pass
a The Sims 417.35:14.5:1
#000000
#CCEFFE
Pass
a Electronic Arts Home17.32:14.5:1
#000000
#CBEFFE
Pass
a Latest Games17.35:14.5:1
#000000
#CCEFFE
Pass
a Coming Soon17.32:14.5:1
#000000
#CBEFFE
Pass
a Free-To-Play17.32:14.5:1
#000000
#CBEFFE
Pass
a EA SPORTS6.27:14.5:1
#000000
#7A9098
Pass
a EA Originals1.00:14.5:1
#000000
#000000
Fail
a Games Library1.00:14.5:1
#000000
#000000
Fail
a EA app Deals1.00:14.5:1
#000000
#000000
Fail
a PlayStation1.00:14.5:1
#000000
#000000
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.

B
Lighthouse Accessibility Audits
Score 87/100 — 5 failing, 26 passed
REVIEW
87

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Battlefield 6 span.eapl-game-box__side-toggle
FC 26 span.eapl-game-box__side-toggle
EA SPORTS™ College Football 26 span.eapl-game-box__side-toggle
The Sims 4 span.eapl-game-box__side-toggle
Apex Legends span.eapl-game-box__side-toggle

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Privacy and Cookie Policy div#truste-consent-text > p > span.no-gpc-detected > a#truste-privacy-button

These are opportunities to improve the legibility of your content.

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
Experience unlimited access to a collection of top EA titles, trials of select … div.eapl-hero__content > h6.eapl-hero__body

These are opportunities to improve keyboard navigation in your application.

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
Austria Belgium Bulgaria Croatia Cyprus Czech Republic Denmark Estonia Finland … select#select
United States United Kingdom Australia France Deutschland Italia 日本 Polska Bras… select#select

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Your Privacy Choices ea-network-footer > ea-network-legal > div#teconsent > a#icon-id0700976302464887
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
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
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.
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
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Document has a main landmark.
Deprecated ARIA roles were not used
All heading elements contain content.
Identical links have the same purpose.
`[accesskey]` values are unique
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
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
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Skip links are focusable.
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.
`<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.
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+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback