Is it possible to expose descendants of childrenArePresentational?

[Malvoz]

The Maps For HTML Community Group has a custom <map> component, but in testing I had found that no child elements of <map> (I believe anything that isn't <area>) are being exposed in the accessibility tree.

Is it possible to tell UAs to expose descendants of childrenArePresentational?

[stevefaulkner]

try adding a role to the map element, for example

<map role="group">
  <h1>test 2</h1>  
</map>

[Malvoz]

Thanks for the quick response @stevefaulkner, I should've described my previous attempts, which include adding role="region" (although specifying role isn't permitted for <map>), tabindex="0" (is focusable but node not exposed) amongst other things. I also tried aria-hidden="false", which I'm not sure is or should be capable of achieving what I want here, but that's not really implemented in browsers I think.

I've tried various things, here's screenshot of only a few attempts I tried just now based on your example suggestion:

[stevefaulkner]

@Malvoz thanks for the info, I see that it is causing issue in chrome, works fine in Firefox.

• theoretically the role should override the native element role, so should not be childrenarepresentational=true,
• aria-hidden=false will be of no help here for a number of reasons

Will look into it more on the morrow, it is late here now :-)

[zcorpan]

Is it specified somewhere that map should have childrenArePresentational?

[scottaohara]

This behavior is not specified in this spec. Rather, I filed a bug against chromium https://bugs.chromium.org/p/chromium/issues/detail?id=1208405 since Firefox and Safari are working as expected.

Leaving this open for tracking purposes, but the ball should be in Chromium's court to fix this.

[Malvoz]

Oops, I forgot to link the chromium bug I filed: https://bugs.chromium.org/p/chromium/issues/detail?id=1147035. Sorry!

In that bug I incorrectly refer to wanting to change the implicit ARIA role, I probably meant to say ARIA semantics, I corrected that statement in a later comment. I hope it's not too confusing, it seems on their response I got my point across.

However, because it seemingly isn't defined anywhere that map should have childrenArePresentational I guess it's also incorrect for me to imply in that bug that a role is required to opt-out of that behavior. I think I should comment on my bug and refer to yours as superseding mine. Does that sound right to you @scottaohara?

[scottaohara]

yes @Malvoz, please refer to mine. it's not really even that the children are treated as presentational (eg role=presentation) - if it was then the child content would still be exposed, but have no roles exposed. The content is rather being flat out ignored.

From what i saw in testing today, the accessibility panels in chrome were exposing the correct information - but something is still weird since, again, regardless of being exposed in the a11y panel, none of the content is actually accessible to the screen readers when using only chromium browsers

[Malvoz]

I filed a bug against chromium https://bugs.chromium.org/p/chromium/issues/detail?id=1208405

@scottaohara The bug you filed was marked as fixed, though I'm not seeing (hearing) any improvements using NVDA. Perhaps I've misunderstood the bug and the fix, perhaps it should now be considered an NVDA issue that the non-area elements aren't announced in your attached HTML file?

[scottaohara]

cc @aleventhal per above comment.

i haven't looked into it / didn't notice it was marked as fixed.