Automated technical assessment of 4 publicly accessible pages · Scanned 25 Aug 2026. Inspected 4 of 5 selected pages (some selected pages could not be inspected).
Findings
Critical
Buttons have no accessible name
Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.
Component
1 affected page
4 instances
WCAG WCAG 2.1 SC 4.1.2 Name, Role, Value (Level A)
Ref SVCNV1
Affected pagehttps://ndn-co.com/catalog/product/%D7%A4%D7%95%D7%9C%D7%99%D7%92%D7%9C/
Elementbutton[onclick="adjustQty(-1)"]
Markup<button class="btn btn-link text-dark border-0 p-0 px-2 shadow-none" type="button" onclick="adjustQty(-1)">
<i class="bi bi-dash fs-5"></i>
</button> How to fixGive it an accessible name that describes the action it performs: provide visible text when a visible label is appropriate, an aria-label for an icon-only control (for example aria-label="Dismiss notification"), or aria-labelledby when an existing visible label already describes it. Avoid vague names such as "Button", "Action", or the component's internal name.
Critical
Buttons have no accessible name
Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.
Component
1 affected page
2 instances
WCAG WCAG 2.1 SC 4.1.2 Name, Role, Value (Level A)
Ref MCNYZ8
Affected pagehttps://ndn-co.com/catalog/product/%D7%A4%D7%95%D7%9C%D7%99%D7%92%D7%9C/
Element#shareButton
Markup<button id="shareButton" class="share-btn btn">
<i class="bi bi-share-fill fs-5 text-dark" style="font-size: 15px;"></i>
</button> How to fixAdd text or an aria-label attribute to the button to provide an accessible name, such as <button id="shareButton" class="share-btn btn" aria-label="Share">
Critical
Form fields are missing labels
Form inputs have no programmatically associated label, so assistive technology cannot announce what to enter.
Component
1 affected page
2 instances
WCAG WCAG 2.1 SC 1.3.1 Info and Relationships (Level A), WCAG 2.1 SC 4.1.2 Name, Role, Value (Level A)
Ref W9OXZC
Affected pagehttps://ndn-co.com/catalog/product/%D7%A4%D7%95%D7%9C%D7%99%D7%92%D7%9C/
Element#quantity-input
Markup<input type="number" id="quantity-input" name="quantity" style="-moz-appearance: textfield;" class="form-control border-0 bg-transparent text-center fw-bold px-0" value="1" min="1" max="99" readonly="">
How to fixAssociate a <label> with each field via for/id, or use aria-label / aria-labelledby. Placeholder text is not a label.
Critical
Form fields are missing labels
Form inputs have no programmatically associated label, so assistive technology cannot announce what to enter.
Component
1 affected page
4 instances
WCAG WCAG 2.1 SC 1.3.1 Info and Relationships (Level A), WCAG 2.1 SC 4.1.2 Name, Role, Value (Level A)
Ref XYEUQ9
Affected pagehttps://ndn-co.com/catalog/product/%D7%A4%D7%95%D7%9C%D7%99%D7%92%D7%9C/
Element#variant-4
Markup<input type="radio" class="btn-check" name="product_variant" id="variant-4" value="4" data-name="סופט פינק" data-extra-price="0.00" data-sku="פוליגל-סופט-פינק" data-stock="3" onchange="updateVariantDetails(this)">
How to fixAdd a programmatically associated label to the form input, using the 'label' element and the 'for' attribute to reference the input's id. For example: <label for='variant-4'>סופט פינק</label>
Critical
Form fields are missing labels
Form inputs have no programmatically associated label, so assistive technology cannot announce what to enter.
Component
1 affected page
2 instances
WCAG WCAG 2.1 SC 1.3.1 Info and Relationships (Level A), WCAG 2.1 SC 4.1.2 Name, Role, Value (Level A)
Ref G4Z7FN
Affected pagehttps://ndn-co.com/catalog/product/%D7%A4%D7%95%D7%9C%D7%99%D7%92%D7%9C/
Element#variant-3
Markup<input type="radio" class="btn-check" name="product_variant" id="variant-3" value="3" data-name="קליר" data-extra-price="0.00" data-sku="פוליגל-קליר" data-stock="3" checked="" onchange="updateVariantDetails(this)">
How to fixAssociate a <label> with each field via for/id, or use aria-label / aria-labelledby. Placeholder text is not a label.
High
Hidden elements can still receive keyboard focus
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Component
4 affected pages
36 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref IC7PCC
Affected pagehttps://ndn-co.com/
Elementdiv#mobileMenu > div:nth-of-type(2) > ul > div:nth-of-type(1) > a
Accessible nameכל המוצרים
Markup<a href="/catalog/" class="btn col-5 btn-outline-primary btn-sm rounded-3 px-3 py-1">כל המוצרים</a>
How to fixTo fix this issue, ensure that the element is either visible when it receives focus or is removed from the tab order. This can be achieved by adding a 'tabindex=-1' attribute to the element or by making sure the element is not hidden when it is focused.
High
Hidden elements can still receive keyboard focus
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Component
4 affected pages
4 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref UWBISR
Affected pagehttps://ndn-co.com/
Elementdiv#mobileMenu > div:nth-of-type(1) > button
Accessible nameסגור את סרגל הניווט
Markup<button type="button" class="btn-close" aria-label="סגור את סרגל הניווט" data-bs-dismiss="offcanvas"></button>
How to fixTo fix this issue, ensure that the button is either visible when it receives focus or is removed from the tab order when it's not visible. This can be achieved by setting the 'tabindex' attribute to '-1' or by hiding the element using 'display: none' or 'visibility: hidden' when it's not intended to be interacted with.
High
Hidden elements can still receive keyboard focus
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Component
4 affected pages
4 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref H8WK6T
Affected pagehttps://ndn-co.com/
Elementa#navbarDropdown
Accessible nameקטלוג
Rolebutton
Markup<a class="nav-link dropdown-toggle fw-bold" href="#" id="navbarDropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">
קטלוג
</a> How to fixTo fix this issue, ensure that the element with the id 'navbarDropdown' is visible when it receives keyboard focus. You can do this by adding a 'display: block' or 'visibility: visible' CSS rule when the element is focused. Alternatively, you can remove the element from the tab order by setting the 'tabindex' attribute to '-1' if it is not intended to be focusable.
High
Hidden elements can still receive keyboard focus
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Component
4 affected pages
4 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref OZYBUN
Affected pagehttps://ndn-co.com/
Elementdiv#navbarDropdownMenu > div > div:nth-of-type(1) > a
Accessible nameכל המוצרים
Markup<a href="/catalog/" class="btn col-md-2 btn-outline-primary btn-sm rounded-3px-3 py-1">כל המוצרים</a>
How to fixTo fix this issue, ensure that the element is either removed from the tab order or made visible when it receives focus. This can be achieved by adding the 'tabindex=-1' attribute to the element or by making it visible using CSS when it has focus.
High
Hidden elements can still receive keyboard focus
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Component
4 affected pages
32 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref WEYHQY
Affected pagehttps://ndn-co.com/
Elementdiv#navbarDropdownMenu > div > div:nth-of-type(2) > div:nth-of-type(1) > p > a
Accessible nameבייסים
Markup<a href="/catalog/?category=בייסים" aria-label="בייסים" class="text-dark fw-bold text-decoration-none">בייסים</a>
How to fixTo fix this issue, ensure that the hidden element is removed from the tab order by setting its 'tabindex' attribute to '-1' or by using 'display: none' or 'visibility: hidden' CSS properties to completely hide it. Alternatively, make the element visible when it receives focus.
Medium
No skip link to main content
The page offers no bypass mechanism, so keyboard users must tab through the full navigation before reaching the main content on every page.
Component
4 affected pages
8 instances
WCAG WCAG 2.1 SC 2.4.1 Bypass Blocks (Level A)
Ref HGV6FI
Affected pagehttps://ndn-co.com/
Elementhtml > body
Accessible nameחנות NDN
קטגוריות
כל המוצרים
בייסים
ג'ל בנייה
ג'ל בנייה בבקבוק
טופ
כלי עבודה
מכשירי חשמל
פוליג'ל
צבעים
מותגים
ADDICT
GELLO
SAHARA
לילה מילאנו
NDN.
קטלוג
קטגוריות
כל המוצרים
בייסים
ג'ל בנייה
ג'ל בנייה בבקבוק
טופ
כלי עבודה
מכשירי חשמל
פוליג'ל
צבעים
מותגים
ADDICT
GELLO
SAHARA
לילה מילאנו
אודותינו
כניסה למערכת
לרשום
0
NDN nails professional
Here will be the subtitle
הקולקציה
צור איתנו קשר
…[truncated by Evolize: exceeded D1 value limit]
Markup<body class="d-flex flex-column min-vh-100" hx-headers="{"X-CSRFToken": "eVON9VqAnlveAjMzxWIUIWVljnutzrV4NxNkl9mo21VOLnHtMWQuLehWhjcYJS8b"}">
<!-- Navigation Bar (Header) -->
<div class="uwy userway_p3" data-uw-feature-ignore="true" data-uw-rm-ignore="true" title="תפריט נגישות" style="background-color: transparent !important; overflow: initial !important;"><div class="userway_buttons_wrapper"><div class="ulsti hidden userway_dark" id="userwayLstIcon" aria-label="תפריט תרגומים" role="button" tabindex="0" aria-haspopup="dialog" data-uw-s19-ignore="" title="תפריט ת… How to fixTo fix this issue, add a skip link to the main content of the page. This can be done by adding an anchor tag with a link to the main content container, and styling it to be visible only when focused. For example: <a href="#main-content" class="skip-link">Skip to main content</a>. Make sure to adjust the href attribute to point to the correct element.
Medium
Touch targets are too small on mobile
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
Component
4 affected pages
16 instances
WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA)
Ref 1Q5MYL
Affected pagehttps://ndn-co.com/
Elementdiv > div:nth-of-type(1) > div:nth-of-type(2) > ul > li:nth-of-type(1) > a
Accessible nameבית
Markup<a href="/" class="text-white-50 text-decoration-none focus-ring focus-ring-light rounded-1">
בית
</a> How to fixIncrease this <a>'s rendered area to at least 24 × 24 CSS pixels, or provide sufficient spacing from adjacent targets. Prefer increasing padding on the existing control (for example the button or link) rather than adding a separate non-interactive wrapper. Observed size: 23 × 17 CSS pixels; required minimum: 24 × 24 CSS pixels.
Low
Navigation regions are not distinguishable
The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.
Component
1 affected page
2 instances
WCAG WCAG 2.1 SC 1.3.1 Info and Relationships (Level A)
Ref KPC2TE
Affected pagehttps://ndn-co.com/catalog/product/%D7%A4%D7%95%D7%9C%D7%99%D7%92%D7%9C/
Elementhtml > body > nav
Accessible nameחנות NDN
קטגוריות
כל המוצרים
בייסים
ג'ל בנייה
ג'ל בנייה בבקבוק
טופ
כלי עבודה
מכשירי חשמל
פוליג'ל
צבעים
מותגים
ADDICT
GELLO
SAHARA
לילה מילאנו
NDN.
קטלוג
קטגוריות
כל המוצרים
בייסים
ג'ל בנייה
ג'ל בנייה בבקבוק
טופ
כלי עבודה
מכשירי חשמל
פוליג'ל
צבעים
מותגים
ADDICT
GELLO
SAHARA
לילה מילאנו
אודותינו
כניסה למערכת
לרשום
0
Markup<nav class="navbar navbar-expand-lg navbar-light bg-white border-bottom sticky-top py-2">
<div class="container flex-wrap">
<button class="navbar-toggler border-0 px-0" aria-label="פתח את סרגל הניווט" type="button" data-bs-toggle="offcanvas" data-bs-target="#mobileMenu">
<span class="navbar-toggler-icon"></span>
</button>
<div class="offcanvas offcanvas-start" tabindex="-1" id="mobileMenu">
<div class="offcanvas-header">
<p class="offcanvas-title h5">חנות NDN</p>
<button type="b… How to fixAdd an accessible name to each navigation landmark to help screen reader users distinguish between them. This can be achieved by adding an 'aria-label' attribute to the navigation element or providing a visible text label.
Low
Touch targets are too small on mobile
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
Component
1 affected page
3 instances
WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA)
Ref 9Y5R65
Affected pagehttps://ndn-co.com/catalog/product/%D7%A4%D7%95%D7%9C%D7%99%D7%92%D7%9C/
Elementmain#main-content > nav > div > ol > li:nth-of-type(1) > a
Accessible nameבית
Markup<a href="/" class="text-decoration-none text-muted">בית</a>
How to fixTo fix this issue, increase the size of the touch target to at least 24x24 pixels. Consider adding padding to the element or increasing the font size to make it easier for users to tap on mobile devices.
Low
Touch targets are too small on mobile
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
Component
1 affected page
3 instances
WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA)
Ref ZWZP5X
Affected pagehttps://ndn-co.com/catalog/product/%D7%A4%D7%95%D7%9C%D7%99%D7%92%D7%9C/
Elementinput#variant-3
Markup<input type="radio" class="btn-check" name="product_variant" id="variant-3" value="3" data-name="קליר" data-extra-price="0.00" data-sku="פוליגל-קליר" data-stock="3" checked="" onchange="updateVariantDetails(this)">
How to fixIncrease this <input>'s rendered area to at least 24 × 24 CSS pixels, or provide sufficient spacing from adjacent targets. Prefer increasing padding on the existing control (for example the button or link) rather than adding a separate non-interactive wrapper. Observed size: 13 × 13 CSS pixels; required minimum: 24 × 24 CSS pixels.
Low
Touch targets are too small on mobile
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
Component
1 affected page
4 instances
WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA)
Ref W3MX09
Affected pagehttps://ndn-co.com/catalog/product/%D7%A4%D7%95%D7%9C%D7%99%D7%92%D7%9C/
Elementdiv > div:nth-of-type(1) > div > div:nth-of-type(2) > p > a
Accessible nameלק ג'ל בצבעים 15 מ"ל
Markup<a aria-label="לק ג'ל בצבעים 15 מ"ל" href="/catalog/product/%D7%9C%D7%A7-%D7%92%D7%9C-%D7%91%D7%A6%D7%91%D7%A2%D7%99%D7%9D-15-%D7%9E%D7%9C/" class="text-dark text-decoration-none focus-ring focus-ring-dark rounded-1">לק ג'ל בצבעים 15 מ"ל</a>
How to fixIncrease the touch target size of the interactive element to at least 24x24px to make it easier for users to activate by touch.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
2 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref 8V3FXG
Affected pagehttps://ndn-co.com/accounts/signup/
Element.form-floating.mb-3:nth-child(3) > .form-text
Accessible nameפורמט: 0501234567 או +972501234567
Markup<div class="form-text">
פורמט: 0501234567 או +972501234567
</div> How to fixIncrease the contrast between the text color and background color of the element with the class 'form-text' to meet the minimum contrast ratio thresholds. Consider using a color contrast analyzer tool to determine the optimal colors.
Low
Touch targets are too small on mobile
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
Component
1 affected page
1 instance
WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA)
Ref VYMS9W
Affected pagehttps://ndn-co.com/accounts/signup/
Elementmain#main-content > p > a
Accessible nameכניסה למערכת
Markup<a href="/accounts/login/">כניסה למערכת</a>
How to fixTo fix this issue, ensure that all interactive elements, such as buttons and links, have a minimum touch target size of 24x24 pixels. Consider increasing the size of the element or adding padding around it to make it easier to tap on mobile devices.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
2 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref 9CJEFM
Affected pagehttps://ndn-co.com/accounts/password/reset/
Elementa[href$="accessibility/"]
Accessible nameהצהרת נגישות
Markup<a href="/accessibility/" class="text-white-50 text-decoration-none focus-ring focus-ring-light rounded-1">
הצהרת נגישות
</a> How to fixTo improve accessibility, increase the contrast between the text color and background color of the link. Consider using a darker or more saturated text color, or a lighter background color. For example, you could change the class 'text-white-50' to a class with a higher contrast ratio.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
1 instance
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref CQCNKS
Affected pagehttps://ndn-co.com/accounts/signup/
Element.form-text > ul > li:nth-child(1)
Accessible nameהסיסמה שלך לא יכולה להיות דומה מדי למידע אישי אחר שלך.
Markup<li>הסיסמה שלך לא יכולה להיות דומה מדי למידע אישי אחר שלך.</li>
How to fixIncrease the contrast between the text color and the background color to meet the minimum contrast ratio thresholds as specified in WCAG 2.1 SC 1.4.3. Consider using a color contrast analyzer tool to determine the optimal colors.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
1 instance
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref U8RUNI
Affected pagehttps://ndn-co.com/catalog/product/%D7%A4%D7%95%D7%9C%D7%99%D7%92%D7%9C/
Element#display-price
Accessible name49.00₪
Markup<span class="fs-2 fw-bold text-dark" style="display:ltr !important;" id="display-price" data-base-price="49.00">
49.00₪
</span> How to fixIncrease the contrast between the text color and the background color of the element with id 'display-price' to meet the minimum contrast ratio thresholds as defined in WCAG 2.1 SC 1.4.3
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
1 instance
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref YMOGWY
Affected pagehttps://ndn-co.com/accounts/signup/
Element.col-lg-4.col-md-6:nth-child(1) > h2
Accessible nameNDN
Markup<h2 class="h5 fw-bold mb-3 text-white">NDN</h2>
How to fixIncrease the contrast between the text color and the background color to meet the minimum contrast ratio thresholds. Consider using a color contrast analyzer tool to determine the optimal colors.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
1 instance
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref KZSLV0
Affected pagehttps://ndn-co.com/
Element.btn-primary.btn-lg[href$="catalog/"]
Accessible nameהקולקציה
Markup<a href="/catalog/" class="btn btn-primary btn-lg rounded-pill px-4 fw-bold shadow-sm">
הקולקציה
</a> How to fixConsider adjusting the text color or background color of the element to improve the contrast ratio. A contrast ratio of at least 4.5:1 for normal text is recommended.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
1 instance
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref E10DG2
Affected pagehttps://ndn-co.com/
Element.pe-lg-5
Accessible nameHere will be the subtitle
Markup<p class="fs-5 text-muted mb-4 pe-lg-5" style="max-width: 460px">
Here will be the subtitle
</p> How to fixTo improve readability, consider increasing the contrast between the text color and the background color. This can be achieved by using a darker or lighter text color, or by adding a background image or color with sufficient contrast. Refer to the Web Content Accessibility Guidelines (WCAG 2.1) for guidance on meeting the minimum contrast ratio thresholds.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
1 instance
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref 1MTX6F
Affected pagehttps://ndn-co.com/
Elementh1
Accessible nameNDN nails professional
Markup<h1 class="display-3 fw-bold text-dark mb-4 lh-sm">
NDN nails professional
</h1> How to fixTo improve the accessibility of this element, consider increasing the contrast between the text color and the background color. This can be achieved by using a darker or lighter text color, or by adding a background image or color that provides sufficient contrast. For example, you could change the text color to a darker shade or add a background color that is lighter or darker than the current background.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
1 instance
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref 1PI283
Affected pagehttps://ndn-co.com/
Element.btn-outline-dark
Accessible nameצור איתנו קשר
Markup<a href="#contact" class="btn btn-outline-dark btn-lg rounded-pill px-4 fw-bold">
צור איתנו קשר
</a> How to fixIncrease the contrast between the text color and background color of the element with the class 'btn btn-outline-dark btn-lg rounded-pill px-4 fw-bold' to meet the minimum contrast ratio thresholds.