Accessibility

F

Heading Hierarchy

Action

31 headings, 3 skip(s)

FIX

31 headings, 3 skip(s)

Multiple H1 headings (3 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

2 empty heading(s)

Empty headings appear in the document outline but provide no information.

H3 The Oscars of Porn
H2 Welcome to Porn Oscars '24
H1 Latest Oscars Nominations
H4 Rii Igaki 井垣凛生 – RII 3 skipped
H4 Rii Igaki 井垣凛生 – RII 2
H4 Mutsuki Morii 守居睦喜 – MUTSUKI 6
H4 Shihoko Yanagi 柳詩歩子 – SHIHOKO 5
H4 Naho Sawabe 澤部梛邦 – NAHO 4
H4 Shihoko Yanagi 柳詩歩子 – SHIHOKO 4
H4 Serina Hiratsuka 平塚芹夏 – SERINA 2
H4 Harlee Rose, Tyler Nixon – ECG2283 A Fist Full Of Money
H1 Porn Oscars / Vote & Win Your favorite Porn Star! What? duplicate H1
H2 Search
H2 Oscars Categories
H2 Latest Nominations
H6 Rii Igaki 井垣凛生 – RII 3 skipped
H6 Rii Igaki 井垣凛生 – RII 2
H6 Mutsuki Morii 守居睦喜 – MUTSUKI 6
H6 Shihoko Yanagi 柳詩歩子 – SHIHOKO 5
H6 Naho Sawabe 澤部梛邦 – NAHO 4
H2 Vote & Win!
H2 Latest Thoughts
H2 Actual Stars
H2 Vote & Win!
H1 (empty)
H2 Latest Nominations
H4 Rii Igaki 井垣凛生 – RII 3 skipped
H2 Search Star / Title
H2 Hall Of Fame
H2 Porn Oscars
H2 (empty)

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

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

D

Web Manifest

Action

Not found

FIX

Not found

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

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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

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)

Skip navigation link detected

1 navigation landmark(s) detected

Breadcrumbs

Search

Skip Link Skip link detected

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.

B

Alt Text Quality

2 of 30 images have issues

REVIEW

2 of 30 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

12 decorative image(s) correctly marked

16 image(s) with good alt text

30 images 16 good alt text 12 decorative 2 missing

Issue	Count
missing	2 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

2 of 5 controls have issues

REVIEW

2 of 5 controls have issues

2 control(s) without accessible label

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

Got: <input type="submit">; <input type="submit">

3 control(s) properly labeled

5 controls

3 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
s	search	Search for:	none
#cat	select	Oscars Categories	for/id
s	search	Search for:	none
input	submit	(none)	none
input	submit	(none)	none

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

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

C

Link & Button Quality

Action

15 issue(s) across 124 links and 2 buttons

REVIEW

15 issue(s) across 124 links and 2 buttons

15 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://pornoscars.com/2026/08/11/rii-igaki-%e4%ba%95%e5%9e%a3%e5%87%9b%e7%94…; https://pornoscars.com/2026/08/11/rii-igaki-%e4%ba%95%e5%9e%a3%e5%87%9b%e7%94…; https://pornoscars.com/2026/08/10/rii-igaki-%e4%ba%95%e5%9e%a3%e5%87%9b%e7%94…; https://pornoscars.com/2026/08/08/mutsuki-morii-%e5%ae%88%e5%b1%85%e7%9d%a6%e…; https://pornoscars.com/2026/08/07/shihoko-yanagi-%e6%9f%b3%e8%a9%a9%e6%ad%a9%…; https://pornoscars.com/2026/08/07/naho-sawabe-%e6%be%a4%e9%83%a8%e6%a2%9b%e9%…; https://pornoscars.com/vote-win/; https://pornoscars.com/2026/08/11/rii-igaki-%e4%ba%95%e5%9e%a3%e5%87%9b%e7%94…; https://pornoscars.com/2024/11/23/zoey-zimmer-stepsis-gets-creampie-discount-…; https://pornoscars.com/2024/12/05/zoey-zimmer-santa-gets-more-than-cookies-th… (+5 more)

1 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: http://precisethemes.com/

108 link(s) with descriptive text

124 links

15 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://pornoscars.com/2026/08/11/rii-ig…	(empty)	empty	Add link text or aria-label
https://pornoscars.com/2026/08/11/rii-ig…	(empty)	empty	Add link text or aria-label
https://pornoscars.com/2026/08/10/rii-ig…	(empty)	empty	Add link text or aria-label
https://pornoscars.com/2026/08/08/mutsuk…	(empty)	empty	Add link text or aria-label
https://pornoscars.com/2026/08/07/shihok…	(empty)	empty	Add link text or aria-label
https://pornoscars.com/2026/08/07/naho-s…	(empty)	empty	Add link text or aria-label
https://pornoscars.com/vote-win/	(empty)	empty	Add link text or aria-label
https://pornoscars.com/2026/08/11/rii-ig…	(empty)	empty	Add link text or aria-label
http://www.waudit.cz/	<!-- document.write('<img load…	img no alt	Add alt attribute to the image
https://pornoscars.com/2024/11/23/zoey-z…	(empty)	empty	Add link text or aria-label
https://pornoscars.com/2024/12/05/zoey-z…	(empty)	empty	Add link text or aria-label
https://pornoscars.com/2024/12/10/zoey-z…	(empty)	empty	Add link text or aria-label
https://pornoscars.com/2024/11/25/zoey-z…	(empty)	empty	Add link text or aria-label
https://pornoscars.com/2024/11/29/zoey-t…	(empty)	empty	Add link text or aria-label
https://pornoscars.com/2024/12/20/zoey-t…	(empty)	empty	Add link text or aria-label
https://pornoscars.com/	(empty)	empty	Add link text or aria-label
http://precisethemes.com/	Precise	new tab	Add '(opens in new tab)' to text

110 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://pornoscars.com/2026/08/11/rii-igaki-%e4%ba%95%e5%9e%a3%e5%87%9b%e7%94…; https://pornoscars.com/2026/08/11/rii-igaki-%e4%ba%95%e5%9e%a3%e5%87%9b%e7%94…; https://pornoscars.com/2026/08/10/rii-igaki-%e4%ba%95%e5%9e%a3%e5%87%9b%e7%94…; https://pornoscars.com/2026/08/08/mutsuki-morii-%e5%ae%88%e5%b1%85%e7%9d%a6%e…; https://pornoscars.com/2026/08/07/shihoko-yanagi-%e6%9f%b3%e8%a9%a9%e6%ad%a9%…; https://pornoscars.com/2026/08/07/naho-sawabe-%e6%be%a4%e9%83%a8%e6%a2%9b%e9%…; https://pornoscars.com/vote-win/; https://pornoscars.com/2026/08/11/rii-igaki-%e4%ba%95%e5%9e%a3%e5%87%9b%e7%94…; https://pornoscars.com/2024/11/23/zoey-zimmer-stepsis-gets-creampie-discount-…; https://pornoscars.com/2024/12/05/zoey-zimmer-santa-gets-more-than-cookies-th… (+5 more)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

http://precisethemes.com/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

B

Tap Target Adequacy

2 tap target(s) too small or too close together

REVIEW

2 tap target(s) too small or too close together

2 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.

C

Mobile-Readable Font Sizes

Action

88% of visible text renders at >= 12 CSS px (7 below threshold)

REVIEW

88% of visible text renders at >= 12 CSS px (7 below threshold)

7 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <a> 10.0px ("Amber Angel"); <a> 10.0px ("Betzz"); <a> 10.0px ("Demy G"); <a> 10.0px ("Julia Devine"); <a> 10.0px ("Lovita Fate").

C

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

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 83/100 — 5 failing, 24 passed

REVIEW

83

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.

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
Rii Igaki 井垣凛生 – RII 3 `div.pt-cv-page > div.col-md-6 > div.pt-cv-ifield > h4.pt-cv-title`
Rii Igaki 井垣凛生 – RII 3 `div.pt-cv-page > div.col-md-12 > div.pt-cv-ifield > h6.pt-cv-title`
Rii Igaki 井垣凛生 – RII 3 `div.pt-cv-page > div.col-md-12 > div.pt-cv-ifield > h4.pt-cv-title`

These are opportunities to improve keyboard navigation in your application.

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.row > div.footer-copyright > div > img `div.row > div.footer-copyright > div > img`
div.row > div.footer-copyright > div > img `div.row > div.footer-copyright > div > img`

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.pt-cv-page > div.col-md-6 > div.pt-cv-ifield > a._self `div.pt-cv-page > div.col-md-6 > div.pt-cv-ifield > a._self`
div.pt-cv-page > div.col-md-12 > div.pt-cv-ifield > a._self `div.pt-cv-page > div.col-md-12 > div.pt-cv-ifield > a._self`
div.pt-cv-page > div.col-md-12 > div.pt-cv-ifield > a._self `div.pt-cv-page > div.col-md-12 > div.pt-cv-ifield > a._self`
div.pt-cv-page > div.col-md-12 > div.pt-cv-ifield > a._self `div.pt-cv-page > div.col-md-12 > div.pt-cv-ifield > a._self`
div.pt-cv-page > div.col-md-12 > div.pt-cv-ifield > a._self `div.pt-cv-page > div.col-md-12 > div.pt-cv-ifield > a._self`
div.pt-cv-page > div.col-md-12 > div.pt-cv-ifield > a._self `div.pt-cv-page > div.col-md-12 > div.pt-cv-ifield > a._self`
section#text-9 > div.textwidget > h1 > a `section#text-9 > div.textwidget > h1 > a`
div.pt-cv-page > div.col-md-12 > div.pt-cv-ifield > a._self `div.pt-cv-page > div.col-md-12 > div.pt-cv-ifield > a._self`
section#text-12 > div.textwidget > p > a `section#text-12 > div.textwidget > p > a`
div.pt-cv-page > div.col-md-6 > div.pt-cv-ifield > a._self `div.pt-cv-page > div.col-md-6 > div.pt-cv-ifield > a._self`
div.pt-cv-page > div.col-md-6 > div.pt-cv-ifield > a._self `div.pt-cv-page > div.col-md-6 > div.pt-cv-ifield > a._self`
div.pt-cv-page > div.col-md-6 > div.pt-cv-ifield > a._self `div.pt-cv-page > div.col-md-6 > div.pt-cv-ifield > a._self`
div.pt-cv-page > div.col-md-6 > div.pt-cv-ifield > a._self `div.pt-cv-page > div.col-md-6 > div.pt-cv-ifield > a._self`
div.pt-cv-page > div.col-md-6 > div.pt-cv-ifield > a._self `div.pt-cv-page > div.col-md-6 > div.pt-cv-ifield > a._self`
div.pt-cv-page > div.col-md-6 > div.pt-cv-ifield > a._self `div.pt-cv-page > div.col-md-6 > div.pt-cv-ifield > a._self`
section#text-2 > div.textwidget > h2 > a `section#text-2 > div.textwidget > h2 > a`

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. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Porn Oscars The Oscars of Porn `div.row > div.footer-copyright > div > a`
Porn Oscars `div.row > div.footer-copyright > div.site-info > a`
Precise `div.row > div.footer-copyright > div.site-info > a`

These are opportunities to improve the legibility of your content.

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
TOPlist `section#text-12 > div.textwidget > p > a#toplisteu206730`
section#text-12 > div.textwidget > p > a `section#text-12 > div.textwidget > p > a`

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

●Input buttons have discernible text.

●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.

●Select elements have associated label elements.

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○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 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

○Buttons have an accessible name

○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 type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○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>`.

○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

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Skip link target(s) don't exist on page: #content

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Page Structure — as a screen reader sees it

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+

Heading Text Quality

All 31 heading(s) have substantive, well-formed text

PASS

All 31 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Form Input Types

5 form control(s) checked, no type mismatches

PASS

5 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

5 form control(s) checked, no input-semantic issues

PASS

5 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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)

Element	Ratio	Required	FG	BG	Result
h1 Latest Oscars Nomina…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Search	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Oscars Categories	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Latest Nominations	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Vote & Win!	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Latest Thoughts	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Actual Stars	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Vote & Win!	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Latest Nominations	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Search Star / Title	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Hall Of Fame	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Porn Oscars	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The Oscars of Porn	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Latest Oscars Nomina…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Porn Oscars	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p The Oscars of Porn /…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Oscars 2024	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Actual Oscars Standi…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Latest Oscars Nomina…	21.00:1	4.5:1	#000000	#FFFFFF	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.