I may be wrong, but I don't think there's any new movement, unfortunately. We should probably re-evaluate given developments (as discussed on this list) re elinks and javascript. I think someone willing to see it through would be in good shape filing a complaint under the ADA with the Justice Dept. Sina Bahram writes: > Hi Janina, > > Speaking of financial institutions ... What is the latest and greatest on > that front? > > For example, if my credit card/bank's website is inaccessible ... Is there > anything at all one can do asides from the usual phone calls to > unknowledgeable individuals? > > Take care, > Sina > > -----Original Message----- > From: speakup-bounces at braille.uwo.ca [mailto:speakup-bounces at braille.uwo.ca] > On Behalf Of Janina Sajka > Sent: Tuesday, July 19, 2005 3:12 PM > To: Speakup is a screen review system for Linux. > Subject: Re: elinks: Harmless Button > > Fascinating. Thanks for posting. > > If I follow this correctly, the button is the code that reads: > > <script > src="https://seal.verisign.com/getseal?host_name=payments.verisign.com&size= > M&use_flash=NO&use_transparent=NO"></script> > > If I had to guess, I'd say this was a graphic intended to give you > confidence in the Book Share SSL Certificate. But, why that requires a > script, or to be wrapped in a div is beyond me. Might be worth a note to > Book Share only because they may have better access to Verisgn for > accessibility issues. I definitely think there are several accessibility > issues with both the form and this "button." > > I don't think Book Share is authorized to just recode this, if it really is > what I think it is. On the other hand, we need the financial services > industry to get a better grip on accessibility, and our national > organizations haven't made much headway in this regard yet. I suspect Book > Share might get a at least a ripple of consciousness from Verisign out of > this. At the absolute least they should know that one of their power users > found the usage inaccessible--meaning that the bulk of their users would be > even more befuddled. > > Steve Holmes writes: > > On Tue, Jul 19, 2005 at 01:24:57PM -0400, Janina Sajka wrote: > > > Best way to answer this question is to examine the source code. With > > > the cat we would use the capital 'E' to expose the text of the > > > anchor link (<a [text]> </a>) > > > > > > Can we do that with the chain? I must confess I don't know, even > > > though I also use elinks sometimes. > > > > > Yes, I checked and normally the Capital E key will do likewise; since > > this is a button however, it doesn't work. I will attach the relevant > > part of the actual HTML so you can see what I mean. I will strip out > > the bulk of the rest of the form because it contains personal > > information and it would be quite large. It is the last table in the > > form and I will include it now. When the screen is showing, you have > > one button on the form and the text of it says "Return to Bookshare.org. > > So I think this particular form might actually come from Verisign. > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -- Janina Sajka Phone: +1.202.494.7040 Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com Bringing the Owasys 22C screenless cell phone to the U.S. and Canada. Go to http://www.ScreenlessPhone.Com to learn more. Chair, Accessibility Workgroup Free Standards Group (FSG) janina at freestandards.org http://a11y.org
