- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Sat, 25 Feb 2023 12:02:00 +0000
- To: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
- Cc: "Bailey, Bruce" <Bailey@access-board.gov>
Hey list, a bit of a WCAG-adjacent question, but: while reviewing https://www.section508.gov/content/mapping-wcag-to-fpc/ for some internal documentation, I came across a few entries that seemed odd - I'm hoping that folks (thinking of Bruce Bailey / USAB here for instance) can elaborate/provide some further context. * 1.1.1 Non-text content: am I right in thinking that it's marked under "Without Hearing" and "Limited Hearing" when the content in question is audio (e.g. a sound cue that has no text alternative/equivalent) * 1.2.1 Audio-only and Video-only (Prerecorded): I'm assuming that for something that is "audio-only", that's when it falls under "Without Hearing" and "Limited Hearing", and when it's "video-only" it falls under "Without Vision" and "Limited Vision" * 1.3.3 Sensory characteristics: shouldn't this also fall under "Without Perception of Color" if the sensory characteristic being used/references is color? * 1.4.1 Use of colour: I assume this doesn't fall under "Without Vision" if the information conveyed through just colour is also conveyed programmatically (so that it's announced by a screen reader, for instance) * 3.1.1 Language of page: why is this marked under "Without Hearing" and "Limited Hearing"? How are these groups affected? * 3.1.2 Language of parts: why is this marked under "Without Hearing" and "Limited Hearing"? How are these groups affected? * 3.2.4 Consistent Identification: it's unclear to me why this has also been marked under "Limited Manipulation" * 3.3.1 Error identification: am I correct in assuming that "Without Perception of Colour" only applies if the reason why something fails this SC is because they're using colour alone to indicate an error? Otherwise, if errors are not indicated in general, would this not be something that fails for *all* groups? * 3.3.2 Labels of instructions: while I understand why this would affect people with "Limited Language, Cognitive, and Learning Abilities", it's unclear why "Limited Vision" has also been singled out as a group affected by this. * 3.3.3 Error suggestion: am I right in thinking that this has been marked under "Limited Manipulation" under the scenario where a site/app should offer an easy way for a user to select (e.g. from a list, or radio buttons) the correct value they intended to use - rather than in cases where the solution would be to provide error suggestion in text (leaving the user to still enter it/correct their entry manually)? * 3.3.4 Error prevention (legal, financial, data): wondering why this has been marked as affecting almost all groups, *but* with the notable omission of "Without Speech" and "Limited Reach and Strength". Is this just because there's an overall decision that *none* of the WCAG SCs relate to those two categories? If the intention is that a lack of error prevention affects everybody and is important enough to flag, then I would have thought this would affect *all* groups. Otherwise, I'd be interested to know if there's specific rationales for the groups that *were* marked as being affected by a failure of this criterion (and if there's any particular nuance of failure that would only relate to specific groups - e.g. I can't currently think of a scenario where a lack of error prevention may be problematic for a user "Without Hearing" and "Without Vision" but fine for a user with "Limited Reach and Strength") * 4.1.1 Parsing: am I right in thinking that this has been flagged under "Limited Manipulation" only for cases where incorrect/broken markup also results in problems relating to, say, keyboard operation/focus order? Further, I'd be interested to know what kinds of failures of this SC would affect people with "Limited Language, Cognitive, and Learning Abilities". * 4.1.2 Name, role, value: similarly, I'm wondering why this SC is also flagged under "Limited Manipulation" and "Limited Language, Cognitive, and Learning Abilities". Is the assumption that users from these categories also often use assistive technology, which will be affected by this? Apologies for the flood of questions, but I'm hoping to bring a bit more clarity here... P -- Patrick H. Lauke https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Saturday, 25 February 2023 12:02:26 UTC