Consider removing normative statement regarding "no accessible object created"

[joanmarie]

In Excluding Elements from the Accessibility Tree, it states:

User agents MUST NOT include any elements, or their descendant content, as an accessible object in the accessibility tree that are indicated as no accessible object created in the SVG Element Mapping Table.

For the most part this JustWorks(tm) in implementations. But if an author applies a role to one of the prohibited elements and that element is rendered, explicit handling might be needed in order to comply with the above normative statement. This is (at least) the case in Chrome. I have a pending implementation. However the reviewer (@aleventhal) stated:

I'm not yet convinced the current code is wrong.

If someone adds role="button" and display:block to a normally hidden tag, and it actually gets rendered, then I think it should be exposed as a button in case it receives focus.

It's also a pretty bizarre case, no?

IOW I don't see the real-world value of the additional lines of code.

And we decided to file an issue here and see if that is something validators should handle, and give user agents more flexibility regarding handling this author error.