W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2008

Re: Request for Comments on Widgets 1.0 Requirements Last Call WD

From: Steven Faulkner <faulkner.steve@gmail.com>
Date: Mon, 4 Aug 2008 15:54:31 +0100
Message-ID: <55687cf80808040754s4c187585sc41ce04df6b15ec@mail.gmail.com>
To: "Marcos Caceres" <marcosscaceres@gmail.com>
Cc: "Arthur Barstow" <art.barstow@nokia.com>, "Sally Cain" <sally.cain@rnib.org.uk>, "Cynthia Shelly" <cyns@exchange.microsoft.com>, wai-xtech@w3.org, public-webapps <public-webapps@w3.org>

Hi Marcos and Arthur, thanks for taking the comments into account.

can I suggest the last part:
"The user interface language MUST also be accessible to screen
readers, allowing relevant sections of text and functionality to be
accessed by non-visual means."

be replaced with something like:

"The name, role and state of all interface elements MUST be available
to assistive technologies such as screen readers, to allow relevant
sections of text and functionality to be accessed"


and the rationale be modified:

from
"screen readers and similar assistive technologies"

to
"screen readers and other assistive technologies"


regards
stevef

2008/8/4 Marcos Caceres <marcosscaceres@gmail.com>:
> Art, Sally, Steve, All
>
> On Mon, Aug 4, 2008 at 9:07 PM, Arthur Barstow <art.barstow@nokia.com> wrote:
>> Sally, Steve, All
>>
>> FYI, Cynthia Shelly [CS] submitted comments that are similar to the ones you
>> submitted regarding requirement #37 [37] of the Widgets Requirement LC WD
>> [LC].
>>
>> Both Marcos [MC] and I [AB] replied to Cynthia's comments. We agree the
>> wording in sentences #2 and #3 needs work and the tentative resolution is to
>> replace this requirement with text like:
>>
>> [[
>> A conforming specification must specify that the language used to declare
>> the user interface of a widget be either HTML or a language that is
>> accessible as defined by [WCAG-2].
>> ]]
>>
>
> The text as it stands today is as follows. I have not had a chance to
> fully address everyone's feedback on this thread yet but will do so by
> the end of the week. Please feel free to comment on the current text.
>
> --
> R37. Language Accessibility
> A conforming specification MUST specify that the language used to
> declare the user interface of a widget be either HTML or a language
> that is accessible at the various levels specified by the WCAG 2.0
> (perceivable, operable, understandable, and robust): specifically, the
> language MUST provide keyboard access to interactive graphical
> elements, and provide means to access the widget's functionality
> through a non-graphical UI. The user interface language MUST also be
> accessible to screen readers, allowing relevant sections of text and
> functionality to be accessed by non-visual means.
>
> Motivation:
>  Compatibility with other standards, current development practice or
> industry best-practices, ease of use, accessibility.
> Rationale:
>  To recommend a language, or a set of languages, that will allow
> authors to realize their designs, while at the same time remaining
> accessible to screen readers and similar assistive technologies.
> --
>
> Kind regards,
> Marcos
>
>
>
> --
> Marcos Caceres
> http://datadriven.com.au
>



-- 
with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium

www.paciellogroup.com | www.wat-c.org
Web Accessibility Toolbar -
http://www.paciellogroup.com/resources/wat-ie-about.html
Received on Monday, 4 August 2008 14:55:13 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:27 GMT