Critical Feature Request: Semantic HTML & Compliance with European Accessibility Act (EAA) 2025

8 Posts

Piet1234 posted this 3 weeks ago

Hello Nicepage Team,
I have been a loyal Nicepage user since the very beginning and love the platform. However, I am facing a critical issue regarding web accessibility.
With the European Accessibility Act (EAA) 2025 approaching, professional designers in the EU are legally required to deliver accessible websites. Currently, Nicepage generates generic structures ("div soup"), which hurts accessibility.
The Request: We urgently need a native option in the editor to manually assign semantic HTML tags (e.g., , , , , ) to blocks and containers.
Without this feature, Nicepage websites will not be compliant with upcoming laws, forcing many professionals to consider alternative tools. Please prioritize this to help us build future-proof websites.
Best regards, Peter

wcag

Vote to pay developers attention to this features or issue.

3 Replies

Order By: Standard | Newest

250 Posts

Gabriele Viola - Web designer, consulente e formatore posted this 3 weeks ago

Hi..

https://www.w3.org/WAI/test-evaluate/tools/list/ use this list, the 1st tool is great

But is not nicepage tool the problem, but how you made the website, contrast, tag, alt text etc scanner will show what's need to be needed to implement and how

Last edited 3 weeks ago by Gabriele Viola - Web designer, consulente e formatore

8 Posts

Piet1234 posted this 3 weeks ago

Hi there,
Thanks for the reply. I am fully aware that contrast and alt-texts are my responsibility as a designer.

However, my request is specifically about Semantic HTML Structure, which is controlled by Nicepage, not me.
The Problem: Nicepage renders almost everything as generic tags. The Requirement: Accessibility scanners (and the law) require semantic landmarks like header, nav, main, article, and footer.
Currently, there is no option in the Nicepage Editor to tell a Block: "Render this as a tag instead of a ."

Please pass this to your dev team. Without semantic tags, Nicepage websites cannot achieve full WCAG compliance, regardless of how good my contrast settings are.
Best regards,

Support Team posted this 3 weeks ago

Hello Peter,

Thank you for your detailed feedback and for raising an important topic. We appreciate your long-term support of Nicepage and your attention to accessibility requirements.

Nicepage provides tools that allow designers to apply certain accessibility best practices, such as using semantic heading elements and adding alternative text to images.
Other aspects of accessibility, including document structure, navigation logic, contrast choices, assistive technology behavior, and overall compliance with standards such as WCAG, depend on how a website is designed, configured, and maintained.

At this time, Nicepage does not provide full manual control over all semantic HTML elements or landmark roles at the block or container level. However, Nicepage uses semantic tags like header, nav, footer, and aside. We understand that increased control over semantic structure may be helpful for users working toward stricter accessibility requirements and regulatory frameworks, including the European Accessibility Act.

Your request has been shared with our development team for consideration as part of future product improvements.

Thank you again for your constructive input and for helping us improve Nicepage.

...................................................
Sincerely,
George.
Nicepage Support Team

Please subscribe to our YouTube channel: http://youtube.com/nicepage?sub_confirmation=1
Follow us on Facebook: http://facebook.com/nicepageapp

Last edited 3 weeks ago by Support Team