Skip to content
https://newgrounds.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
40
GRADE
F
FIX
9
REVIEW
3
PASS
1
INFO
0
Checks
13
1 PASS 3 REVIEW 9 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV SEARCH MAIN (missing!) CONTENTINFO (missing!)

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
Heading Hierarchy
Action
64 headings, 6 skip(s)
FIX
64 headings, 6 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Movie Title
  • H2 Featured Movies
  • H2 Featured Games
  • H2 Featured Art
  • H2 Featured Audio
  • H4 Solicitude skipped
  • H4 Phoenix Skies & Sayuri Anahi - Call Me
  • H4 Dusqk - Dreams99 (Softboy7 Remix)
  • H4 Sidequest - Score
  • H4 Endless Groove
  • H4 Buried From Inside (feat Ilya Mirosh)
  • H4 Teminite & SLUGZ - Underworld (Cloudy Parallels Remix)
  • H4 lasagna meal
  • H4 Far From Home...
  • H4 for lack of love
  • H4 Manni D.P. Character Voice Demo Reel | 2026
  • H4 Demo Reel
  • H4 Zombie-Pimp / 107 / A100
  • H4 Ben-To | Three Episode Rule 42
  • H2 Featured Series & Collections
  • H4 PUNCH PUNCH FOREVER! skipped
  • H4 Anomaly Report
  • H4 Bridge Kids
  • H4 Sublo & Tangy Mustard
  • H4 Voodoo Vids
  • H4 Madness
  • H4 Flash Foward 2026
  • H4 March 2026 Mix
  • H4 Ludum Dare 59
  • H4 Animation Schools
  • H2 Legendary Games
  • H4 Best of March 2026! skipped
  • H2 P-Bot's Daily Picks
  • H4 SUPER VATIS 3-D! skipped
  • H4 AI Knowledge
  • H4 Memory Card 3D Art Collab 2026
  • H4 Coin Club presents: Flip for your life!
  • H4 Murder T.V. pilot episode
  • H2 Artist News
  • H2 Takeover Tuesday's Top Picks
  • H4 SIX SEVEN THE GAME skipped
  • H4 Trail Cam Explorer
  • H4 Dragonic Troubles - Zaaztoons
  • H4 Memory Card 3D Art Collab 2026
  • H4 BNUUY POUNCE
  • H2 Best New Games & Movies!
  • H4 Sonya the Dog - Episode 5 "Salt" (Eng dub) skipped
  • H4 Nhoran64 Re-Animated - Spongebob SquarePants Scene 40!.
  • H4 Smell That?
  • H4 Bogus Pokus! Hat Wink
  • H4 Let's go Gambling [Frickbear's 3 animation]
  • H4 Splash Woman
  • H4 2D v 3D
  • H4 RiOT ROAD Short: Flying John
  • H4 quien sos vos? (español)
  • H4 CLOVER YOU FUCKING IDIOT
  • H4 Sonya vs Tsubaki (Pivot Sprites Battle)
  • H4 cornfed laugh
  • H2 Latest
  • H3 FEATUREDCONTENT
  • H4 Main Sections
  • H4 Extra, Extra!
  • H4 Community
  • H4 NG Related

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

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

F
Alt Text Quality
Action
6 of 115 images have issues
FIX
6 of 115 images have issues
Critical::
6 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
6 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 decorative image(s) correctly marked
Info::
108 image(s) with good alt text
115 images 108 good alt text 1 decorative 6 missing
IssueCount
missing6 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
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Page Title NG Guard ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #262425
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 ModePartial Dark Mode
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 1 <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.
C
Favicon & Branding
Action
11 icon(s) detected
REVIEW
11 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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Movie Title
1.49:1
#000000
on
#172F34
needs 3.0:1 (large text)
24px · mid-page · over background image/gradient
h2 Featured Movies
2.65:1
#000000
on
#515151
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Games
2.65:1
#000000
on
#515151
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Art
2.65:1
#000000
on
#515151
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Audio
2.65:1
#000000
on
#515151
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Series & Collections
2.65:1
#000000
on
#515151
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Legendary Games
2.65:1
#000000
on
#515151
needs 3.0:1 (large text)
24px · bottom of viewport
h2 P-Bot's Daily Picks
2.65:1
#000000
on
#515151
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Artist News
2.65:1
#000000
on
#515151
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Takeover Tuesday's Top Picks
2.65:1
#000000
on
#515151
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Best New Games & Movies!
2.65:1
#000000
on
#515151
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Latest
2.65:1
#000000
on
#515151
needs 3.0:1 (large text)
24px · bottom of viewport
title Newgrounds.com — Everything, By Everyo…
1.70:1
#000000
on
#323538
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
div Saving
1.42:1
#000000
on
#26282A
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
div NaN:NaN
1.03:1
#000000
on
#070506
needs 4.5:1 (normal text)
16px · top of page (header area)
div NaN:NaN
1.18:1
#000000
on
#161819
needs 4.5:1 (normal text)
16px · top of page (header area)
a Newgrounds
1.18:1
#000000
on
#171819
needs 4.5:1 (normal text)
16px · above the fold
a Login
1.90:1
#000000
on
#3B3C3D
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Sign Up
1.04:1
#000000
on
#03070A
needs 4.5:1 (normal text)
16px · above the fold
a Movies
1.37:1
#000000
on
#0C2836
needs 4.5:1 (normal text)
16px · above the fold

4 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Movie Title1.49:13.0:1
#000000
#172F34
Fail
h2 Featured Movies2.65:13.0:1
#000000
#515151
Fail
h2 Featured Games2.65:13.0:1
#000000
#515151
Fail
h2 Featured Art2.65:13.0:1
#000000
#515151
Fail
h2 Featured Audio2.65:13.0:1
#000000
#515151
Fail
h2 Featured Series & Co…2.65:13.0:1
#000000
#515151
Fail
h2 Legendary Games2.65:13.0:1
#000000
#515151
Fail
h2 P-Bot's Daily Picks2.65:13.0:1
#000000
#515151
Fail
h2 Artist News2.65:13.0:1
#000000
#515151
Fail
h2 Takeover Tuesday's T…2.65:13.0:1
#000000
#515151
Fail
h2 Best New Games & Mov…2.65:13.0:1
#000000
#515151
Fail
h2 Latest2.65:13.0:1
#000000
#515151
Fail
title Newgrounds.com — E…1.70:14.5:1
#000000
#323538
Fail
div Saving1.42:14.5:1
#000000
#26282A
Fail
div NaN:NaN1.03:14.5:1
#000000
#070506
Fail
div NaN:NaN1.18:14.5:1
#000000
#161819
Fail
a Newgrounds1.18:14.5:1
#000000
#171819
Fail
a Login1.90:14.5:1
#000000
#3B3C3D
Fail
a Sign Up1.04:14.5:1
#000000
#03070A
Fail
a Movies1.37:14.5:1
#000000
#0C2836
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 81/100 — 5 failing, 16 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.

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
HappyHarry div.span-1 > a.item-portalsubmission-small > div.item-details > span
nammac div.span-1 > a.item-portalsubmission-small > div.item-details > span
Junkster div.span-1 > a.item-portalsubmission-small > div.item-details > span
Northflowo div.span-1 > a.item-portalsubmission-small > div.item-details > span
reyamily div.span-1 > a.item-portalsubmission-small > div.item-details > span
DeskFable div.span-1 > a.item-portalsubmission-small > div.item-details > span
LunarDragonEnt div.span-1 > a.item-portalsubmission-small > div.item-details > span
Earth-Mage-2000 div.span-1 > a.item-portalsubmission-small > div.item-details > span
ActiveObjectX div.span-1 > a.item-portalsubmission-small > div.item-details > span
matt-likes-swords div.span-1 > a.item-portalsubmission-small > div.item-details > span
voidgazerBon div.span-1 > a.item-portalsubmission-small > div.item-details > span
rmcco div.span-1 > a.item-portalsubmission-small > div.item-details > span
Doriencey div.span-1 > a.item-portalsubmission-small > div.item-details > span
2dengine div.span-1 > a.item-portalsubmission-small > div.item-details > span
Cyranek div.span-1 > a.item-portalsubmission-small > div.item-details > span
Song — Drum N Bass div.item-audiosubmission-medium > a.item-link > div > span.notation
Song — Dubstep div.item-audiosubmission-medium > a.item-link > div > span.notation
Song — Drum N Bass div.item-audiosubmission-medium > a.item-link > div > span.notation
Song — Cinematic div.item-audiosubmission-medium > a.item-link > div > span.notation
Song — House div.item-audiosubmission-medium > a.item-link > div > span.notation
Song — Heavy Metal div.item-audiosubmission-medium > a.item-link > div > span.notation
Song — Dubstep div.item-audiosubmission-medium > a.item-link > div > span.notation
Song — Indie div.item-audiosubmission-medium > a.item-link > div > span.notation
Song — Drum N Bass div.item-audiosubmission-medium > a.item-link > div > span.notation
Song — Goth div.item-audiosubmission-medium > a.item-link > div > span.notation
Voice — Voice Demo div.item-audiosubmission-medium > a.item-link > div > span.notation
Voice — Voice Demo div.item-audiosubmission-medium > a.item-link > div > span.notation
Podcast — Discussion div.item-audiosubmission-medium > a.item-link > div > span.notation
Podcast — Discussion div.item-audiosubmission-medium > a.item-link > div > span.notation
by Sodoj div.item-details > div.item-details-main > div.detail-title > span
by ActiveObjectX div.item-details > div.item-details-main > div.detail-title > span
by pinmoBOT div.item-details > div.item-details-main > div.detail-title > span
by Junkster div.item-details > div.item-details-main > div.detail-title > span
by deathink div.item-details > div.item-details-main > div.detail-title > span
from MrPurpleMrPurple: li > a.item-user > div.item-details > div.news-author-small
from Repperoni: li > a.item-user > div.item-details > div.news-author-small
from ItsGrilledPasta: li > a.item-user > div.item-details > div.news-author-small
by MihaP div.item-details > div.item-details-main > div.detail-title > span
Game div.item-details-meta > dl > dd > strong.color-game
by StitchMiss div.item-details > div.item-details-main > div.detail-title > span
Game div.item-details-meta > dl > dd > strong.color-game
by Zaaz div.item-details > div.item-details-main > div.detail-title > span
Movie div.item-details-meta > dl > dd > strong.color-movie
by pinmoBOT div.item-details > div.item-details-main > div.detail-title > span
Game div.item-details-meta > dl > dd > strong.color-game
by Psycho-Dolphin div.item-details-main > div > div.detail-title > span
Illustration div.item-details-meta > dl > dd > strong.color-art
Games div.footer-navigation-cell > ul > li > a
Movies div.footer-navigation-cell > ul > li > a
Art div.footer-navigation-cell > ul > li > a
Audio div.footer-navigation-cell > ul > li > a
Your Feed div.footer-navigation-cell > ul > li > a
Series div.footer-navigation-cell > ul > li > a
Collections div.footer-navigation-cell > ul > li > a
Playlists div.footer-navigation-cell > ul > li > a
Game Judging div.footer-navigation-cell > ul > li > a
Movie Judging div.footer-navigation-cell > ul > li > a
Classic Portal div.footer-navigation-cell > ul > li > a
Snag a T-Shirt div.footer-navigation-cell > ul > li > a
Creator Resources div.footer-navigation-cell > ul > li > a
Forums div.footer-navigation-cell > ul > li > a
Chat div.footer-navigation-cell > ul > li > a
Calendar div.footer-navigation-cell > ul > li > a
Artist News div.footer-navigation-cell > ul > li > a
Rankings div.footer-navigation-cell > ul > li > a
NG Wiki div.footer-navigation-cell > ul > li > a
About div.footer-navigation-cell > ul > li > a
Help / FAQ div.footer-navigation-cell > ul > li > a
Contact Us div.footer-navigation-cell > ul > li > a
Support NG! div.footer-navigation-cell > ul > li > a
The Staff div.footer-navigation-cell > ul > li > a
History div.footer-navigation-cell > ul > li > a
RSS div.footer-navigation-cell > ul > li > a
Copyright div.footer-navigation-cell > ul > li > a

These are opportunities to improve the legibility of your content.

Tables and lists

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Game 2,012 Views (Everyone) a.item-portalsubmission > div.item-details > div.item-details-meta > dl
Game 1,715 Views (Everyone) a.item-portalsubmission > div.item-details > div.item-details-meta > dl
Movie 2,160 Views (Ages 13+) a.item-portalsubmission > div.item-details > div.item-details-meta > dl
Game 405 Views (Ages 13+) a.item-portalsubmission > div.item-details > div.item-details-meta > dl
Illustration 171 Views (Ages 13+) a.item-portalitem-art > div.item-details > div.item-details-meta > dl

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
Solicitude div.item-audiosubmission-medium > a.item-link > div > h4.detail-title
PUNCH PUNCH FOREVER! div.item-details > div.item-details-main > div.detail-title > h4
SUPER VATIS 3-D! div.item-details > div.item-details-main > div.detail-title > h4
SIX SEVEN THE GAME div.item-details > div.item-details-main > div.detail-title > h4

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
Games div.footer-navigation-cell > ul > li > a
Movies div.footer-navigation-cell > ul > li > a
Art div.footer-navigation-cell > ul > li > a
Audio div.footer-navigation-cell > ul > li > a
Your Feed div.footer-navigation-cell > ul > li > a
Series div.footer-navigation-cell > ul > li > a
Collections div.footer-navigation-cell > ul > li > a
Playlists div.footer-navigation-cell > ul > li > a
Game Judging div.footer-navigation-cell > ul > li > a
Movie Judging div.footer-navigation-cell > ul > li > a
Classic Portal div.footer-navigation-cell > ul > li > a
Snag a T-Shirt div.footer-navigation-cell > ul > li > a
Forums div.footer-navigation-cell > ul > li > a
Chat div.footer-navigation-cell > ul > li > a
Calendar div.footer-navigation-cell > ul > li > a
Artist News div.footer-navigation-cell > ul > li > a
Rankings div.footer-navigation-cell > ul > li > a
NG Wiki div.footer-navigation-cell > ul > li > a
About div.footer-navigation-cell > ul > li > a
Help / FAQ div.footer-navigation-cell > ul > li > a
Contact Us div.footer-navigation-cell > ul > li > a
Support NG! div.footer-navigation-cell > ul > li > a
The Staff div.footer-navigation-cell > ul > li > a
History div.footer-navigation-cell > ul > li > a
RSS div.footer-navigation-cell > ul > li > a
Copyright div.footer-navigation-cell > ul > li > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.webkit html.webkit

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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●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.
●Definition list items are wrapped in `<dl>` elements
●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
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○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
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted 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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○The page contains a heading, skip link, or landmark region
○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
○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.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#topsearch_texttextSearch Newgrounds...aria-label
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback