You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that I raised w3c/ttml2#612 for the referenced point about TTML2 doing this. I haven't yet checked if TTML2 does it, but I think that every deprecated feature is described as such in text as well as in colour.
See w3c/ttml2#612 (comment) regarding TTML2 - @skynavga has determined that there are no instances where colour alone is used to indicate deprecation in TTML2.
The Working Group just discussed APA comment: Meet WCAG SC 1.4.1 requirement imsc#317, and agreed to the following resolutions:
RESOLUTION: WG agrees with the comment, and notes that the TTWG does not use colour alone to signal deprecation in any specification.
The full IRC log of that discussion
<nigel> Topic: APA comment: Meet WCAG SC 1.4.1 requirement imsc#317
<nigel> github: https://github.com//issues/317
<nigel> Pierre: This is not an issue because we do not use colour to signal deprecation in IMSC 1.1.
<nigel> Nigel: In fact we do not use colour alone to signal deprecation in any of our specifications.
<nigel> RESOLUTION: WG agrees with the comment, and notes that the TTWG does not use colour alone to signal deprecation in any specification.
From https://lists.w3.org/Archives/Public/public-tt/2018Jan/0270.html
Section 2 Documentation Conventions (applies also to Timed Text Markup Language 2 (TTML2) https://www.w3.org/TR/ttml2/ section 2.3). For accessibility of the spec, information such as whether an element is deprecated or obsoleted should not be indicated by color (or background color) alone (cf. WCAG 2.0 SC 1.4.1 https://www.w3.org/WAI/WCAG20/quickref/#visual-audio-contrast-without-color ).
The text was updated successfully, but these errors were encountered: