The web accessibility specialist courses from Deque are really thorough but all the “must, should, may” language is super confusing. Just tell me the WCAG level instead 😬

@emmaDawsonDev this! not naming the WCAG SCs specifically makes it super hard for me to make notes and to apply the techniques they introduce in practical scenarios.

i still struggle to understand many of the ideas they share. for example, classifying a missing title attribute on an iframe as a bypass blocks failure? what?

@raacz106 I may have missed the one about iframes or not got that far yet but I was trying to go through the multimedia section and all the must, should, mays left me so confused. Then they showed it in table format and it broke my brain 😩

@emmaDawsonDev @raacz106 To be fair, the multimedia SCs are kind of a clusterfuck, even the most experienced find them hard to reconcile.

MUST is mandatory, MAY is optional, but SHOULD could be anything from “probably mandatory but it’s not quite clear” to “best practise depending on who you ask” to “ought to be mandatory but doesn’t reliably work” to “your guess is as good as mine”

@siblingpastry @raacz106 it’s not just the multimedia ones, that was just an example of the latest chapter I’ve read. The problem is they don’t even use must for A, should for AA and may for AAA and I just find the terminology feels problematic because if you’re going for AA then all A and AA are must, if you’re going for AAA then all are must. I don’t understand why they can’t just refer to wcag levels 🤷🏻‍♀️

@emmaDawsonDev @raacz106 Ah okay, yeah that’s bollocks, these terms relate to aspects of a particular SC, as in, whether you must do x to conform with that SC.

So yeah — all SCs are required within a specified conformance level, which in practise means — you have to satisfy all applicable A and AA criteria, but AAA is an optional ideal.

In common usage “must” and “have to” mean the same thing, but WCAG terms have contextual meanings, they’re being sloppy with language.

@emmaDawsonDev @raacz106 But to co-opt the similar language — A and AA are both “must” while AAA is “idealistic should” but “pragmatic may”.

The difference between A and AA is largely academic, there are no reasonable circumstances where you would only aim for Level A. If the course describes AA as discretionary in any sense, then it’s essentially wrong.

@siblingpastry James, I am saving this post of yours to quote someday because I just had a discussion with a friend about the SHOULD in a specification and how it can be misinterpreted or misused to create unusable components. It's a long story but your post is so perfect I love it :D
@SaraSoueidan @siblingpastry you both probably know this but they are defined in https://www.ietf.org/rfc/rfc2119.txt
@hdv I did not know that! This is excellent. And timely!! Thank you Hidde 🥳 @siblingpastry

@SaraSoueidan @hdv I wasn't being entirely serious there, I hope the semi-sarcasm was apparent ☺️

But yeah the conceit with SHOULD is that "the full implications must be understood" rests on subjective interpretation, potentially on incomplete knowledge, and changes over time in ways that amplify or ambiguate those things.

@siblingpastry Yes, of course it was! :D That's why I loved it. And yes, agreed. "potentially incomplete knowledge" is the problem.
@hdv @SaraSoueidan @siblingpastry oh, I wonder if this is what they are referring to in deque, which is where my initial frustration (and simblingpastry’s answer) came from
@emmaDawsonDev @hdv @SaraSoueidan If they're using these terms to describe whether or not a whole SC is applicable to content or conformance statements, then they're just plain wrong. More than that I couldn't say without seeing the material. But it's also possible that they're using the words in the regular english sense rather than the RFC sense. Do they use them capitalized?

@emmaDawsonDev @hdv @SaraSoueidan For example:

* You MUST provide text alternatives for non-text content unless exceptions apply (valid use)
* You SHOULD conform with all relevant AA criteria (invalid use, misappropriation of the term)

@siblingpastry @hdv @SaraSoueidan They are capitalized. Some examples from the audio description section I just worked through:
Prerecorded multimedia MUST include audio descriptions

Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description SHOULD be provided for all prerecorded multimedia content

Audio descriptions MAY be provided for live multimedia content

@emmaDawsonDev @hdv @SaraSoueidan Okay this explains the confusion.

They're using "MUST" to mean "This is a AA requirement" and "MAY" to mean "This is a AAA requirement". Not quite clear on what the "SHOULD" is intended to mean, since it seems to mean "This is a AAA requirement" with some nuance that isn't stated, but probably relates to how extended AD for precorded media is easier to implement than AD for live media.

So yeah, they're misappropriating the terms.