Detail of BeSmartRoof's technological rooftop and solar panel icon.

ACCESSIBILITY STATEMENT

besmartroof.es

Compliance Status

Be Smart Roof (hereinafter also referred to as the Website) is partially compliant with Royal Decree 1112/2018, of September 7, due to the non-conformity of the aspects indicated below.

Inaccessible Content

The content listed below is inaccessible for the following reasons:

a. Non-compliance with RD 1112/2018: Not applicable. It meets 100% of web accessibility criteria.

    • Criterion 5 – General requirements: Not applicable.
  • Incompatible means may be required to activate some accessibility features [requirement number 5.2 Activation of accessibility features, from UNE-EN 301549:2022].
    • Criterion 6 – Bidirectional voice communication capability: Not applicable.
  • It may not be possible to guarantee a frequency range whose upper limit is at least 7000Hz [requirement number 6.1 Voice bandwidth, from UNE-EN 301549:2022].
  • It may not be possible to provide a bidirectional communication mode via RTT [requirement number 6.2.1.1 RTT communication, from UNE-EN 301549:2022].
  • It may not be possible to provide a bidirectional voice and text communication mode simultaneously [requirement number 6.2.1.2 Simultaneous voice and text, from UNE-EN 301549:2022].
  • It may not clearly differentiate between sent and received text in RTT communications [requirement number 6.2.2.1 Visually distinguishable on-screen presentation, from UNE-EN 301549:2022].
  • It may not be possible to determine the RTT sending and receiving direction by software [requirement number 6.2.2.2 Software-determinable sending and receiving direction, from UNE-EN 301549:2022].
  • It may not be possible to provide speaker identification for RTT [requirement number 6.2.2.3 Speaker identification, from UNE-EN 301549:2022].
  • There may not be a visual on-screen indicator of real-time audio activity [requirement number 6.2.2.4 Visual audio indicator with real-time text, from UNE-EN 301549:2022].
  • It may not be possible to guarantee compatibility with other systems with RTT functionalities [requirement number 6.2.3 Interoperability, from UNE-EN 301549:2022].
  • It may not be possible to guarantee that RTT input is transmitted to the network within 500ms [requirement number 6.2.4 RTT responsiveness, from UNE-EN 301549:2022].
  • An alternative to voice for assistance or interactive response tasks may not be provided [requirement number 6.4 Alternatives to voice-based services, from UNE-EN 301549:2022].
  • It may not be possible to guarantee a minimum QVGA resolution for video functionalities [requirement number 6.5.2 Resolution, from UNE-EN 301549:2022].
  • It may not be possible to guarantee a minimum video frame rate of 20 FPS during communications [requirement number 6.5.3 Frame rate, from UNE-EN 301549:2022].
  • The maximum time of 100ms between the presentation of voice and video to the user may not be exceeded [requirement number 6.5.4 Audio and video synchronization, from 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, from UNE-EN 301549:2022].
    • Criterion 7 – Video capability: Not applicable.
  • There may be a video player that does not have an operating mode that allows existing subtitles to be displayed [requirement number 7.1.1 Subtitle playback, from UNE-EN 301549:2022].
  • There may be a video player that does not have an operating mode that allows audio to be synchronized with subtitles [requirement number 7.1.2 Subtitle synchronization, from 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, from UNE-EN 301549:2022].
  • The user may not be able to adapt subtitle characteristics to their individual requirements [requirement number 7.1.4 Subtitle characteristics, from UNE-EN 301549:2022].
  • A mode of operation that facilitates spoken output of available subtitles may not always be provided [requirement number 7.1.5 Spoken subtitles, from 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, from 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, from 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, from UNE-EN 301549:2022].
  • Some pages include a video player that does not provide controls for subtitle and audio description playback at the same interaction level as other controls [requirement number 7.3 User controls for subtitles and audio description, from UNE-EN 301549:2022].
    • Criterion 9 – Requirements applicable to web pages: Not applicable.
  • There is non-textual content that lacks a text alternative, or has an inadequate alternative [requirement number 9.1.1.1 Non-text content, from UNE-EN 301549:2022].
  • Some recorded videos do not have text-based alternatives or audio alternatives [requirement number 9.1.2.1 Audio-only and video-only, from UNE-EN 301549:2022].
  • Some recorded videos may not contain subtitles [requirement number 9.1.2.2 Captions (Prerecorded), from UNE-EN 301549:2022].
  • Some prerecorded videos on the website do not have audio descriptions or alternative media [requirement number 9.1.2.3 Audio Description or Alternative Media, from UNE-EN 301549:2022].
  • Some prerecorded videos on the website do not have audio descriptions or alternative media [requirement number 9.1.2.5 Audio Description (Prerecorded), from UNE-EN 301549:2022].
  • On some pages, information, structure, and relationships are not software-determined or do not have a text alternative [requirement number 9.1.3.1 Info and Relationships, from UNE-EN 301549:2022].
  • Some pages do not have at least one correct reading sequence defined by the program [requirement number 9.1.3.2 Meaningful Sequence, from UNE-EN 301549:2022].
  • Identification of elements based solely on sensory characteristics such as shape, color, size, visual location, orientation, or sound [requirement number 9.1.3.3 Sensory Characteristics, from UNE-EN 301549:2022].
  • Content does not adapt when screen orientation changes [requirement number 9.1.3.4 Orientation, from UNE-EN 301549:2022].
  • There are form elements where the input purpose is not identified [requirement number 9.1.3.5 Identify Input Purpose, from UNE-EN 301549:2022].
  • On some pages, color has been used as the sole visual means to convey information, indicate an action, elicit a response, or distinguish a visual element [requirement number 9.1.4.1 Use of Color, from UNE-EN 301549:2022].
  • There are sound elements that play automatically, and there is no mechanism to pause or stop them [requirement number 9.1.4.2 Audio Control, from UNE-EN 301549:2022].
  • On some pages, the text contrast ratio might not be at least 4.5:1 [requirement number 9.1.4.3 Contrast (Minimum), from UNE-EN 301549:2022].
  • There are errors on some pages related to text size and its customization capability when zooming [requirement number 9.1.4.4 Resize Text, from UNE-EN 301549:2022].
  • There are text-based images [requirement number 9.1.4.5 Images of Text, from UNE-EN 301549:2022].
  • There are errors when customizing font size, zoom level, or text spacing [requirement number 9.1.4.10 Reflow, from UNE-EN 301549:2022].
  • Insufficient contrast in interface components or graphic objects [requirement number 9.1.4.11 Non-text Contrast, from UNE-EN 301549:2022].
  • There is text that does not display correctly when spaces and line heights are changed [requirement number 9.1.4.12 Text Spacing, from 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 Content on Hover or Focus, from UNE-EN 301549:2022].
  • There are pages where keyboard navigation is not optimal, and errors appear [requirement number 9.2.1.1 Keyboard, from UNE-EN 301549:2022].
  • There are components that, upon receiving focus, prevent it from being passed to another element using only the Tab key or arrow keys [requirement number 9.2.1.2 No Keyboard Trap, from UNE-EN 301549:2022].
  • There are keyboard shortcuts that do not work [requirement number 9.2.1.4 Character Key Shortcuts, from UNE-EN 301549:2022].
  • There is a time limit set that cannot be stopped, adjusted, or extended [requirement number 9.2.2.1 Timing Adjustable, from UNE-EN 301549:2022].
  • There may be automatically moving information that does not have controls to pause, control, or hide it [requirement number 9.2.2.2 Pause, Stop, Hide, from 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 Three Flashes or Below Threshold, from UNE-EN 301549:2022].
  • On some pages, there is no mechanism to skip blocks of content that are repeated across multiple pages [requirement number 9.2.4.1 Bypass Blocks, from UNE-EN 301549:2022].
  • Inadequate description of some web page titles [requirement number 9.2.4.2 Page Titled, from UNE-EN 301549:2022].
  • In some documents, sequential keyboard navigation might not have a consistent order [requirement number 9.2.4.3 Focus Order, from UNE-EN 301549:2022].
  • The purpose of the portal’s links, headings, or labels may not always be sufficiently descriptive or consistent for all users [requirement number 9.2.4.4 Link Purpose (In Context), from UNE-EN 301549:2022].
  • Links to related content pages or alternative navigation methods are not always offered [requirement number 9.2.4.5 Multiple Ways, from UNE-EN 301549:2022].
  • There are headings with repeated and/or uninformative text [requirement number 9.2.4.6 Headings and Labels, from UNE-EN 301549:2022].
  • The focus location is not always visible when navigating with the keyboard [requirement number 9.2.4.7 Focus Visible, from UNE-EN 301549:2022].
  • There are elements that use multipoint or path-based gestures that cannot be operated with only a single pointer or without a path-based gesture [requirement number 9.2.5.1 Pointer Gestures, from UNE-EN 301549:2022].
  • There are pages where an event cannot be canceled by pressing the mouse [requirement number 9.2.5.2 Pointer Cancellation, from UNE-EN 301549:2022].
  • There are interface components that do not have visible labels [requirement number 9.2.5.3 Label in Name, from UNE-EN 301549:2022].
  • There is functionality operable only by movement [requirement number 9.2.5.4 Motion Actuation, from UNE-EN 301549:2022].
  • On some pages, the default language used is not indicated [requirement number 9.3.1.1 Language of Page, from UNE-EN 301549:2022].
  • There might be occasional editing and language identification failures in some parts of the web page [requirement number 9.3.1.2 Language of Parts, from UNE-EN 301549:2022].
  • There are components that, upon receiving focus, initiate a change of context [requirement number 9.3.2.1 On Focus, from UNE-EN 301549:2022].
  • User interaction with some controls causes page changes without prior warning [requirement number 9.3.2.2 On Input, from 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, from UNE-EN 301549:2022].
  • Certain interactive elements are not presented consistently in all cases, as they are displayed with different visual styles [requirement number 9.3.2.4 Consistent Identification, from UNE-EN 301549:2022].
  • There are uninformative error messages, or error messages that are not grouped into a single message, as well as a lack of suggestions in forms for correctly filling in fields [requirement number 9.3.3.1 Error Identification, from UNE-EN 301549:2022].
  • There are forms with mandatory fields where the user is not informed of this, as well as fields lacking a text example of the field format [requirement number 9.3.3.2 Labels or Instructions, from UNE-EN 301549:2022].
  • There might be an input error in some field/form that the user is not notified of a suggestion to resolve [requirement number 9.3.3.3 Error Suggestion 333, from UNE-EN 301549:2022].
  • 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), from 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 Parsing, from 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 accessibility guidelines [requirement number 9.4.1.2 Name, Role, Value, from UNE-EN 301549:2022].
  • On some pages, status messages might not be programmatically determined through functions or properties [requirement number 9.4.1.3 Status Messages, from UNE-EN 301549:2022].
  • Some WCAG 2.1 requirements are not met [requirement number 9.6 WCAG Conformance Requirements, from 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 text alternative [requirement number 10.1.1.1 Non-text content, from 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, from UNE-EN 301549:2022].
  • Videos may lack subtitles and audio descriptions [requirement number 10.1.2.2 Captions (Prerecorded), from UNE-EN 301549:2022].
  • There may be no 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 Media, from UNE-EN 301549:2022].
  • An audio description may not be provided for all recorded video content within synchronized multimedia [requirement number 10.1.2.5 Audio Description (Prerecorded), from UNE-EN 301549:2022].
  • In some documents, information, structure, and relationships are not software-determined or do not have a text alternative [requirement number 10.1.3.1 Info and Relationships, from UNE-EN 301549:2022].
  • Some documents do not have at least one correct reading sequence defined by the program [requirement number 10.1.3.2 Meaningful Sequence, from UNE-EN 301549:2022].
  • There may be documents for which no other accessible alternative exists to operate and understand the content [requirement number 10.1.3.3 Sensory Characteristics, from UNE-EN 301549:2022].
  • There may be documents whose content does not adapt when the screen orientation changes [requirement number 10.1.3.4 Orientation, from UNE-EN 301549:2022].
  • In some forms, the input field that collects user information does not have its purpose identified [requirement number 10.1.3.5 Identify Input Purpose, from UNE-EN 301549:2022].
  • In some documents, color has been used as the sole 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, from UNE-EN 301549:2022].
  • There are audio elements in some documents that play automatically, and there is no mechanism to pause or stop them [requirement number 10.1.4.2 Audio Control, from UNE-EN 301549:2022].
  • In some documents, the text contrast ratio might not be at least 4.5:1 [requirement number 10.1.4.3 Contrast (Minimum), from 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, content may lose functionality or information when enlarged [requirement number 10.1.4.4 Resize Text, from 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 Images of Text, from UNE-EN 301549:2022].
  • In some documents, content may lose functionality or information when enlarged [requirement number 10.1.4.10 Reflow, from UNE-EN 301549:2022].
  • In some documents, the contrast of user interface components and graphic objects might not reach 3:1 with adjacent colors [requirement number 10.1.4.11 Non-text Contrast, 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, from UNE-EN 301549:2022].
  • The content of some documents does not receive keyboard focus, preventing any action from being performed [requirement number 10.1.4.13 Content on Hover or Focus, from UNE-EN 301549:2022].
  • There are documents that cannot be fully operated via the keyboard [requirement number 10.2.1.1 Keyboard, from UNE-EN 301549:2022].
  • In some documents, headings have not been defined, and keyboard navigation is not possible [requirement number 10.2.1.2 No Keyboard Trap, from UNE-EN 301549:2022].
  • In some documents, keyboard shortcuts do not work [requirement number 10.2.1.4 Character Key Shortcuts, from UNE-EN 301549:2022].
  • In some documents, a time limit is set that cannot be stopped, adjusted, or extended [requirement number 10.2.2.1 Timing Adjustable, from 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, Hide, from 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 Three Flashes or Below Threshold, from UNE-EN 301549:2022].
  • There may be documents that do not have a title [requirement number 10.2.4.2 Page Titled, from UNE-EN 301549:2022].
  • In some documents, headings have not been defined, and keyboard navigation is not possible [requirement number 10.2.4.3 Focus Order, from UNE-EN 301549:2022].
  • Some documents may contain links whose specific purpose may not be textually defined [requirement number 10.2.4.4 Link Purpose (In Context), from UNE-EN 301549:2022].
  • In some documents, a heading or control name may not be sufficiently descriptive of its purpose [requirement number 10.2.4.6 Headings and Labels, from UNE-EN 301549:2022].
  • The focus location is not always visible when navigating some documents with the keyboard [requirement number 10.2.4.7 Focus Visible, from UNE-EN 301549:2022].
  • In some documents, there may be elements that use multipoint or path-based gestures that cannot be operated with only a single pointer or without a path-based gesture [requirement number 10.2.5.1 Pointer Gestures, from UNE-EN 301549:2022].
  • There are documents where an event cannot be canceled by pressing the mouse [requirement number 10.2.5.2 Pointer Cancellation, from UNE-EN 301549:2022].
  • There are documents where some labels accompanying controls do not have the same name [requirement number 10.2.5.3 Label in Name, from UNE-EN 301549:2022].
  • There are documents whose functionality is operable only by movement [requirement number 10.2.5.4 Motion Actuation, from UNE-EN 301549:2022].
  • There may be documents in which the main language is not identified [requirement number 10.3.1.1 Language of Page, from UNE-EN 301549:2022].
  • There may be content or phrases within some documents whose language cannot be programmatically determined [requirement number 10.3.2.1 Language of Parts, from UNE-EN 301549:2022].
  • There may be components in some documents that, upon receiving focus, initiate a change of context [requirement number 10.3.2.1 On Focus, from UNE-EN 301549:2022].
  • User interaction with some controls causes page changes without prior warning [requirement number 10.3.2.2 On Input, from UNE-EN 301549:2022].
  • There are data input fields with automatic error detection capability that do not identify where or how the error occurs [requirement number 10.3.3.1 Error Identification, from UNE-EN 301549:2022].
  • In some forms within some documents, an automatic context change might occur without warning the user [requirement number 10.3.3.2 Labels or Instructions, from UNE-EN 301549:2022].
  • In some documents, there might be an input error in some field/form that the user is not notified of a suggestion to resolve [requirement number 10.3.3.3 Error Suggestion, from UNE-EN 301549:2022].
  • In some documents, there may be forms for data collection or those that are legally or financially binding that are not reversible, reviewable, or require confirmation before submission [requirement number 10.3.3.4 Error Prevention (Legal, Financial, Data), from UNE-EN 301549:2022].
  • In some documents, there may be duplicate attributes and IDs [requirement number 10.4.1.1 Parsing, from 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 accessibility guidelines [requirement number 10.4.1.2 Name, Role, Value, from 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, from UNE-EN 301549:2022].
    • Criterion 11 – Requirements applicable to software: Not applicable.
  • The browser’s user visual preferences are not respected on the page [requirement number 11.7 User Preferences, from UNE-EN 301549:2022].
  • The information necessary for accessibility may not be compatible with the format used for the authoring tool’s output [requirement number 11.8.1 Content Management Technology, from UNE-EN 301549:2022].
  • There may not be a mechanism that allows content to be created in an accessible way [requirement number 11.8.2 Accessible Content Creation, from 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, from UNE-EN 301549:2022].
  • There may not be an accessibility checker repair mechanism [requirement number 11.8.4 Repair Service, from UNE-EN 301549:2022].
  • No template may be available that is compatible with creating content compliant with the requirements of chapters 9 (Web) or 10 (Non-web Documents) [requirement number 11.8.5 Templates, from UNE-EN 301549:2022].
    • Criterion 12 – Requirements applicable to documentation and support services: Not applicable.
  • Product documentation does not list or explain all available accessibility features [requirement number 12.1.1 Accessibility and Compatibility Features, from UNE-EN 301549:2022].
  • Product documentation may not be entirely in accessible formats [requirement number 12.1.2 Accessible Documentation, from UNE-EN 301549:2022].
  • Support services do not provide all information on the accessibility features included in the product documentation [requirement number 12.2.2 Information on Accessibility and Compatibility Features, from 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, from UNE-EN 301549:2022].
  • Documentation provided by support services may not be in an accessible format [requirement number 12.2.4 Accessible Documentation, from UNE-EN 301549:2022].

b. Disproportionate burden: Not applicable.

c. Content not within the scope of applicable legislation:

  • There may be office files in PDF and other formats published before September 20, 2018, that do not fully comply with all accessibility requirements. However, efforts have been made to ensure most of them do.
  • There may be third-party content not developed by 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 updates or system changes, not all generated or auto-generated content may comply with all accessibility regulations.

Preparation of this accessibility statement

This statement was prepared on 04/01/2026

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

Last review of the statement: 04/01/2026

Observations and contact details

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

  • Reporting any possible non-compliance by this website.
  • Reporting other difficulties in accessing content.
  • Making any other query or suggestion for improvement related to the website’s accessibility.

Through the following channels:

  • Email: info@besmartroof.es
  • Phone: 986 421 571

In accordance with 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 excluded from the scope of application of RD 1112/2018 as established by Article 3, paragraph 4.
    • Content exempt from compliance with accessibility requirements due to imposing a disproportionate burden.

In the Accessible Information Request, the facts, reasons, and request must be clearly specified to confirm 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 content of this website.

Optional content

The currently visible version of this website is from 04/01/2026, and on that date, the accessibility level then in force was reviewed.

From that date, daily partial reviews of new or modified web content are carried out, both for templates and for published final pages and documents, to ensure compliance with the accessibility requirements of Standard UNE-EN 301549:2022, 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 for images.
  • Links provide details of the hyperlink’s function or destination.
  • Use of W3C standards: XHTML 1.0, CSS 3.0, WAI AA.

Compatibility

The website:

  • 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 for correct viewing on any resolution and desktop, tablet, or mobile device (responsive design)
  • has been developed using HTML5 as the markup language and CSS 3 style sheets for its design.

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

Logotipo de BeSmartRoof optimizado para fondos oscuros y diseño tecnológico.
Powered by  GDPR Cookie Compliance
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.