This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
- Guideline 1.1, 1.2 This section says conform to WCAG. For P1 this definition, http://www.w3.org/TR/2004/WD-ATAG20-20041122/#priority-Relative-To-WCAG-Interface, includes the following in WCAG 1.0: 6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. [Priority 1] This is wrong and should be struck or should be written such that P1 can be satisfied for WCAG 1.0 or WCAG 2.0 P1. Any reference to WCAG 1.0 should be removed or modified. This WCAG 1.0 checkpoint is obsolete. I am concerned that this impacts both JavaScript generated content as well as XForms where, in fact, programmatic objects are bound to the data model and follow an active MVC architecture. This would appear that a mode should be available to turn active content off in the user agent and still work or that someone would need to provide an alternative page equivalent for this type of content although it is not how this would work in the case of forms which are active.