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
My initial reaction is that explaining why it's not required in policies is beyond the scope of this resource. This resource is to tell people what they need to do and give them guidance on how to do it.
I think we would not want to explain why it is not required in policies anyway -- we generally stay away from such commenting in resources such as this. At most, we might try to explain why it's at AAA in WCAG. But even that I think is "a can of worms" and not in scope for this resource.
+1 to not going that far. I think it is important to keep outreach and standards separate, the audience, ton, and approach is different.
Moreover, the need of sign language (and the fact that some deaf people do not understand sign language) are well covered in the introduction.
Sign language is the native language of many people who are Deaf. Some do not read or understand written language well — especially at the speed of most captions.
From Sylvie e-mail:
In Sign languages page:
Shouldn't it be explained why it is not required. Often, deaf people are not satisfied that sign language is not available.
The text was updated successfully, but these errors were encountered: