BARRIEREFREIHEIT
SECTION 1
LISE BERNARD has undertaken to make its website https://lise-bernard.com/ accessible, in accordance with the Royal Decree 12/11/2018, of September 7 (hereinafter, Royal Decree 1112/2018, of September 7) transposing Directive (EU) 2016/2102 of the European Parliament and of the Council (1)].
This accessibility statement applies to the website https://lise-bernard.com/
Compliance status
This website is partially in accordance with Royal Decree 1112/2018, of September 7, due to the lack of conformity of the aspects indicated below.
Content not accessible
The content listed below is not accessible for the following reasons:
1) | Lack of compliance with Royal Decree 11/12/2018, of September 7:There could be occasional low-contrast errors that are nevertheless solved with the accessibility tool WP Accessibility available on all pages of the site allowing toggling to high contrast and page size letter X5 on both web and mobile devices.
Some of the links may not have a discernible name, however through the tabulation you will obtain a previous indication of the destination of the link. |
2 ) | Disproportionate burdenDoes not apply |
3) | The content does not fall within the scope of applicable lawThe client currently manages its web tool, so it is possible that web changes occur after December 2022 that do not meet the accessibility requirements. However, the developers undertake to maintain surveillance of the web content during the contractual period of one year. |
Preparation of this accessibility statement
This statement was prepared on MARCH 1, 2023.
The method used to prepare the declaration has been a self-assessment carried out by the body itself (MARABELIA COOP.V) through the tools Lighthouse, Webaim.org and WAVE (Web Accessibility Evaluation Tools).
A web browsing accessibility test has been carried out through the tool integrated in Chrome Version 110.0.5481.177 (Official Build) (x86_64) Chromevox Screen Reader Version 53.0.2784.13.
The results report is attached in Annex 1 of this declaration.
Observations and contact details
You can make communications about accessibility requirements (article 10.2.a) of Royal Decree 1112/2018, of September 7) such as:
- Report any possible breach by this website.
- Convey other content access difficulties.
- Formulate any other query or suggestion for improvement regarding the accessibility of the website.
You can also request in accessible format information that does not meet the accessibility requirements, either because it is excluded, or because it is exempt due to disproportionate burden; or make a complaint for non-compliance with accessibility requirements.
Through the following ways:
Email: hello@marabelia.com
Telephones: 655 28 25 86 – 605 46 29 05
The communications will be attended and treated with total confidentiality by MARABELIA COOP.V, as the unit responsible for the contents of this website.
Application procedure
Through this procedure, you can initiate a claim to know and oppose the reasons for the rejection of a request for accessible information or complaint, urge the adoption of the appropriate measures in the case of not agreeing with the decision adopted, or expose the reasons why it is considered that the response does not meet the required requirements.
SECTION 2
This accessibility statement is accessible to the public through the “accessibility” link in the “footer” section of all pages of the site https ://lise-bernard.com/ and is directly accessible via the link https://lise-bernard.com/accessibility.
The currently visible version of this website is from December 2022 and on that date the current accessibility level was reviewed.
As of said date, partial daily reviews of the new or modified web content will be carried out, both of the templates and of the final pages and documents published, in order to ensure compliance with the accessibility requirements of the UNE-EN 301549 Standard. :2019, considering the exceptions of Royal Decree 1112/2018, of September 7.
Among others, the following measures are adopted to facilitate accessibility:
- Using alt text on images
- Links provide details of the function or destination of the hyperlink
- Use of W3C standards: XHTML 1.0, CSS 3.0, WAI AA.
- Built-in accessibility tools like WP Accessibility for improved navigation.
Applicable law
(1) Directive (EU) 2016/2102 of the European Parliament and of the Council, of October 26, 2016, on the accessibility of websites and applications for mobile devices of public sector bodies (OJ L 327, 2.12.2016, p. 1).
(2) Execution Decision (EU) 2018/1523 of the Commission, of October 11, 2018, which establishes an accessibility declaration model in accordance with Directive (EU) 2016/2102 of the European Parliament and of the Council on the accessibility of websites and mobile applications of public sector bodies (OJ L 256 of 10.12.2018, p. 103).
ANNEX 1
Via Accessibility Lighthouse Tool in Chrome Version 110.0.5481.177
Lack of conformity
AIR
[aria-hidden=“true“]elements contain focusable descendantsThese are opportunities to improve the use of ARIA in your application, which can improve the experience for users of assistive technology, such as a screen reader.*
*Some low-contrast glitches that are nevertheless resolved with the accessibility tool WP Accessibility available on all pages of the site allowing toggling to high contrast and X5 font size on both web and mobile devices.
Additional elements (manual verification)
The page has a logical tab order.
Interactive controls are focusable from the keyboard
Interactive elements indicate their purpose and status
The user’s focus is directed to the new content added to the page.
User focus is not accidentally stuck in a region
Custom controls have associated labels
Custom controls have ARIA roles
The visual order on the page follows the DOM order
Offscreen content is hidden from assistive technology
HTML5 featured elements are used to improve navigation
Passed audits (24)
[aria-*]attributes match their roles [aria-hidden=“true“]is not present in the <body> [role]I have all the necessary [aria-*]attributesElements with ARIA [role]requiring children to contain a specific content [role]have all required children.
[role]s are contained by their required parent element [role] values are valid [aria-*]attributes have valid values [aria-*]attributes are valid and not misspelledButtons have an accessible name
ARIA IDs are unique
Image elements have [alt] attributes
Form elements have associated tags
[user-scalable=“no“]is not used in the <meta name=“viewport“>element and the [maximum-scale]attribute is not less than 5. [aria-hidden=“true“]elements do not contain focusable descendantsThe page contains a header, skip link, or historical region
The document has a <title>element
[id]attributes of active and focusable elements are unique<html>element has a [lang]attribute
<html>element has a valid value for its [lang]attribute
Links have a discernible name
Lists only contain <li>elements and script support elements ( <script>and <template>).
List elements ( <li>) are contained within <ul>or <ol>parent elements
No element has [tabindex]value mgreater than 0
Header elements appear in descending sequential order
Not applicable (21)
[accesskey] values are uniquebutton, link, and menuitem elements have accessible names
ARIA input fields have accessible names
AIR insert elements have accessible names
AIR progressbar elements have accessible names
ARIA toggle fields have accessible names
AIR tooltiple elements have accessible names
AIR treeitem elements have accessible names
<dl>’s contain only correctly ordered <dt>and <dd>groups, <script>, <template>or <div>elements.
The elements of the definition list are wrapped in <dl>elements
No form field has multiple labels
<frame>or <iframe>elements have a title
<input type=“image“>elements have [alt]text
Document does not use <meta http-equiv=“refresh“>
<object>elements have alt text
Cells in a <table>element using the [headers] attribute refer to table cells within the table itself.
<th>elements and elements with [role=“columnheader“/“rowheader“]have data cells that describe them.
[lang]attributes have a valid value<video>elements contain a <track>element with [kind=“captions“]
MARABELIA COOP.V
F989654589
MARCH 1, 2023