RE: [action] VoiceXML and WCAG

Hi,
Here some note from our representative inside VoiceXML WG. Note is with >.
He is in cc.



Level 3 Success Criteria for Guideline 1.1

For prerecorded multimedia content, a combined transcript of captions and
audio descriptions of video is available.

Not applicable (multimedia).
><Audio> Provide a multimedia content (pre-registred file)

Level 1 Success Criteria for Guideline 1.3

1. Structures within the content can be programmatically determined.

Until I find evidence to the contrary, a VoiceXML document must meet this
success criterion or the voice application will not work. However, if
VoiceXML is used to present structured text (newspaper articles, any
non-fiction or fiction), there are no elements to mark headings, quotes,
etcetera. There is even no element for descriptive titles (see discussion of
Guideline 2.4 Level 2 SC 3 below).

>If the rule is related only to a presentation feeling.. SSML with
<emphasis>  can be very usefull, even quotes can be transled in <break>

Guideline 2.2 Allow users to control time limits on their reading or
interaction

> There are different properties (for speech imput and for dtmf imput) to
control complete time-out and singular occurence time-out

Level 1 Success Criteria for Guideline 2.2
1. Content is designed so that time-outs are not an essential part of
interaction, or .

However, the use of this feature does not meet any of the bullet points of
this success criterion. I am not sure if it is possible to store the timeout
value in a variable, then reference this variable in the timeout attribute
and increment it in <noinput>, or to prompt the user for a new value.

> In a dialog prompts have to be designed, and u can include for example the
timeout. 
>In tapered prompts for example:
> 	<form id="one">
		<field name="one">
			<prompt timeout="120s">First prompt</prompt>
			<noinput count="1">
				<prompt timeout="150s">Second
prompt</prompt>
			</noinput>
			<noinput count="2">
				<prompt timeout="170s">Third prompt</prompt>
			</noinput>
		</field>	
	</form>
>
the user is allowed to deactivate the time-out or ..
> But.. there is also a timeout property, so.. it's possible to ask to user
if it prefer to have or not timeout, and then set the property, and turn-off
the timeout attribute

2. Moving or time-based content can be paused by the user.
If a prompt does not specify a noinput timeout, the application uses a
platform-specific default timeout. It is not obvious how content can be
paused by the user.

> for long prompt, for example: a mail reader, yoi can set <mark> tag ..
even if is not well supported at this time.

Guideline 2.5 Help users avoid mistakes and make it easy to correct them

Level 2 Success Criteria for Guideline 2.5

1. If an input error is detected, the error is identified and provided to
the user in text.
It is not possible to detect errors, only that inputs don't match grammars,
so VoiceXML applications don't need to do anthing to meet this criterion.

> there are, more than <noinput> or <nomatch>, other errors, for example the
resource is not available, etc..
> these errors can be catched by <catch> element and a can be sumbit a
prompt.

Received on Thursday, 29 September 2005 16:30:38 UTC