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

The current spec states:

"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 various levels: it should provide keyboard
access to interactive graphical elements, and provide means to access
the widget's functionality through an non-graphical UI. The declared
interface may also be accessible to screen readers, allowing relevant
sections of text and functionality to be accessed by non-visual means.

Compatibility with other standards, current development practice or
industry best-practices, ease of use.
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. "

In order for a widget to be accessible would it not be a MUST
requirement that keyboard access be provided or able to be provided
uisng the language of choice?
Also why is that the "declared interface may also be accessible to
screen readers"? again for it to be considered accessible would it not
be that a widget MUST be accessible to AT or abkle to be made
available using the language of choice?

apologies if I am missing something here.


2008/7/31 Arthur Barstow <>:
> This is a reminder August 1 is the end of the comment period for the Widgets
> 1.0 Requirements Last Call Working Draft.
> -Regards, Art Barstow
> Begin forwarded message:
>> From: Arthur Barstow <>
>> Date: June 26, 2008 4:50:51 PM EDT
>> To:
>> Cc: Marcos Caceres <>
>> Subject: Request for Comments on Widgets 1.0 Requirements Last Call WD
>> Al, P&F WG,
>> On June 25 the Web Applications WG published a Last Call Working Draft of
>> the Widgets 1.0 Requirements document:
>> [[
>> <>
>> Abstract: This document lists the design goals and requirements that a
>> specification would need to address in order to standardize various aspects
>> of widgets. Widgets are small client-side Web applications for displaying
>> and updating remote data, that are packaged in a way to allow download and
>> installation on a client machine, mobile phone, or mobile Internet device.
>> Typical examples of widgets include clocks, CPU gauges, sticky notes,
>> battery-life indicators, games, and those that make use of Web services,
>> like weather forecasters, news readers, email checkers, photo albums and
>> currency converters.
>> Introduction: A widget is an interactive single purpose application for
>> displaying and/or updating local data or data on the Web, packaged in a way
>> to allow a single download and installation on a user's machine or mobile
>> device. A widget may run as a stand alone application (meaning it can run
>> outside of a Web browser), or may be embedded into a Web document. In this
>> document, the runtime environment on which a widget is run is referred to as
>> a widget user agent and a running widget is referred to as an instantiated
>> widget. Prior to instantiation, a widget exists as a widget resource. For
>> more information about widgets, see the Widget Landscape document.
>> ]]
>> We would appreciate any comments your WG has on this LC document,
>> especially those requirements relevant to your WG's domain/scope. The
>> comment period ends 1 August 2008.
>> -Regards, Art Barstow

with regards

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

Received on Thursday, 31 July 2008 13:21:45 UTC