Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 6 REVIEW 5 FIX

Tabindex Anti-Patterns

Action

0 positive, 170 -1-on-focusable

FIX

0 positive, 170 -1-on-focusable

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

tabindex="-1" on naturally-focusable <a>

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.

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.

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 ✗

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Back-to-top link detected

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Link & Button Quality

2 issue(s) across 316 links and 1 buttons

REVIEW

2 issue(s) across 316 links and 1 buttons

2 link(s) with no accessible text

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

Got: #; a#scroll-up

2 link(s) open in new tab without warning

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

Got: https://pkadoras.com; https://afthemes.com/products/chromenews/

312 link(s) with descriptive text

316 links

2 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
#	(empty)	empty	Add link text or aria-label
https://pkadoras.com	escorts	new tab	Add '(opens in new tab)' to text
https://afthemes.com/products/chromenews…	ChromeNews	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label

313 links and buttons have descriptive text

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

#; a#scroll-up

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.

https://pkadoras.com; https://afthemes.com/products/chromenews/

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

Mobile-Readable Font Sizes

97% of visible text renders at >= 12 CSS px (2 below threshold)

REVIEW

97% of visible text renders at >= 12 CSS px (2 below threshold)

2 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: <span> 0.0px ("Botón claro/oscuro"); <a> 0.0px ("Suscríbete").

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.

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA 2 pass AA only

title Uber Porno - En la era del delivery de s…

1.29:1

#000000

#202020

needs 4.5:1 (normal text)

16px · top of page (header area)

a Inicio

2.28:1

#000000

#003BB3

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
title Uber Porno - En la e…	1.29:1	4.5:1	#000000	#202020	Fail
a Saltar al contenido	4.82:1	4.5:1	#000000	#797979	Pass
span agosto 12, 2026	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span 11:26:25 AM	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Uber Porno	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p En la era del delive…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Menú principal	6.06:1	4.5:1	#000000	#6689D1	Pass
a Inicio	2.28:1	4.5:1	#000000	#003BB3	Fail
a Galerías	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Listas	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Posteos	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Botón claro/oscuro	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Buscar:	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Suscríbete	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Últimas noticias	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span La evolución de las…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span De las webcams caser…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span El advenimiento de l…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Las 15 aplicaciones …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Amor, lujuria y algo…	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.

Lighthouse Accessibility Audits

Score 87/100 — 3 failing, 25 passed

REVIEW

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Menú principal `div.offcanvas-navigaiton > div.navigation-container > nav.main-navigation > span.toggle-menu`

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
escorts `div.col-66 > div.read-descprition > div.post-description > a`

These are opportunities to improve the legibility of your content.

Names and labels

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.header-promotion > div.banner-promotions-wrapper > div.promotion-section > a `div.header-promotion > div.banner-promotions-wrapper > div.promotion-section > 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.

○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

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

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

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

Heading Hierarchy

66 headings, 1 skip(s)

PASS

66 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H4 (missing H2)

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

H1 Uber Porno
H4 La evolución de las citas personales skipped
H4 De las webcams caseras a OnlyFans: la revolución del contenido íntimo en la era digital
H4 El advenimiento de la IA en las relaciones amorosas y sexuales
H4 Las 15 aplicaciones de encuentros más usadas en el mundo
H4 Amor, lujuria y algoritmos: la era moderna de la intimidad digital
H4 La evolución de las citas personales
H4 De las webcams caseras a OnlyFans: la revolución del contenido íntimo en la era digital
H4 El advenimiento de la IA en las relaciones amorosas y sexuales
H4 Las 15 aplicaciones de encuentros más usadas en el mundo
H4 Amor, lujuria y algoritmos: la era moderna de la intimidad digital
H3 Amor, lujuria y algoritmos: la era moderna de la intimidad digital
H3 La evolución de las citas personales
H3 De las webcams caseras a OnlyFans: la revolución del contenido íntimo en la era digital
H3 El advenimiento de la IA en las relaciones amorosas y sexuales
H3 Las 15 aplicaciones de encuentros más usadas en el mundo
H3 Amor, lujuria y algoritmos: la era moderna de la intimidad digital
H3 La evolución de las citas personales
H3 De las webcams caseras a OnlyFans: la revolución del contenido íntimo en la era digital
H3 El advenimiento de la IA en las relaciones amorosas y sexuales
H3 Las 15 aplicaciones de encuentros más usadas en el mundo
H3 Amor, lujuria y algoritmos: la era moderna de la intimidad digital
H2 Tendencias Ahora
H3 Las 15 aplicaciones de encuentros más usadas en el mundo
H3 Amor, lujuria y algoritmos: la era moderna de la intimidad digital
H3 La evolución de las citas personales
H3 De las webcams caseras a OnlyFans: la revolución del contenido íntimo en la era digital
H3 El advenimiento de la IA en las relaciones amorosas y sexuales
H3 Las 15 aplicaciones de encuentros más usadas en el mundo
H3 Amor, lujuria y algoritmos: la era moderna de la intimidad digital
H3 La evolución de las citas personales
H3 De las webcams caseras a OnlyFans: la revolución del contenido íntimo en la era digital
H3 El advenimiento de la IA en las relaciones amorosas y sexuales
H3 Las 15 aplicaciones de encuentros más usadas en el mundo
H3 Amor, lujuria y algoritmos: la era moderna de la intimidad digital
H2 Selecciones del editor
H3 El advenimiento de la IA en las relaciones amorosas y sexuales
H3 Las 15 aplicaciones de encuentros más usadas en el mundo
H3 Amor, lujuria y algoritmos: la era moderna de la intimidad digital
H3 La evolución de las citas personales
H3 De las webcams caseras a OnlyFans: la revolución del contenido íntimo en la era digital
H3 El advenimiento de la IA en las relaciones amorosas y sexuales
H3 Las 15 aplicaciones de encuentros más usadas en el mundo
H3 Amor, lujuria y algoritmos: la era moderna de la intimidad digital
H3 La evolución de las citas personales
H3 De las webcams caseras a OnlyFans: la revolución del contenido íntimo en la era digital
H3 El advenimiento de la IA en las relaciones amorosas y sexuales
H3 Las 15 aplicaciones de encuentros más usadas en el mundo
H3 Amor, lujuria y algoritmos: la era moderna de la intimidad digital
H2 Entradas destacadas
H3 La evolución de las citas personales
H3 De las webcams caseras a OnlyFans: la revolución del contenido íntimo en la era digital
H3 El advenimiento de la IA en las relaciones amorosas y sexuales
H3 Las 15 aplicaciones de encuentros más usadas en el mundo
H3 Amor, lujuria y algoritmos: la era moderna de la intimidad digital
H3 La evolución de las citas personales
H3 De las webcams caseras a OnlyFans: la revolución del contenido íntimo en la era digital
H3 El advenimiento de la IA en las relaciones amorosas y sexuales
H3 Las 15 aplicaciones de encuentros más usadas en el mundo
H3 Amor, lujuria y algoritmos: la era moderna de la intimidad digital
H2 Te pueden interesar
H3 La evolución de las citas personales
H3 De las webcams caseras a OnlyFans: la revolución del contenido íntimo en la era digital
H3 El advenimiento de la IA en las relaciones amorosas y sexuales
H3 Las 15 aplicaciones de encuentros más usadas en el mundo
H3 Amor, lujuria y algoritmos: la era moderna de la intimidad digital

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

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 61 images OK

PASS

All 61 images OK

61 image(s) with good alt text

61 images 61 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit">

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
s	search	Buscar:	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

A+

Form Input Types

2 form control(s) checked, no type mismatches

PASS

2 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

2 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 "es"

PASS

Lang attribute set to "es"

<html lang="es"> is set and valid

Got: es

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

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.

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