Skip to content
https://screenrant.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
5
REVIEW
8
PASS
0
INFO
0
Checks
13
8 REVIEW 5 FIX
F
Heading Hierarchy
Action
55 headings, 4 skip(s)
FIX
55 headings, 4 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Michael's Projected Box Office Record Climbs Despite Rotten Tomatoes Debut
  • H3 X-Files Reboot Gets Seal Of Approval From Yet Another Original Star
  • H3 Helaena Targaryen’s House Of The Dragon Season 3 Return Revealed
  • H3 Normal Is A Final Destination-Style “Anti-Action” Movie
  • H3 Michael Review
  • H2 Popular News
  • H3 Netflix's 5-Part 'Squid Game Meets Ocean's 11' Series Has Some Of Its Best Plot Twists
  • H3 MGM+'s From Season 4 Returns To Record Audience Rotten Tomatoes Score
  • H3 10 Best Villains In Invincible Season 4, Ranked
  • H3 Taylor Sheridan’s Adaptation Of A Controversial Non-Fiction Book Will Be His Most Important Western
  • H2 Movie Reviews
  • H5 You, Me & Tuscany Review: A Predictable Romcom Saved By The Charm Of Its Stars skipped
  • H5 Outcome Review: Jonah Hill’s Hollywood Satire Misuses Keanu Reeves
  • H5 Jerry Maguire Review: 30 Years Later, This Tom Cruise Classic Feels Like It’s From A Bygone Era
  • H2 TV Reviews
  • H5 Daredevil: Born Again Season 2 Review - This Is The Show Marvel Fans Have Been Waiting For skipped
  • H5 For All Mankind Season 5 Review: Apple TV's Otherworldly Sci-Fi Is At Its Peak
  • H5 Sullivan's Crossing Season 4 Review: The CW's Drama Still Feels Like Home Despite Scott Patterson's Exit
  • H2 Exclusive Stories
  • H3 The Origins Of Bob Odenkirk & Derek Kolstad’s Violent New Nobody 2 Follow-Up Explained By Normal Director
  • H3 Matlock Finale Is "Emotionally Expensive" & Will Change Everything
  • H3 Michael Director Addresses Original 4-Hour Cut & Changes From "The Best Editors In The World"
  • H3 For All Mankind EPs Tease Even Bigger Mission Beyond Titan in Future Seasons
  • H3 Maggie Lawson Reveals Why Sarah’s Boston Blue Proposal Scene Was The Most Emotional Day On Set
  • H2 Shorts
  • H3 Top Gun 3 is coming but can it actually live up to Maverick’s success
  • H3 Steven Spielberg’s Disclosure Day is hiding something huge and that’s why the buzz keeps growing
  • H3 Alan Ritchson’s Reacher Is Exactly What Modern Action Needed
  • H3 Scream changed horror… so why does the franchise feel off now?
  • H3 Karl Urban Teases An Explosive Series Finale For The Boys
  • H2 Latest
  • H5 Netflix's 5-Part 'Squid Game Meets Ocean's 11' Series Has Some Of Its Best Plot Twists skipped
  • H5 MGM+'s From Season 4 Returns To Record Audience Rotten Tomatoes Score
  • H5 10 Best Villains In Invincible Season 4, Ranked
  • H5 Taylor Sheridan’s Adaptation Of A Controversial Non-Fiction Book Will Be His Most Important Western
  • H5 The Monsterverse Is Teasing A Twist The Godzilla Franchise Hasn't Seen In 35 Years
  • H5 Netflix's 8-Hour Supernatural Thriller That's Dark Meets Mike Flanagan Is One Of Its Best To Binge
  • H5 27 Years Later, DC's 3-Part Cyberpunk Series Is Still One Of The Genre's Best
  • H5 28 Years Later, Zoro Just Broke His Biggest Promise To Luffy With One Heartbreaking Moment
  • H5 Netflix's Emmy-Winning Thriller Series Returns With 58% Viewership Drop For Season 2
  • H5 HBO's 8-Part 'Stranger Things Meets Lovecraft' Series Fixed An Iconic Franchise
  • H5 Netflix's 3-Part Sci-Fi Series That's Designed To Be Binged Is One Of Its Best Space Shows
  • H5 After 39 Years, The Simpsons Is Right To Break Its Number 1 Rule
  • H5 What Star Wars Fans Need To Learn From Marvel's Greatest Living Writer
  • H5 Star Wars Officially Brings Back One Of The Most Broken Force Powers
  • H5 Robert Pattinson & Zendaya's New Movie Officially Crosses Rare Box Office Milestone In All Of A24's History
  • H5 DC Unveils a Batman Icon's Official Super Saiyan Form (Yes, Literally)
  • H5 Netflix’s #1 Hit Horror Series Proves The Streamer Will Be Just Fine Without Mike Flanagan
  • H5 Disney's New Movie Secretly Already Debuted Over 5 Years Ago
  • H5 Titus Welliver's 2025 Dracula Sequel Adaptation Officially Releases On Hulu Next Month
  • H5 The Day Of The Jackal Season 2 Images Reveal Eddie Redmayne's Return As The Deadly Assassin
  • H3 Trending
  • H5 Silo Promises To Be An Entirely New Show When It Returns For Season 3 skipped
  • H5 Harry Potter Still Hasn’t Officially Cast A Key Character Missing From The Movies
  • H5 Star Trek's 6 TV & Movie Eras Explained

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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
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::
3 navigation landmark(s) detected
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 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 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
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 ASIDE CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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
Alt Text Quality
5 of 57 images have issues
REVIEW
5 of 57 images have issues
Warning::
5 image(s) with generic alt text
Info::
2 image(s) with alt text over 125 characters
Info::
50 image(s) with good alt text
57 images 50 good alt text 5 generic
IssueCount
generic5 image(s)
too long2 image(s)
C
Form Accessibility
Action
3 of 13 controls have issues
REVIEW
3 of 13 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="showMoreToggle">; <input type="checkbox" id="expandMenuListDefault">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q" id="js-search-input">
Info::
10 control(s) properly labeled
13 controls
10 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
#side_menucheckboxMenufor/id
#navItems-MoviescheckboxSubmenufor/id
#navItems-TVcheckboxSubmenufor/id
#navItems-Reality TVcheckboxSubmenufor/id
#navItems-GamingcheckboxSubmenufor/id
#navItems-ComicscheckboxSubmenufor/id
#navItems-AnimecheckboxSubmenufor/id
#navItems-MusiccheckboxSubmenufor/id
#navItems-MorecheckboxMore Submenufor/id
#search-menucheckboxClosefor/id
#js-search-inputtext(Search ScreenRant)placeholder only
#showMoreTogglecheckbox(none)none
#expandMenuListDefaultcheckbox(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="checkbox" id="showMoreToggle">; <input type="checkbox" id="expandMenuListDefault">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="text" name="q" id="js-search-input">

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
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 ScreenRant ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
7 icon(s) detected
REVIEW
7 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
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 5 fail WCAG AA
REVIEW

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

15 pass 5 fail WCAG AA 1 pass AA only
title ScreenRant: Movie News, Movie Reviews, M…
1.10:1
#000000
on
#101010
needs 4.5:1 (normal text)
16px · top of page (header area)
span Menu
1.10:1
#000000
on
#101010
needs 4.5:1 (normal text)
16px · top of page (header area)
span Movie Lists
2.16:1
#000000
on
#4C4335
needs 4.5:1 (normal text)
16px · above the fold
span Movie Trailers
1.10:1
#000000
on
#11100E
needs 4.5:1 (normal text)
16px · above the fold
span Submenu
1.10:1
#000000
on
#101010
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Popular News18.76:13.0:1
#000000
#F2F2F2
Pass
h2 Movie Reviews18.76:13.0:1
#000000
#F2F2F2
Pass
h2 TV Reviews18.76:13.0:1
#000000
#F2F2F2
Pass
h2 Exclusive Stories18.76:13.0:1
#000000
#F2F2F2
Pass
h2 Shorts18.76:13.0:1
#000000
#F2F2F2
Pass
h2 Latest18.76:13.0:1
#000000
#F2F2F2
Pass
h3 Trending18.76:13.0:1
#000000
#F2F2F2
Pass
title ScreenRant: Movie Ne…1.10:14.5:1
#000000
#101010
Fail
span Menu1.10:14.5:1
#000000
#101010
Fail
span Sign in now15.20:14.5:1
#000000
#F2D8AD
Pass
span Close16.33:14.5:1
#000000
#F8E0B6
Pass
span Movies17.47:14.5:1
#000000
#FBE8C7
Pass
span Submenu18.11:14.5:1
#000000
#FBEDCE
Pass
span Movie Features16.86:14.5:1
#000000
#F4E5C5
Pass
span Movie News11.96:14.5:1
#000000
#D0C2A8
Pass
span Movie Reviews5.94:14.5:1
#000000
#928774
Pass
span Movie Lists2.16:14.5:1
#000000
#4C4335
Fail
span Movie Trailers1.10:14.5:1
#000000
#11100E
Fail
span Submenu1.10:14.5:1
#000000
#101010
Fail
span TV Features18.76:14.5:1
#000000
#F2F2F2
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.

B
Lighthouse Accessibility Audits
Score 81/100 — 5 failing, 20 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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.w-hub-video > div#left-block-articles > div.w-control-arrows > button#previous-btn div.w-hub-video > div#left-block-articles > div.w-control-arrows > button#previous-btn
div.w-hub-video > div#left-block-articles > div.w-control-arrows > button#next-btn div.w-hub-video > div#left-block-articles > div.w-control-arrows > button#next-btn

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text

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.

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
SEE MORE div.left-column > div.w-hub-video > div.hub-header > a.section-view-all-link
SEE MORE div.right-column > div#left-block > div.hub-header > a.section-view-all-link
Mar 25, 2026 div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
Mar 23, 2026 div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
Apr 18, 2026 div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
SEE MORE section#exclusives > div.w-hub-widgets > div.hub-header > a.section-view-all-link
SEE MORE section#shorts > div.w-hub-widgets > div.hub-header > a.section-view-all-link
ALL div.section-header > div.listing-tabs > div > a#listing-tabs-latest
2 minutes ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
6 minutes ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
17 minutes ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
32 minutes ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 hour ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 hour ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 hour ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
3 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
3 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
3 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
3 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
3 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
3 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
3 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
3 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date

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
You, Me & Tuscany Review: A Predictable Romcom Saved By The Charm Of Its Stars div#left-block-articles > div.display-card > div.w-display-card-content > h5.display-card-title
Daredevil: Born Again Season 2 Review - This Is The Show Marvel Fans Have Been … div.hub-vertical-list > div.display-card > div.w-display-card-content > h5.display-card-title
Netflix's 5-Part 'Squid Game Meets Ocean's 11' Series Has Some Of Its Best Plot… div.sentinel-home-list > div.display-card > div.w-display-card-content > h5.display-card-title

These are opportunities to improve keyboard navigation in your application.

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
Liam Crowley div.w-display-card-meta > div.w-author > div.w-author-name > a.meta_txt
div.w-display-card-details > div.w-display-card-extra > div.total-info > a.total-info-number div.w-display-card-details > div.w-display-card-extra > div.total-info > a.total-info-number
Tatiana Hullender div.w-display-card-meta > div.w-author > div.w-author-name > a.meta_txt
div.w-display-card-details > div.w-display-card-extra > div.total-info > a.total-info-number div.w-display-card-details > div.w-display-card-extra > div.total-info > a.total-info-number
Join Our Team div.footer-content-el > ul > li > a.text
Our Audience div.footer-content-el > ul > li > a.text
About Us div.footer-content-el > ul > li > a.text
Press & Events div.footer-content-el > ul > li > a.text
Review Policy div.footer-content-el > ul > li > a.text
Media Coverage div.footer-content-el > ul > li > a.text
Contact Us div.footer-content-el > ul > li > a.text
Advertising div.footer-content-el > ul.align-right > li > a.text
Careers div.footer-content-el > ul.align-right > li > a.text
Terms div.footer-content-el > ul.align-right > li > a.text
Privacy div.footer-content-el > ul.align-right > li > a.text
Policies div.footer-content-el > ul.align-right > li > a.text

These items highlight common accessibility best practices.

○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
●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.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●Elements use only permitted ARIA attributes
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○`<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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback