SRs Nov 5 action items: update

Updated action items report...feedback welcome, thanks!

ACTION 1: Sharron - the first mention of widgets clarify what we mean by it.
Please see question 4 on 
<http://www.w3.org/WAI/EO/Drafts/ARIA/faq.html#intent>ARIA FAQs and comment

ACTION 2: Sharron FAQ rewrite Question 8

Q8 formerly asked:  Is ARIA too complex for web authors to get it 
right?  It now says...


8. Does using ARIA make web authoring much more complex?

ARIA is not any more complex than developing cross-browser, custom 
JavaScript widgets. Many authors will run JavaScript toolkits with 
powerful pre-built widgets. ARIA support should be - and is - being 
added to these toolkits, which authors can then reuse. While it is 
not extremely likely for an individual author to use ARIA directly, 
it is reasonable to expect that an array of organizations require web 
applications to be accessible. In addition, testing tools are being 
developed as are examples and "best practices" documents, to guide 
web authors who want to use ARIA.

ACTION 3: Sharron to consider how to introduce Overview - as opening 
sentence or question 1?

There is too much information on the Overview page to fold it into 
FAQ document.  My opinion is that we should shorten the information 
on the overview  by taking the second paragraph from the "Making AJAX 
...accessible" and putting it into the questions.

The result would be:
1. On the Overview:
Making Ajax and related technologies Accessible:
Many Web applications developed with Ajax, DHTML, and other 
technologies pose accessibility challenges. For example, if the 
content of a Web page changes in response to user actions, that new 
content may not be available to some people, such as people who are 
blind or people with cognitive disabilities who use a screen 
reader.  WAI-ARIA addresses accessibility challenges by defining how 
information about these features can be provided to assistive 
technology. More specifically, ARIA provides a framework for adding 
attributes to identify features for user interaction, how they relate 
to each other, and their current state. With ARIA, an advanced Web 
application can be made accessible and usable to people with disabilities.

2. In the FAQs:
Why is ARIA needed?
Web sites are increasingly using more advanced and complex user 
interface controls, such as tree controls for Web site navigation. To 
provide an accessible user experience to people with disabilities, 
assistive technologies must be able to interact with these controls. 
However, the information that the assistive technologies need is not 
available to most current Web technologies.

Accessibility should not hold web authors back from innovating, 
however. Several basic Javascript widgets are commonly used and yet 
conspicuously missing from HTML 4. The problem is not that JavaScript 
is bad for accessibility, but that there is no mechanism to describe 
what the script is visually portraying to a user. The ARIA initiative 
seeks to make accessibility possible for such JavaScript widgets.

ACTION: Sharron to make business/usability case strong and near the 
frontand in a basic, non-detailed way
Working on this one...more soon.

ACTION: Sharron, for the faq, clearly distinguish the two and point 
to the other
Working with Lisa Pappas on this, will report next week.