Add a rule to check if a page has a sign language widget

[mindrockets]

This rule is implemented currently for the Mind Rockets Sign Language Widget, but it could also be extended in the future for other automated Sign Language widgets.

In addition, it checks if there are any tags in the page which detects the page has anything related to deaf or sign language.

[tombrunet]

41.2.1 is not part of any of the indicated standards. This rule also seems to be specific to your product. Can you provide more information regarding a supported standard to support this?

[mindrockets]

Hello

Regarding to number 41.2.1 as an error code it is not mentioned anywhere, we can change the number if it is the problem, however regarding the Sign language inclusions

Sign Language is mentioned in AAA, in the below sections, however, it looks like it's only mentioned for video/audio media and not for text in the website. Most probably because the text to sign technology is still very new and is not widely known.

Standard requirements AAA (1.2.6) https://www.w3.org/TR/WCAG21/#sign-language-prerecorded

[image: image.png]

And in: https://www.w3.org/WAI/WCAG21/Understanding/sign-language-prerecorded#techniques

But it is clearly stated in the benefits that peaple who speak sign language find it very difficult to read written text

While at the time of writing WCAG21, sign language web readers was not commonly known and it was very difficult to record a video for each paragraph and below you can see it in the benefits.

The following benefits are stated, those benefits extend to the written content not only prerecorded audio and video as the same case exists for Deaf individuals.

" Benefits

• People whose human language is a sign language sometimes have limited reading ability. These individuals may not be able to read and comprehend the captions and thus require a sign language interpretation to gain access to the synchronized media content.

"

Regards,

On Mon, Oct 10, 2022, 7:04 PM Tom Brunet @.***> wrote:

41.2.1 is not part of any of the indicated standards. This rule also seems to be specific to your product. Can you provide more information regarding a supported standard to support this?

— Reply to this email directly, view it on GitHub https://github.com/IBMa/equal-access/pull/1105#issuecomment-1273453320, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANTFQUJ4W6UK4NGPPDHPOZLWCQWAHANCNFSM6AAAAAARAKUBBI . You are receiving this because you authored the thread.Message ID: @.***>

[tombrunet]

These tools focus on checking compliance with global policies and standards. At the moment, that is defined by WCAG 2.0, WCAG 2.1, and WAI-ARIA. You'll need to work through the standards organizations to better define the requirement.

[mindrockets]

Dear Tom,

Thanks for the reference, we went back and studied WCAG 2.1 and it seems we have missed section 3.1.5 in our earlier study which states that providing Sign Language is a sufficient technique to address section 3.1.5 Reading Level - AAA.

Below are the references: How to Meet WCAG (Quickref Reference) (w3.org) https://www.w3.org/WAI/WCAG21/quickref/?currentsidebar=%23col_overview&showtechniques=124%2C125%2C133%2C144%2C145%2C146%2C148%2C149%2C1411%2C245%2C246%2C248%2C311%2C315#reading-level Reading level AAA, And after Reviewing WCAG 2.1 Sign Language is stated under sufficient techniques, with details in

G160: Providing sign language versions of information, ideas, and processes that must be understood in order to use the content (w3.org) https://www.w3.org/WAI/WCAG21/Techniques/general/G160.html

Highlights from G160:

"Providing sign language versions of information, ideas, and processes that must be understood in order to use the content" ..... "Description For some people who are deaf or have certain cognitive disabilities, sign language may be their first language. A sign language version of the page may be easier for them to understand than a written language version. The objective of this technique is to provide sign language versions of content that help signing users understand difficult text that describes concepts or processes. The sign language content is provided in addition to the text.

Since this is supplemental content (and not sign language for speech in content) it should be viewed as separate from the content and would not necessarily be synchronized. Although there may be occasions when that would be useful, it is not required.

To make the sign language version available with the rest of the Web page contents, the video may be embedded in the Web page directly or the Web page may include a link that brings up a video player in a separate window. The sign language version could also be provided via a link to a separate Web page that displays the video.

Sign language is a three-dimensional, visual language that uses the hands, arms, shoulders, head, face, lips and tongue of the signer. For viewers to understand what is being signed, the video must record the sign language completely. Generally speaking, the signer should be as close to the camera as possible without risking cut-offs (such as hands moving outside the video)."

All the best,

Mahmoud

On Fri, Oct 14, 2022 at 6:12 AM Tom Brunet @.***> wrote:

These tools focus on checking compliance with global policies and standards. At the moment, that is defined by WCAG 2.0, WCAG 2.1, and WAI-ARIA. You'll need to work through the standards organizations to better define the requirement.

— Reply to this email directly, view it on GitHub https://github.com/IBMa/equal-access/pull/1105#issuecomment-1278415723, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANTFQUOGFH2MSJKJJ7SYDHTWDDFS3ANCNFSM6AAAAAARAKUBBI . You are receiving this because you authored the thread.Message ID: @.***>

--

Mahmoud Darawsheh Founder - Chief Executive Officer , Mind Rockets Inc

+962 79 7710 994 | @.***

www.mindrocketsinc.com

Grow Building 23, King Hussein Business Park Amman - Jordan