We’re creating an inclusive digital world We help organisations be more inclusive and accessible. Together, we create enjoyable, efficient online and mobile experiences for everyone.
Lovely and clear. A few minor comments/additions: 6:37 visual location has been out-of-scoped from the (current) SC though. from the understanding document "If the help item is visually in a different location, but in the same serial order, that is not helpful from a user's point of view, but it would not fail this criterion." 13:17 duplicate ID issues can also arise with things like <label for="…">, or aria-labelledby/aria-describedby that end up pointing to the wrong element (the first one with the duplicate ID) ... but again, real-world issues manifest themselves already (and much better/clearer) in other SCs like 1.3.1 Info and Relationships or 4.1.2 Name, Role, Value. 25:04 annoyingly, the classic old google maps had that nice set of directional buttons (flashing way back to dev.opera.com/articles/keyboard-accessible-google-maps/) ... 38:44 I believe that that tiny log-in target already fails as is (without the "adding negative margin" bit later on), as the 24x24 circle intersects on the left with the right-hand side of the dropdown toggle's target area (and if the disabled control on the right was active, it'd also fail for intersection with the left-hand side of *that* target) 46:32 another case that fails are those cases where you as a user have set up/been given a PIN, but then the login form asks you to enter the 3rd, 5th, 10th character from that, as that doesn't allow you to easily copy/paste (assuming you stored the complete PIN somewhere like in a password manager), and you have to either spend lots of cognitive effort working out which char is the 3rd, which is the 5th, etc for you to then copy/paste that particular character, or retype it manually. 54:27 from the understanding document: "This Success Criterion does not add a requirement to store information between sessions. A process is defined on the basis of an activity and is not applicable when a user returns after closing a session or navigating away."
