Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

ADA Liferay WAVE error

Written By

Pooja Bhambani

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • When we run WAVE analysis on Liferay site and, even on vanilla bundle, one of the error is “Empty Button” under the element with the id of “hrefFM” is observed.
  • Steps to reproduce
    1. Install the WAVE tool for Chrome.
    2. Start up the bundle and login.
    3. Run the WAVE tool and observe that there are empty button errors.
    4. Keep Styles off.
    5. Click on details tab > error > cross sign > code. 
    This code is showing like this:
     
    <form action="#" class="hide" id="hrefFm" method="post" name="hrefFm" aria-hidden="true"><span></span>

    <input hidden="" type="submit">

    </form>

Environment

  • Liferay DXP 7.0
  • Liferay DXP 7.1
  • Liferay DXP 7.2
  • Liferay DXP 7.3

Resolution

  • The observed behavior is a known issue/bug.
  • If the hotfix is required for this issue, please create a support ticket requesting hotfix by attaching patch details.
  • Installing Fix Packs and Hotfixes on Liferay DXP will guide to install this hotfix in the respective environment.

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?