|
|
| code logs -> 2023 -> Tue, 22 Aug 2023 | < code.20230821.log - code.20230823.log > |
| --- Log opened Tue Aug 22 00:00:51 2023 |
| 00:39 | | himi [sjjf@Nightstar-1drtbs.anu.edu.au] has joined #code |
| 00:39 | | mode/#code [+o himi] by ChanServ |
| 02:38 | | Degi_ [Degi@Nightstar-kcu.3m1.188.77.IP] has joined #code |
| 02:39 | | Degi [Degi@Nightstar-06h.vfj.55.78.IP] has quit [Ping timeout: 121 seconds] |
| 02:39 | | Degi_ is now known as Degi |
| 02:59 | | panzerfaus [uid279771@Nightstar-l49s2t.irccloud.com] has quit [[NS] Quit: Connection closed for inactivity] |
| 05:36 | | Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Connection closed] |
| 06:11 | | himi [sjjf@Nightstar-1drtbs.anu.edu.au] has quit [Ping timeout: 121 seconds] |
| 06:51 | < abudhabi> | https://twitter.com/_nateraw/status/1693669927540928931/photo/1 |
| 08:09 | | himi [sjjf@Nightstar-o4k.pal.170.103.IP] has joined #code |
| 08:09 | | mode/#code [+o himi] by ChanServ |
| 09:31 | | Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code |
| 09:31 | | mode/#code [+qo Vornicus Vornicus] by ChanServ |
| 14:30 | < ErikMesoy> | Accessibility question: there's an interface at work with [back] [next] [cancel] buttons presented in that visual order, but the designer wants the [next] button to be the default and expects that to be the most common flow, so Tab-navigation highlights them in the order [next] [back] [cancel]. Does one of you happen to know if this is covered somewhere in a11y guidelines? |
| 14:32 | < ErikMesoy> | Workplace team has been staring at the decision and hoping there's An Official Rule about it somewhere, because nobody wants to be the one picking which 2 to satisfy out of 3 intuitive-but-contradictory constraints here. |
| 14:34 | <&ToxicFrog> | For additional confusion, in terms of visual layouts most GUIs put next/prev on the right/left edges respectively, so it would typically be something like [prev] --padding-- [cancel] [next] |
| 14:34 | <&ToxicFrog> | That said, it sounds like tab order is orthogonal here -- what you might actually want is for next to be focused by default and tab order to be unchanged. |
| 14:36 | < ErikMesoy> | No, we definitely want the default focus to be in the textfield where a reason for using the interface is required. ("what are you contacting us about?") Then tab from there to [Next] button. |
| 14:40 | <&ToxicFrog> | Aah. |
| 14:43 | | abudhabi [abudhabi@Nightstar-0c61rt.supernova.orange.pl] has quit [Ping timeout: 121 seconds] |
| 14:56 | | abudhabi [abudhabi@Nightstar-3oums5.supernova.orange.pl] has joined #code |
| 15:04 | <@macdjord> | ErikMesoy: [back] should definitely be to the left of [next], and tab-selection should follow physical layout. If that means you have to tab twice in the most common case, so be it. |
| 15:11 | < ErikMesoy> | macdjord: I would greatly appreciate if you can point to An Official Rule on this. What we've found in e.g. WCAG 2.4.3 does not appear to be determinative - it says "meaning and operability must be preserved", but elements may have a tab order different from character order or physical layout (case in point: Search bars) |
| 15:14 | <@macdjord> | ErikMesoy: No rule, sorry. This is just 'as a user, it would be Weird and Confusing to me if an interface did otherwise'. |
| 17:25 | | panzerfaus [uid279771@Nightstar-l49s2t.irccloud.com] has joined #code |
| 17:36 | | Emmy [Emmy@Nightstar-qo29c7.fixed.kpn.net] has joined #code |
| 17:41 | <~Vornicus> | The default action goes far right usually |
| 17:41 | <~Vornicus> | cancel usually goes somewhere to the left |
| 17:42 | <~Vornicus> | I'm poking through some interface guideline documents to see if I can find anything. |
| 18:06 | <~Vornicus> | vaaaague |
| 20:41 | | panzerfaus [uid279771@Nightstar-l49s2t.irccloud.com] has quit [[NS] Quit: Connection closed for inactivity] |
| 20:43 | | panzerfaus [uid279771@Nightstar-l49s2t.irccloud.com] has joined #code |
| 22:49 | | himi [sjjf@Nightstar-o4k.pal.170.103.IP] has quit [Ping timeout: 121 seconds] |
| --- Log closed Wed Aug 23 00:00:53 2023 |
|
| code logs -> 2023 -> Tue, 22 Aug 2023 | < code.20230821.log - code.20230823.log > |
|
|