Skip to content
https://he.wikipedia.org

Accessibility

· 22 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
6
REVIEW
4
PASS
12
INFO
0
Checks
22
12 PASS 4 REVIEW 6 FIX
F
Alt Text Quality
Action
50 of 83 images have issues
FIX
50 of 83 images have issues
Critical::
49 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
48 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
1 image(s) with filename as alt text
Info::
2 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
29 image(s) with good alt text
83 images 29 good alt text 2 decorative 1 generic 49 missing
IssueCount
missing49 image(s)
filename1 image(s)
too long2 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
Tabindex Anti-Patterns
Action
0 positive, 10 -1-on-focusable
FIX
0 positive, 10 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button>
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.)
Info::
tabindex="-1" on naturally-focusable <a id="ca-talk-sticky-header">
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.)
Info::
tabindex="-1" on naturally-focusable <a id="ca-subject-sticky-header">
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.)
Info::
tabindex="-1" on naturally-focusable <a id="ca-history-sticky-header">
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.)
Info::
tabindex="-1" on naturally-focusable <a id="ca-watchstar-sticky-header">
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.)
Info::
tabindex="-1" on naturally-focusable <a id="ca-edit-sticky-header">
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.)
Info::
tabindex="-1" on naturally-focusable <a id="ca-ve-edit-sticky-header">
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.)
Info::
tabindex="-1" on naturally-focusable <a id="ca-viewsource-sticky-header">
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.)
Info::
tabindex="-1" on naturally-focusable <button id="p-lang-btn-sticky-header">
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.)
Info::
tabindex="-1" on naturally-focusable <a id="ca-addsection-sticky-header">
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.)
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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
9 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 9 <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
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

B
Lighthouse Accessibility Audits
Score 87/100 — 4 failing, 28 passed
REVIEW
87

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

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
td > span > a > img.mw-file-element td > span > a > img.mw-file-element
td > span > a > img.mw-file-element td > span > a > img.mw-file-element
td > span > a > img.mw-file-element td > span > a > img.mw-file-element
td > span > a > img.mw-file-element td > span > a > img.mw-file-element
td > span > a > img.mw-file-element td > span > a > img.mw-file-element
td > span > a > img.mw-file-element td > span > a > img.mw-file-element
td > span > a > img.mw-file-element td > span > a > img.mw-file-element
td > span > a > img.mw-file-element td > span > a > img.mw-file-element
td > span > a > img.mw-file-element td > span > a > img.mw-file-element
td > span > a > img.mw-file-element td > span > a > img.mw-file-element
td > span > a > img.mw-file-element td > span > a > img.mw-file-element
td > span > a > img.mw-file-element td > span > a > img.mw-file-element
p > span > a > img.mw-file-element p > span > a > img.mw-file-element
span#maimpagebox > span > a.mw-file-description > img.mw-file-element span#maimpagebox > span > a.mw-file-description > img.mw-file-element
center > figure#mwJg > span#mwJw > img#mwKA center > figure#mwJg > span#mwJw > img#mwKA

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header.header-container > div.minerva-header > nav.navigation-drawer > input#main-menu-input header.header-container > div.minerva-header > nav.navigation-drawer > input#main-menu-input

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
h2#אירועים_בלוח_העברי_2 > span#maimpagebox > span > a.mw-file-description h2#אירועים_בלוח_העברי_2 > span#maimpagebox > span > a.mw-file-description

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.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
מתמטיקה פיזיקה כימיה אמנות ספרות רפואה ספורט דת מוזיקה כלכלה … div#mwGQ > div#mwRQ > center > table
○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
●Buttons have an accessible name
●Input buttons have discernible text.
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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
●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
●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
●Touch targets have sufficient size and spacing.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○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
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
A
Landmark Structure
15 landmarks
PASS
15 landmarks
Info::
<main> landmark present
Info::
9 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "אתר" SEARCH 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+
Heading Hierarchy
21 headings
PASS
21 headings
Info::
Single H1 present
  • H3 טיפ
  • H1 עמוד ראשי
  • H2 הידעת
  • H2 פורטלים
  • H2 הציטוט היומי
  • H2 הטיפ היומי
  • H2 חדשות ואקטואליה
  • H2 ערך מומלץ
  • H2 תמונת היום
  • H2 היום בהיסטוריה
  • H2 אירועים בלוח העברי
  • H2 ערך מומלץ
  • H2 פורטלים
  • H2 הציטוט היומי
  • H2 תמונת היום
  • H2 הטיפ היומי
  • H2 הידעת
  • H2 היום בהיסטוריה
  • H2 אירועים בלוח העברי
  • H2 חדשות ואקטואליה
  • H2 ויקיפדיה מופעלת על ידי קרן ויקימדיה, המפעילה מספר מיזמים רב־לשוניים וחופשיים נוספים:מיזמי ויקימדיה נוספים:
A
Form Accessibility
1 of 16 controls have issues
PASS
1 of 16 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="search">
Info::
15 control(s) properly labeled
16 controls
15 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#vector-main-menu-dropdown-checkboxcheckboxתפריט ראשיaria-label
#searchInputsearchחיפוש בוויקיפדיהaria-label
#vector-appearance-dropdown-checkboxcheckboxמראהaria-label
#skin-client-pref-vector-feature-custom-font-size-value-0radioקטןfor/id
#skin-client-pref-vector-feature-custom-font-size-value-1radioרגילfor/id
#skin-client-pref-vector-feature-custom-font-size-value-2radioגדולfor/id
#skin-client-pref-vector-feature-limited-width-value-1radioרגילfor/id
#skin-client-pref-vector-feature-limited-width-value-0radioרחבfor/id
#skin-client-pref-skin-theme-value-osradioאוטומטיfor/id
#skin-client-pref-skin-theme-value-dayradioבהירfor/id
#skin-client-pref-skin-theme-value-nightradioכההfor/id
#vector-user-links-dropdown-checkboxcheckboxכלים אישייםaria-label
#vector-variants-dropdown-checkboxcheckboxשינוי הגוון השפהaria-label
#vector-page-tools-dropdown-checkboxcheckboxכליםaria-label
#p-lang-btn-checkboxcheckboxמעבר לערך בשפה אחרת. זמין ב־346 שפותaria-label
searchsearch(חיפוש בוויקיפדיה)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="search" name="search">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A+
Form Input Types
16 form control(s) checked, no type mismatches
PASS
16 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
16 form control(s) checked, no input-semantic issues
PASS
16 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "he"
PASS
Lang attribute set to "he"
Info::
<html lang="he"> is set and valid
Got: he
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 34 visible text node(s) render at >= 12 CSS pixels
PASS
All 34 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
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)
ElementRatioRequiredFGBGResult
h3 טיפ21.00:13.0:1
#000000
#FFFFFF
Pass
title ויקיפדיה21.00:14.5:1
#000000
#FFFFFF
Pass
a לדלג לתוכן21.00:14.5:1
#000000
#FFFFFF
Pass
span תפריט ראשי21.00:14.5:1
#000000
#FFFFFF
Pass
div תפריט ראשי21.00:14.5:1
#000000
#FFFFFF
Pass
button העברה לסרג…21.00:14.5:1
#000000
#FFFFFF
Pass
button הסתרה21.00:14.5:1
#000000
#FFFFFF
Pass
div ניווט21.00:14.5:1
#000000
#FFFFFF
Pass
span עמוד ראשי21.00:14.5:1
#000000
#FFFFFF
Pass
span ברוכים הבא…21.00:14.5:1
#000000
#FFFFFF
Pass
span שינויים אח…21.00:14.5:1
#000000
#FFFFFF
Pass
span ערכים מומל…21.00:14.5:1
#000000
#FFFFFF
Pass
a דיווח על טע…21.00:14.5:1
#000000
#FFFFFF
Pass
span פורטלים21.00:14.5:1
#000000
#FFFFFF
Pass
span ערך אקראי21.00:14.5:1
#000000
#FFFFFF
Pass
a ארגז החול21.00:14.5:1
#000000
#FFFFFF
Pass
li ניתן לבצע נ…21.00:14.5:1
#000000
#FFFFFF
Pass
div קהילה21.00:14.5:1
#000000
#FFFFFF
Pass
span שער הקהילה21.00:14.5:1
#000000
#FFFFFF
Pass
span עזרה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.

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

Send Feedback