Re: 48-Hour Call for Consensus (CfC): Proposed TTML Comments


´╗┐On 2/19/20, 3:37 PM, "Janina Sajka (" <> wrote:


    This is a Call for Consensus (CfC) to the Accessible Platform
    Architectures (APA) Working Group proposing the following review
    response on:

    ttml profiles for internet media subtitles and = captions 1.2;;sdata=DQGIFGCeJzoIoUvq7Ixh7SJqN0XHa1%2BqABxvsvy%2BmmQ%3D&amp;reserved=0

    This draft response was first posted to APA on 22 January last at:;;sdata=3Uox90o6y4PU89ClpRz%2BuAU48wBl1a%2Fb5NMEu7jeMz0%3D&amp;reserved=0

    It's language has been tweaked by yours truly.

    <begin draft comment>

    1.)    Reference to WCAG 2.1:

    We appreciate the addition of section
    <;;sdata=4jnqmlm9Cmau9Q9Hov5Zp9TFOJDZkl4Cy9HxBUuVXX0%3D&amp;reserved=0> D.1
    WCAG Considerations and its content.  This is very helpful.  We would, though,
    like to change the phrasing "WCAG 2.1 recommends" to "WCAG 2.1 requires",
    because the WCAG success criteria are normative requirements rather than

    2.)    Requested Additional WCAG 2.1 References:

    In addition to the guidelines and success criteria you already reference, we
    would like to see references to the following WCAG 2.1 success criteria that are
    also applicable to the TTML profiles specification:

    a.        <;;sdata=fswJIeA0wHYY5trKyBtAursoLiFfLwZWr%2BGbLnrfazg%3D&amp;reserved=0> Success Criterion 1.4.3 Contrast (Minimum) (applying to the text-only profile)

    b.        <;;sdata=UWEFSeuQt3K8FlM%2BNVZtJUpYIK7UQ9pAZmPKVvt53Ow%3D&amp;reserved=0> Success Criterion 1.4.11 Non-text Contrast (applying to the image-only profile)

    c.        <;;sdata=DS%2FTIGOhLj5LNiJ%2B4NJTlm3P6cfGa%2BQl9zYDMTgZXd8%3D&amp;reserved=0> Success Criterion 3.1.1 Language of Page (using the xml:lang attribute)

    d.        <;;sdata=TVg94ytlm3GHOKdziZQDsHfknEYlaQ3jLTVMZxTI%2FIo%3D&amp;reserved=0> Success Criterion 3.1.2 Language of Parts (using the xml:lang attribute)

    3.)    Reference to MAUR:  We also appreciate the addition of section D.2 MAUR
    Thank you. We trust the MAUR will continue helpful to the wider community.

    4.)     With respect to the
    <;;sdata=Wer7CjZNgMm%2FmIM8yeUe1NUG0pIbW%2B476MmsIZQLYtU%3D&amp;reserved=0> 7.12.2 altText
    named metadata item, this is directly related to the accessibility requirement
    of having an alternate text version for images (<;;sdata=4elaTmAxZjKVBFEnHHyKwnLsaJzbzjfxhbKmTDIPksQ%3D&amp;reserved=0> Success Criterion 1.1.1
    Non-text Content). Could you add a note here saying something like: "Note:
    Authors are encouraged to provide text alternatives for every non-decorative
    image and/or compound image set by using the altText named metadata item. This is
    necessary for making the image in the document accessible to persons with (visual)
    disabilities, thus complying with
    <;;sdata=4elaTmAxZjKVBFEnHHyKwnLsaJzbzjfxhbKmTDIPksQ%3D&amp;reserved=0> W CAG
    2.1 success criterion 1.1.1 (Non-text content)."

    5.)    Suggested Introduction Section for First-Time Readers: The document
    would be easier to read and understand for first-time readers if it had an
    introduction that guided the reader to a better understanding of its content.
    Such an introduction could serve to introduce the reader to items such as the

    a.       Why are profiles needed for text-only and image-only captions/subtitles?

    b.       What are typical use cases for image-only captions/subtitles?

    6.)    There is a general issue with the way that an author specifies layout
    characteristics of captions and subtitles, such as font size, font family,
    line height, background and positioning.  It should be made clear that authors
    can and should define the viewport and text characteristics, but these
    definitions may be overridden by the user by setting up their user agent to
    better meet their particular needs as users (cf. MAUR, 3.7 Requirements on the
    use of the viewport
    For example, a user with vision impairment who also requires caption support
    may want to have all captions displayed in the lower third of the screen with
    a large font, disregarding the definition of various viewports and font types
    defined by the author.  We recommend adding a note to the spec to advise
    authors that  the final rendition of their document may not follow their
    specified styling and positioning, but follow user-defined styling and
    positioning instead.

    7.)     <;;sdata=EO1tttBc7nk2EDIDFzimvN3BrnST79DzE1t2lIyCbuE%3D&amp;reserved=0>
    Section C. Forced content: This seems like a temporary solution to us.
    Mightn't it be better to define semantic layers of information so that each
    layer could be made visible and invisible at runtime as appropriate for the
    user?  For example, the user might want to see either speech-only (subtitles),
    narration speech only (parts of subtitles), foreign-language speech-only
    (parts of subtitles) or some combination of these.


    ***Action to Take***

    This CfC is now open for objection, comment, as well as statements of
    support via email. Silence will be interpreted as support, though
    messages of support are certainly welcome.

    If you object to this proposed action, or have comments concerning this
    proposal, please respond by replying on list to this message no later
    than 23:59 (Midnight) Boston Time, Tuesday 25 February.

    NOTE: This Call for Consensus is being conducted in accordance with the
    APA Decision Policy published at:;;sdata=ATUN7ogY%2FC8ju2oJ0c2YZTN3F5DttUfky8k4lj6aNZs%3D&amp;reserved=0

    Our thanks to Dr. Gottfried Zimmerman for reviewing the TTML
    specification and providing us with his recommended response above as
    logged in.  Action-2224<;;sdata=ybzaMgFx%2BI9KwfiH9FKgz%2FwNVNgxdGApjkUwURtdI4g%3D&amp;reserved=0>.


    Janina Sajka

    Linux Foundation Fellow
    Executive Chair, Accessibility Workgroup:;;sdata=Lt%2BWxEntoi915GZjGwbgDRp22RkxRrO13eimCj1uKaA%3D&amp;reserved=0

    The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
    Chair, Accessible Platform Architectures;;sdata=zq6pcHKksEV13Y0Cwm%2FfzJ6x9LWzGUmuWLSplwNqy0Y%3D&amp;reserved=0


This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

Thank you for your compliance.


Received on Wednesday, 26 February 2020 02:17:30 UTC