Public accessibility assessment

Accessibility issues detected on test2.marchadelnorte.com

Evolize inspected 5 publicly accessible pages on test2.marchadelnorte.com and detected 26 automatically identifiable accessibility findings. 7 findings were classified as critical or high priority. The findings map to 8 WCAG success criterions. The sections below show affected pages, technical evidence and recommended remediation. The most frequent issues involve page has no main landmark, hidden elements can still receive keyboard focus, interactive controls are not keyboard-accessible.

26findings detected

7critical + high

5pages inspected

27 Aug 2026assessed

Independent public assessment. test2.marchadelnorte.com is not necessarily affiliated with or a customer of Evolize.

MONITOR THIS WEBSITE RUN A FREE ASSESSMENT

01 · Accessibility summary

02 · Priority findings

High Page has no main landmarkWCAG 1.3.1 (A) · 5 pages · 10 instances
High Hidden elements can still receive keyboard focusWCAG 2.4.3 (A) · 5 pages · 30 instances
High Hidden elements can still receive keyboard focusWCAG 2.4.3 (A) · 5 pages · 10 instances
High Hidden elements can still receive keyboard focusWCAG 2.4.3 (A) · 5 pages · 10 instances
High Interactive controls are not keyboard-accessibleWCAG 2.1.1 (A) · 1 page · 12 instances

03 · WCAG criteria affected

Criterion	Name	Level	Findings	Pages
1.4.3	Contrast (Minimum)	AA	9	3
2.1.1	Keyboard	A	4	5
2.4.3	Focus Order	A	4	5
2.2.2	Pause, Stop, Hide	A	3	5
2.5.8	Target Size (Minimum)	AA	3	5
4.1.2	Name, Role, Value	A	3	5
1.3.1	Info and Relationships	A	2	5
1.4.1	Use of Color	A	1	1

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

High

Page has no main landmark

WCAG 1.3.1 (A)10 instances5 affected pages

ComponentRef F1CR29

No <main> or role=main region is present, so screen reader users cannot jump to primary content.

Affected pagehttps://test2.marchadelnorte.com/

Elementbody#top

Accessible nameMarchadel Norte Inicio Inscripción Inscritos BTT, eBIKE y Gravel Trail, Speed Trail y Andarines Prueba Combinada Marcha Familiar Información Noticias Recorrido Reglamento Alojamientos Restaurantes Clasificación Contacto Trasierra · Ruiloba XIII MARCHA DEL NORTE 2026 14 de FEBRERO de 2026 a las 11:00 Inscripción Un año más, tras el éxito de ediciones anteriores, la organización de las fiestas patronales de Trasierra (Ruiloba) os presenta la Marcha del Norte. …[truncated by Evolize: exceeded D1 value limit]

Markup

<body id="top">
<div class="main-container">
    <div class="container-fluid m-0 p-0">
        <nav class="navbar navbar-expand-lg bg-white navbar-light sticky-top p-0 my-0">
            <a href="/" class="navbar-brand d-flex align-items-center py-3">
                <div class="m-0 logo" role="img" aria-label="Logotipo"></div>
                <span class="brand-text">Marcha<br>del Norte</span>
            </a>
            <button type="button" class="navbar-toggler me-4" data-bs-toggle="collapse" data-bs-target="#navbarCollapse" aria-controls="navbarCollapse" aria-expanded="false" aria-label=…

How to fixAdd a <main> element or an element with role="main" to define the primary content region of the page, allowing screen reader users to easily navigate to the main content.

Affected pages/ /inscritos/btt /inscritos/trail /inscritos/combinada /inscripcion

High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)60 instances5 affected pages

ComponentRef 3YNKS8

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

Affected pagehttps://test2.marchadelnorte.com/

Elementdiv#navbarCollapse > div > div:nth-of-type(1) > div > a:nth-of-type(1)

Accessible nameBTT, eBIKE y Gravel

Markup

<a href="/inscritos/btt" class="dropdown-item">BTT, eBIKE y Gravel</a>

How to fixTo fix this issue, remove the element from the tab order by setting 'tabindex=-1' or make the element visible when it receives focus. Ensure that all interactive elements are visible when they receive keyboard focus.

Affected pages/ /inscritos/btt /inscritos/trail /inscritos/combinada /inscripcion

ComponentRef 3X94BG

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

Affected pagehttps://test2.marchadelnorte.com/

Elementdiv#navbarCollapse > div > a:nth-of-type(1)

Accessible nameInicio

Markup

<a href="/" class="nav-item nav-link active">Inicio</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 the 'display: none' or 'visibility: hidden' CSS properties to completely hide it. Alternatively, make the element visible when it receives focus.

Affected pages/ /inscritos/btt /inscritos/trail /inscritos/combinada /inscripcion

ComponentRef K6FEDK

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

Affected pagehttps://test2.marchadelnorte.com/

Elementdiv#navbarCollapse > div > div:nth-of-type(1) > a

Accessible nameInscritos

Rolebutton

Markup

<a href="#" class="nav-link dropdown-toggle " data-bs-toggle="dropdown" role="button">Inscritos</a>

How to fixTo fix this issue, remove the element from the tab order by setting 'tabindex' to '-1' or by making the element visible when it receives focus. Alternatively, consider removing the 'role' attribute if the element does not need to be focusable.

Affected pages/ /inscritos/btt /inscritos/trail /inscritos/combinada /inscripcion

ComponentRef 7MQQ5T

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

Affected pagehttps://test2.marchadelnorte.com/inscripcion

Elementinput#mujer

Markup

<input id="mujer" name="genero" type="radio" checked="" class="form-check-input" value="1" required="">

How to fixKeep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.

High

Interactive controls are not keyboard-accessible

WCAG 2.1.1 (A)12 instances1 affected page

ComponentRef B7I25E

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.

Affected pagehttps://test2.marchadelnorte.com/inscripcion

Elementa#pills-btt40-tab

Accessible nameBTT

Roletab

Markup

<a class="nav-link active" id="pills-btt40-tab" data-bs-toggle="tab" data-bs-target="#pills-btt40" role="tab" aria-controls="pills-btt40" aria-selected="true" value="BTT">BTT</a>

How to fixAdd a tabindex attribute to the element or ensure it has focusable semantics to make it reachable by keyboard.

High

Links must be distinguishable without relying on color

WCAG 1.4.1 (A)4 instances1 affected page

ComponentRef QXP2JK

Links must be distinguishable without relying on color

Affected pagehttps://test2.marchadelnorte.com/

Elementp > a[href$="alojamientos"]

Accessible namealojamientos

Markup

<a href="/alojamientos">alojamientos</a>

How to fixTo make links distinguishable without relying on color, consider adding an underline or a bold style to the link text. For example, the link 'alojamientos' could be underlined or displayed in bold to differentiate it from the surrounding text.

High

Elements must only use permitted ARIA attributes

WCAG 4.1.2 (A)12 instances5 affected pages

ComponentRef T3RIOE

Elements must only use permitted ARIA attributes

Affected pagehttps://test2.marchadelnorte.com/inscripcion

Element.logo-marquee

Accessible namePatrocinadores

Markup

<div class="logo-marquee publi1-carousel mt-3" aria-label="Patrocinadores">

How to fixTo fix this issue, ensure that the ARIA attributes used on the element are permitted. In this case, the 'aria-label' attribute is used on a 'div' element. Consider using a more semantic HTML element, such as a 'h3' or 'p', or ensure that the 'aria-label' is necessary and used correctly.

Affected pages/inscritos/btt /inscritos/trail /inscritos/combinada /inscripcion

ComponentRef UU37WL

Elements must only use permitted ARIA attributes

Affected pagehttps://test2.marchadelnorte.com/

Element.logo-marquee--rtl

Accessible nameColaboradores

Markup

<div class="logo-marquee logo-marquee--rtl publi2-carousel mt-3" aria-label="Colaboradores">

How to fixReview the usage of ARIA attributes on the elements with class 'logo-marquee' and ensure that only permitted attributes are used. Consider removing or replacing 'aria-label' with a valid alternative, such as providing a text description or using a different ARIA attribute that is applicable for the element's role.

ComponentRef V19WXE

Elements must only use permitted ARIA attributes

Affected pagehttps://test2.marchadelnorte.com/

Element.publi1-carousel

Accessible namePatrocinadores

Markup

<div class="logo-marquee publi1-carousel mt-3" aria-label="Patrocinadores">

How to fixTo fix this issue, ensure that the ARIA attributes used on the elements are permitted. In this case, the `aria-label` attribute is used on a `div` element with the class `logo-marquee publi1-carousel mt-3`. Check if this attribute is necessary and if it's correctly implemented. Consider removing or replacing it with a permitted attribute if possible.

Medium

Content sits outside any landmark region

WCAG 1.3.1 (A)8 instances4 affected pages

ComponentRef UU9QU9

Meaningful content is not contained in a landmark (header/nav/main/footer/aside), so assistive-technology users cannot reach it via landmark navigation.

Affected pagehttps://test2.marchadelnorte.com/inscritos/btt

Elementbody#top > div > div > div:nth-of-type(2) > section > div

Accessible nameInscritos en BTT, eBIKE y Gravel Solo aparecen participantes con el pago confirmado. 3 inscritos Dorsal Modalidad Nombre Apellidos 5 BTT 70 Km Pablo Caviee Asda 6 BTT 70 Km Prueba 232122 Script Redsys 7 BTT 70 Km Prueba 002735 Script Redsys

Markup

<div class="container home-wrap">
        <h1 class="text-primary inscritos-page__title">
            
            Inscritos en BTT, eBIKE y Gravel
            
        </h1>
        <p class="inscritos-lead">
            Solo aparecen participantes con el pago confirmado.
        </p>

        
        <article class="inscritos-block" id="btt">
            
            <p class="inscritos-block__count inscritos-block__count--solo">3 inscritos</p>
            

            
            <div class="inscritos-table-wrap">
                <table class="inscritos-table">
                    <thead…

How to fixWrap the content in a landmark region such as a header, nav, main, or footer to enable assistive technology users to reach it via landmark navigation. For example, wrap the element <h1 class="hero-title">XIII MARCHA DEL NORTE 2026</h1> in a <main> or <header> tag.

Affected pages/ /inscritos/btt /inscritos/trail /inscritos/combinada

Medium

Touch targets are too small on mobile

WCAG 2.5.8 (AA)13 instances5 affected pages

ComponentRef 7F88V

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

Affected pagehttps://test2.marchadelnorte.com/inscritos/btt

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

Accessible nameMarcha del Norte

Markup

<a href="/">Marcha del Norte</a>

How to fixIncrease the touch target size of the interactive element to at least 24x24 pixels to make it easier for users to activate by touch.

Affected pages/ /inscritos/btt /inscritos/trail /inscritos/combinada /inscripcion

ComponentRef 02UA88

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

Affected pagehttps://test2.marchadelnorte.com/

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

Accessible namealojamientos

Markup

<a href="/alojamientos">alojamientos</a>

How to fixIncrease the size of the touch target to at least 24x24 pixels to make it easier for users to activate by touch.

ComponentRef MIZBJM

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

Affected pagehttps://test2.marchadelnorte.com/inscripcion

Elementinput#mujer

Markup

<input id="mujer" name="genero" type="radio" checked="" class="form-check-input" value="1" required="">

How to fixIncrease the size of the touch target to at least 24x24 pixels to ensure reliable activation by touch. Consider adding padding or increasing the size of the surrounding element to achieve this.

Medium

Text has insufficient colour contrast

WCAG 1.4.3 (AA)42 instances3 affected pages

ComponentRef N8ZM2C

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

Affected pagehttps://test2.marchadelnorte.com/inscritos/btt

Elementth:nth-child(1)

Accessible nameDorsal

Markup

<th scope="col">Dorsal</th>

How to fixIncrease the contrast between the text color and background color of the table header cells to meet the minimum contrast ratio thresholds.

ComponentRef BZ4H0M

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

Affected pagehttps://test2.marchadelnorte.com/inscripcion

Element#inputDonativo

Accessible nameImporte del donativo

Markup

<input id="inputDonativo" min="0" class="form-control text-center" value="0.00" step="0.01" aria-label="Importe del donativo">

How to fixTo improve the accessibility of this form, consider adjusting the colors used for the text and background to meet the minimum contrast ratio of 4.5:1 for normal text. You can use online tools to check the contrast ratio and select colors that are accessible to users with visual impairments.

ComponentRef L2LDB5

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

Affected pagehttps://test2.marchadelnorte.com/inscripcion

Element#club

Markup

<input type="text" class="form-control form-control-sm" id="club" name="club" value="">

How to fixTo fix this issue, adjust the text and background colors of the input field to meet the minimum contrast ratio of 4.5:1 for normal text. You can use a color contrast analyzer tool to find suitable colors.

ComponentRef 5NRCX3

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

Affected pagehttps://test2.marchadelnorte.com/inscripcion

Element#nombre

Markup

<input type="text" class="form-control form-control-sm" name="nombre" id="nombre" placeholder="Nombre" value="" required="">

How to fixIncrease the contrast between the text color and background color of the input field to meet the minimum contrast ratio thresholds. This can be achieved by adjusting the CSS styles for the .form-control class.

ComponentRef 416PBY

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

Affected pagehttps://test2.marchadelnorte.com/

Element.hero-kicker

Accessible nameTrasierra · Ruiloba

Markup

<p class="hero-kicker">Trasierra · Ruiloba</p>

How to fixTo improve the accessibility of the page, consider adjusting the color scheme to increase the contrast between the text and background colors. A contrast ratio of at least 4.5:1 for normal text is recommended. You can use online tools to help determine the contrast ratio and select more accessible colors.

ComponentRef 4SRV2I

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

Affected pagehttps://test2.marchadelnorte.com/

Elementh1

Accessible nameXIII MARCHA DEL NORTE 2026

Markup

<h1 class="hero-title">XIII MARCHA DEL NORTE 2026</h1>

How to fixTo improve readability, consider adjusting the color scheme of the hero-title element to meet the minimum contrast ratio thresholds. You can use online tools to calculate the contrast ratio between the text color and background color. Aim for a contrast ratio of at least 4.5:1 for normal text.

ComponentRef 6I5BG

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

Affected pagehttps://test2.marchadelnorte.com/

Element.hero-date

Accessible name14 de FEBRERO de 2026 a las 11:00

Markup

<p class="hero-date">14 de FEBRERO de 2026 a las 11:00</p>

How to fixTo improve readability, consider increasing the contrast between the text color and background color of the element with class 'hero-date'. This can be achieved by adjusting the CSS styles to use a darker or lighter color for the text or background, ensuring a minimum contrast ratio of 4.5:1 for normal text.

ComponentRef CND33N

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

Affected pagehttps://test2.marchadelnorte.com/inscripcion

Element#donativoDecrementa

Accessible nameRestar donativo

Markup

<button id="donativoDecrementa" class="btn btn-primary btn-lg" type="button" aria-label="Restar donativo">−</button>

How to fixIncrease the contrast between the text color and the background color of the button with id 'donativoDecrementa' to meet the minimum contrast ratio thresholds as defined in WCAG 2.1 SC 1.4.3.

ComponentRef 8VZZ4K

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

Affected pagehttps://test2.marchadelnorte.com/inscripcion

Element#provincia

Accessible nameA Coruña Álava Albacete Alicante Almería Asturias Ávila Badajoz Barcelona Burgos Cáceres Cádiz Cantabria Castellón Ceuta Ciudad Real Córdoba Cuenca Girona Granada Guadalajara Guipúzcoa Huelva Huesca Islas Baleares Jaén La Rioja Las Palmas León Lleida Lugo Madrid Málaga Melilla Murcia Navarra Ourense Palencia Pontevedra Salamanca Santa Cruz de Tenerife Segovia Sevilla Soria Tarragona Teruel Toledo Valencia Valladolid Vizcaya Zamora Zaragoza

Markup

<select class="form-select form-select-sm" id="provincia" name="provincia" required="">

How to fixTo improve the accessibility of this form, consider increasing the contrast between the text color and the background color. This can be achieved by adjusting the CSS styles for the select element or its parent container. A contrast ratio of at least 4.5:1 for normal text is recommended.

Medium

Carousel has no accessible controls

WCAG 2.1.1 (A)12 instances5 affected pages

ComponentRef MBUXQP

A carousel/slider exposes no previous/next or pause controls, so keyboard and assistive-technology users cannot navigate or stop it. Requires manual review of the specific widget.

Affected pagehttps://test2.marchadelnorte.com/inscritos/btt

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

Accessible namePatrocinadores

Markup

<div class="logo-marquee publi1-carousel mt-3" aria-label="Patrocinadores">
    <div class="logo-marquee-track">
        
            
                <div class="publi1-item">
                    <div class="logo-tile publi1-img">
                        <img src="/static/img/logospublicidad/cajarural.webp" alt="Caja Rural">
                    </div>
                </div>
            
                <div class="publi1-item">
                    <div class="logo-tile publi1-img">
                        <img src="/static/img/logospublicidad/cocacola.webp" alt="Coca-Cola">
                  …

How to fixAdd previous/next or pause controls to the carousel/slider, ensuring they are accessible via keyboard and assistive technologies. Consider using ARIA attributes to provide a clear and consistent navigation experience for all users.

Affected pages/inscritos/btt /inscritos/trail /inscritos/combinada

ComponentRef 98YOC9

A carousel/slider exposes no previous/next or pause controls, so keyboard and assistive-technology users cannot navigate or stop it. Requires manual review of the specific widget.

Affected pagehttps://test2.marchadelnorte.com/

Elementbody#top > div > div > div:nth-of-type(2) > section:nth-of-type(2) > div:nth-of-type(1)

Accessible namePatrocinadores

Markup

<div class="logo-marquee publi1-carousel mt-3" aria-label="Patrocinadores">
    <div class="logo-marquee-track">
        
            
                <div class="publi1-item">
                    <div class="logo-tile publi1-img">
                        <img src="/static/img/logospublicidad/cajarural.webp" alt="Caja Rural">
                    </div>
                </div>
            
                <div class="publi1-item">
                    <div class="logo-tile publi1-img">
                        <img src="/static/img/logospublicidad/cocacola.webp" alt="Coca-Cola">
                  …

How to fixAdd previous/next or pause controls to the carousel/slider that can be accessed by keyboard and assistive-technology users. Ensure these controls are properly labeled and announced to screen readers.

ComponentRef 5DQS74

A carousel/slider exposes no previous/next or pause controls, so keyboard and assistive-technology users cannot navigate or stop it. Requires manual review of the specific widget.

Affected pagehttps://test2.marchadelnorte.com/inscripcion

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

Accessible namePatrocinadores

Markup

<div class="logo-marquee publi1-carousel mt-3" aria-label="Patrocinadores">
    <div class="logo-marquee-track">
        
            
                <div class="publi1-item">
                    <div class="logo-tile publi1-img">
                        <img src="/static/img/logospublicidad/cajarural.webp" alt="Caja Rural">
                    </div>
                </div>
            
                <div class="publi1-item">
                    <div class="logo-tile publi1-img">
                        <img src="/static/img/logospublicidad/cocacola.webp" alt="Coca-Cola">
                  …

05 · Pages inspected

/inscripcion33 findings High
/22 findings High
/inscritos/btt11 findings High
/inscritos/combinada10 findings High
/inscritos/trail10 findings High

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 test2.marchadelnorte.com

01 · Accessibility summary

02 · Priority findings

03 · WCAG criteria affected

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

04 · All detected findings

Page has no main landmark

Hidden elements can still receive keyboard focus

Interactive controls are not keyboard-accessible

Links must be distinguishable without relying on color

Elements must only use permitted ARIA attributes

Content sits outside any landmark region

Touch targets are too small on mobile

Text has insufficient colour contrast

Carousel has no accessible controls

05 · Pages inspected

06 · About this assessment

07 · Continuous monitoring

Other public accessibility assessments