Might be a duplicate? #1389

While closely related, the focus of #1389 primarily revolves around "implicit presentational roles" (such as <button><h1 aria-label=1></h1></button>), whereas the current request specifically targets "inherited presentational roles" (<table role="presentation">...</table>).

As outlined in the "Presentational Roles Conflict Resolution" chapter:

User agents MUST NOT expose elements having explicit or inherited presentational role in the accessibility tree, with these exceptions:

"implicit presentational roles" are beyond the scope (to determine with #1389 if it is expected or not), while "inherited presentational roles" fall within it.

@spectranaut, for simplicity's sake, since this issue is closely linked to #1389, I'm more than happy to add this bit into the other ticket and closing this one. Let me know if it makes sense or if we want to keep these as 2 separate things.

A few notes as a recap before proceeding with the PR:

• I've retested the behavior on Chrome, Safari, and Firefox, (just to be sure) and they all identify the td element in my first example as "Generic" or "No matching ARIA role."
• Since we agreed that if the presentational role is inherited, the content of the presentational ancestor element should continue to be presentational regardless of any global ARIA state or property, the applicability of the 3rd bullet point is limited to elements with an explicit presentational role.

Therefore, I will restrict the applicability of the 3rd bullet to elements with an explicit presentational role. I will also clearly specify what user agents must do when encountering a global state or property on an element with an inherited presentational role.