RE: Agenda

Attendance (9):  Alastair Campbell, Bruce Bailey, Dan Bjorge, Francis Storr, Giacomo Petri, Gundula Niemann, Mike Gower, Scott O’Hara, Theo Hale.

At top of call, Mike highlighted some consolidation of some wiki<https://github.com/w3c/wcag/wiki/> pages and the addition of a WCAG 2 style guide<https://github.com/w3c/wcag/wiki/WCAG-2-style-guide> which builds off the WAI and W3C style guides.

  1.  Review ‘For discussion’ items on project board
     *   Update/correct 3.3.1 understanding by patrickhlauke · Pull Request #1803<https://github.com/w3c/wcag/pull/1803> – Please add your thumbs-up (or thumbs-down and comment) to the thread.
     *   2.5.3 - control with label but no accname by patrickhlauke · Pull Request #2057<https://github.com/w3c/wcag/pull/2057> – Please weigh in on conversation.  On the call, there was more support that F111 was closer tied to 2.5.3 than 4.1.2.

  2.  Discussion on potential tweaks to Reflow, was the bulk of our hour.
     *   Please see:  Reflow scratchpad - Google Docs<https://docs.google.com/document/d/1NhXS0Gfdsgl67pIhK0BYmayTq_v45CJMP0Ve36Uui3Q/> which memorializes the conversation.
     *   The main concern is clarifying what counts for “Except for parts of the content which require two-dimensional layout for usage or meaning.”
        *   The archetypes are data tables and columns like traditional newspaper print, but very often the patterns are not clear cut.
        *   A common UI paradigm is three columns:  Navigation, Canvas, Effects/Attributes/Status.  Menus and navigation controls are select-and-done, so they should use responsive design.  But often columns are programmatically tied to each other and cannot reflow without losing utility.  Comments in the margin of a word processing document is familiar example where the two-dimensional layout is essential.  A print-preview feature was another example that came up, as line wrapping would defeat the feature.
        *   It can be a judgement call to distinguish between functional requirement and preference and what “essential” means.
     *   Please see examples in Reflow - unclear requirement leads to wrong tests · Issue #3378<https://github.com/w3c/wcag/issues/3378#issuecomment-1766220849>
     *   Also see Initial draft update to reflow by alastc · Pull Request #3695<https://github.com/w3c/wcag/pull/3695>
     *   Scott shared a table that works for Reflow (codepen.io)<https://codepen.io/scottohara/pen/QWomqKp>
     *   Clarify toolbar exception in Understanding Reflow 1.4.10 · Issue #916<https://github.com/w3c/wcag/issues/916#issuecomment-540168775> is also related, but as discussed, sometimes the toolbar effects are tied to parts of the canvas.
     *   Clarification on definition of "scrolling in two dimensions" in 1.4.10 · Issue #2119<https://github.com/w3c/wcag/issues/2119#issuecomment-1947673049> also came up during the call.
     *   It can be difficult to distinguish between functional requirement and preference.
Next week, we are back to our routine schedule, queuing up Drafted for AG approval.
Two weeks from now we will revisit this Reflow conversation.