@bruce-usab Thanks for opening this. Assigning to @daniel-montalvo and myself. Daniel will have to do a change to the classes and document build script to allow us to have a "(Modified)" parenthetic available for use. Then I can add the class to those instances where we replaced the note, specifically to SC 4.1.2, and potentially also to the "accessibility supported" definition where we replaced all 5 notes with a single note (currently marked as "Added").

Thanks @bruce-usab @maryjom

I will be putting together a PR for this. IT still would require a little bit of editorial work to identify which notes we want to mark as "modified" and then add the corresponding class, we can decide as we see the PR in-place.

Hi @bruce-usab @maryjom

See this pr preview

I've added the logic to treat these "modiified" notes as such.

@bruce-usab let me know if that's what you want and then we'll merge the script updates and probably open another issue for the editorial work to determine which notes will be marked as "modified".

Thank you @daniel-montalvo , yes that is what I am looking for.

I think any notes where we (quite correctly) purged "must" should also get the (modified) tag. Those are the SC related to non-interference, 1.4.2 - Audio Control, 2.1.2 - No Keyboard Trap, 2.3.1 - Three Flashes or Below Threshold, and 2.2.2 - Pause, Stop, Hide.

A bit off topic, but related to #680 and #682 is that there are a few more non-normative notes which make use of the word "must":

• Note 2 of 4.1.1 Parsing
• Note 1 of accessibility supported in glossary
• Note 2 of web page in glossary

May want to use "Replaced" rather than "Modified" because we only use this in 2 places where we replaced the notes with a significantly rewritten one.

@daniel-montalvo Please check on whether we have a "replaced" tag to use.