On Fri, 10 Mar 2023 19:50:03 GMT, Alexander Zuev <kiz...@openjdk.org> wrote:
>> Abhishek Kumar has updated the pull request incrementally with one >> additional commit since the last revision: >> >> Whitespace error fix and unused image file removed > > My question would be - is it really necessary to bring the entire HTML set > from the demo to test the accessibility? Can we just create a small and > simple HTML document with some structure that should be interpreted as a > document with nested children? Additionally - i do not understand why do we > even need an interactive UI test with the robot and such. Why is it > necessary? Why simple creation of JEditorPane and assigning url to it does > not work? @azuev-java As suggested, I tried to create two simple html files for test. Modified the test case to load the url and get the accessible child count for both html files. The usage of robot as well as interactive UI is removed. Cross-checked with the JAccessWalket tool, the child count is same for the test and in JAccessWalker component tree. Extra delay added in test case to get the correct child count else the child count always returns 1. ------------- PR: https://git.openjdk.org/jdk/pull/12707
