Aug 15
Empty h4 Element Causing Accessibility Issues - Bug Report & Fix
**Issue Description:**
UMSO automatically generates an empty h4 element that breaks the heading hierarchy and causes accessibility errors in Google PageSpeed Insights / Lighthouse tests.
**Error Details:**
Google PageSpeed Insights reports: "Heading elements are not in a sequentially-descending order" because an empty h4 element exists without preceding h2/h3 elements.
**Technical Details:**
- CSS Path: `div._d08e5ece > div._a7708051 > div._5f4ecbf2 > h4._1451106c`
- Generated HTML: `<h4 class="_1451106c um-text"></h4>`
- Element dimensions: 483x0px (empty/no content)
**Impact:**
- Reduces accessibility score from 97 to lower values
- Violates WCAG heading hierarchy guidelines
- Affects SEO and user experience
**Workaround Solution:**
Users can add this CSS to their header code:
/* Fix for empty h4 element */
h4._1451106c:empty {
display: none !important;
}
**Request:**
Please fix this bug in the page builder to prevent empty heading elements from being generated. This would help all UMSO users achieve better accessibility scores without needing manual CSS fixes.
Reviewing