Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wording of example for WCAG SC 1.1.1 #551

Open
nigelmegitt opened this issue May 14, 2020 · 1 comment
Open

Wording of example for WCAG SC 1.1.1 #551

nigelmegitt opened this issue May 14, 2020 · 1 comment
Assignees
Milestone

Comments

@nigelmegitt
Copy link
Contributor

As I noted in #526 (comment) relating to the example in the section about meeting WCAG success criterion 1.1.1, I think the wording of this example could do with a bit of a rewrite.

Relative to this text:

 <aside class="example">Considering a subtitling and captioning practice where italics are used to indicate an off screen
        speaker context (for example a voice from a radio), an author can choose to include this functional information in the text
        equivalent; for example, by including the word "Radio: " before the image equivalent text. Note that images in an <a>Image
        Profile</a> <a>Document Instance</a> that are intended for use as <em>captions</em>, i.e. intended for a hard of hearing
        audience, might already include this functional information in the rendered text.</aside>

I'm not clear on whether "might already include this functional information" is referring to the italic styling or to the added word "Radio: ", and this seems important to this note. I think it is saying that the image might render text in italics but the text equivalent might include "Radio: " and not be in italics. Also should we not include ttm:role here?

Furthermore, it is not clear here why the author would not use tts:fontStyle="italic" in this example, i.e. something more like this for the second line:

        speaker context (for example a voice from a radio). As an alternative or addition to specifying <code>tts:fontStyle="italic"</code>, an author could choose to include this semantic information in the text

Instead of functional information in the rendered text., it would be clearer if it said presentation style in the rendered text..

As noted by @palemieux , the original text of the example came from a long thread culminating in the current text as proposed by @JLBirch.

@nigelmegitt
Copy link
Contributor Author

I've just enjoyed re-reading the thread and believe I understand what was intended now.

Suggested alternatives:

  1. Drop Image Profile from 1.3, and make 1.2 the last version of IMSC with Image Profile. Consequently this whole section could be removed (alongside many others).
  2. Rewrite the note as follows:
 <aside class="example">Considering a subtitling and captioning practice where
        styling is used to convey meaning,
        for example using italics to indicate an off screen speaker context
        speaker context such as a voice from a radio,
        an author can choose to describe this sense in the text equivalent;
        in this example, by including the word "Radio: " before the image equivalent text.
        Note that images in an <a>Image Profile</a>
        <a>Document Instance</a> that are intended for use as <em>captions</em>,
        i.e. intended for a hard of hearing audience,
        might already include this styling in the rendered text.</aside>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants