Accessibility issues detected on hoop.photo
Evolize inspected 5 publicly accessible pages on hoop.photo and detected 15 automatically identifiable accessibility findings. 4 findings were classified as critical or high priority. The findings map to 8 WCAG success criterions. The sections below show affected pages, technical evidence and recommended remediation. The most frequent issues involve links lack accessible text, page has no main landmark, images lack text alternatives.
Independent public assessment. hoop.photo is not necessarily affiliated with or a customer of Evolize.
01 · Accessibility summary
Evolize inspected 5 publicly accessible pages on hoop.photo and detected 15 automatically identifiable accessibility findings. 4 findings were classified as critical or high priority. The findings map to 8 WCAG success criterions. The sections below show affected pages, technical evidence and recommended remediation. The most frequent issues involve links lack accessible text, page has no main landmark, images lack text alternatives.
02 · Priority findings
03 · WCAG criteria affected
| Criterion | Name | Level | Findings | Pages |
|---|---|---|---|---|
| 2.5.8 | Target Size (Minimum) | AA | 6 | 5 |
| 1.3.1 | Info and Relationships | A | 2 | 4 |
| 1.4.3 | Contrast (Minimum) | AA | 2 | 2 |
| 1.1.1 | Non-text Content | A | 1 | 1 |
| 1.4.10 | Reflow | AA | 1 | 1 |
| 2.1.1 | Keyboard | A | 1 | 1 |
| 2.4.4 | Link Purpose (In Context) | A | 1 | 1 |
| 3.1.1 | Language of Page | A | 1 | 1 |
Absence of a criterion here does not indicate conformance with it — only that no automatically detectable issue was found for it.
A scan shows today's exposure. Monitoring shows what changes next.
Evolize continuously rescans public websites, detects newly introduced or recurring accessibility issues, tracks remediation and verifies fixes.
04 · All detected findings
Links lack accessible text
ComponentRef TYR9PZ
Links expose no accessible name, so their destination is unknown to screen reader users.
https://hoop.photo/privacy/.d-inline-flex<a href="/" class="d-inline-flex link-body-emphasis text-decoration-none">
<img class="logo_img" src="images/logo_hoop.png" width="100" height="100">
</a>Page has no main landmark
ComponentRef WCMT8M
No <main> or role=main region is present, so screen reader users cannot jump to primary content.
https://hoop.photo/html > body<body data-rsssl="1"> <div id="container"> <div id="main"> <div> <img id="logo_hoop" src="/images/logo_hoop.png" alt="hoop_logo"> </div> <div id="content"> <h1 id="headline"><span id="background">Hoop, make new friends <span id="highlight">all over the world</span> 🌎</span></h1> <div id="store-button"> <a href="https://apps.apple.com/us/app/hoop-find-make-new-friends/id1442571346" target="_blank"> <img class="store_image" src="/images/app_store_en.png" alt="app_store"> </a> <a href="https://play.google.com/store/apps/details?id=com.dazz…
/ /guidelines /terms /parents_guideImages lack text alternatives
ComponentRef XEKG39
Informative images have no alternative text, so their meaning is unavailable to people using assistive technology.
https://hoop.photo/privacy/img<img class="logo_img" src="images/logo_hoop.png" width="100" height="100">
Scrollable region must have keyboard access
ComponentRef KLMM73
Scrollable region must have keyboard access
https://hoop.photo/privacy/.row:nth-child(3) > .col-md-12 > .table-responsive<div class="table-responsive">
Content sits outside any landmark region
ComponentRef PBUPGM
Meaningful content is not contained in a landmark (header/nav/main/footer/aside), so assistive-technology users cannot reach it via landmark navigation.
https://hoop.photo/parents_guide/div#container > p:nth-of-type(1)<p>Last updated on 05 December 2025</p>
/guidelines /terms /parents_guideTouch targets are too small on mobile
ComponentRef 71R595
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
https://hoop.photo/div#footer > a:nth-of-type(1)<a href="https://hoop.photo">Download</a>
/ /guidelines /parents_guideComponentRef 1P808M
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
https://hoop.photo/terms/div#container > p:nth-of-type(5) > a:nth-of-type(6)<a href="/privacy" target="_blank">Privacy Policy</a>
ComponentRef 34RHK2
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
https://hoop.photo/privacy/div > table > tbody > tr:nth-of-type(2) > td:nth-of-type(4) > a<a href="https:// policies.google.com/ privacy?fg=1" target="_blank">https:// policies.google.com/ privacy?fg=1</a>
ComponentRef 2KHYWD
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
https://hoop.photo/parents_guide/div#container > div:nth-of-type(5) > p:nth-of-type(4) > a<a href="mailto:[email removed]">[email removed]</a>
Page language is not declared
ComponentRef QRHHZL
The document has no lang attribute, so assistive technology cannot select the correct pronunciation.
https://hoop.photo/terms/html<html>
Content overflows horizontally on narrow viewports
ComponentRef 31DOVB
The page scrolls horizontally at a mobile width, indicating content that does not reflow.
https://hoop.photo/privacy/html<html lang="en" data-bs-theme="auto"><head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="description" content="">
<title>Privacy policy</title>
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@docsearch/css@3">
<link href="css/bootstrap.min.css" rel="stylesheet">
<link rel="icon" type="image/png" href="images/fav.png">
<style>
h1, h2, h3, h4, h5, h6 {
font-family: "Playfair Display", Georgia, "Times New Roman", serif;
}
tbody, td, tfoot, th, thead, tr {
…Touch targets are too small
ComponentRef 1ZO3GM
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
https://hoop.photo/terms/a[href$="hoop.photo/"]<a href="https://hoop.photo/">Download</a>
ComponentRef 1ZO3LN
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
https://hoop.photo/terms/#footer > p > a[href$="safety"]<a href="/safety">Safety</a>
Text has insufficient colour contrast
ComponentRef PZOE2I
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
https://hoop.photo/parents_guide/.active<a class="active" href="/parents_guide">Parent Guide to Hoop</a>
ComponentRef T60BZD
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
https://hoop.photo/privacy/.mb-5.lead:nth-child(42)<p class="lead mb-5">
05 · Pages inspected
06 · About this assessment
Evolize inspects publicly accessible website pages using automated browser-based testing and deterministic accessibility rules. Automated testing can identify many reproducible technical issues but cannot determine complete WCAG or legal compliance.
- Publicly accessible surfaces only — no credentials, private systems, or source-code access.
- Findings apply to the pages and states successfully inspected; automated analysis may not detect every issue.
- Results reflect the site at the scan date and may have changed since.
Evolize provides digital risk intelligence and does not provide legal advice, certify compliance, or guarantee that litigation will not occur. Methodology · Security · Example assessment
07 · Continuous monitoring
This public report captures one assessment. Evolize monitoring rescans the website, detects new and recurring findings, tracks changes over time and verifies corrections.
Is information in this report inaccurate or outdated? Request a correction or removal.