From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by listman.redhat.com (Postfix) with ESMTP id CF5183EB38 for ; Sun, 26 May 2002 20:22:07 -0400 (EDT) Received: (from mail@localhost) by int-mx1.corp.redhat.com (8.11.6/8.11.6) id g4QIM7U05007 for blinux-list@listman.redhat.com; Sun, 26 May 2002 14:22:07 -0400 Received: from mx1.redhat.com (mx1.redhat.com [172.16.48.31]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with SMTP id g4QIM7r05003 for ; Sun, 26 May 2002 14:22:07 -0400 Received: from mail.rack66.net (qmailr@slider.rack66.net [212.3.252.135]) by mx1.redhat.com (8.11.6/8.11.6) with SMTP id g4R0F8f17499 for ; Sun, 26 May 2002 20:15:08 -0400 Received: (qmail 24111 invoked by uid 1000); 27 May 2002 00:26:33 -0000 Date: Mon, 27 May 2002 02:26:33 +0200 From: Peter Durieux To: blinux-list@redhat.com Subject: Re: dealing with javascript Message-ID: <20020527002632.GB7221@debian> References: <15596.31791.84467.201839@pjrnb-as.dar.csiro.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15596.31791.84467.201839@pjrnb-as.dar.csiro.au> User-Agent: Mutt/1.3.28i X-Loop: blinux-list@redhat.com Sender: blinux-list-admin@redhat.com Errors-To: blinux-list-admin@redhat.com X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.0.1 Precedence: bulk Reply-To: blinux-list@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: Hi, I know there is a project on sourforge. Netrik is a text browser that may support js, c http://netrik.sourceforge.net. I haven't tested the last versions. grtz -Peter On Thu, May 23, 2002 at 03:20:47PM +1000, RAYNER Peter wrote: > I guess we're all running into problems with javascript more and more > often. I'm wondering if it's time to put some collective effort into > a solution and, if so, what it might be. > The last time this topic turned up on the emacs-w3 list, Bill Perry's > suggestion was for some kind of external parser, rather than extending > the capabilities of emacs-w3 itself. > The other alternatives I see are to wait and hope the netscape > accessibility efforts make the problem go away or to extend the > capabilities of some other access tool. > Does anyone have any suggestions for which alternative might be > preferable? If we do decide on an external filter what kinds of > capabilities must it have? The few times I've looked inside > inaccessible pages the JS seems to be doing uninteresting things like > drop-down lists which could easily be handled other ways. But I don't > know enough about the capabilities of javascript to know what other > kinds of events we might have to deal with. I'm happy to try and hack > something together to do this provided there's a reasonable chance of > success; it's about time I brushed up my perl anyway. There also > look to be some open-source implementations of interpretters out there > we could possibly modify for the task. > So do people have a view of whether and how to go forward with this? > Any currently active projects? Other comments > cheers > Peter Rayner > > > > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://listman.redhat.com/mailman/listinfo/blinux-list