RE: Notes from call

Thanks Jon.

I think there is consensus about page tab content needing reflow, and allowing that tabs may be off the screen in that size view port.

We also have consensus that carousel-like content might not be a control.  Your example of things like video posters from a streaming service are in that category.

With your example, does each poster need to fit 320 by 240 to pass?

Same question, what about each grid item of your web store example (i.e., multiple columns and rows)?

The non-wrapping code block is a good example illustrating that the exception is tricky.  HTML can word wrap easily enough, but many programing languages lack that flexibility.

Again, thanks for the examples and your feedback!


From: Jon Avila
Sent: Monday, March 18, 2024 6:01 PM
To: WCAG 2.x issues list <public-wcag2-issues@w3.org>
Subject: RE: Notes from call

Other situations related to reflow include that I think could pass:

  *   Page tabs (where some tabs may be off the screen in that size view port) but that individually fit within the view.
  *   Horizontal scrolling controls like carousels but that may not be carousels – things like video posters in a streaming service
  *   Grids that are not data tables – e.g. itunes store songs in multiple columns and rows where each item fits into the view without requiring scrolling an individual item

What is the consensus then on short blocks of horizontally scrolling text that are shorter than 256pixels – would these fail because you have to scroll horizontally even though you only have to scroll in one direction to read the text – but the page as a whole is vertically scrolling?  An example here might be a non-wrapping code block that is shorter than 256px.  Materially the horizontally scrolling content is difficult to track for some users.

Jonathan