New (proposed) SC 3.1.6 A mechanism is available for finding specific pronunciation of words where meaning cannot be determined without pronunciation

Hello, Team B!.

You may recall that at the end of the October f2f meeting in Seattle,
Gregg and Makoto were given an action to develop a proposal about
pronunciation. (Quick background: The May 2005 proposal for GL 3.1
included a proposed SC about pronunciation. The proposal was rejected at
the Brussels f2f (June 2005) and the rejection was ratified on the call
following the Brussels meeting. However, the issue was raised again at
the October f2f during the discussion of JIS comments, and the action
was assigned to Gregg and Makoto. This proposal is the result.)

It comes to Team B because we're "responsible" for GL 3.1, so we should
review and then send it to the WG for survey next week if possible.

This message includes only the proposed wording for the SC, plus links
to the proposed How to Meet 3.1.6 document and a sufficient HTML
technique.

Proposed wording for SC 3.1.6
<proposed>
3.1.6 A Mechanism is available for identifying specific pronunciation of
words where meaning cannot be determined without pronunciation. (Level
3)
</proposed>
How to Meet 3.1.6
http://trace.wisc.edu/wcag_wiki/index.php?title=How_to_Meet_Success_Crit
erion_3.1.6
(Note that there is still some discussion about wording in the Intent
section, but the document in the WIKI is ready for review.)


The HTML technique is called "Using the Ruby element"
http://trace.wisc.edu/wcag_wiki/index.php?title=Using_the_ruby_element


Thanks much,
JOhn
"Good design is accessible design." 
John Slatin, Ph.D.
Director, Accessibility Institute
University of Texas at Austin
FAC 248C
1 University Station G9600
Austin, TX 78712
ph 512-495-4288, f 512-495-4524
email jslatin@mail.utexas.edu
web http://www.utexas.edu/research/accessibility/


 

Received on Friday, 3 March 2006 19:11:39 UTC