ACTION-2038: Run the webkit aria-modal test file to see what happens vis-a-vis the background.

Using the OS X accessibility explorer to examine the accessibility trees with the modal dialog showing versus not, I'm not seeing any difference regarding inclusion of the background content in the tree. And VoiceOver still lets me read it.

HOWEVER, I modified the Layout Test in question to dump the accessibility tree when the modal dialog was showing. Results:

AXRole: AXWebArea AXValue:
AXRole: AXGroup AXValue:
AXRole: AXHeading AXValue: 3
AXRole: AXGroup AXValue:
AXRole: AXButton AXValue:
AXRole: AXButton AXValue:

Then I did the same for when the modal dialog was dismissed. Results:

AXRole: AXWebArea AXValue:
AXRole: AXGroup AXValue:
AXRole: AXStaticText AXValue: Other page content with
AXRole: AXLink AXValue:
AXRole: AXStaticText AXValue: a dummy focusable element
AXRole: AXGroup AXValue:
AXRole: AXButton AXValue:
AXRole: AXGroup AXValue:

So at least as far as WebKit/Safari is concerned, when the modal dialog is showing, the background content is pruned from the tree; when the modal dialog is not showing, the background content is present in the tree.

So my original theory seems to be correct. What *might* (??) be the case is that some of the support will need to be implemented in the accessibility clients. But that would be a question for Apple.

Ugh. Whitespace got stripped out of my trees. :( Thanks Tracker. Trying again with periods.

==============

Using the OS X accessibility explorer to examine the accessibility trees with the modal dialog showing versus not, I'm not seeing any difference regarding inclusion of the background content in the tree. And VoiceOver still lets me read it.

HOWEVER, I modified the Layout Test in question to dump the accessibility tree when the modal dialog was showing. Results:

AXRole: AXWebArea AXValue:
....AXRole: AXGroup AXValue:
........AXRole: AXHeading AXValue: 3
............AXRole: AXGroup AXValue:
................AXRole: AXButton AXValue:
................AXRole: AXButton AXValue:

Then I did the same for when the modal dialog was dismissed. Results:

AXRole: AXWebArea AXValue:
....AXRole: AXGroup AXValue:
........AXRole: AXStaticText AXValue: Other page content with
........AXRole: AXLink AXValue:
............AXRole: AXStaticText AXValue: a dummy focusable element
....AXRole: AXGroup AXValue:
........AXRole: AXButton AXValue:
....AXRole: AXGroup AXValue:

So at least as far as WebKit/Safari is concerned, when the modal dialog is showing, the background content is pruned from the tree; when the modal dialog is not showing, the background content is present in the tree.

So my original theory seems to be correct. What *might* (??) be the case is that some of the support will need to be implemented in the accessibility clients. But that would be a question for Apple.