Legacy Knowledge Base
Published Jul. 2, 2025

Certain portlets have aria-autocomplete attributes

Written By

Alfonso Crisci

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

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

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

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

Issue

  • While inspecting the DOM for certain portlets (Page Comments, Blogs, etc ...) deployed on DXP pages, users may notice the below aria attributes:

    aria-autocomplete="list" aria-expanded="false" aria-owns="yui_patched_v3_18_1_1_1616595356184_5727"
    Even if the element will not be of autocomplete type.

Environment

  • Liferay DXP 7.0+

Resolution

  • The attributes are intended: this is because of the Autocomplete plugin, first added in 7.0. Here is a dev blog post about it: New feature for Liferay 7: Autocomplete lists in CKEditor.

  • This plugin is responsible for providing an autocomplete feature on screen names with the default configuration. The feature is hidden until mentioning a screen name starting with the @ character.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base