I have a case where a checkbox in front of a row in a table only appears when the row is hovered over or once it receives keyboard focus. This is likely an accessibility problem for voice control users (and also, of course, a general usability problem for all users as its discoverability hinges on user actions on the page), but does not seem to fall under any particular success criterion.
One likely candidate is 1.4.11 Non-text Contrast - when focused, element contrast is sufficient (4,8:1 when suffuciently magnified to avoid anti-aliasing effects), when not, its contrast is 1:1 (=non existent). Is this sophisty of the "how can I punish that" kind?
