ACCESSIBILITY STATEMENT

This standard establishes the functional requirements that will guarantee that ICT products and services are accessible to all people; for example, from a mobile phone, to computers, through web pages; thus, the requirements for the web are based on the WCAG 2.1 web content accessibility guidelines, developed by W3C, being in line with those indicated in the Spanish standard UNE 139803, 'Accessibility requirements for Web content'. 
Standard EN 301 549 v2.1.2 (2018-08) "Accessibility requirements for ICT products and services" specifies the accessibility functional requirements applicable to products and services that include ICT (websites, software, native apps, documents, hardware, etc). In addition to describing the testing procedures and the evaluation methodology to follow for each accessibility requirement. 

Web Content Accessibility Guidelines (WCAG) 2.1

The Web Content Accessibility Guidelines (WCAG) 2.1 They are the latest version of the W3C (World Wide Web Consortium) Web Content Accessibility Guidelines.

The rule  EN 301-549 v2.1.2 (2018-08) is aligned with WCAG 2.1 and therefore introduces all the changes incorporated into the latter: new compliance criteria, new guideline "2.5 Entry Modes", etc.

It is also worth mentioning that in this new version the pre-existing compliance criteria in WCAG 2.0 have not been modified, not even their numbering.

This accessibility statement applies to the website: https://transmargaz.com

 

compliance status

This website is partially compliant with RD 1112/2018 due to the exceptions and the lack of conformity of the aspects indicated below.

 

content not accessible

The content listed below is not accessible for the following reasons:

 

Lack of compliance with RD 1112/2018

 

    • There are logos and images with confusing text and complex images without a textual description [requirement number 9.1.1.1 Non-text content, of UNE-EN 301549:2022].
    • There are invisible labels in form elements [requirement number 9.1.3.1 Information and relations, of UNE-EN 301549:2022].
    • There are tables not adapted to small screen sizes and form fields that do not display correctly on small screen sizes on outdated and obsolete devices [requirement number 9.1.4.10 Readjustment of text, from UNE-EN 301549:2022].
    • There is text that when changing the spaces and line heights is not displayed correctly [requirement number 9.1.4.12 Text spacing, from UNE-EN 301549:2022].
    • There are elements that are not accessible by keyboard, such as links to social networks, the text editor for comments, elements to sort search results, the pagination of search results [requirement number 9.2.1.1 Keyboard, of UNE-EN 301549:2022].
    • There are elements that do not receive the focus and therefore cannot be interacted with using the keyboard, for example [requirement number 9.2.4.3 Focus order, of UNE-EN 301549:2022].
    • There are images, infographics, link or button text, headline text, and content that are not translated into other languages [requirement number 9.3.1.2 Language of the parties, from UNE-EN 301549:2022].
    • The same icon is being used for different purposes on some page, causing confusion [requirement number 9.3.2.4 Coherent identification, from UNE-EN 301549:2022].
    • There are error messages that are not very descriptive, or error messages that are not grouped into a single message, as well as a lack of suggestions in the form to fill in the fields correctly [requirement number 9.3.3.1 Identification of errors, from UNE-EN 301549:2022].
    • There are forms with mandatory fields where the user is not informed of this, as well as fields where a textual example of the field format is missing. [requirement number 9.3.3.2 Labels and instructions, of UNE-EN 301549:2022].
    • There are form fields where an error is reported when an incorrect value is entered but a suggestion for its correction is not reported [requirement number 9.3.3.3 Suggestions for errors, of UNE-EN 301549:2022].
    • There are pages that may contain syntax errors and therefore some support product may not interpret the content correctly [requirement number 9.4.1.1 Processing, from UNE-EN 301549:2022].
    • There are pages in which support products will not be able to obtain information, interact and be aware of the state of the user interface controls, such as help messages, action result status messages, link attributes , top and footer menus, page language image... that cannot be read by screen readers at the moment they appear [requirement number 9.4.1.2 Name, function, value of UNE-EN 301549:2022].
    • There could be occasional editing errors on some web page.

 

disproportionate burden

    • Does not apply.

 

The content does not fall within the scope of the law applicable.

 

    • There may be office files in PDF or other published formats that do not fully meet all accessibility requirements. Although efforts have been made to ensure that most of them do comply.

 

Preparation of this accessibility statement.

This statement was prepared on May 25, 2023.
The method used to prepare the declaration has been a self-assessment carried out by the web designer-developer himself.

 

Observations and contact information

Can do communications on accessibility requirements (article 10.2.a) of RD 1112/2018) such as:

  • report any possible breach by this website
  • transmit others access difficulties to content
  • formulate any other question or suggestion for improvement regarding the accessibility of the website

through the next Contact Form or by calling 942 938 904

 

You can present:

  • Complaint regarding compliance with the requirements of RD 1112/2018 or
  • Accessible Information Request Relative to:
    • contents what are they excluded of the area of application of RD 1112/2018 as established by article 3, section 4
    • contents what are they exempt of the compliance of accessibility requirements by imposing a disproportionate burden.

In the Request for accessible information, the facts, reasons, and request that make it possible to verify that it is a reasonable and legitimate request must be clearly specified.

 

 

Application procedure.

 

If, once a request for accessible information or complaint has been made, it has been rejected, the decision is not agreed, or the response does not meet the requirements set forth in article 12.5, the person concerned may initiate a claim. Likewise, a claim may be initiated in the event that the period of twenty business days has elapsed without having obtained a response.

 

optional content

This website applies the requirements of the Standard UNE-EN 301549:2022 considering the exceptions of RD 1112/2018.

The last accessibility review was carried out in December 2022.

The website is optimized for all the web browsers most used by users such as Microsoft edge and the latest versions of FireFox, Safari, Opera and Google Chrome. The resolution Web minimum recommended is 1280×1024. (less than 2% are using 1024x768 4:3 XVGA resolutions)

The website is designed for Responsive viewing, which is optimally displayed on tablet and mobile devices. On these devices it is optimized for viewing in the latest current versions of Chrome for mobile, Firefox for mobile, Safari mobile, Opera Mini and native Android browser.

It incorporates a series of keyboard shortcuts to facilitate navigation through the portal Depending on the browser from which the portal is being accessed, it will be necessary to use a combination of keys or others to use the keyboard shortcuts:

 

 
OSBrowserkey combination
windowsinternet explorerAlt + Shortcut key
Google ChromeAlt + Shortcut key
SafariAlt + Shortcut key
FirefoxAlt + Shift + Shortcut key
MACSafariCtrl + Alt + Shortcut Key
Google ChromeCtrl + Alt + Shortcut Key
FirefoxCtrl + Shortcut Key
ubuntuFirefoxAlt + Shift + Shortcut key