Re: Scripting

Wendy,

thanks for your fairly comprehensive reply, to a different question.
On the positive side, The bugzilla interface looks great.
It doesn't seem that appropriate for shifting the whole document across  
though. I also have a life.
Accessible scripting does need a large document

the 4 open issues listed are only a few of the ones we covered, should  
they be dated, to give some idea of progress?
Beneath each open issue there appears the following:
Techniques for WCAG 2.0 | Client Side Scripting Techniques | proposal |  
2003-02-12 15:29:54 | NEW | WCAG Bugzilla Issue #197
What is its purpose? they look like links but aren't, at least the last  
one is but when I tried to add a comment, by clicking on "WCAG Bugzilla  
Issue #197" I repeatedly get an 'Internal Server Error'

am awaiting password(20 minutes later), to add a new topic,
tried again, and this time received email changing password??
now however I get the Internal Server Error when trying to log in.
tried alternate email address, new password, Internal Server Error
Gave Up for today!

4 open issues, does not look like a whole lot of effort for 12 months.
Is WCAG planning to contribute significant effort in the next 12 months?

NB:	The SVG condensed report has no open issues, shurely shome mishtake?

Do you consider that WCAG is on track with regard to techniques?
SVG and Scripting?
Who is the lead on these?

Please remember that I offered to manage development of the Scripting  
document, but you demurred, insisting that you were in control.
Where is the evidence that you are progressing this?

My apologies if this seems forceful, I only wish to see progress, and  
this is not readily apparent.

Jonathan


On Monday, June 16, 2003, at 07:55  pm, Wendy A Chisholm wrote:

>
> If you would like the WCAG WG to discuss a specific issue,
>
> 1. check if the issue is already in the issues list
> links to condensed bug report lists:  
> http://trace.wisc.edu/bugzilla_wcag/condensedreports/
> we have 4 open issues related to client-side scripting:
> http://trace.wisc.edu/bugzilla_wcag/condensedreports/ 
> clientside_issues.php
>
> 2.  If your issue is not on the issues list
> create a new issue in the WCAG Bugzilla database
> http://trace.wisc.edu/bugzilla_wcag/
>
> 3. Propose a solution to the issue and send it to the mailing list
> For example, refer to this message from Michael Cooper about using the  
> summary attribute on Table elements.  He summarizes the possibilities  
> and proposes a solution.   
> http://lists.w3.org/Archives/Public/w3c-wai-gl/2003AprJun/0294.html
>
> Another good example:
> summarize the issue and raise questions that we need to answer about a  
> particular technique:
> http://lists.w3.org/Archives/Public/w3c-wai-gl/2003AprJun/0215.html
>
> ===
> While scripting issues have not been the core of our discussions, we  
> have been making progress. Here is an overview of what's been  
> happening with Techniques for WCAG 2.0  
> (http://www.w3.org/WAI/GL/wcag20.html#techs).
>
> 1. updating issues lists.
> all previous HTML issues have been moved to bugzilla
>
> 2. discussing open issues on Wednesday telecons and mailing list
> primarily addressing HTML issues, summary of those discussed in the  
> last few weeks:
> - tables
> - alt/title/longdesc
> - abbr/acronym
>
> 3. designing schema and tools for techniques
> http://www.w3.org/WAI/GL/WCAG20/sources/xmlspec-tech.dtd
>
> 4. converting old html techniques to new dtd
> Loretta is doing this. She is also converting the PDF Techniques to  
> the new dtd
>
> Best,
> --wendy
>
>
> At 11:11 AM 6/14/2003, Jonathan Chetwynd wrote:
>> The regular annual wake for:
>> "Client-side Scripting Techniques for Web Content Accessibility  
>> Guidelines 2.0"
>> http://www.learningdifficulty.org/develop/script-techs.html
>>
>> is fast approaching.
>>
>>
>> Please can anyone advise me in what sense is WCAG fulfilling it scope  
>> with respect to scripting?
>> other W3C technologies?
>>
>> thanks
>>
>> Jonathan
>> http://www.peepo.com
>> enabling people with a severe learning difficulty to browse the web  
>> independently
>>
>> Congratulations on the working group logo 'b-10-family1.png' though  
>> this is perhaps not ideal as a name, how about 'working group  
>> logo.png'.
>> Sorry not to have contributed more, perhaps its time I rejoined as an  
>> active participant.
>
> -- 
> wendy a chisholm
> world wide web consortium
> web accessibility initiative
> http://www.w3.org/WAI/
> /--

Received on Tuesday, 17 June 2003 01:59:05 UTC