Reserva Ahora

Accessibility statement

ACCESSIBILITY STATEMENT

https://balconesdebentomiz.es/

Compliance status

Balcones de Bentomiz (hereinafter, also Website) is partially compliant with Royal Decree 1112/2018, of September 7, due to the lack of conformity of the aspects indicated below.

Non-accessible content

The content below is not accessible for the following reasons:

a. Non-compliance with RD 1112/2018: Does not apply. Complies with 100% of the web accessibility criteria.

    • Criterion 5 – General requirements: Does not apply.
  • Non-compatible means may be required to activate some accessibility features [requirement number 5.2 Activation of accessibility features, of UNE-EN 301549:2022].
    • Criterion 6 – Two-way voice communication capability: Does not apply.
  • It may not be possible to guarantee a frequency range whose upper limit is at least 7000Hz [requirement number 6.1 Bandwidth for voice, 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 two-way 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 be possible to clearly differentiate the text sent from the text received in RTT communications [requirement number 6.2.2.1 Visually differentiable on-screen presentation, of UNE-EN 301549:2022].
  • It may not be possible to determine by software the sending and receiving direction of RTT [requirement number 6.2.2.2 Sending and receiving direction determinable by software, of UNE-EN 301549:2022].
  • It may not be possible to provide speaker identification by RTT [requirement number 6.2.2.3 Speaker identification, of UNE-EN 301549:2022].
  • There may not be a visual indicator on the screen of real-time audio activity [requirement number 6.2.2.4 Visual indicator of audio with real-time text, of UNE-EN 301549:2022].
  • It may not be possible to guarantee compatibility with other systems with RTT functionalities [requirement number 6.2.3 Interoperability, of UNE-EN 301549:2022].
  • It may not be possible to guarantee that the RTT input is transmitted to the network within 500ms [requirement number 6.2.4 RTT response capacity, of UNE-EN 301549:2022].
  • It may not be possible to provide an alternative to voice 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 the 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].
  • It may not be possible to exceed the maximum time of 100ms between the presentation of voice and video to the user [requirement number 6.5.4 Audio and video synchronization, of UNE-EN 301549:2022].
  • There may not be a mode for speaker identification for real-time sign language users [requirement number 6.5.6 Speaker identification with video communication, of UNE-EN 301549:2022].
    • Criterion 7 – Video capability: Does not apply.
  • There may be a video player that does not have a mode of operation that allows existing subtitles to be displayed [requirement number 7.1.1 Subtitle playback, of UNE-EN 301549:2022].
  • There may be a video player that does not have a mode of operation that allows audio to be synchronized with subtitles [requirement number 7.1.2 Subtitle synchronization, of UNE-EN 301549:2022].
  • There may be a video player that does not have a subtitle saving system [requirement number 7.1.3 Subtitle preservation, of UNE-EN 301549:2022].
  • The user may not be able to adapt the characteristics of the subtitles to their individual requirements [requirement number 7.1.4 Subtitle characteristics, of UNE-EN 301549:2022].
  • A mode of operation that facilitates 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 a player that does not have a mode to select and play available audio descriptions [requirement number 7.2.1 Audio description playback, of UNE-EN 301549:2022].
  • There may be a player that does not have a mode to synchronize available audio descriptions [requirement number 7.2.2 Audio description synchronization, of UNE-EN 301549:2022].
  • There may be a player that does not have a mode to save available audio descriptions [requirement number 7.2.3 Audio description preservation, of UNE-EN 301549:2022].
  • Some pages incorporate a video player that does not provide controls for the playback of subtitles and audio description at the same level of interaction as the rest of the controls [requirement number 7.3 User controls for subtitles and audio description, of UNE-EN 301549:2022].
    • Criterion 9 – Requirements applicable to web pages: Does not apply.
  • There is non-textual content that lacks a textual alternative, or that has an alternative that is not adequate [requirement number 9.1.1.1 Non-textual content, of UNE-EN 301549:2022].
  • Some recorded videos do not have text-based or audio alternatives [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 Subtitles (recorded), of UNE-EN 301549:2022].
  • Some pre-recorded videos on the website do not have audio description or alternative media [requirement number 9.1.2.3 Audio description or alternative medium, of UNE-EN 301549:2022].
  • Some pre-recorded videos on the website do not have audio description or alternative media [requirement number 9.1.2.5 Audio description (recorded), of UNE-EN 301549:2022].
  • On some pages, the information, structure and relationships are not determined by software or do not have an 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 program [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 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 form elements in which the purpose of the entry is not identified [requirement number 9.1.3.5 Identify input purpose, of UNE-EN 301549:2022].
  • On some pages, color has been used as the only visual means to transmit 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 play 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 the text size and its possibility of personalization when zooming [requirement number 9.1.4.4 Text resizing, of UNE-EN 301549:2022].
  • There are pre-designed images based only on text [requirement number 9.1.4.5 Images of text, 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 reflow, 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 dismissed without moving the pointer or changing the mouse focus [requirement number 9.1.4.13 Hover or focus content, of UNE-EN 301549:2022].
  • There are pages where keyboard navigation is not optimal and errors appear [requirement number 9.2.1.1 Keyboard, of UNE-EN 301549:2022].
  • There are components that, when receiving focus, prevent it from being passed to another only with the tab or direction keys [requirement number 9.2.1.2 No keyboard trap, 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 some time limit established that cannot be stopped, adjusted or extended [requirement number 9.2.2.1 Adjustable time, of UNE-EN 301549:2022].
  • There may be some automatically moving information that does not have controls to pause, control or hide [requirement number 9.2.2.2 Pause, stop and hide, of UNE-EN 301549:2022].
  • There may be elements that flash more than three times in a second or above the general threshold [requirement number 9.2.3.1 Threshold of three flashes or less, of UNE-EN 301549:2022].
  • On some pages there is no mechanism to skip blocks of content that are repeated on several pages [requirement number 9.2.4.1 Bypass blocks, of UNE-EN 301549:2022].
  • Inadequate description of some of the titles of the web pages [requirement number 9.2.4.2 Page titled, of UNE-EN 301549:2022].
  • In some documents, sequential navigation using the keyboard may not have a consistent order [requirement number 9.2.4.3 Focus order, of UNE-EN 301549:2022].
  • The purpose of the links, headers or labels of the portal may not always be descriptive or consistent enough for all users [requirement number 9.2.4.4 Link purpose (in context), of UNE-EN 301549:2022].
  • Links to related content pages or alternative forms of navigation are not always offered [requirement number 9.2.4.5 Multiple ways, of UNE-EN 301549:2022].
  • There are headers with repeated and/or poorly descriptive text [requirement number 9.2.4.6 Headers and labels, of UNE-EN 301549:2022].
  • The location of the focus is not always visible when navigating with the keyboard [requirement number 9.2.4.7 Focus visible, of UNE-EN 301549:2022].
  • There are elements that use multi-point or route-based that cannot be operated with only one pointer or without a route-based gesture [requirement number 9.2.5.1 Pointer gestures, of UNE-EN 301549:2022].
  • There are pages where an event cannot be canceled when the mouse is clicked [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 Label in name, of UNE-EN 301549:2022].
  • There is functionality only operable through movement [requirement number 9.2.5.4 Activation by movement, of UNE-EN 301549:2022].
  • On 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 specific editing and language identification failures in some part of the web page [requirement number 9.3.1.2 Language of parts, of UNE-EN 301549:2022].
  • There are components that, when receiving focus, initiate a change of context [requirement number 9.3.2.1 On focus, of UNE-EN 301549:2022].
  • The user’s interaction with a control causes page changes without prior warning [requirement number 9.3.2.2 On input, of UNE-EN 301549:2022].
  • There may be pages with inconsistent navigation, due to different links with 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 shown with different visual styles [requirement number 9.3.2.4 Consistent identification, of UNE-EN 301549:2022].
  • There are poorly descriptive error messages, 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 Error identification, of UNE-EN 301549:2022].
  • There are forms with mandatory fields where the user is not informed of this, as well as fields where there is no textual example of the field format [requirement number 9.3.3.2 Labels or instructions, of UNE-EN 301549:2022].
  • There could be some input error in some field/form that the user was not notified of the suggestion to solve it [requirement number 9.3.3.3 Error suggestion, of UNE-EN 301549:2022].
  • In the data entry does not detect errors or 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 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, role, value, of UNE-EN 301549:2022].
  • On some pages, status messages may not be programmatically determined 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 WCAG guidelines conformance requirements, of UNE-EN 301549:2022].
    • Criterion 10 – Requirements applicable to non-web documents: Does not apply.
  • There may be documents with images that do not have an adequate textual alternative [requirement number 10.1.1.1 Non-textual content, of UNE-EN 301549:2022].
  • There may be no equivalent alternative for audio-only or recorded video-only 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 Subtitles (recorded), of UNE-EN 301549:2022].
  • There may not be an alternative for time-based media or an audio description for recorded video content in synchronized multimedia [requirement number 10.1.2.3 Audio description or alternative medium, of UNE-EN 301549:2022].
  • An 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 documents, the information, structure and relationships are not determined by software or do not have an 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 program [requirement number 10.1.3.2 Meaningful sequence, of UNE-EN 301549:2022].
  • There may be documents which there is no other accessible alternative with which to operate and understand the content [requirement number 10.1.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 does not have the purpose identified [requirement number 10.1.3.5 Identify input purpose, of UNE-EN 301549:2022].
  • In some documents, color has been used as the only visual means to transmit information, indicate an action, provoke 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 play 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 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, images of text may have been used instead of text to convey information [requirement number 10.1.4.5 Images of text, 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 Text reflow, 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, of 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 does not receive keyboard focus with which to perform any action [requirement number 10.1.4.13 Hover or focus content, of UNE-EN 301549:2022].
  • There are documents in which it is not possible to operate fully via the keyboard [requirement number 10.2.1.1 Keyboard, of UNE-EN 301549:2022].
  • In some documents, the headings have not been defined and it is not possible to navigate by 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 documents, there is a time limit that cannot be stopped, adjusted, or extended [requirement number 10.2.2.1 Adjustable time, of UNE-EN 301549:2022].
  • Some documents may contain automatically moving information that does not have controls to pause, control, or hide it [requirement number 10.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 titled, of UNE-EN 301549:2022].
  • In some documents, the headings have not been defined and it is not possible to navigate by keyboard [requirement number 10.2.4.3 Focus order, of UNE-EN 301549:2022].
  • Some documents may contain links that may not have the specific purpose defined textually [requirement number 10.2.4.4 Link purpose (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 the keyboard through some documents [requirement number 10.2.4.7 Visible focus, of UNE-EN 301549:2022].
  • In some documents, there may be elements that use multipoint or path-based elements that cannot be operated with only one 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 canceled by clicking the mouse [requirement number 10.2.5.2 Pointer cancellation, of UNE-EN 301549:2022].
  • There are documents that have some labels that accompany the controls do not have the same name [requirement number 10.2.5.3 Label in name, of UNE-EN 301549:2022].
  • There are documents whose functionality is only operable through movement [requirement number 10.2.5.4 Motion actuation, 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 content or phrases within some documents whose language cannot be determined programmatically [requirement number 10.3.2.1 Language of parts, of UNE-EN 301549:2022].
  • There may be components in some documents that, when focused, initiate a change of context [requirement number 10.3.2.1 On focus, of UNE-EN 301549:2022].
  • User interaction with some control causes page changes without prior warning [requirement number 10.3.2.2 On input, 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 Error identification, of UNE-EN 301549:2022].
  • In some forms in some documents, there could be an automatic context change without warning the user [requirement number 10.3.3.2 Labels or instructions, of UNE-EN 301549:2022].
  • In some documents, there could be an input error in some field/form that does not notify the user of the suggestion to solve it [requirement number 10.3.3.3 Error suggestion, of UNE-EN 301549:2022].
  • In some documents, there may be a form for data collection or that legally or financially compromise that are not reversible, reviewable, or have confirmation before sending them [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 Parsing, of UNE-EN 301549:2022].
  • In some documents, 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, role, value, of UNE-EN 301549:2022].
  • In some documents, status messages might not be programmatically determined 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 user’s visual preferences of the browser are not respected on the page [requirement number 11.7 User preferences, of UNE-EN 301549:2022].
  • The information necessary for accessibility may not be compatible with the format used for the output of the authoring tool [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 way [requirement number 11.8.2 Creating accessible content, of UNE-EN 301549:2022].
  • There is no mechanism for preserving accessibility information during transformations [requirement number 11.8.3 Preserving accessibility information during transformations, of UNE-EN 301549:2022].
  • There may not be an accessibility checker repair mechanism [requirement number 11.8.4 Repair service, of UNE-EN 301549:2022].
  • There may not be a template available that supports the creation of content that complies with the requirements of chapters 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 the accessibility features available [requirement number 12.1.1 Accessibility and compatibility features, of UNE-EN 301549:2022].
  • The product documentation may not be completely in accessible formats [requirement number 12.1.2 Accessible documentation, of UNE-EN 301549:2022].
  • The support services do not provide all the information on the 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 cannot always be adapted 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 office automation files in PDF and other formats published before September 20, 2018 that do not fully comply with all accessibility requirements. Although most of them have been made to comply.

  • 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 prerecorded files published before 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 the systems, not all generated or self-generated content may comply with all accessibility regulations.

Preparation of this accessibility statement

This statement was prepared on 2025-12-22

The method used to prepare the declaration was a self-assessment carried out by the company itself.

Last review of the statement: 2025-12-22

Observations and contact information

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

  • Report any possible breach by this website.

  • Transmit other difficulties of access to the content.

  • Formulate any other query or suggestion for improvement related to the accessibility of the website.

Through the following channels:

  • Email: info@balconesdebentomiz.es

  • Phone: 665882824

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 regarding:

    • Content that is excluded from the scope of application of RD 1112/2018 as established by article 3, section 4.

    • Content that is exempt from compliance with accessibility requirements due to imposing a disproportionate burden.

In the Request for accessible information, the facts, reasons and request that allow to verify that it is a reasonable and legitimate request must be specified, with all clarity.

The communications will be received and processed by the management of the company, as the unit responsible for the contents of this website.

Optional content

The currently visible version of this website is from 2025-12-22 and on that date the review of the level of accessibility in force at that time was made.

From that date, partial daily reviews of new or modified web content are carried out, both of the templates and of the published final 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.

  • The links offer details of the function or destination of the hyperlink.

  • Use of W3C standards: XHTML 1.0, CSS 3.0, WAI AA.

Compatibility

The website:

  • has been designed adapting to the standards and regulations in force in relation to accessibility, complying with the priority 2 (AA) verification points defined in the Web Content Accessibility Guidelines (WCAG 2.1) specification

  • is optimized for the latest versions of Chrome, Edge, Firefox, Safari and Opera

  • is designed for correct viewing in any resolution and desktop, tablet or mobile device (responsive design)

  • has been made using HTML5 as a markup language and CSS 3 style sheets for its design.

In addition, continuous work is carried out on auditing and reviewing content to facilitate its interpretation and improve navigation through the web portal.

Stay up to date with our news

Sign up for our newsletter

Rural apartments

Celebration hall

Events

Support

Quality seals

Address

Balcones de Bentomiz
Calle Descansadero, 8, 29753 Arenas, Málaga
665882824

info@balconesdebentomiz.es

Follow us

logo_faldon_tr-2048x136-Blanco

Copyright © All rights reserved - Balcones de Bentomiz is a brand of BEN-ARENAS S.L.

Marriata Template Kit by Jegtheme