Accessibility issues detected on willythewheel.co.il

01 · Accessibility summary

Evolize inspected 5 public pages on willythewheel.co.il and detected 34 accessibility findings. The most widespread issue was "Hidden elements can still receive keyboard focus", detected on 5 inspected pages. The most affected inspected page was "/books", where 21 findings were detected. The assessment identified findings mapped to 5 WCAG success criterions. The sections below prioritize the broadest issues and provide technical evidence for each detected finding.

02 · Start here

These findings combine the highest severity and broadest reach detected during this assessment.

1. High

   Hidden elements can still receive keyboard focus

   WCAG 2.4.3 (A) · 5 inspected pages · 50 instances
   Why this matters

   An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

   Recommended action

   To fix this issue, ensure that all interactive elements are visible when they receive keyboard focus. Consider adding a `display: none` or `visibility: hidden` style to the element when it's not intended to be visible, or remove it from the tab order by setting `tabindex=-1`.

   View technical evidence →
2. High

   Hidden elements can still receive keyboard focus

   WCAG 2.4.3 (A) · 5 inspected pages · 40 instances
   Why this matters

   An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

   Recommended action

   To fix this issue, ensure that all focusable elements are visible to sighted keyboard users. You can do this by removing the element from the tab order if it's not visible, or by making the element visible when it receives focus. For the specific element <a href="/=#why-willy">למה וילי</a>, consider adding a visible styling or reordering the navigation to exclude hidden elements.

   View technical evidence →
3. High

   Hidden elements can still receive keyboard focus

   WCAG 2.4.3 (A) · 5 inspected pages · 10 instances
   Why this matters

   An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

   Recommended action

   To fix this issue, ensure that all focusable elements are visible. You can do this by adding a 'display: none;' or 'visibility: hidden;' style to the element when it's not intended to be visible, or by removing the element from the DOM when it's not needed. Alternatively, you can use JavaScript to remove the element from the tab order when it's not visible.

   View technical evidence →
4. High

   Elements must only use permitted ARIA attributes

   WCAG 4.1.2 (A) · 5 inspected pages · 10 instances
   Why this matters

   Elements must only use permitted ARIA attributes

   Recommended action

   Remove the 'aria-label' attribute from the 'div' element with class 'share-buttons' or replace it with a permitted ARIA attribute. Ensure that the element has a valid and descriptive accessible name.

   View technical evidence →
5. High

   Content overflows horizontally on narrow viewports

   WCAG 1.4.10 (AA) · 5 inspected pages · 5 instances
   Why this matters

   The page scrolls horizontally at a mobile width, indicating content that does not reflow.

   Recommended action

   To fix the horizontal overflow issue, ensure that all content is contained within the viewport and reflows properly on smaller screens. Consider using CSS media queries to adjust the layout for different screen sizes, or use a responsive design framework that automatically adapts to various viewport widths.

   View technical evidence →

03 · WCAG criteria affected

Absence of a criterion here does not indicate conformance with it — only that no automatically detectable issue was found for it.

04 · All detected findings

<div class="share-buttons" aria-label="שיתוף העמוד">

<div class="hero-art" aria-label="הכירו את וילי הגלגל"><div class="sun-orbit" aria-hidden="true"></div><div class="book-stage"><img alt="איור השער של וילי הגלגל" class="book-cover" fetchpriority="high" height="1536" src="/images/willy-hebrew/bridge-cover.webp?v=20260828" width="1024"></div></div>

<a href="/#why-willy">למה וילי</a>

<a href="/#why-willy">למה וילי</a>

<a aria-label="פתחו את המשחק עם וילי" class="header-kids-link" href="/kids">לשחק עם וילי</a>

<html lang="he" dir="rtl"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><link rel="preload" href="/images/willy-hebrew/bridge-cover.webp?v=20260828" as="image" fetchpriority="high"><link rel="preload" href="/images/willy-youtube-conversation-hebrew.jpg?v=20260828" as="image"><link rel="stylesheet" href="/assets/index-D2sIcb0-.css" data-rsc-css-href="/assets/index-D2sIcb0-.css" data-precedence="vite-rsc/importer-resources"><script async="" data-ga-id="G-TDQ5704PCZ" src="https://www.googletagmanager.com/gtag/js?id=G-TDQ5704PCZ"></script><link rel…

<p class="hero-lead">סיפור חם ומסקרן לילדים, ושיחה פשוטה להורים על חברות, השתתפות ועזרה.</p>

<h1>ספרי ילדים על חברות, קבלת האחר ושייכות — בדרך שמתאימה לכולם</h1>

<p class="footer-heading">לאן יוצאים?</p>

<p class="footer-heading">למשפחה ולמבוגרים</p>

<strong>וילי הגלגל</strong>

<h2 id="author-willy-title">וילי והחברים שלו יוצאים ביחד להרפתקה.</h2>

<span class="youtube-watch-label" aria-hidden="true">צפו עכשיו</span>

<p>שיחה מונפשת לילדים, להורים ולאנשי חינוך על בחירה, עזרה ושייכות.</p>

<a class="button" href="/books/the-little-wheel-who-could">להתחיל את ההרפתקה</a>

<p class="eyebrow">סיפורים לילדים בגילאי 4–8 ולמי שהולך איתם</p>

<span aria-hidden="true">←</span>

<p class="hero-promise">הכירו את וילי, גלגל קטן שרוצה להגיע לפיקניק עם המשפחה והחברים. כשהגשר עוצר אותו, כולם שואלים איך מוצאים דרך נגישה שמאפשרת להשתתף יחד.</p>

<span aria-hidden="true">←</span>

<span class="book-order">הספר הראשון</span>

<strong>חשוב לדעת על הסיפורים בעברית ובאנגלית:</strong>

<p class="regional-price-note">הספר המודפס זמין לרכישה ב־Amazon. המחיר והמשלוח מוצגים לפי כתובת היעד.</p>

<h2>וילי והגשר</h2>

<p class="statement-date">נבדק ועודכן: 30 באוגוסט 2026</p>

<p>בסיפור אחד גשר עם מדרגות עוצר את וילי. בסיפור השני הוא בודק דרך שנפגעה בחורף ועוזר לקהילה לתקן אותה. בשניהם מקשיבים לווילי, מתכננים יחד ומוצאים פתרון שמאפשר ליותר אנשים להשתתף.</p>

<p class="edition-note catalog-edition-note"><strong>חשוב לדעת על הסיפורים בעברית ובאנגלית:</strong> <!-- -->הסיפורים בעברית ובאנגלית הם עיבודים נפרדים מעולמו של וילי ואינם תרגום מילולי זה של זה.</p>

<p class="purchase-note">ספר מודפס — ספר פיזי שנשלח לכתובת<!-- --> · <!-- -->34<!-- --> עמודים · <!-- -->$12.99</p>

<a aria-label="לרכישת הספר המודפס ב־Amazon — נפתח בלשונית חדשה" class="button" href="https://www.amazon.com/dp/B0HG96ZXCR" rel="noopener noreferrer" target="_blank">לרכישת הספר המודפס ב־Amazon<span aria-hidden="true"> ↗</span></a>

<strong>כאן מכירים את וילי. הספר פותח שאלה פשוטה: מה עושים כשכולם רוצים להגיע יחד, אבל הדרך עוצרת אחד מהם?</strong>

<a class="button button-secondary" href="/books/the-little-wheel-who-could">להכיר את הסיפור</a>

<p>בדרך לפיקניק, וילי מגיע לגשר אבן שהעלייה אליו עשויה מדרגות שאינן מתאימות לגלגליו. האם המשפחה והחברים ימצאו דרך להמשיך ביחד?</p>

<a class="button button-secondary" href="/books/winding-path">להכיר את הסיפור</a>

<a href="mailto:[email removed]">[email removed]</a>

<a href="mailto:[email removed]?subject=%D7%A4%D7%A0%D7%99%D7%99%D7%94%20%D7%91%D7%A0%D7%95%D7%A9%D7%90%20%D7%A0%D7%92%D7%99%D7%A9%D7%95%D7%AA%20%D7%91%D7%90%D7%AA%D7%A8%20%D7%95%D7%99%D7%9C%D7%99%20%D7%94%D7%92%D7%9C%D7%92%D7%9C">[email removed]</a>

05 · Most affected inspected pages

• /booksHigh
  22 findings

  • High Content overflows horizontally on narrow viewports
  • High Elements must only use permitted ARIA attributes
  • High Hidden elements can still receive keyboard focus
  • Medium Text has insufficient colour contrast
• /High
  20 findings

  • High Content overflows horizontally on narrow viewports
  • High Elements must only use permitted ARIA attributes
  • High Hidden elements can still receive keyboard focus
  • Medium Text has insufficient colour contrast
• /accessibilityHigh
  13 findings

  • High Content overflows horizontally on narrow viewports
  • High Elements must only use permitted ARIA attributes
  • High Hidden elements can still receive keyboard focus
  • Medium Text has insufficient colour contrast
  • Low Touch targets are too small on mobile
• /about-the-authorHigh
  12 findings

  • High Content overflows horizontally on narrow viewports
  • High Elements must only use permitted ARIA attributes
  • High Hidden elements can still receive keyboard focus
  • Medium Text has insufficient colour contrast
• /contactHigh
  9 findings

  • High Content overflows horizontally on narrow viewports
  • High Elements must only use permitted ARIA attributes
  • High Hidden elements can still receive keyboard focus
  • Medium Text has insufficient colour contrast
  • Low Touch targets are too small on mobile

06 · About this 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.

Reports with similar accessibility findings