RE: SC 1.4.10 Reflow - scrollbar by design a fail or not?

Hi Joppe,



thanks for the feedback!



I handn't noticed the keyboard accessibility problems yet. On the Technobility website the arrow keys do work when the focus is in one of the blocks of content. So I can get all blocks nicely into view. Yes, there is no focus on the scrollbar, but the arrow keys do work.



But, with the menu that may be a problem. Part of the linktext is unreadable using the TAB-key to navigate through the links. But if I look at it on a mobile device I can swipe the menu and I can see all the links. Would that then fail SC 1.4.10? Or would it fail a different SC and if so, which one.



Met vriendelijke groet,
Gerard Copinga




CARDAN Technobility

TalentSquare 13, 5038 LX Tilburg

Postbus 1340, 5004 BH Tilburg

Telefoon +31 (0)88 500 4070

Internet https://www.technobility.nl/







---- Op do, 24 jun 2021 12:58:16 +0200 Joppe Kroon <J.Kroon@topdesk.com> schreef ----



Hi,

 

If I try to access these blocks using a keyboard I find that the last item doesn’t actually scroll into view if the screen size happens to fit just half of the last block in it.

On the IKEA website the scrollbar is focusable, and it scrolls on arrow keys so it is solvable there. But the other two websites do not have any such provisions.

 

Scroll into view on focus is really buggy, also with CSS scroll-snap. I’m not sure if any SC specifically addresses this,  but I wouldn’t advise creating an interface that relies on this.

 

Cheers,

Joppe

 

 

From: mailto:gerard@cardan.com
 Sent: donderdag 24 juni 2021 09:17
 To: mailto:w3c-wai-ig@w3.org
 Subject: SC 1.4.10 Reflow - scrollbar by design a fail or not?

 

Hello,


 


we have some doubts about the following examples, whether they fail SC 1.4.10 Reflow or not. These are examples of using a scrollbar by design and not showing a scrollbar that's
 been placed there by a User Agent. We need some clarification because we do expert reviews for our customers and need to know whether these examples fail or not. There are some different opinions about this (internally), so hopefully some of you can clarify
 things for us.


 


If you look at the website https://www.ikea.com/nl/nl/ (Sorry, Dutch website) you see some blocks of content half-way
 with arrow buttons to scroll left and right and you will see a scrollbar below these blocks of content. Would this example fail 1.4.10 or not and why? On a screen with a width of 320 pixels you will have to scoll horizontally of view all the blocks, but the
 contents of each block can be read without scrolling.


A similar example but with more contents per block can be found on this website: https://technobility.nl/ (also Dutch,
 sorry). Look at the blocks of content below the heading "Onze diensten". It's a kind of slider but also with a scrollbar on smaller size viewports. Is this a fail or not and why (not)?


And what about this example: look at https://magazine.forumstandaardisatie.nl/ (also Dutch). There is
 a menu with links like "Portfolio", "Monitor Open standaarden", etc. On a smaller viewport, by design, you will see a scrolbar just for this menu. Is this a fail or not?


 


Is there a difference between a scrollbar set by a UserAgent and by design? Or is that not relevant?


 


The menu is one line of 'text'. So, to use the menu itself you only need te scroll in one direction (horizontally). Does that mean it will not fail 1.4.10?


 


What am I missing here in my understanding of this SC?


 


Hope someone can help...


 


Met vriendelijke groet,
 Gerard Copinga

 


 


CARDAN Technobility


TalentSquare 13, 5038 LX Tilburg


Postbus 1340, 5004 BH Tilburg


Telefoon +31 (0)88 500 4070


Internet https://www.technobility.nl/