[Bug 24168] New: Please revise new normative statement and example

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24168

            Bug ID: 24168
           Summary: Please revise new normative statement and example
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML Image Description Extension
          Assignee: chaals@yandex-team.ru
          Reporter: laura.lee.carlson@gmail.com
        QA Contact: public-html-bugzilla@w3.org
                CC: public-html-admin@w3.org

Hi Chaals and Mark,

I just noticed the following new spec text [1] that states:

Quote
"Authors should not rely solely on longdesc where standards exist to provide
direct, structured access.

This section is informative

For example a MathML version of mathematical content, or an SVG image that uses
the accessibility features of SVG, can provide better accessibility to users
with appropriate technology. In such cases, it is appropriate to use longdesc
as a fallback strategy, in combination with more modern techniques."
Unquote

This text contains incorrect and prejudicial longdesc information as it infers
that longdesc is not modern. The fact that we have a brand new longdesc spec
and new a longdesc implementation with FireFox does indeed make longdesc
modern.

In addition the normative statement is confusing in relation to
aria-describedat. Using a bridging technology would backward. Please consult
[2] for full rationale. HTML has native, built-in long description semantics
with longdesc.  

Please change the following:

Current Text:
"Authors should not rely solely on longdesc where standards exist to provide
direct, structured access." 

To something such as:
"Authors may use other standards in addition to longdesc if those standards
provide semantic, programmatic, direct, and structured access." 

Current Text:
"For example a MathML version of mathematical content, or an SVG image that
uses the accessibility features of SVG, can provide better accessibility to
users with appropriate technology. In such cases, it is appropriate to use
longdesc as a fallback strategy, in combination with more modern techniques."

To something such as:
"For example a MathML version of mathematical content, or an SVG image that
uses the accessibility features of SVG, can provide good accessibility to users
with appropriate technology. In such cases, it is appropriate to use those
techniques in combination with longdesc."

Thank you for your consideration.

[1]
https://dvcs.w3.org/hg/html-proposals/raw-file/default/longdesc1/longdesc.html#authors
[2] http://www.d.umn.edu/~lcarlson/research/constriants/bridging.html

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 26 December 2013 15:47:38 UTC