Describe your concern

The ARIA spec (https://www.w3.org/TR/wai-aria-1.2/#generic) describes a ‘generic’ element as a container with no semantic meaning on its own, and it also indicates generic elements are exposed in accessibility APIs to assistive technology. It is understandable if a generic element has a native attribute (such as tabindex=‘0’) or a global aria attribute (e.g., aria-live) so such state or property can be provided to an AT. However, for a generic element (e.g., div) without any native semantic or aria attribute (including one that can exclude the element from the accessibility tree), such as <div> a div </div>, if it maps to the accessibility API, what semantic meaning in the generic element is conveyed to an AT? If not mapped over, the spec should be clear on this.
During our test, we noticed that Chrome displays a ‘generic’ role in the accessibility tree only if the element is in focus (e.g., with tabindex=‘0’) or with an accessible name (title attribute).
Please clarify the mapping of the ‘generic’ role.

Link to the version of the specification or documentation you were looking at at.

https://w3c.github.io/aria/#generic

Link to documentation:

Does the issue exists in the editors draft (the editors draft is the most recent draft of the specification)?
Yes