Re: [csswg-drafts] [css-nav-1] Reordered sequential navigation (#3377)

It seems like an overstatement to say that 2D has no inherent order, quite a lot of it does.  When you get a 2d thing to read, unless there is a real design problem you shouldn't be looking at it and thinking "these things have no relationship and I can read every bit in any order equally well.  Many of the reasons that we have many of the concepts that we do come stem from that observation.  As @patrickhlauke says, it isn't just 'focus navigation' that that applies to.

Focus is especially tricky though and I think this get especially interesting as we reshape interfaces and order isn't _critically_ important... Kind of like the difference between a list and an unordered list.   Imagine a gallery of images, which are links and have some brief text associated with them.  Each has different aspect ratios and sizes and the author is more concerned with balancing aesthetics than, for example, when they were posted.  Depending on the user's screen size, the best "fits" can change - perhaps on a nice big screen we get 15 'rows' and 3 'columns' with a few images 'spanning'... but as things scale down, something a further down moves 'up' in the order to better fit.   If that's the case, and you are _only_ using a reader it might be fine that those don't actually match actually - but, today, this would leave a strange gap where keyboard users experience something that clearly does not match the 'expected' order.  A tab press on the second image might 'jump' the user to what they perceive as the 25th image, and the next to the 5th, and so on.  

I feel like at a minimum, the 'order isn't critically important' case isn't actually that rare in responsive design and could be better addressed.


-- 
GitHub Notification of comment by bkardell
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3377#issuecomment-443786997 using your GitHub account

Received on Monday, 3 December 2018 17:05:38 UTC