Public accessibility assessment

Accessibility issues detected on lvtredesign.mstarproject.com

Evolize inspected 4 public pages on lvtredesign.mstarproject.com and detected 54 automatically identifiable accessibility findings.

54Findings detected

11WCAG criteria affected

4Pages inspected

20 Aug 2026Assessment date

Highest detected severity: Critical · 23 high-priority findings · 80% inspected-page coverage

Most widespread issueButtons have no accessible nameDetected on 4 inspected pages

Most affected page/products/3g-ab050745 findings detected

Most represented WCAG criterionWCAG 1.4.3 — Contrast (Minimum)22 detected findings

Is lvtredesign.mstarproject.com your website?

Keep this assessment current and get notified when new accessibility issues are detected.

MONITOR THIS WEBSITE RUN A FREE ASSESSMENT

Not your website? Scan your own site →

01 · Accessibility summary

Evolize inspected 4 public pages on lvtredesign.mstarproject.com and detected 54 accessibility findings. The most widespread issue was "Buttons have no accessible name", detected on 4 inspected pages. The most affected inspected page was "/products/3g-ab0507", where 45 findings were detected. The assessment identified findings mapped to 11 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.

Critical
Buttons have no accessible name
WCAG 4.1.2 (A) · 4 inspected pages · 8 instances
Why this matters
Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.
Recommended action
Add a text description or aria-label attribute to the button elements so that their purpose can be understood by assistive technology.
View technical evidence →
Critical
Links lack accessible text
WCAG 2.4.4 (A) · 1 inspected page · 2 instances
Why this matters
Links expose no accessible name, so their destination is unknown to screen reader users.
Recommended action
Add text to the link, such as the logo name, or provide an alternative text using the 'aria-label' attribute for screen readers to announce the link purpose.
View technical evidence →
Critical
Links lack accessible text
WCAG 2.4.4 (A) · 1 inspected page · 2 instances
Why this matters
Links expose no accessible name, so their destination is unknown to screen reader users.
Recommended action
Add accessible text to the link, such as an aria-label attribute or a text description within the link element, to inform screen reader users of the link's destination.
View technical evidence →
Critical
Links lack accessible text
WCAG 2.4.4 (A) · 1 inspected page · 2 instances
Why this matters
Links expose no accessible name, so their destination is unknown to screen reader users.
Recommended action
Add accessible text to the link, such as an aria-label attribute or a text description within the link element, to inform screen reader users of the link's destination.
View technical evidence →
Critical
Links lack accessible text
WCAG 2.4.4 (A) · 1 inspected page · 2 instances
Why this matters
Links expose no accessible name, so their destination is unknown to screen reader users.
Recommended action
This link exposes no accessible text. Add visible text that identifies its destination, or remove the link if it serves no purpose. For an icon-only link, provide an aria-label describing where it goes. The link points to /ru.
View technical evidence →

03 · WCAG criteria affected

Criterion	Name	Level	Findings	Pages	Reach
1.4.3	Contrast (Minimum)	AA	22	4	4 / 4
2.5.8	Target Size (Minimum)	AA	7	4	4 / 4
1.3.1	Info and Relationships	A	6	4	4 / 4
1.1.1	Non-text Content	A	4	4	4 / 4
2.4.4	Link Purpose (In Context)	A	4	4	4 / 4
2.1.1	Keyboard	A	3	1	1 / 4
2.4.3	Focus Order	A	3	4	4 / 4
4.1.2	Name, Role, Value	A	3	4	4 / 4
3.3.2	Labels or Instructions	A	2	1	1 / 4
1.4.4	Resize Text	AA	1	4	4 / 4
2.4.1	Bypass Blocks	A	1	4	4 / 4

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

Critical

Buttons have no accessible name

WCAG 4.1.2 (A)9 instances4 inspected pages

Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.

Why it matters

Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.

Recommended correction

Add a text description or aria-label attribute to the button elements so that their purpose can be understood by assistive technology.

View 9 affected elements

Component · Ref P619CX

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Element.header__search-submit

Markup

<button class="btn__clear header__search-submit gradient__main">

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Component · Ref J0RN9D

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Elementbutton[data-id="380485"]

Accessible name1 Pirkt

Markup

<button rel="nofollow" class="btn btn__block produ..." id="add_link_EEW_AB0507_..." data-id="380485" onclick="if(check_in_cart($(t...">

Critical

Links lack accessible text

WCAG 2.4.4 (A)8 instances4 inspected pages

Links expose no accessible name, so their destination is unknown to screen reader users.

Why it matters

Links expose no accessible name, so their destination is unknown to screen reader users.

Recommended correction

Add accessible text to the link, such as an aria-label attribute or a text description within the link element, to inform screen reader users of the link's destination.

View 8 affected elements

Component · Ref F0VWMH

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Element.header__logo

Markup

<a href="/" class="header__logo flex__block">

Component · Ref KUKMJ5

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Element.header__logo

Markup

<a href="/" class="header__logo flex__block">

Component · Ref B3DZNQ

Affected pagehttps://lvtredesign.mstarproject.com/lt/pages/user_new_account/

Element.header__logo

Markup

<a href="/lt" class="header__logo flex__block">

Component · Ref ZC1SGP

Affected pagehttps://lvtredesign.mstarproject.com/ru/pages/user_new_account/

Element.header__logo

Markup

<a href="/ru" class="header__logo flex__block">

High

Text has insufficient colour contrast

WCAG 1.4.3 (AA)126 instances4 inspected pages

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Why it matters

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Recommended correction

To improve the accessibility of this link, consider changing the background color or the text color to meet the minimum contrast ratio of 4.5:1 for normal text. You can use online tools to help determine the contrast ratio and select suitable colors.

View 126 affected elements

Component · Ref SHS09F

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Element.header__top-email

Accessible name[email removed]

Markup

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

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Component · Ref AX504B

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Element.header__main-catalog-link > span:nth-child(2)

Accessible nameKatalogs

Markup

<span>Katalogs</span>

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Component · Ref 3T802P

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Element.footer__contacts-title-online > span

Accessible nameTiešsaistē

Markup

<span>Tiešsaistē</span>

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Component · Ref V6OWK3

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Elementa[href="javascript:void(0)"] > span[itemprop="name"]

Accessible nameReģistrācija

Markup

<span itemprop="name">Reģistrācija</span>

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Component · Ref 2MMCX2

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Elementlabel[for="registration__login"]

Accessible namepieteikties *

Markup

<label class="input__label" for="registration__login">pieteikties <span class="required">*</span></label>

Affected pages/pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Component · Ref QADBDE

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Element.input__checkbox-line-text

Accessible nameEs piekrītu. Lietotāja līgums

Markup

<div class="input__checkbox-line-text input__checkbox-line-text-grey">
            Es piekrītu. <a href="/pages/terms_of_use/" target="_blank">Lietotāja līgums</a>
        </div>

Affected pages/pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Component · Ref VSZSCK

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Element#icart_id

Accessible name0

Markup

<span id="icart_id">0</span>

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Component · Ref IUJJ62

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Element.product__page-attributes:nth-child(2) > .product__page-attribute.flex__block > .product__page-attribute-name

Accessible nameKods:

Markup

<div class="product__page-attribute-name">Kods:</div>

Component · Ref YLO72O

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Element.btn__small > .flex__block > span

Accessible nameAtrast

Markup

<span>Atrast</span>

Component · Ref C1FRZZ

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Element.price__base > span

Accessible name24.10 €

Markup

<span>24.10 €</span>

Component · Ref URKUWO

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Element.product__page-buy-bottom-price-new

Accessible name24.10 €

Markup

<div class="product__page-buy-bottom-price product__page-buy-bottom-price-new">24.10 €</div>

Component · Ref JH7484

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Element

.product__page-attributes-block > .product__page-attributes > .product__page-attribute.flex__block:nth-child(1) > .product__page-attribute-name

Accessible nameRažotājs:

Markup

<div class="product__page-attribute-name">Ražotājs:</div>

Component · Ref W2705W

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Element#add_link_EEW_AB0507_171_2 > span

Accessible namePirkt

Markup

<span>Pirkt</span>

Component · Ref CXRFOW

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Element#select2-xs9i-container > .select2-selection__placeholder

Accessible nameIzvēlieties zīmolu

Markup

<span class="select2-selection__placeholder">Izvēlieties zīmolu</span>

Component · Ref LMK5A5

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Element.product__page-price-new

Accessible name24.10 €

Markup

<div class="product__page-price-new">24.10 €</div>

Component · Ref GX76BJ

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Element.scroll__to-js > span

Accessible nameVisi raksturlielumi

Markup

<span>Visi raksturlielumi</span>

Component · Ref MZVRPP

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Element

.product__page-attributes-blocks > .product__page-attributes:nth-child(1) > .product__page-attribute.flex__block > .product__page-attribute-name

Accessible nameRažotājs:

Markup

<div class="product__page-attribute-name">Ražotājs:</div>

Component · Ref T290A8

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Element.product__page-attribute.flex__block:nth-child(2) > .product__page-attribute-name

Accessible nameKods:

Markup

<div class="product__page-attribute-name">Kods:</div>

Component · Ref IFV1J5

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Elementa[aria-label="Profile"] > .mobile__menu-text

Accessible namePierakstīties

Markup

<span class="mobile__menu-text">Pierakstīties</span>

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account

Component · Ref BE5G1X

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Element.product__page-delivery-line.flex__block:nth-child(2) > .product__page-delivery-line-name

Accessible nameСамовывоз из офиса:

Markup

<div class="product__page-delivery-line-name">Самовывоз из офиса:</div>

Component · Ref JTP6KV

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Element.product__card-buy-link-text

Accessible namePirkt

Markup

<span class="product__card-buy-link-text">Pirkt</span>

Component · Ref QEMG17

Affected pagehttps://lvtredesign.mstarproject.com/lt/pages/user_new_account/

Element.mobile__menu-header-catalog-link > .mobile__menu-text

Accessible nameKatalogas

Markup

<span class="mobile__menu-text">Katalogas</span>

High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)80 instances4 inspected pages

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

Why it 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 correction

To fix this issue, ensure that all focusable elements are visible to sighted keyboard users. You can do this by either removing the element from the tab order or making it visible when it receives focus. In this case, the element with the class 'header__catalog-left-menu-link' is not visible but remains in the tab order. Consider adding a style to make it visible when focused, such as 'outline' or 'box-shadow', or remove the 'tabindex' attribute if it's not necessary for the element to be focusable.

View 80 affected elements

Component · Ref 5UWRSH

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Elementdiv > div > div:nth-of-type(2) > ul > li:nth-of-type(1) > a

Accessible nameAksesuāri

Markup

<a href="/select/39-aksessuapyi/" data-id="122" data-level-show="2" class="header__catalog-left-menu-link flex__block header__catalog-menu-link-js">
                                        <span class="header__catalog-left-menu-icon"><img src="/imgbank/Image/rubricator/Aksessuari.png"></span>
                                        <span class="header__catalog-left-menu-text">Aksesuāri</span>
                                                                                    <span class="header__catalog-left-menu-arrow"><svg width="24" height="24"><use xlink:href="/assets/site/images/icons.svg…

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Component · Ref B9WW04

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Elementdiv > div:nth-of-type(1) > div > div > div:nth-of-type(2) > button

Accessible nameNotīrīt

Markup

<button class="btn__clear header__search-history-clear-js">Notīrīt</button>

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Component · Ref 3FYHSA

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Elementdiv > div > nav:nth-of-type(1) > ul > li:nth-of-type(1) > a

Accessible namePiegāde un saņemšana

Markup

<a href="/pages/delivery/">Piegāde un saņemšana</a>

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

High

Images lack text alternatives

WCAG 1.1.1 (A)60 instances4 inspected pages

Informative images have no alternative text, so their meaning is unavailable to people using assistive technology.

Why it matters

Informative images have no alternative text, so their meaning is unavailable to people using assistive technology.

Recommended correction

Add an alt attribute to the img tag, for example: <img src="/assets/site/images/images/images/footer/gls.png" alt="GLS logo">

View 60 affected elements

Component · Ref 8VKDNR

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Element.copyright__icon:nth-child(4) > img

Markup

<img src="/assets/site/images/images/images/footer/gls.png">

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Component · Ref FKF1WU

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Element.copyright__block:nth-child(3) > .copyright__block-inner.flex__block > .copyright__icon:nth-child(2) > img

Markup

<img src="/assets/site/images/images/images/footer/mastercard.png">

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Component · Ref 31R2N3

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Element.registration__advantages-image > img

Markup

<img src="/assets/site/images/images/images/pages/registration_img.png">

Affected pages/pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Component · Ref GS7Z4G

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Element.product__page-delivery-line-icons > div:nth-child(1) > img

Markup

<img src="/assets/site/images/images/images/checkout/delivery/item_4.png">

High

Zooming and scaling must not be disabled

WCAG 1.4.4 (AA)8 instances4 inspected pages

Zooming and scaling must not be disabled

Why it matters

Zooming and scaling must not be disabled

Recommended correction

Review the affected element and correct the reported accessibility issue.

View 8 affected elements

Component · Ref 99YZ8P

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Elementmeta[name="viewport"]:nth-child(9)

Markup

<meta name="viewport" content="initial-scale=1, maximum-scale=1">

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

High

Interactive controls are not keyboard-accessible

WCAG 2.1.1 (A)8 instances1 inspected page

A control that responds to clicks (a clickable element or an ARIA widget) cannot receive keyboard focus, so keyboard and switch users cannot operate it.

Why it matters

A control that responds to clicks (a clickable element or an ARIA widget) cannot receive keyboard focus, so keyboard and switch users cannot operate it.

Recommended correction

Add a positive tabindex value to the element or use a native HTML button element to make it focusable by keyboard.

View 8 affected elements

Component · Ref 5XTLXX

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Elementdiv#product__page-gallery > div:nth-of-type(2)

Accessible namePrevious slide

Rolebutton

Markup

<div class="swiper-button-prev product__page-gallery-prev swiper-button-disabled swiper-button-lock" tabindex="-1" role="button" aria-label="Previous slide" aria-controls="swiper-wrapper-89f4f7d8aca10927c" aria-disabled="true">
                    <svg width="24" height="24"><use xlink:href="/assets/site/images/icons.svg#arrow"></use></svg>
                </div>

Component · Ref QZKSCQ

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Elementdiv:nth-of-type(2) > div > div > label > div > div:nth-of-type(2)

Accessible nameMūsu noliktava

Markup

<div class="filters__checkbox-inner-text" onclick="document.location='/products/3g-ab0507/ourstore/'">Mūsu noliktava</div>

Component · Ref 2KDYAF

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Elementdiv#product__page-gallery > div:nth-of-type(3)

Accessible nameNext slide

Rolebutton

Markup

<div class="swiper-button-next product__page-gallery-next swiper-button-disabled swiper-button-lock" tabindex="-1" role="button" aria-label="Next slide" aria-controls="swiper-wrapper-89f4f7d8aca10927c" aria-disabled="true">
                    <svg width="24" height="24"><use xlink:href="/assets/site/images/icons.svg#arrow"></use></svg>
                </div>

Medium

No skip link to main content

WCAG 2.4.1 (A)8 instances4 inspected pages

The page offers no bypass mechanism, so keyboard users must tab through the full navigation before reaching the main content on every page.

Why it matters

The page offers no bypass mechanism, so keyboard users must tab through the full navigation before reaching the main content on every page.

Recommended correction

Add a skip link to the main content of the page, allowing keyboard users to bypass the navigation. This can be achieved by adding an anchor link with a visually hidden text, that becomes visible when focused, and links to the main content container.

View 8 affected elements

Component · Ref KI20RL

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Elementhtml > body

Accessible name<iframe src="https://www.googletagmanager.com/ns.html?id=G-F7PJHX8KND" height="0" width="0" style="display:none;visibility:hidden"></iframe> /* <![CDATA[ */ try { if(typeof jaxon.config == undefined) jaxon.config = {}; } catch(e) { jaxon = {}; jaxon.config = {}; }; jaxon.config.requestURI = "https://lvtredesign.mstarproject.com/pages/user_new_account/"; jaxon.config.statusMessages = true; jaxon.config.waitCursor = true; jaxon.config.version = "Jaxon 4.x"; jaxon.config.defaultMode = "asynchronous"; jaxon.config.defaultMethod = "POST"; jaxon.config.responseType = "JSON"; jaxon_process_form = function() { return jaxon.request({ jxnfun: 'process_form' }, { parameters: arguments }); }; jaxon_process_browse_url = function() { return jaxon.request({ jxnfun: 'process_browse_url' }, { parameters: arguments }); }; jaxon.dialogs = {}; jaxon.dom.ready(function() { jaxon.command.handler.register("jquery", (args) => jaxon.cmd.script.execute(args)); jaxon.command.handler.register("bags.set", (args) => { for (const bag in args.data) { jaxon.ajax.parameters.bags[bag] = args.data[bag]; } }); }); jaxon.command.handler.register("rd", (command) => { const { data: sUrl, delay: nDelay } = command; if (nDelay <= 0) { window.location = sUrl; return true; } window.setTimeout(() => window.location = sUrl, nDelay * 1000); return true; }); /* ]]> */ Акции Piegāde un saņemšana Garantija Par uzņēmumu Pircējiem Piegādātājiem +371 286 66 672 [email removed] LV LV LT RU Katalogs Meklēšanas vēsture Notīrīt Nekas netika atrasts. Lūdzu, mēģiniet mainīt meklēšanas kritērijus vai zvaniet mums Nekas netika atrasts. Lūdzu, mēģiniet mainīt meklēšanas kritērijus vai zvaniet mums Pierakstīties Garāža 0 …[truncated by Evolize: exceeded D1 value limit]

Markup

<body>

    
    <!-- Google Tag Manager (noscript) -->
    <noscript><iframe src="https://www.googletagmanager.com/ns.html?id=G-F7PJHX8KND"
                      height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
    <!-- End Google Tag Manager (noscript) -->
    


<script src="/vendor/jaxon-php/jaxon-js/dist/jaxon.core.js"></script>



<script>
/* <![CDATA[ */
try {
    if(typeof jaxon.config == undefined)
        jaxon.config = {};
}
catch(e) {
    jaxon = {};
    jaxon.config = {};
};

jaxon.config.requestURI = "https://lvtredesign.mstarproject.com/pages/user…

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Medium

Touch targets are too small on mobile

WCAG 2.5.8 (AA)50 instances4 inspected pages

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Why it matters

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Recommended correction

Increase the size of the touch target to at least 24x24 pixels to make it easier for users to tap on mobile devices. Consider adding padding or increasing the font size of the phone number to achieve this.

View 50 affected elements

Component · Ref DEWDC9

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Elementdiv > div > nav:nth-of-type(2) > ul > li:nth-of-type(1) > a

Accessible name+371 286 66 672

Markup

<a href="tel:+37128666672" class="header__top-phone">
                                    <svg width="10" height="10"><use xlink:href="/assets/site/images/icons.svg#point"></use></svg>
                                    <span>+371 286 66 672</span>
                                </a>

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Component · Ref KRDO13

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Elementdiv:nth-of-type(1) > div:nth-of-type(1) > div > div > div:nth-of-type(3) > button

Accessible nameLV

Markup

<button class="header__top-dropdown-link btn__clear">
                            <span>LV</span>
                            <svg width="18" height="18" class="header__top-dropdown-icon-arrow">
                                <use xlink:href="/assets/site/images/icons.svg#arrow"></use>
                            </svg>
                        </button>

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Component · Ref G0SCC2

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Elementdiv > div:nth-of-type(1) > div > ul > li:nth-of-type(1) > a

Accessible nameTiešsaistes veikals auto detaļām

Markup

<a href="/" itemprop="item">
                                <span itemprop="name">Tiešsaistes veikals auto detaļām</span>
                                <meta itemprop="position" content="1">
                            </a>

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Component · Ref YWPPIF

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Elementform#registration__form > div:nth-of-type(10) > label > div:nth-of-type(2) > a

Accessible nameLietotāja līgums

Markup

<a href="/pages/terms_of_use/" target="_blank">Lietotāja līgums</a>

Affected pages/pages/user_new_account /lt/pages/user_new_account

Component · Ref 89VDQE

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Elementdiv#home_car_select_brand > select

Accessible nameACURA ALFAROMEO AUDI BENTLEY BMW CADILLAC CHEVROLET CHRYSLER CITROËN DACIA DAF DAIHATSU DODGE FIAT / ALFA / LANCIA FORD HONDA HUMMER HYUNDAI INFINITI ISUZU IVECO JAGUAR JEEP JOHN DEERE KIA LAMBORGHINI LANCIA LAND ROVER LEXUS LINCOLN MAN MAZDA MERCEDES BENZ MINI MITSUBISHI NISSAN OPEL PEUGEOT PORSCHE RENAULT SAAB SCANIA SEAT SKODA SMART SSANG YONG SUBARU SUZUKI TOYOTA VOLKSWAGEN VOLVO

Markup

<select class="select__2 input__select select__2-js select2-hidden-accessible" data-placeholder="Izvēlieties zīmolu" data-clear="1" data-required="1" onchange="if(this.value){jaxon_process_browse_url(this.selectedOptions[0].dataset.url);}" data-select2-id="select2-data-1-b3ta" tabindex="-1" aria-hidden="true">

        <option value="" data-select2-id="select2-data-3-mjop"></option>

                                    <option value="acura" data-url="/?action=car_select&amp;cat=&amp;model_group=&amp;data[id_model]=&amp;car_select[model]=&amp;category=&amp;subcategory=&amp;locale=lv&amp;year=&a…

Medium

Navigation regions are not distinguishable

WCAG 1.3.1 (A)48 instances4 inspected pages

The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.

Why it matters

The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.

Recommended correction

Add an accessible name to each navigation landmark using 'aria-label' or 'aria-labelledby' attributes to distinguish them for screen reader users

View 48 affected elements

Component · Ref 6WZGVR

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Elementdiv:nth-of-type(1) > div > div > div:nth-of-type(3) > div > nav

Accessible nameLV LT RU

Markup

<nav class="header__langs-menu">
                                <ul>
                                                                            <li>
                                            <a href="https://lvtredesign.mstarproject.com/pages/user_new_account/" class="current">
                                                <span>LV</span>
                                                                                                    <svg width="14" height="9">
                                                        <use xlink:href="/assets/site/images/icons.svg#check"></use>
        …

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Component · Ref RGV2JV

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Elementheader > div:nth-of-type(1) > div:nth-of-type(1) > div > div > nav:nth-of-type(1)

Accessible namePiegāde un saņemšana Garantija Par uzņēmumu Pircējiem Piegādātājiem

Markup

<nav class="header__top-menu">
                        <ul class="flex__block">
                                                            <li><a href="/pages/delivery/">Piegāde un saņemšana</a></li>
                                                            <li><a href="/pages/privacy-policy/">Garantija</a></li>
                                                            <li><a href="/pages/about/">Par uzņēmumu</a></li>
                                                            <li><a href="/pages/additional_customer/">Pircējiem</a></li>
                                                    …

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Medium

Touch targets are too small

WCAG 2.5.8 (AA)8 instances4 inspected pages

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Why it matters

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Recommended correction

Increase the size of the touch target to at least 24x24 pixels to make it easier for users to activate by touch. Consider adding padding or increasing the size of the surrounding element to achieve this.

View 8 affected elements

Component · Ref I21LZJ

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Elementli:nth-child(1) > .header__top-phone[href="tel:+37128666672"]

Accessible name+371 286 66 672

Markup

<a href="tel:+37128666672" class="header__top-phone">
                                    <svg width="10" height="10"><use xlink:href="/assets/site/images/icons.svg#point"></use></svg>
                                    <span>+371 286 66 672</span>
                                </a>

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Component · Ref E1N6TK

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Element.header__top-email

Accessible name[email removed]

Markup

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

Affected pages/products/3g-ab0507 /pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Medium

Page has no level-one heading

WCAG 1.3.1 (A)6 instances3 inspected pages

The page exposes no <h1>, so its topic is not conveyed in the heading structure.

Why it matters

The page exposes no <h1>, so its topic is not conveyed in the heading structure.

Recommended correction

Add a level-one heading (<h1>) to the page to convey its topic and structure the content in a logical and consistent way. This heading should be descriptive, concise, and indicate the main subject of the page.

View 6 affected elements

Component · Ref EZG3BY

Affected pagehttps://lvtredesign.mstarproject.com/pages/user_new_account/

Elementhtml > body

Markup

<body>

    
    <!-- Google Tag Manager (noscript) -->
    <noscript><iframe src="https://www.googletagmanager.com/ns.html?id=G-F7PJHX8KND"
                      height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
    <!-- End Google Tag Manager (noscript) -->
    


<script src="/vendor/jaxon-php/jaxon-js/dist/jaxon.core.js"></script>



<script>
/* <![CDATA[ */
try {
    if(typeof jaxon.config == undefined)
        jaxon.config = {};
}
catch(e) {
    jaxon = {};
    jaxon.config = {};
};

jaxon.config.requestURI = "https://lvtredesign.mstarproject.com/pages/user…

Affected pages/pages/user_new_account /lt/pages/user_new_account /ru/pages/user_new_account

Medium

Form fields use placeholder text as the only label

WCAG 1.3.1 (A)10 instances1 inspected page

Fields rely on placeholder text instead of a real label. The placeholder disappears once the user types, and it is not exposed as a programmatic label.

Why it matters

Fields rely on placeholder text instead of a real label. The placeholder disappears once the user types, and it is not exposed as a programmatic label.

Recommended correction

Add a visible label to the form field, using the 'label' HTML element, and associate it with the input field using the 'for' attribute. For example: <label for='filters_price_min'>Price Min</label> <input type='text' name='filter[price][min]' class='input__text' id='filters_price_min' value='24.10'>

View 10 affected elements

Component · Ref QFKT0W

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Elementinput#filters_price_min

Markup

<input type="text" name="filter[price][min]" class="input__text" id="filters_price_min" value="24.10" placeholder="24.10">

Component · Ref Y78XVH

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Elementdiv > div:nth-of-type(3) > div:nth-of-type(2) > div:nth-of-type(1) > div > input

Markup

<input type="text" name="q" class="input__text js-search-parameters" autocomplete="off" placeholder="Meklēt">

Medium

List items are not inside a list

WCAG 1.3.1 (A)2 instances1 inspected page

A <li> appears outside a <ul> or <ol>, so the list relationship is not conveyed to assistive technology.

Why it matters

A <li> appears outside a <ul> or <ol>, so the list relationship is not conveyed to assistive technology.

Recommended correction

Wrap related <li> elements in a <ul> or <ol>, or use a different element for non-list content.

View 2 affected elements

Component · Ref YRLU8B

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Element.product__card

Accessible name3G Bremžu klucis 420x180 AB0507 29.16 € 24.10 € 1 Pirkt

Markup

<li class="product__card flex__block product__card-js">

Low

ARIA attributes have invalid values

WCAG 4.1.2 (A)12 instances1 inspected page

ARIA attributes reference ids that do not exist or hold invalid values, breaking the accessibility tree.

Why it matters

ARIA attributes reference ids that do not exist or hold invalid values, breaking the accessibility tree.

Recommended correction

Ensure that all ARIA attributes have valid values and reference existing ids. For the 'aria-labelledby' and 'aria-controls' attributes, verify that the referenced elements exist in the DOM and have the correct ids.

View 12 affected elements

Component · Ref MZN7US

Affected pagehttps://lvtredesign.mstarproject.com/products/3g-ab0507/

Elementspan[aria-labelledby="select2-xs9i-container"]

Accessible nameIzvēlieties zīmolu

Rolecombobox

Markup

<span class="select2-selection select2-selection--single" role="combobox" aria-haspopup="true" aria-expanded="false" tabindex="0" aria-disabled="false" aria-labelledby="select2-xs9i-container" aria-controls="select2-xs9i-container">

05 · Most affected inspected pages

/products/3g-ab0507/Critical49 findings
/lt/pages/user_new_account/Critical31 findings
/pages/user_new_account/Critical30 findings
/ru/pages/user_new_account/Critical28 findings

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.

MONITOR THIS WEBSITE SEE PRICING

Is information in this report inaccurate or outdated? Request a correction or removal.

Accessibility issues detected on lvtredesign.mstarproject.com

Is lvtredesign.mstarproject.com your website?

01 · Accessibility summary

02 · Start here

Buttons have no accessible name

Links lack accessible text

Links lack accessible text

Links lack accessible text

Links lack accessible text

03 · WCAG criteria affected

A scan shows today's exposure. Monitoring shows what changes next.

04 · All detected findings

Buttons have no accessible name

Links lack accessible text

Text has insufficient colour contrast

Hidden elements can still receive keyboard focus

Images lack text alternatives

Zooming and scaling must not be disabled

Interactive controls are not keyboard-accessible

No skip link to main content

Touch targets are too small on mobile

Navigation regions are not distinguishable

Touch targets are too small

Page has no level-one heading

Form fields use placeholder text as the only label

List items are not inside a list

ARIA attributes have invalid values

05 · Most affected inspected pages

06 · About this assessment

07 · Continuous monitoring

Reports with similar accessibility findings