updated tests testable statements/expected results

Hi Mark,

I updated the tests. I noticed that the text for testing the
bounds/location in the platform accessibility API was missing for the
drawFocusIfNeeded test cases. I update that information in the expected
result. I also added 2 tests drawFocusIfNeeded test that deals with
scrolling the focus into view and scrolling the window.

https://www.w3.org/wiki/HTML/Canvas_Task_Force/CR-Test

I could do similar scrolling exercises for the hit testing locations but
ran out of gas.

I would a step 14 in addHitRegion ()


   1.	Inform the user of new locations resulting from the path. The full
      location of the corresponding fallback controls are passed to the
      accessibility API, if supported. User agents may wait until the next
      time the event loop reaches its "update the rendering" step to inform
      the user.


"Inform the user", as used in this section, could mean calling a system
accessibility API, which would notify assistive technologies such as
magnification tools. To properly drive magnification based on a focus
change, a system accessibility API driving a screen magnifier needs the
bounds for the newly focused object. The methods above are intended to
enable this by allowing the user agent to report the bounding box of the
path used to render the focus outline as the bounds of the control element
passed as an argument.


Rich Schwerdtfeger