E-mail List Archives
Re: code triggering WAVE
From: Jared Smith
Date: May 11, 2010 5:18PM
- Next message: Jared Smith: "Re: ARIA Examples Specific to Alert"
- Previous message: Seth Kane: "ARIA Examples Specific to Alert"
- Next message in Thread: None
- Previous message in Thread: James Bailey: "Re: code triggering WAVE"
- View all messages in this Thread
On Tue, May 11, 2010 at 2:49 PM, James Bailey < <EMAIL REMOVED> > wrote:
> I think I was hoping against hope that there was something that could be done about code inserted by a third party (the web host).
Nope. There isn't really a way to manipulate the 3rd party content. In
this case, the tracking image missing alt text is not a very serious
accessibility issue - it would generally be ignored by a screen
reader. I guess you might be able to apply additional scripting to add
an empty alt attribute to the image after it is injected into the
page, but I don't think this is necessary.
> the toolbar flags it while submitting the URL to the WAVE server does not. I presume that is some web anomaly.
The server version of WAVE (wave.webaim.org) evaluates that rendered
version of the page after CSS has been applied. For security reasons,
we cannot process external javascript through our web site. Javascript
is stripped out of these reports and javascript issues are generally
not reported. With the Firefox toolbar, the page is evaluated after
both CSS and javascript have been applied to the page, thus the
discrepancy.
Jared
- Next message: Jared Smith: "Re: ARIA Examples Specific to Alert"
- Previous message: Seth Kane: "ARIA Examples Specific to Alert"
- Next message in Thread: None
- Previous message in Thread: James Bailey: "Re: code triggering WAVE"
- View all messages in this Thread