Appointment

www.agilexperience.co

Accessibility

Compliance status

AgileXperience (hereinafter also Website) is partially compliant with Royal Decree 1112/2018, of September 7, due to the non-compliance of the aspects listed below.

Content not accessible

The content below is not accessible for the following reasons:

a. Lack of compliance with RD 1112/2018: Not applicable. Meets 100% of the web accessibility criteria.

    • Criterion 5 – General requirements: Not applicable.
      Non-compliant means may be required to activate some accessibility feature [requirement number 5.2 Activation of accessibility features, of UNE-EN 301549:2022].
    • Criterion 6 – Two-way voice communication capability: Not applicable.
  • A frequency range with an upper limit of at least 7000Hz may not be guaranteed [requirement number 6.1 Voice bandwidth, of UNE-EN 301549:2022].
  • It may not be possible to provide a two-way communication mode via RTT [requirement number 6.2.1.1 Communication via RTT, of UNE-EN 301549:2022].
  • It may not be possible to provide a bidirectional communication mode of voice and text simultaneously [requirement number 6.2.1.2 Simultaneous voice and text, of UNE-EN 301549:2022].
  • It may not clearly differentiate sent text from received text in RTT communications [requirement number 6.2.2.1 Visually distinguishable on-screen presentation, of UNE-EN 301549:2022].
  • The RTT send and receive address may not be software determinable [requirement number 6.2.2.2.2 Software determinable send and receive address, of UNE-EN 301549:2022].
  • Speaker identification by RTT may not be provided [requirement number 6.2.2.3 Speaker identification, of UNE-EN 301549:2022].
  • There may not be an on-screen visual indicator of real-time audio activity [requirement number 6.2.2.4 Visual audio indicator with real-time text, of UNE-EN 301549:2022].
  • It may not be able to guarantee compatibility with other systems with RTT functionality [requirement number 6.2.3 Interoperability, of UNE-EN 301549:2022].
  • It may not be able to guarantee that the RTT input is transmitted to the network within 500ms [requirement number 6.2.4 RTT Responsiveness, of UNE-EN 301549:2022].
  • An alternative to voice may not be provided to perform interactive assistance or response tasks [requirement number 6.4 Alternatives to voice-based services, of UNE-EN 301549:2022].
  • It may not be possible to guarantee a minimum resolution of QVGA in video functionalities [requirement number 6.5.2 Resolution, of UNE-EN 301549:2022].
  • It may not be possible to guarantee a minimum video frequency of 20 FPS during communications [requirement number 6.5.3 Frame rate, of UNE-EN 301549:2022].
  • The maximum time of 100ms between voice and video presentation to the user may not be exceeded [requirement number 6.5.4 Synchronization of audio and video, of UNE-EN 301549:2022].
    There may not be a mode for speaker identification for sign language users in real time [requirement number 6.5.6 Speaker identification with video communication, of UNE-EN 301549:2022].
    • Criterion 7 – Video capacity: Not applicable.
  • It is possible that there is a video player that does not have an operation mode that allows displaying the existing subtitles [requirement number 7.1.1 Playback of subtitles, of UNE-EN 301549:2022].
  • It is possible that there is a video player that does not have an operation mode that allows synchronizing the audio with the subtitles [requirement number 7.1.2 Synchronization of subtitles, of UNE-EN 301549:2022].
  • It is possible that there is a video player that does not have a subtitle saving system [requirement number 7.1.3 Preservation of subtitles, of UNE-EN 301549:2022].
  • The user may not be able to adapt the subtitle characteristics to his individual requirements [requirement number 7.1.4 Subtitle characteristics, of UNE-EN 301549:2022].
  • A mode of operation that provides a spoken output of the available subtitles may not be provided in all cases [requirement number 7.1.5 Spoken subtitles, of UNE-EN 301549:2022].
  • There may be some players that do not have a mode for selecting and playing available audio descriptions [requirement number 7.2.1 Playback of audio description, of UNE-EN 301549:2022].
  • There may be a player that does not have a way to synchronize available audiodescriptions [requirement number 7.2.2 Synchronization of the audiodescription, of UNE-EN 301549:2022].
    It is possible that there is a player that does not have a way to save available audio descriptions [requirement number 7.2.3 Preservation of audio description, of UNE-EN 301549:2022].
  • Some page incorporates a video player that does not provide controls for captioning and audio description playback at the same level of interaction as the rest of the controls [requirement number 7.3 User controls for captioning and audio description, of UNE-EN 301549:2022].
    • Criterion 9 – Requirements applicable to web pages: Not applicable.
  • There are non-textual contents that lack a textual alternative, or that have an alternative that is not adequate [requirement number 9.1.1.1.1 Non-textual content, of UNE-EN 301549:2022].
  • Some recorded videos do not have text-based alternatives or audio alternative [requirement number 9.1.2.1 Audio only and video only, of UNE-EN 301549:2022].
  • Some recorded videos may not contain subtitles [requirement number 9.1.2.2.2 Subtitles (recorded), of UNE-EN 301549:2022].
  • Some pre-recorded videos on the website do not have audio description or alternative means [requirement number 9.1.2.3 Audio description or alternative means, of UNE-EN 301549:2022].
  • Some pre-recorded videos on the website do not have audio description or alternative means [requirement number 9.1.2.5 Audio description (recorded), of UNE-EN 301549:2022].
  • In some pages the information, structure and relationships are not determined by software or do not have alternative as text [requirement number 9.1.3.1 Information and relationships, of UNE-EN 301549:2022].
  • Some pages do not have at least one correct reading sequence defined by software [requirement number 9.1.3.2 Meaningful sequence, of UNE-EN 301549:2022].
    Identification of elements only sensory characteristics such as shape, color, size, visual location, orientation or sound [requirement number 9.1.3.3.3 Sensory characteristics, of UNE-EN 301549:2022].
  • The content does not adapt when changing the screen orientation [requirement number 9.1.3.4 Orientation, of UNE-EN 301549:2022].
  • There are elements of forms in which the purpose of the entry is not identified [requirement number 9.1.3.5 Identify the purpose of the entry, of UNE-EN 301549:2022].
  • On some pages color has been used as the only visual means to convey information, indicate an action, provoke a response or distinguish a visual element [requirement number 9.1.4.1 Use of color, of UNE-EN 301549:2022].
  • There are sound elements that are played automatically and there is no mechanism to pause or stop it [requirement number 9.1.4.2 Audio control, of UNE-EN 301549:2022].
  • On some pages the contrast ratio in text may not be at least 4.5:1 [requirement number 9.1.4.3 Contrast (minimum), of UNE-EN 301549:2022].
  • There are errors on some pages related to text size and its customizability when zooming in [requirement number 9.1.4.4.4 Text resizing, of UNE-EN 301549:2022].
  • There are clipart images based only on text [requirement number 9.1.4.5 Text images, of UNE-EN 301549:2022].
  • There are errors when customizing the font size, zoom level or text spacing [requirement number 9.1.4.10 Text Reset, of UNE-EN 301549:2022].
    Insufficient contrast in interface components or graphic objects [requirement number 9.1.4.11 Contrast of non-text content, of 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, of UNE-EN 301549:2022].
  • When an element receives the pointer or keyboard focus, additional content is displayed that cannot be discarded without moving the pointer or changing the mouse focus [requirement number 9.1.4.13 Content with hover or focus, of UNE-EN 301549:2022].
  • There are pages where keyboard navigation is not optimal and errors appear [requirement number 9.2.1.1.1 Keyboard, of UNE-EN 301549:2022].
  • There are components that, when receiving the focus, prevent moving it to another one only with the tab key or arrow keys [requirement number 9.2.1.2 No focus traps, of UNE-EN 301549:2022].
  • There are keyboard shortcuts that do not work [requirement number 9.2.1.4 Shortcuts with character keys, of UNE-EN 301549:2022].
  • There is a time limitation that cannot be stopped, adjusted or extended [requirement number 9.2.2.1 Adjustable time, of UNE-EN 301549:2022].
  • There may be some information in automatic motion that does not have controls to pause, control or hide [requirement number 9.2.2.2.2 Pause, stop and hide, of UNE-EN 301549:2022].
  • There may be elements that flash more than three times in one second or above the general threshold [requirement number 9.2.3.1 Threshold of three flashes or less, of UNE-EN 301549:2022].
  • In some pages there is no mechanism to omit blocks of content that are repeated in several pages [requirement number 9.2.4.1 Avoid blocks, of UNE-EN 301549:2022].
  • Inadequate description of some of the titles of the web pages [requirement number 9.2.4.2 Titling of pages, of UNE-EN 301549:2022].
  • In some documents the sequential keyboard navigation may not have a consistent order [requirement number 9.2.4.3 Order of focus, of UNE-EN 301549:2022].
  • The purpose of links, headings or portal labels may not always be sufficiently descriptive or consistent for all users [requirement number 9.2.4.4.4 Purpose of links (in context), of UNE-EN 301549:2022].
  • Links to related content pages or alternative forms of navigation are not always provided [requirement number 9.2.4.5 Multiple paths, of UNE-EN 301549:2022].
  • There are headings with repeated and/or not very descriptive text [requirement number 9.2.4.6 Headings and labels, of UNE-EN 301549:2022].
  • The location of the focus is not always visible when navigating with a keyboard [requirement number 9.2.4.7 Visible focus, of UNE-EN 301549:2022].
  • There are elements using multipoint or path-based that cannot be operated with only a pointer or without a path-based gesture [requirement number 9.2.5.1 Pointer gestures, of UNE-EN 301549:2022].
  • There are pages where an event cannot be cancelled by clicking the mouse [requirement number 9.2.5.2 Pointer cancellation, of UNE-EN 301549:2022].
  • There are interface components that do not have visible labels [requirement number 9.2.5.3 Name label, of UNE-EN 301549:2022].
  • There is functionality that can only be operated by movement [requirement number 9.2.5.4 Activation by movement, of UNE-EN 301549:2022].
  • In some pages the default language used is not indicated [requirement number 9.3.1.1 Language of the page, of UNE-EN 301549:2022].
  • There could be occasional failures of editing and identification of the language in some parts of the web page [requirement number 9.3.1.2 Language of the parts, of UNE-EN 301549:2022].
  • There are components that when receiving the focus, initiate a context switch [requirement number 9.3.2.1 When receiving the focus, of UNE-EN 301549:2022].
  • User interaction with a control causes page changes without prior warning [requirement number 9.3.2.2.2 When receiving input, of UNE-EN 301549:2022].
  • There may be pages with incoherent navigation, due to different links to the same destination [requirement number 9.3.2.3 Consistent navigation, of UNE-EN 301549:2022].
  • Certain interactive elements are not presented consistently in all cases, as they are displayed in different visual styles [requirement number 9.3.2.4 Consistent identification, of UNE-EN 301549:2022].
  • There are error messages that are not very descriptive, or error messages that are not grouped in 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, of UNE-EN 301549:2022].
  • There are forms with mandatory fields where the user is not informed about it, as well as fields where a textual example of the field format is missing [requirement number 9.3.3.2 Labels or instructions, of UNE-EN 301549:2022].
  • There could be an input error in a field/form that the user is not notified of the suggestion to solve it [requirement number 9.3.3.3.3.3 Suggestions in case of errors 333, of UNE-EN 301549:2022].
  • The data entry does not detect errors and does not provide the user with an opportunity to correct them [requirement number 9.3.3.4 Error prevention (legal, financial, data), of UNE-EN 301549:2022].
  • There may be errors in the use of HTML and WAI-ARIA 1.1 tags and attributes [requirement number 9.4.1.1.1 Processing, of UNE-EN 301549:2022].
  • On some pages user interface components such as form elements, links and script-generated components do not follow the structure recommended by the accessibility guidelines [requirement number 9.4.1.2 Name, function, value, of UNE-EN 301549:2022].
  • In some pages the status messages may not be determined programmatically through functions or properties [requirement number 9.4.1.3 Status messages, of UNE-EN 301549:2022].
    Some of the WCAG 2.1 requirements are not met [requirement number 9.6 Conformance requirements of the WCAG guidelines, of UNE-EN 301549:2022].
    • Criterion 10 – Requirements applicable to non-web documents: Not applicable.
  • There may be documents with images that do not have an adequate textual alternative [requirement number 10.1.1.1.1 Non-textual content, of UNE-EN 301549:2022].
  • There may be no equivalent alternative for audio-only or video-only recorded content [requirement number 10.1.2.1 Audio only and video only, of UNE-EN 301549:2022].
  • Videos may lack subtitles and audio descriptions [requirement number 10.1.2.2.2 Subtitles (recorded), of UNE-EN 301549:2022].
  • There may not be an alternative for tempodependent media or an audio description for recorded video content in synchronized multimedia [requirement number 10.1.2.3 Audio description or alternative media, of UNE-EN 301549:2022].
  • Audio description may not be provided for all recorded video content within synchronized multimedia content [requirement number 10.1.2.5 Audio description (recorded), of UNE-EN 301549:2022].
  • In some document the information, structure and relationships are not determined by software or do not have alternative as text [requirement number 10.1.3.1 Information and relationships, of UNE-EN 301549:2022].
  • Some documents do not have at least one correct reading sequence defined by software [requirement number 10.1.3.2
  • Meaningful sequence, of UNE-EN 301549:2022].
  • There may be documents for which there is no other accessible alternative with which to operate and understand the content [requirement number 10.1.3.3.3 Sensory characteristics, of UNE-EN 301549:2022].
  • There may be documents whose content does not adapt when changing the screen orientation [requirement number 10.1.3.4 Orientation, of UNE-EN 301549:2022].
    In some forms the input field that collects information about the user has not identified the purpose [requirement number 10.1.3.5 Identify the purpose of input, of UNE-EN 301549:2022].
  • In some documents color has been used as the only visual means to convey information, indicate an action, elicit a response or distinguish a visual element [requirement number 10.1.4.1 Use of color, of UNE-EN 301549:2022].
  • There are audio elements in some documents that are played automatically and there is no mechanism to pause or stop it [requirement number 10.1.4.2 Audio control, of UNE-EN 301549:2022].
  • In some documents the contrast ratio in text may not be at least 4.5:1 [requirement number 10.1.4.3 Contrast (minimum), of UNE-EN 301549:2022].
  • In some texts the size cannot be changed by up to 200 percent without loss of content or functionality and in some documents the content may lose functionality or information when the content is enlarged [requirement number 10.1.4.4 Text resizing, of UNE-EN 301549:2022].
  • In some documents, text images may have been used instead of text to convey information [requirement number 10.1.4.5 Text images, of UNE-EN 301549:2022].
  • In some documents the content may lose functionality or information when the content is enlarged [requirement number 10.1.4.10 Resetting of text, of UNE-EN 301549:2022].
  • In some documents the contrast of user interface components and graphic objects may not reach 3:1 with adjacent colors [requirement number 10.1.4.11 Contrast of non-text content, from UNE-EN 301549:2022].
  • In some texts it is not possible to override the specified text spacing [requirement number 10.1.4.12 Text spacing, of UNE-EN 301549:2022].
  • The content of some documents do not receive keyboard focus with which to perform any action [requirement number 10.1.4.13 Content with hover or focus, of UNE-EN 301549:2022].
  • There are documents in which it is not possible to operate entirely through the keyboard [requirement number 10.2.1.1.1 Keyboard, of UNE-EN 301549:2022].
    In some documents the headings have not been defined and it is not possible to navigate through the keyboard [requirement number 10.2.1.2 No focus traps, of UNE-EN 301549:2022].
  • In some documents there are keyboard shortcuts that do not work [requirement number 10.2.1.4 Shortcuts with character keys, of UNE-EN 301549:2022].
  • In some document there is a time limitation that cannot be stopped, adjusted or extended [requirement number 10.2.2.1 Adjustable time, of UNE-EN 301549:2022].
  • A document may contain information in automatic movement that does not have controls to pause, control or hide [requirement number 10.2.2.2.2 Pause, stop and hide, of UNE-EN 301549:2022].
  • Some documents may contain elements that flash more than three times in one second or above the general threshold [requirement number 10.2.3.1 Threshold of three flashes or less, of UNE-EN 301549:2022].
  • There may be documents that do not have a title [requirement number 10.2.4.2 Page titling, of UNE-EN 301549:2022].
  • In some documents the headings have not been defined and the keyboard cannot be navigated [requirement number 10.2.4.3 Order of focus, of UNE-EN 301549:2022].
  • Some document may contain a link that may not have the specific purpose textually defined [requirement number 10.2.4.4.4 Purpose of links (in context), of UNE-EN 301549:2022].
  • In some documents there may be a heading or control name that is not sufficiently descriptive of its purpose [requirement number 10.2.4.6 Headings and labels, of UNE-EN 301549:2022].
  • The location of the focus is not always visible when navigating with a keyboard through a document [requirement number 10.2.4.7 Visible focus, of UNE-EN 301549:2022].
  • In some document there may be elements using multipoint or path-based that cannot be operated with only a pointer or without a path-based gesture [requirement number 10.2.5.1 Pointer gestures, of UNE-EN 301549:2022].
  • There are documents where an event cannot be cancelled by clicking the mouse [requirement number 10.2.5.2 Pointer cancellation, of UNE-EN 301549:2022].
  • There are documents that have some labels accompanying the controls that do not have the same name [requirement number 10.2.5.3 Name label, of UNE-EN 301549:2022].
  • There are documents whose functionality is only operable through movement [requirement number 10.2.5.4 Activation through movement, of UNE-EN 301549:2022].
  • There may be documents in which the main language is not identified [requirement number 10.3.1.1 Language of the page, of UNE-EN 301549:2022].
  • There may be contents or phrases within some documents whose language cannot be determined by program [requirement number 10.3.2.1 Language of parts, of UNE-EN 301549:2022].
  • There may be components in some documents that when receiving the focus, initiate a context switch [requirement number 10.3.2.1 When receiving the focus, of UNE-EN 301549:2022].
  • The interaction of the user with some control, causes page changes without prior warning [requirement number 10.3.2.2.2 When receiving inputs, of UNE-EN 301549:2022].
  • There are data entry fields with automatic error detection capability that do not identify where or how the error occurs [requirement number 10.3.3.1 Identification of errors, of UNE-EN 301549:2022].
  • In some form of some document, some automatic context change could occur without warning the user [requirement number 10.3.3.2 Labels or instructions, of UNE-EN 301549:2022].
  • In some document, there could be an input error in some field/form that the user is not notified of the suggestion to solve it [requirement number 10.3.3.3.3 Suggestions in case of errors, of UNE-EN 301549:2022].
  • In some document there may be some form for data collection or legally or financially compromising data that are not reversible, reviewable or have confirmation before sending [requirement number 10.3.3.4 Error prevention (legal, financial, data), of UNE-EN 301549:2022].
  • In some documents there may be duplicate attributes and IDs [requirement number 10.4.1.1.1 Processing, of UNE-EN 301549:2022].
  • In some document user interface components such as form elements, links and script-generated components do not follow the structure recommended by the accessibility guidelines [requirement number 10.4.1.2 Name, function, value, of UNE-EN 301549:2022].
  • In some documents the status messages may not be determined programmatically through functions or properties [requirement number 10.4.1.3 Status messages, of UNE-EN 301549:2022].
    • Criterion 11 – Requirements applicable to software: Not applicable.
  • The visual user preferences of the browser are not respected on the page [requirement number 11.7 User preferences, of UNE-EN 301549:2022].
  • The information required for accessibility may not be compatible with the format used for the authoring tool output [requirement number 11.8.1 Content management technology, of UNE-EN 301549:2022].
  • There may not be a mechanism to create content in an accessible form [requirement number 11.8.2 Creation of accessible content, of UNE-EN 301549:2022].
  • There is no mechanism for preserving accessibility information during transformations [requirement number 11.8.3 Preservation of accessibility information during transformations, of UNE-EN 301549:2022].
  • An accessibility checker repair mechanism may not be available [requirement number 11.8.4 Repair service, of UNE-EN 301549:2022].
  • There may be no template available that supports content creation according to the requirements of chapter 9 (Web) or 10 (Non-web documents) [requirement number 11.8.5 Templates, of UNE-EN 301549:2022].
    • Criterion 12 – Requirements applicable to documentation and support services: Not applicable.
  •  The product documentation does not list or explain all available accessibility features [requirement number 12.1.1 Accessibility and compatibility features, of UNE-EN 301549:2022].
  • Product documentation may not be completely in accessible formats [requirement number 12.1.2 Accessible documentation, of UNE-EN 301549:2022].
    Support services do not provide all the information on accessibility features included in the product documentation [requirement number 12.2.2 Information on accessibility and compatibility features, of UNE-EN 301549:2022].
    Support services may not always be able to adapt to the communication needs of users with disabilities [requirement number 12.2.3 Effective communication, of UNE-EN 301549:2022].
  • There may be documentation provided by support services that is not in an accessible format [requirement number 12.2.4 Accessible documentation, of UNE-EN 301549:2022].

b. Disproportionate burden: Not applicable.

c. Content does not fall within the scope of applicable law:

  • There may be PDF office automation files and other formats published prior to September 20, 2018 that do not fully meet all accessibility requirements. Although efforts have been made to ensure that most of them do.
  • There may be third-party content that is not developed in this Unit or under its control such as images, interactive maps, videos, documents, players, etc.
  • There may be pre-recorded files published prior to September 20, 2018 that do not fully comply with all accessibility requirements.
    Parts or all of the website may be created with a CMS (WordPress, Shopify, PrestaShop, etc), so due to some update or change in systems, not all generated or self-generated content may comply with all accessibility regulations.

Preparation of this accessibility statement

La presente declaración fue preparada el día 21/04/2024

El método empleado para preparar la declaración ha sido una autoevaluación llevada a cabo por la propia empresa.

Última revisión de la declaración: 21/04/2024

Observaciones y datos de contacto

 

You can make communications about accessibility requirements (Article 10.2.a of Royal Decree 1112/2018 of 7 September) such as, for example:

  • Report any possible non-compliance by this website.
  • Transmit other difficulties in accessing the content.
  • Formulate any other query or suggestion for improvement relating to the accessibility of the website.

Through the following channels:

  • E-mail: hello@agilexperience.co
  • Telephone: 642087729

According to Article 10.2.b of RD 1112/2018, you can also submit:

  • A complaint regarding compliance with the requirements of RD 1112/2018.
  • A request for accessible information relating to:

 

    • Contents that are excluded from the scope of application of RD 1112/2018 as established by Article 3, paragraph 4.
    • Contents that are exempt from compliance with accessibility requirements for imposing a disproportionate burden.

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

Communications will be received and processed by the company’s management, as the unit responsible for the contents of this website.

Optional content

The currently visible version of this website is dated 04/21/2024 and on that date the current accessibility level was revised at that time.

From that date onwards, partial daily reviews of new or modified web content are carried out, both of the templates and of the final published pages and documents, in order to ensure compliance with the accessibility requirements of the UNE-EN 301549:2022 Standard, considering the exceptions of Royal Decree 1112/2018, of September 7.

Among others, the following measures are adopted to facilitate accessibility:

  • Use of alternative text in images.
  • Links provide details of the function or destination of the hyperlink.
  • Use of W3C standards: XHTML 1.0, CSS 3.0, WAI AA.

Compatibility

The web site:

  • has been designed adapting to current standards and regulations regarding accessibility, complying with the priority 2 (AA) checkpoints defined in the Web Content Accessibility Guidelines (WCAG 2.1) specification.
  • is optimized for the latest current versions of Chrome, Edge, Firefox, Safari and Opera
    is designed to be displayed correctly in any resolution and on any desktop, tablet or mobile device (responsive design)
    has been made using HTML5 as markup language and CSS 3 style sheets for its design.

In addition, a continuous audit and revision of content is carried out to facilitate its interpretation and improve navigation through the web portal.

21/04/2024.

When do we start?

Write us by WhatsApp

+34 642 08 77 29

Greet us by email

hello@agilexperience.co

Instagram
  • Copyright © 2024 Agilexperience
  • All rights reserved
×
Skip to content