Skip to content
https://asroma.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
71
GRADE
C
FIX
6
REVIEW
11
PASS
7
INFO
0
Checks
24
7 PASS 11 REVIEW 6 FIX
D
Mobile Keyboard & Autofill
Action
2/2 eligible field(s) missing autocomplete or inputmode
FIX
2/2 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.
Got: <input type="email">
Warning::
1 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.
Got: <input type="email">
D
Tabindex Anti-Patterns
Action
0 positive, 20 -1-on-focusable
FIX
0 positive, 20 -1-on-focusable
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
tabindex="-1" on naturally-focusable <button>
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.)
Info::
tabindex="-1" on naturally-focusable <button>
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.)
Info::
tabindex="-1" on naturally-focusable <button>
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.)
Info::
tabindex="-1" on naturally-focusable <button>
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.)
Info::
tabindex="-1" on naturally-focusable <button>
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.)
Info::
tabindex="-1" on naturally-focusable <button>
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.)
Info::
tabindex="-1" on naturally-focusable <button>
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.)
Info::
tabindex="-1" on naturally-focusable <button>
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.)
Info::
tabindex="-1" on naturally-focusable <button>
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
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::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (2 found)
A page should have only one <main> landmark.
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
No contentinfo (footer) 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 header NAV "Main site navigation" MAIN CONTENTINFO (missing!)

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

B
Heading Hierarchy
42 headings
REVIEW
42 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Info::
1 hidden heading(s) (aria-hidden)
  • H3 Authentic Match Jersey 2026/27
  • H3 AS Roma Away Authentic Match Shorts 2026/27
  • H3 Away Jersey 2026/27
  • H3 Away Jersey 2026/27, Kids
  • H3 Away Baby Kit 2026/27 3 - 18 months
  • H3 Home Authentic Match Jersey 2026/27
  • H3 AS Roma Home Authentic Match Shorts 2026/27
  • H3 Home Jersey 2026/27
  • H3 Home Match Jersey 2026/27, Woman
  • H3 2026/27 Goalkeeper Match Jersey, Green
  • H3 Home Jersey 2026/27, Kids
  • H3 Home Match Mini Kit 2026/27 18 months - 6 years
  • H3 Home Baby Kit 2026/27 3 - 18 months
  • H3 Hooded Full-Zip Anthem Jacket 2026/27
  • H3 AS Roma Travel Cotton T-Shirt 2026/27
  • H3 AS Roma Sweatshirt Travel 2026/27
  • H3 Track Top Travel with full zip AS Roma 2026/27
  • H3 Training Jersey 2026/27
  • H3 Sleeveless Training Jersey 2026-27
  • H3 Training Shorts 2026-27
  • H3 Saint Barth “Portofino” "Roma Ti Amo" T-shirt, Men's, White
  • H3 Saint Barth AS Roma Swimsuit with Lupetto Logo Print, Men, Red
  • H3 Saint Barth "Portofino" "Roma Ti Amo" T-shirt, Kids, White
  • H3 Saint Barth AS Roma Swimsuit with Lupetto Logo Print, Men, Red
  • H2 .
  • H2 ..
  • H2 Cookies on AS Roma websites
  • H2 Privacy Preference Center
  • H2 Privacy Preference Center hidden
  • H3 Your Privacy
  • H3 Performance Cookies
  • H3 Targeting Cookies
  • H3 Social Media Cookies
  • H3 Functional Cookies
  • H3 Strictly Necessary Cookies
  • H4 Your Privacy
  • H4 Performance Cookies
  • H4 Targeting Cookies
  • H4 Social Media Cookies
  • H4 Functional Cookies
  • H4 Strictly Necessary Cookies
  • H3 Cookie List

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

C
Alt Text Quality
Action
8 of 165 images have issues
REVIEW
8 of 165 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
6 image(s) with generic alt text
Info::
5 decorative image(s) correctly marked
Info::
152 image(s) with good alt text
165 images 152 good alt text 5 decorative 6 generic 2 missing
IssueCount
missing2 image(s)
generic6 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

B
Form Accessibility
4 of 15 controls have issues
REVIEW
4 of 15 controls have issues
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="query">; <input type="text" name="query">; <input type="email">; <input type="text" name="phone" id="phone-number">
Info::
11 control(s) properly labeled
15 controls
11 labeled
4 placeholder only
0 unlabeled
ControlTypeLabelMethod
#menu-checkboxcheckboxmenuaria-label
#privacy-checkboxcheckboxI confirm that I have read the privacy policy.for/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#ot-group-id-C0005checkboxSocial Media Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#chkbox-idcheckboxcheckbox labelfor/id
inputemail(Email address)placeholder only
#phone-numbertext(Phone Number)placeholder only
querytext(Search here ...)placeholder only
querytext(Search...)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="query">; <input type="text" name="query">; <input type="email">; <input type="text" name="phone" id="phone-number">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

B
Form Input Types
4 input(s) using type=text where a specific type would help
REVIEW
4 input(s) using type=text where a specific type would help
Info::
Input "query" should use type="search" (currently type="text")
Field name "query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "query" should use type="search" (currently type="text")
Field name "query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "phone" should use type="tel" (currently type="text")
Field name "phone" suggests type="tel". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="tel">.
Info::
Input "vendor-search-handler" should use type="search" (currently type="text")
Field name "vendor-search-handler" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
B
Iframe Accessibility
2/4 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/4 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
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.
Warning::
<iframe> missing title attribute (src="https://identity.asroma.com/js/sso.htm?APIKey=3_gt294H9QAFy3KB3mMbUm6fhaIUoduC7…")
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.
B
Tap Target Adequacy
1 tap target(s) too small or too close together
REVIEW
1 tap target(s) too small or too close together
Info::
1 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Fuori gioco - offside! - AS Roma ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 81/100 — 6 failing, 25 passed
REVIEW
81

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

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to last slide div.asr-shop__main-wrapper > div#shop-Away Kit 2026/27 > div.splide__arrows > button.splide__arrow
Next slide div.asr-shop__main-wrapper > div#shop-Away Kit 2026/27 > div.splide__arrows > button.splide__arrow
Go to slide 1 div#shop-Away Kit 2026/27 > ul.splide__pagination > li > button.splide__pagination__page
Go to slide 2 div#shop-Away Kit 2026/27 > ul.splide__pagination > li > button.splide__pagination__page
Go to slide 3 div#shop-Away Kit 2026/27 > ul.splide__pagination > li > button.splide__pagination__page
Go to slide 4 div#shop-Away Kit 2026/27 > ul.splide__pagination > li > button.splide__pagination__page
Go to slide 5 div#shop-Away Kit 2026/27 > ul.splide__pagination > li > button.splide__pagination__page

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
login icon div.asr-header__controls > div.asr-header__account > div.asr-header__account-btn > div.asr-header__login-btn-icon

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
AWAY KIT 2026/27 div.asr-shop > header.asr-shop__header > div.asr-shop__tabs > button.asr-shop__tab
HOME KIT 2026/27 div.asr-shop > header.asr-shop__header > div.asr-shop__tabs > button.asr-shop__tab
TRAINING KIT 2026/27 div.asr-shop > header.asr-shop__header > div.asr-shop__tabs > button.asr-shop__tab
SAINT BARTH div.asr-shop > header.asr-shop__header > div.asr-shop__tabs > button.asr-shop__tab
TICKETS div.asr-page-footer__alpha-wrapper > div.asr-page-footer__menu > div.asr-page-footer__menu-root > div.asr-page-footer__menu-root-link
TEAMS div.asr-page-footer__alpha-wrapper > div.asr-page-footer__menu > div.asr-page-footer__menu-root > div.asr-page-footer__menu-root-link
ROMANISTI div.asr-page-footer__alpha-wrapper > div.asr-page-footer__menu > div.asr-page-footer__menu-root > div.asr-page-footer__menu-root-link
CLUB div.asr-page-footer__alpha-wrapper > div.asr-page-footer__menu > div.asr-page-footer__menu-root > div.asr-page-footer__menu-root-link
NEWS div.asr-page-footer__alpha-wrapper > div.asr-page-footer__menu > div.asr-page-footer__menu-root > a.asr-page-footer__menu-root-link
AS ROMA STORES div.asr-page-footer__menu > div.asr-page-footer__menu-root > div.asr-page-footer__menu-children > a.asr-page-footer__menu-child
ONLINE STORE div.asr-page-footer__menu > div.asr-page-footer__menu-root > div.asr-page-footer__menu-children > a.asr-page-footer__menu-child
STADIUM div.asr-page-footer__menu > div.asr-page-footer__menu-root > div.asr-page-footer__menu-children > a.asr-page-footer__menu-child
CONTACT US div.asr-page-footer__menu > div.asr-page-footer__menu-root > div.asr-page-footer__menu-children > a.asr-page-footer__menu-child
© 2018-2026 A.S. Roma S.r.l. – EU VAT IT01180281006 - all rights reserved. The … div.asr-page-footer__beta > div.asr-page-footer__beta-wrapper > div.asr-page-footer__copyright-notice > p

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.gc-col-12 > div.asr-homepage-latest-articles > div.slider-controls > img.slider-arrow-left div.gc-col-12 > div.asr-homepage-latest-articles > div.slider-controls > img.slider-arrow-left
div.gc-col-12 > div.asr-homepage-latest-articles > div.slider-controls > img.slider-arrow-right div.gc-col-12 > div.asr-homepage-latest-articles > div.slider-controls > img.slider-arrow-right

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to slide 1 div#shop-Away Kit 2026/27 > ul.splide__pagination > li > button.splide__pagination__page

These items highlight common accessibility best practices.

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
AS Roma cookie policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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
●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
●`[role]` values are valid
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○`<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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○`[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.
○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
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
2 heading(s) are too short (≤2 characters) to convey meaning
Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H2: "." - H2: ".."
Got: 2 ≤2-char heading(s)
A+
Form Input Quality
15 form control(s) checked, no input-semantic issues
PASS
15 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Mobile-Readable Font Sizes
All 1 visible text node(s) render at >= 12 CSS pixels
PASS
All 1 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Cookies on AS Roma w…17.94:13.0:1
#000000
#EDEDED
Pass
h2 Privacy Preference C…17.94:13.0:1
#000000
#EDEDED
Pass
h2 Privacy Preference C…17.94:13.0:1
#000000
#EDEDED
Pass
h3 Authentic Match Jers…17.94:13.0:1
#000000
#EDEDED
Pass
h3 AS Roma Away Authent…17.94:13.0:1
#000000
#EDEDED
Pass
h3 Away Jersey 2026/2717.94:13.0:1
#000000
#EDEDED
Pass
h3 Away Jersey 2026/27,…17.94:13.0:1
#000000
#EDEDED
Pass
h3 Away Baby Kit 2026/2…17.94:13.0:1
#000000
#EDEDED
Pass
h3 Home Authentic Match…17.94:13.0:1
#000000
#EDEDED
Pass
h3 AS Roma Home Authent…17.94:13.0:1
#000000
#EDEDED
Pass
h3 Home Jersey 2026/2717.94:13.0:1
#000000
#EDEDED
Pass
h3 Home Match Jersey 20…17.94:13.0:1
#000000
#EDEDED
Pass
h3 2026/27 Goalkeeper M…17.94:13.0:1
#000000
#EDEDED
Pass
h3 Home Jersey 2026/27,…17.94:13.0:1
#000000
#EDEDED
Pass
h3 Home Match Mini Kit …17.94:13.0:1
#000000
#EDEDED
Pass
h3 Home Baby Kit 2026/2…17.94:13.0:1
#000000
#EDEDED
Pass
h3 Hooded Full-Zip Anth…17.94:13.0:1
#000000
#EDEDED
Pass
h3 AS Roma Travel Cotto…17.94:13.0:1
#000000
#EDEDED
Pass
h3 AS Roma Sweatshirt T…17.94:13.0:1
#000000
#EDEDED
Pass
h3 Track Top Travel wit…17.94:13.0:1
#000000
#EDEDED
Pass

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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback