AEM page structure is Broken, How do you fix? | Community
Skip to main content
Level 2
December 2, 2020
Solved

AEM page structure is Broken, How do you fix?

  • December 2, 2020
  • 2 replies
  • 2076 views

The out-of-box page structure in AEM is broken and do not conform to HTML5 Standards making it very difficult to implement any decent accessible page structures, it's a `<div>` nightmare :), I'm wondering how you guys deal with this.

 

 

The new semantic elements introduced in HTML5 bring the ability to describe the structure of a web document in a standard way. They bring a big advantage for people having HTML5 browsers and needing the structure to help them understand the page, for instance people needing the help of some assistive technology. These new semantic elements are simple to use and, with very few burdens, can be made to work also in non-HTML5 browsers. Therefore they should be used without restrictions.

 

 

 

Great reads on the topic

https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Using_HTML_sections_and_outlines#Problems_solved_by_HTML5

 

https://web.dev/use-semantic-html/

 

We.retail screenshot

 

 

Thanks in Advance

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by mariia_lukianets

This can be fixed by implementing a custom page. You can inherit from the OOTB page (use sling:resourceSuperType property) and redefine the markup according to your needs.
This tutorial walks you through extending a core component, for Page the process similar since Page is also a component in AEM:
https://experienceleague.adobe.com/docs/experience-manager-learn/spa-react-tutorial/extend-component.html?lang=en#extend-component 


2 replies

Level 2
December 3, 2020

 


 
Updating Media

 

mariia_lukianetsAdobe EmployeeAccepted solution
Adobe Employee
December 3, 2020

This can be fixed by implementing a custom page. You can inherit from the OOTB page (use sling:resourceSuperType property) and redefine the markup according to your needs.
This tutorial walks you through extending a core component, for Page the process similar since Page is also a component in AEM:
https://experienceleague.adobe.com/docs/experience-manager-learn/spa-react-tutorial/extend-component.html?lang=en#extend-component 


Level 2
December 9, 2020
Hi, thanks for the response is there any plans to fix this in future releases?