Detailed legal provisions
The numbered provisions below set out the relevant policy and contractual framework. Details that depend on a particular transaction or processing operation should be confirmed directly with the company before relying on them.
1. Purpose and current status
ENERGOBUILD aims to make its website and research materials usable by people with different access needs. Full accessibility conformance has not been established. If a page or document is difficult to use, contact us using the instructions in section 15.
2. Operator and covered interfaces
The proposed operator is ENERGO BUILD LTD. / „ЕНЕРГО БИЛД“ ООД, EIK 207451381, subject to registry and responsible-provider verification. Scope should include www.energobuild.eu, EN/BG navigation, content pages, search, documents, enquiry forms, account or checkout if enabled, confirmation messages and third-party components integrated into the customer journey. A third-party redirect is not automatically outside the customer's accessibility experience. Verified support contact and exact routes remain pending.
3. EU and Bulgarian legal framework
Directive (EU) 2019/882 (European Accessibility Act) applies to specified products and services, including covered consumer e-commerce services, from 28 June 2025 subject to statutory transition rules. Bulgaria transposed it through the Accessibility Requirements for Products and Services Act, promulgated 11 April 2025. Applicability to ENERGOBUILD depends on actual activities, B2C service scope and exemptions. The public-sector Web Accessibility Directive is not automatically applicable to an ordinary private commercial website.
4. Microenterprise and burden exceptions
The EAA exempts microenterprises providing covered services from the Directive's service accessibility requirements. Whether ENERGOBUILD qualifies requires verified employee count, annual turnover or balance sheet and legal interpretation; it cannot be inferred from company size or website appearance. Fundamental-alteration or disproportionate-burden routes require a legally grounded documented assessment where available; they are not automatic exemptions. Voluntary inclusive design remains the target even if an exemption is established.
5. WCAG 2.2 AA design target
The engineering target is WCAG 2.2 Level AA across perceivable, operable, understandable and robust principles. It includes semantic headings, alternatives for meaningful images, captions where applicable, adequate contrast, keyboard access, visible focus, reflow, accessible authentication and usable touch targets. A target is not a statement of achieved conformance. Automated tools alone cannot establish WCAG compliance; representative manual and assistive-technology testing is required.
6. EN 301 549 version and harmonisation
EN 301 549 v4.1.1 was published in September 2026 and adopts WCAG 2.2 for relevant ICT accessibility requirements. Publication alone does not make it the currently cited harmonised legal reference: at the research date, AccessibleEU states that v3.2.1 remains the cited reference until the European Commission cites the new version in the Official Journal. Recheck the Official Journal at legal approval and distinguish technical target, harmonised presumption of conformity and other EAA obligations.
7. Navigation and keyboard interaction
All primary navigation, language switching, menus, accordions, modals, cookie controls and any future ordering process should work by keyboard without traps. Provide a visible focus indicator, logical tab order, skip link, landmarks and descriptive page titles. Interactive states must be programmatically conveyed rather than communicated solely by colour or animation. These behaviours require real desktop and mobile testing and are not currently verified.
8. Typography, contrast and responsive layout
Content should remain readable at user-controlled zoom and text spacing, support responsive reflow without losing functions, and meet applicable contrast criteria for text and interactive components. Avoid conveying warnings solely by colour. Provide accessible language metadata for EN and BG and appropriate reading order for translated sections. Decorative 3D visuals must not obscure text or block controls. Actual contrast measurements and zoom tests are pending.
9. Motion, parallax, 3D and reduced motion
Motion graphics, parallax, 3D scenes, autoplay and scroll-triggered effects must not prevent reading, navigation or task completion. Respect prefers-reduced-motion and provide a functionally equivalent low-motion experience. Avoid flashing content that violates seizure-safety criteria; offer pause/stop controls where applicable. Critical legal, pricing and checkout information must be available without animation or WebGL. Reduced-motion behaviour and mobile performance are not yet tested.
10. Forms, errors and contact pathways
Enquiry, newsletter, consent and future order forms must have persistent labels, clear instructions, accessible required-field indicators, field-level error messages and correction opportunities. Error identification must not rely only on red borders. Validation and success messages should be announced to assistive technology where appropriate. Do not ask users to disclose passwords, full card numbers or sensitive health details in accessibility feedback.
11. Accessible e-commerce and payment
If B2C checkout is activated, product information, total prices, tax, withdrawal choices, authentication, payment, error recovery, order confirmation and refunds must be perceivable, operable, understandable and robust. The EAA explicitly addresses identification, security and payment functionality in covered e-commerce services. Test both the merchant interface and any embedded or redirected PSP flow with keyboard, screen reader and mobile accessibility tools. EUR is the verified Wix site currency; USD acceptance and PSP approval remain unverified.
12. Accessible digital research and files
Research PDFs, tables, charts and downloadable files should provide meaningful document titles, logical heading structure, reading order, tagged PDF where applicable, table headers, text alternatives, selectable text and sufficient contrast. Data visualisations require textual explanation of key findings, not colour-only legends. File-level accessibility must be tested independently of the website. Do not promise every legacy report is accessible without inventory and remediation; provide a reasonable accessible alternative request path.
13. Third-party controls
The site uses Wix for hosting and cookie settings. Some controls rely on third-party services. If a control prevents you from accessing information, contact us so we can help you find an accessible alternative.
14. Accessibility barriers
We do not yet have a complete list of accessibility barriers. If you encounter a problem using the navigation, cookie settings or a document, please describe where it occurred and what you were trying to do. See section 15 for how to request an accessible alternative.
15. Feedback and accessible alternatives
If you experience a barrier, contact energobuild.contact@gmail.com and provide the page or document title, a description of the difficulty, preferred response format and optional assistive technology details. Do not submit passwords, full card data or unnecessary sensitive personal data. The operator should acknowledge the request, assess a reasonable accessible alternative and communicate an outcome without undue delay, subject to applicable law.
16. Accessibility assessment
An automated check alone cannot show whether a person can complete a task on the website. Keyboard navigation, text resizing, screen readers, mobile devices and downloadable documents each require separate assessment. A complete assessment has not yet been established.
17. Changes to this statement
Accessibility information may change when the website, its documents or its services change. For questions about the current accessibility of a specific page or document, use the feedback contact in section 15. This statement does not limit any right or remedy under applicable law.
18. Rights, privacy and legal documents
Requests for accessibility assistance must be handled consistently with GDPR minimisation, lawful purpose, restricted access and appropriate retention. Users retain all applicable consumer, disability, data-protection and contractual rights. Accessibility information supplements Legal Notice, Terms, Privacy, Cookies, Pricing, Refunds, Delivery, Licence and Disclaimer. No statement here waives mandatory rights or falsely guarantees that all content is accessible.