You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The guidelines provide guidance for people and organizations that produce digital assets and technology of varying size and complexity. This includes large, dynamic, and complex websites. Our intent is to provide guidance for a diverse group of stakeholders including content creators, browsers, authoring tools, assistive technologies, and more.
This is possibly poorly named, since 'Scope' isn't really a requirement. However, more broadly this sort of guidance does not belong in the standard but in supporting material. This may be a broader requirement of the W3C/WAI community rather than a specific requirement of the Guidelines.
The text was updated successfully, but these errors were encountered:
This is possibly poorly named, since 'Scope' isn't really a requirement.
Will be addressed through issue #44, to evaluate whether all requirements from WCAG 3 are testable.
However, more broadly this sort of guidance does not belong in the standard but in supporting material.
Is addressed through the revised text proposed for issue #224: "The guidelines provide guidance and a conformance model for people and organizations that produce digital assets and technology of varying size and complexity. This includes large, dynamic, and complex websites. The associated informative materials will include guidance for a diverse group of stakeholders including content creators, browsers, authoring tools, assistive technologies, and more."
This may be a broader requirement of the W3C/WAI community rather than a specific requirement of the Guidelines.
Core level guidance needs to be part of the WCAG 3 package, regardless which W3C/WAI group it comes from. Removing this part could result in this not being addressed.
Relates to:
This is possibly poorly named, since 'Scope' isn't really a requirement. However, more broadly this sort of guidance does not belong in the standard but in supporting material. This may be a broader requirement of the W3C/WAI community rather than a specific requirement of the Guidelines.
The text was updated successfully, but these errors were encountered: