Before telling a frames to test, axe-core sends a ping, to check if the frame has a compatible version of axe-core in it. This is to avoid a scenario where it waits a whole minute for a frame to send back results, only to find that that didn't have axe-core in it at all.
In scenarios where we can guarantee this unnecessary waiting doesn't happen, such as browser extensions, we don't need to send this ping message. A simple solve for this could be to set allow pingWaitTime: 0, to just skip the ping step, and go right to the run command.
Before telling a frames to test, axe-core sends a ping, to check if the frame has a compatible version of axe-core in it. This is to avoid a scenario where it waits a whole minute for a frame to send back results, only to find that that didn't have axe-core in it at all.
In scenarios where we can guarantee this unnecessary waiting doesn't happen, such as browser extensions, we don't need to send this ping message. A simple solve for this could be to set allow
pingWaitTime: 0, to just skip the ping step, and go right to the run command.