Ian Hickson wrote:
On Sun, 5 Feb 2006, dolphinling wrote:
Actually, the javascript solution would be _superior_ to the XBL one in
this case. The screenreader wouldn't pick up on the XBL at all, and
would read the content as-is, likely confusing the user.
Um, there's no reason an aural browser couldn't support XBL.
Hmm, I suppose not. Something still strikes me as making the javascript
solution better, though. Perhaps it's a question of localized content
vs. localized presentation of content.
--
dolphinling
<http://dolphinling.net/>
