Expected Result: The hit region associated with the control and id matches the new region and the bounds of the control matches, in the accessibility API for this control, the region location in terms of a best fit rectangle in screen coordinates.

Test file: The test file should set up a hit region for a fallback element using addHitRegion with an associated id and the corresponding fallback element represented by the control. Also at load time the hit region should be rendered in the DOM outside the canvas area for visible inspection. An HTML button should be visible so that, when pressed, makes the new association of id, and control, with the new non-null hit region and renders the id and associated region information for visible inspection in the DOM. An accessibility test tool should be used so that the tester can validate that the region associated with the control matches the screen location of the hit region as a best fit rectangle.