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 264063EAA1 for ; Thu, 23 May 2002 01:22:48 -0400 (EDT) Received: (from mail@localhost) by int-mx1.corp.redhat.com (8.11.6/8.11.6) id g4N5MmJ18023 for blinux-list@listman.redhat.com; Thu, 23 May 2002 01:22:48 -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 g4N5Mml18019 for ; Thu, 23 May 2002 01:22:48 -0400 Received: from pjrnb-as.dar.csiro.au (CPE-144-137-52-178.vic.bigpond.net.au [144.137.52.178]) by mx1.redhat.com (8.11.6/8.11.6) with SMTP id g4N5G4M22092 for ; Thu, 23 May 2002 01:16:05 -0400 Received: (from ray060@localhost) by pjrnb-as.dar.csiro.au (8.11.3/8.11.3) id g4N5Kqd13492; Thu, 23 May 2002 15:20:52 +1000 X-Authentication-Warning: pjrnb-as.dar.csiro.au: ray060 set sender to peter.rayner@csiro.au using -f From: RAYNER Peter MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15596.31791.84467.201839@pjrnb-as.dar.csiro.au> Date: Thu, 23 May 2002 15:20:47 +1000 To: blinux-list@redhat.com Subject: dealing with javascript X-Mailer: VM 6.95 under Emacs 20.7.1 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 X-Reply-To: peter.rayner@csiro.au List-Help: List-Post: List-Subscribe: , List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: 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