This Wiki page is edited by participants of the HTML Accessibility Task Force. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Task Force participants, WAI, or W3C. It may also have some very useful information.

Summary of 2013-12-16 Meeting

From HTML accessibility task force Wiki
Jump to: navigation, search

Agenda

  • Should work on drawCustomFocusRing go to L2?
  • Walk through existing Canvas 2D Accessibility bugs
  • Should scrollPathIntoView refer to fallback elements rather than "notional children" having a defined location?

Summary

The Canvas Sub-Group discussed the results of the TF CfC on whether or not to move drawCustomFocusRing (dCFR) to Canvas L2. Paul Cotton asked the Canvas Sub-Group to come to a determination on what it wanted to do in regards to dCFR and they decided it would be best moved to L2 but that they would not push all dCFR related bugs wholesale to the L2 component but continue making progress on them whenever they applied to L1 and to mirror that work in L2.

The Canvas Sub-Group came to a resolution on Bug 23978 (Informing the user shouldn't be optional) to clarify the reason for informing the Accessibility API (AAPI) of the location of the elements on the canvas and to make it required rather than optional.

While we moved Bug 23979 to L2 we discussed it extensively and made progress drafting text to differentiate and better explain the purpose for dCFR when compared to drawSystemFocusRing (dSFR), including a possible name change. This discussion created an action-224 to open a new bug on dSFR to clarify when and how location information should be presented to and updated in the AAPI

We continued a discussion that originated on the list regarding more accurate wording in the scrollPathIntoView() method and resolved to pick it up at our next meeting which is Monday January 6th