W3C

Edit comment LC-2062 for Web Applications Working Group

Quick access to

Previous: LC-2061 Next: LC-1993

Comment LC-2062
:
Commenter: David Poehlman <david.poehlman@handsontechnologeyes.com>

or
Resolution status:

+1, not that Ihave a vote <g>
chiming in here on this,

You might pick this up, but one instance of language is written as
"langauge".

for symetry, compactness and accuracy I suggest:
replace "assistive technologies such as screen readers" with:
"screen readers and other assistive technologies"
----- Original Message -----
From: "Steven Faulkner" <faulkner.steve@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>
Sent: Tuesday, August 05, 2008 4:22 AM
Subject: Re: Request for Comments on Widgets 1.0 Requirements Last Call WD



+1

2008/8/5 Marcos Caceres <marcosscaceres@gmail.com>:
> Hi Steve, Cynthia, and Sally,
>
> On Tue, Aug 5, 2008 at 12:54 AM, Steven Faulkner
> <faulkner.steve@gmail.com> wrote:
>> Hi Marcos and Arthur, thanks for taking the comments into account.
>
> No probs. Thanks for taking the time to provide them.
>
>> 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"
>
> Ok. Done.
>
>>
>> and the rationale be modified:
>>
>> from
>> "screen readers and similar assistive technologies"
>>
>> to
>> "screen readers and other assistive technologies"
>
> Ok, below is the final text which hopefully addresses everyone's
> comments. To assist me with the Last Call Disposition of Comments,
> could you please acknowledge if you are satisfied (or not) with what
> is now in the spec:
> --
> 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
> langauge MUST provide keyboard access to interactive graphical
> elements, and provide means to access the widget's functionality
> through a non-graphical UI. For the user interface language, the 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.
>
> 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 other assistive technologies.
>
> --
>
> Thank you all again for taking the time to comment and improve this
> requirement.
>
> Kind regards,
> Marcos
>
> --
> Marcos Caceres
> http://datadriven.com.au
>
(space separated ids)
(Please make sure the resolution is adapted for public consumption)


Developed and maintained by Dominique Hazaël-Massieux (dom@w3.org).
$Id: 2062.html,v 1.1 2017/08/11 06:46:04 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org