[WCAG2ICT] Meeting minutes from the 16 March meeting

Last Thurday’s meeting (on 16 March) was focused on discussions of developing notes for SCs 4.1.3 Status Messages and 2.5.2 Pointer Cancellation. The minutes were brief to provide for active discussions and working on notes offline in the issue. Unfortunately, the minutes didn’t get properly generated so here’s the gist of what was captured (with a few fill-ins from me). If anyone has anything to add or change from this, let me know.

attendees: maryjom, ThorstenKatzmann, PhilDay, ChrisLoiselle, BryanTrogdon, Devanshu, LauraBMiller
maryjom: Today is a working session to work on SCs, so no minutes are required, though we can take some brief notes. Meeting will use a queue. Reminder: add yourself using "q+".
Agenda 1:  4.1.3 Status Messages - discuss and develop guidance

·         https://github.com/w3c/wcag2ict/issues/35

·         Laura indicated she was taking notes for this SC on her own, since this is her assigned SC

·         10:15:41 AM LauraBMiller Original SC text: In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.

·         10:15:41 AM LauraBMiller Proposed content: Status messages should be presented to the user.

·         10:16-10:20 AM Discussion among participants regarding the following points:

o   The TF is unable to significantly change the SC as proposed above, though it would be a good idea for WCAG 3.

o   This SC would be applicable to non-web software and documents as written, but the clause “In content implemented using markup languages” greatly narrows the scope for non-web software. It limits to a very small number of software programs, as few are implemented using markup. Therefore, removal of this phrase would be needed (or a note to address that it would make sense to apply it more broadly to non-web software.

·         10:20-10:36 AM Discussion on the need for a note for software with closed functionality and that we need to avoid normative-sounding language like “requires”, “must”, etc.

o   Eventually settled on this note, to go into the section on SC problematic for closed functionality.

“Non web technology with closed functionality would need equivalent facilitation in terms of providing immediate focus or access to the status messages.”

·         10:38 AM How to propose the WCAG2ICT drafted content, open an issue using the template https://github.com/w3c/wcag2ict/issues/new/choose get started template direct link. An example Closed functionality specific issue is #44 https://github.com/w3c/wcag2ict/issues/44.

·

Agenda 2: 2.5.2 Pointer Cancellation - discuss and develop guidance
·        https://github.com/w3c/wcag2ict/issues/32
·        Mary Jo's breakdown of thinking about this sc: https://github.com/w3c/wcag2ict/issues/32#issuecomment-1461027721 We went over these.
·        PhilDay: Definition of single pointer https://www.w3.org/TR/WCAG22/#dfn-single-pointer - pointer input that operates with one point of contact with the screen, including single taps and clicks, double-taps and clicks, long presses, and path-based gestures. No discussion of mouse, trackball or other single pointer methods.  Only talked about in the Understanding doc.
·         Maryjom: I can open an issue about that. Perhaps a note could be added to the definition to indicate that, by default, mouse, trackballs, and other such pointing devices are also sources of a single pointer.
·         ChrisLoisell: Points out - A path-based gesture involves an interaction where not just the endpoints matter. If going through an intermediate point (usually near the start of the gesture) also affects its meaning then it is a path-based gesture. The user engages a pointer (starting point), carries out a movement that goes through at least one intermediate-point before disengaging the pointer (end point). The intermediate point defines the gesture as requiring a specific path, even if the complete path is not defined.
I think within a tablet, you could use the gesture, but you could also pair a Bluetooth device so that is why they include both? https://www.irccloud.com/pastebin/jx6Mgpyi/
OOPS, the command to make minutes should be “rrsagent, make minutes” instead of “rssagent, make minutes”.