- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Mon, 21 Oct 2019 13:21:14 +0000
- To: Sailesh Panchang <sailesh.panchang@deque.com>
- CC: "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Hi Sailesh, I think Jonathan's point was that there are some web sites/applications which do their own thing from a focus point of view. That means it is a problem that cannot be solved on the users-agent end, at least for those scenarios. Also, as Katie said, we have no mechanism to create a new user-agent guideline in WCAG 2.x. > There is no need to impose a fallback requirement for content authors. Unfortunately there is, as without a new HTML/JS property to identify focus, a simple user-agent fix would not be reliable. There is an author component to this, otherwise the user-stylesheets approach would be more reliable. Even then, it is not an easy thing to do, and this is something that should not (IMHO) require particular technology. Ideally the author requirement for this SC will reduce over time if developments like this [1] from Microsoft become more widespread, but even then there are still instances completely under author control. Cheers, -Alastair 1] https://blogs.windows.com/msedgedev/2019/10/15/form-controls-microsoft-edge-chromium/
Received on Monday, 21 October 2019 13:21:18 UTC