- From: Dominic Mazzoni <dmazzoni@google.com>
- Date: Mon, 30 Sep 2013 23:48:21 -0700
- To: Rik Cabanier <cabanier@gmail.com>
- Cc: "whatwg@whatwg.org" <whatwg@whatwg.org>, Ian Hickson <ian@hixie.ch>
On Mon, Sep 30, 2013 at 5:42 PM, Rik Cabanier <cabanier@gmail.com> wrote: > Where does it say in the spec that if you have assistive technology > enabled, focus rings should not be drawn? > if as a web author I call drawCustomFocusRing and it returns false, I'm not supposed to draw anything according to the spec. That's what doesn't make sense to me. It would take an element in fallback content as an argument. That would >> allow assistive technology to be notified. >> > > As Ian pointed out, the accessibility software could do that. > scrollPathIntoView can't be used to notify accessibility software of the focused object location as-is because it doesn't have an element to fire on, and it doesn't know if the scrolling is because of focus or not. If we added a canvas fallback element as a parameter to scrollPathIntoView, I don't think we'd need drawCustomFocusRing.
Received on Tuesday, 1 October 2013 06:48:48 UTC