Skip to content
https://tau.ac.il

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
No dark mode signals
FIX
No dark mode signals
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 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
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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
14 headings
REVIEW
14 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 מה חדש
  • H2 "אנחנו נקום. לא כי קל לנו, אלא כי אין לנו ברירה"
  • H3 מה קורה
  • H2 קהילת אוניברסיטת תל אביב מתייחדת עם זכר חלליה
  • H2 קוראים בעקבותיהם
  • H2 למה חשוב שתשלימו שעות שינה?
  • H2 בחזרה לקמפוס
  • H2 למה ואיזה סוג אימון מתאימים להתמודדות עם סטרס?
  • H2 מלגות שכר לימוד מלאות למשרתי.ות מילואים
  • H2 חרבות ברזל: מסלול קבלה מיוחד לתואר ראשון
  • H2 איך תקחו את הקפה הקר לטיול?
  • H2 אוניברסיטת תל אביב בליגת העל
  • H2 ועידת תל אביב 2026: עתיד ישראל
  • H2 בואו ליום הפתוח לתואר ראשון ושני

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

B
Form Accessibility
2 of 3 controls have issues
REVIEW
2 of 3 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="prot" id="edit-prot">; <input type="submit" name="op" id="edit-submit">
Info::
1 control(s) properly labeled
3 controls
1 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#edit-search-block-form--2textחיפושaria-label
#edit-prottext(none)none
#edit-submitsubmit(none)none

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

<input type="text" name="prot" id="edit-prot">; <input type="submit" name="op" id="edit-submit">

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
Color Contrast (Screenshot)
Action
20 text elements analyzed, 15 fail WCAG AA
REVIEW

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

5 pass 15 fail WCAG AA
h2 "אנחנו נקום. לא כי קל ל…
2.57:1
#000000
on
#534E4F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 קהילת אוניברסיטת תל א…
2.57:1
#000000
on
#534E4F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 קוראים בעקבותיהם
2.57:1
#000000
on
#534E4F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 למה חשוב שתשלימו שעות …
2.57:1
#000000
on
#534E4F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 בחזרה לקמפוס
2.57:1
#000000
on
#534E4F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 למה ואיזה סוג אימון מת…
2.57:1
#000000
on
#534E4F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 מלגות שכר לימוד מלאות …
2.57:1
#000000
on
#534E4F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 חרבות ברזל: מסלול קבלה…
2.57:1
#000000
on
#534E4F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 איך תקחו את הקפה הקר ל…
2.57:1
#000000
on
#534E4F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 אוניברסיטת תל אביב בל…
2.57:1
#000000
on
#534E4F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ועידת תל אביב 2026: עתיד …
2.57:1
#000000
on
#534E4F
needs 3.0:1 (large text)
24px · bottom of viewport
h2 בואו ליום הפתוח לתואר …
2.57:1
#000000
on
#534E4F
needs 3.0:1 (large text)
24px · bottom of viewport
h3 מה חדש
2.57:1
#000000
on
#534E4F
needs 3.0:1 (large text)
19px · bottom of viewport
h3 מה קורה
2.57:1
#000000
on
#534E4F
needs 3.0:1 (large text)
19px · bottom of viewport
a תפריט עליון
2.06:1
#000000
on
#414141
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

1 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 "אנחנו נקום…2.57:13.0:1
#000000
#534E4F
Fail
h2 קהילת אוני…2.57:13.0:1
#000000
#534E4F
Fail
h2 קוראים בעק…2.57:13.0:1
#000000
#534E4F
Fail
h2 למה חשוב שת…2.57:13.0:1
#000000
#534E4F
Fail
h2 בחזרה לקמפ…2.57:13.0:1
#000000
#534E4F
Fail
h2 למה ואיזה ס…2.57:13.0:1
#000000
#534E4F
Fail
h2 מלגות שכר ל…2.57:13.0:1
#000000
#534E4F
Fail
h2 חרבות ברזל:…2.57:13.0:1
#000000
#534E4F
Fail
h2 איך תקחו את…2.57:13.0:1
#000000
#534E4F
Fail
h2 אוניברסיטת…2.57:13.0:1
#000000
#534E4F
Fail
h2 ועידת תל אב…2.57:13.0:1
#000000
#534E4F
Fail
h2 בואו ליום ה…2.57:13.0:1
#000000
#534E4F
Fail
h3 מה חדש2.57:13.0:1
#000000
#534E4F
Fail
h3 מה קורה2.57:13.0:1
#000000
#534E4F
Fail
title האוניברסיט…21.00:14.5:1
#000000
#FFFFFF
Pass
a תפריט עליו…2.06:14.5:1
#000000
#414141
Fail
a תפריט ראשי21.00:14.5:1
#000000
#FFFFFF
Pass
a תוכן ראשי21.00:14.5:1
#000000
#FFFFFF
Pass
a אלפון21.00:14.5:1
#000000
#FFFFFF
Pass
a סגל21.00:14.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.

B
Lighthouse Accessibility Audits
Score 80/100 — 3 failing, 17 passed
REVIEW
80

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div#banner-35391 > div.rbanner-video-ctrl > button#rbanner-video-play div > div#banner-35391 > div.rbanner-video-ctrl > button#rbanner-video-play

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. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
עצרת יום הזיכרון לחללי מערכות ישראל ופעולות האיבה 2026 div#masonry-item- > a > div.masonry-item > div.masonry-item-body
13/04/2026 div.news-box-container > div.news-item > div.news-bottom > label.news-date
20/04/2026 div.news-box-container > div.news-item > div.news-bottom > label.news-date
20/04/2026 div.news-box-container > div.news-item > div.news-bottom > label.news-date
16/04/2026 div.news-box-container > div.news-item > div.news-bottom > label.news-date
לכל החדשות div.news-total > div.news-bottom-container > div.news-bottom-link > a.news-bottom-text
יום הזיכרון a > div.masonry-item > div.masonry-item-cat > span.masonry-item-cat-text
יום הזיכרון a > div.masonry-item > div.masonry-item-cat > span.masonry-item-cat-text
29/05/2026, 09:00 div.event-item-inner > a.event-title > div.event-bottom > label.event-date
לכל האירועים div.events-total > div.events-bottom-container > div.events-bottom-link > a.events-bottom-text
פודקאסט a > div.masonry-item > div.masonry-item-cat > span.masonry-item-cat-text
פתיחת סמסטר ב' - עדכון לסטודנטים.ות 12.4.26 div#654645 > a > div.masonry-item > div.masonry-item-body
פודקאסט a > div.masonry-item > div.masonry-item-cat > span.masonry-item-cat-text
חרבות ברזל a > div.masonry-item > div.masonry-item-cat > span.masonry-item-cat-text
לימודים a > div.masonry-item > div.masonry-item-cat > span.masonry-item-cat-text
לכבוד האביב: הטבה מיוחדת על כל הפריטים בחנות המותג עד סוף אפריל div#4456456456 > a > div.masonry-item > div.masonry-item-body
דירוגים a > div.masonry-item > div.masonry-item-cat > span.masonry-item-cat-text
קריאה לפעולה, הזמנה לחשוב, לשאול, ולפעול יחד למען עתידה של מדינת ישראל div#masonry-item- > a > div.masonry-item > div.masonry-item-body
הרשמה ללימודים div.spotlights-grid > div#6546546 > div.masonry-register-header-wrapper > span.masonry-register-category
יום שישי | 29.5 | 13:00-9:00 | בקמפוס div#6546546 > div.masonry-register-content > div.masonry-register-body-wrapper > p.masonry-register-body
לפרטים נוספים div.masonry-register-footer > div.masonry-register-button > a.masonry-register-text > span.masonry-register-text-inner
מידע כללי div.tau_main_footer_block > ul.menu > li.first > a
לימודים div.tau_main_footer_block > ul.menu > li.expanded > a
סגל ומינהלה div.tau_main_footer_block > ul.menu > li.expanded > a
נגישות div.tau_main_footer_block > ul.menu > li.expanded > a
אוניברסיטת תל אביב div.full_line > div.width_margin > div.rc-recog-address-wrapper > div.rc-recog-uni-name
P.O. Box 39040, Tel Aviv 6997801 div.full_line > div.width_margin > div.rc-recog-address-wrapper > div.rc-recog-uni-address

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
●Image elements have `[alt]` attributes
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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 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
○`<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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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
○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.
○Identical links have the same purpose.
○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
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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.
Page Structure — as a screen reader sees it
BANNER header NAV "פרורי לחם" MAIN CONTENTINFO footer

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

A+
Alt Text Quality
All 20 images OK
PASS
All 20 images OK
Info::
15 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
20 images 5 good alt text 15 decorative
All images have appropriate alt text.
A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title דף לא נמצא | אוניברסיטת ת"א ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback