W3C

– DRAFT –
WCAG2ICT Sub-group on SC Problematic for Closed Functionality

31 May 2023

Attendees

Present
LauraBMiller, maryjom, Sam
Regrets
-
Chair
Mary Jo Mueller
Scribe
LauraBMiller

Meeting minutes

scribe, LauraBMiller

Review spreadsheet starting with 2.1.4 Character Key Shortcuts

Attendees: Sam Ogami, Maryjom

Maryjom: a keyboard interface is not AT (disagree with EN standard)

Requirement should apply as written.

Sam agrees.

2.2.1 Timing Adjustable

Yes applies. (Sam, Laura, MaryJo agree).

Security Reasons for time outs not being extended would be applicable

Topic 2.2.2 Pause Stop Hide

MaryJoM - this should apply as-is. Phil's concern is covered by the essential exception

Topic 2.3.1 Three Flashes or Below Threshold

Applies as-is

2.4.1 Bypass Blocks

Applies as is.

2.4.2 Page titled

Laura believes that this is dependent upon the page content.

Problematic for kiosks and other closed systems. We need to extend the note.

<maryjom> We need to extend the note because many closed functionality products focus each view of screen content to a single function - like asking a single question. Adding a page title for each would be distracting and take the user more time to take action and complete transactions.

<Sam> sorry. were having a car seat problem

2.4.3 Focus Order

Good as is.

Topic 2.4.4 Link Purpose (in context)

Applies as is.

Topic 2.4.5 Multiple Ways

<maryjom> The WCAG2ICT interpretation of this SC replaced "sets of Web pages" with "set of software programs" which is extremely rare - especially for Closed functionality software.

2.4.6 Headings and labels

Applies as is

2.4.7 Focus Visible NEXT WEEK.

Applies as is.

Minutes manually created (not a transcript), formatted by scribe.perl version 210 (Wed Jan 11 19:21:32 2023 UTC).

Diagnostics

Succeeded: s/in for/for/

Maybe present: Attendees

All speakers: Attendees, Maryjom

Active on IRC: LauraBMiller, maryjom, Sam