Could defeat auto-forward. JW Various ways to implement. Easily avoided if using server-side techniques or scripting techniques. UAs should fix, but I'm not sure whether taking a requirement out since UAs should fix is reasonable. In ERT WG haven't figured out how to determine that javascript is accessible or not much less how to control parts of it.
People define own functions.
But at least you can stop the action of it. GV Always be the until user agents bit. Think we need to tackle it in 3 ways. Define what people need to do to make pages accessible on a conceptual level. Then work with user agents to get them to get rid of quirks caused by past user agents.