Standard being reported: Section 6: Web Content Accessibility Guidelines and Subsection Ten: Use interim solutions.
The standard may be accessed here.
Older browsers cannot always display assistive technologies correctly. Also, older assistive technologies have a harder time rendering information correctly. Changing the current window or popping up new windows can be disorienting to users as well. Consequently, it is advised that designers apply the checkpoints (none of which have a Priority 1 standing) until user agents (as the issue is on their end) address these particular issues. These checkpoints are not expected to be necessary in the future. The different checkpoints include: allowing users to turn off spawned windows; properly position labels for forms, provide a linear text alternative; include default place-holding characters in edit boxes and text areas; and include non-link printable characters between adjacent links.
This standard can be implemented fairly easy, and should certainly be implemented by those who have users using older browsers or technologies visiting their site on a regular basis. By following the checkpoints (mentioned above), it is fairly easy to help those using older technologies until adaptations are made by the developers of browsers and assistive technologies. As this probably won't be in the next set of guidelines, it isn't as critical as other guidelines.
Sorry...I just thought with the captain issue in question, I'd throw
in my name for consideration.
Pintel