Accesibility Statement
Website: Mariscal Abogados — https://www.mariscal-abogados.com
Commitment to Accessibility
Mariscal Abogados is committed to making its website accessible in compliance, to the extent possible, with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, and with the harmonised standard UNE-EN 301549:2019, taken as technical references by Royal Decree 1112/2018.
Although this website belongs to a private sector entity and is not subject to the general legal accessibility obligations established by said Royal Decree for the public sector, Mariscal Abogados voluntarily assumes this commitment as part of its quality policy and equal access to information for all users, including persons with disabilities.
This accessibility statement applies to the website www.mariscal-abogados.com.
Compliance Status
This website is partially compliant with WCAG 2.1 Level AA due to the exceptions and non-compliance issues outlined below.
Non-Accessible Content
The content listed below is not fully accessible for the following reasons:
a) Non-compliance with WCAG 2.1 AA
| # | Affected content / element | WCAG Criterion | Issue description |
| 1 | Format error messages in the contact form | 3.3.3 Error Suggestion | When the email or phone field is filled out in an incorrect format, the notification next to the field is generic (“Please check your answer”) instead of specifying the particular issue (invalid email or phone format). The field itself is correctly identified and described (HappyForms automatically associates aria-describedby/aria-invalid with the error field), meaning criterion 3.3.1 (Level A, Error Identification) is met; the outstanding requirement is message specificity, a Level AA criterion. Two custom code fixes have been tested without success; the form’s messaging system (free or paid) does not allow a different message per field or validation type, and the reason why the custom code is not taking effect remains to be determined. Pending further technical investigation. |
b) Content not within the scope of the review
- PDF documents and other office files (publications, downloadable articles) have not been individually reviewed to verify their accessibility tagging
Preparation of this Accessibility Statement
This statement was prepared on February 10, 2026, and last reviewed on September 15, 2026.
The method used to prepare the statement was a self-assessment carried out by the information society service provider itself, through:
- A preliminary technical diagnosis (Phase 1), conducted on February 10, 2026, based on a manual review of code, semantic structure, keyboard navigation, color contrast, forms, and images of key pages on the site, according to WCAG 2.1 AA criteria.
- A remediation action plan (Phase 2), dated March 2, 2026, prioritizing detected issues into critical, medium, and minor, and detailing the applicable technical solution for each.
- The implementation of viable critical and medium technical fixes via code (theme and templates), along with the progressive correction of content (alternative texts, heading hierarchy, and other elements) by the editorial team.
- An additional review (Phase 3), completed on September 11, 2026, focusing on global site components (cookie banner, header, footer, slider, error page) and a representative sample of each page template type, verifying the actual state of the production site following the remediation of previous phases.
- A remediation closure (Phase 4), completed on September 15, 2026, in which the visible focus indicator and redundant links on card listings were fixed across most affected templates, leaving only the two items detailed in the non-accessible content table pending.
Last statement review: September 15, 2026.
Feedback and Contact Information
You can send communications regarding accessibility requirements, such as:
- Reporting any potential non-compliance by this website.
- Reporting other content access difficulties.
- Submitting any other query or suggestion for improvement regarding website accessibility.
Through the following channel email address: [email protected]
Communications should state the reason for the issue, the page(s) where it was detected, the browser and operating system used, and, if possible, a screenshot to help diagnose the problem.
