User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.79 Safari/537.36

Steps to reproduce:

Here's a codepen which shows the nesting of a document inside an application. The nested document has a tabindex of zero, so that you can move from interaction to browsing. This is exactly according to the spec.

https://codepen.io/brennanyoung/pen/jOEVRRv

Links to (and citations from) the relevant parts of the spec are given in that codepen.

Actual results:

I notice that the accessibility dev tools flags this with the warning "Focusable elements should have interactive semantics".

That's mostly true. But the document role is different. It's intended to be both focusable and non-interactive. That's the use case. It's the only focusable element which should behave like that. This is a bogus warning, and therefore a bug.

Expected results:

The spec for role=document says that it should contain (browsable, non-interactive) rich text content.

The use-case is when you are in forms/applications mode and you want to re-enter browse mode.

Example of role=document inside role=application

Hi brennan,

I'll assign this issue to the "Core: Disability Access AP" area and hopefully someone from their team will look over it.

Regards,
Virginia

The priority flag is not set for this bug.
:Jamie, could you have a look please?

For more information, please visit auto_nag documentation.