1.3.4 Support Personalization (minimum) ยง <https://rawgit.com/w3c/wcag21/FPWD_review/guidelines/index.html#support-personalization-minimum> A Proposed ISSUE 1 This is a proposed Success Criterion that has not yet been formally approved by the Working Group. Discussion of the issue is available in Issue 6 <https://github.com/w3c/wcag21/issues/6> and Pull Request 125 <https://github.com/w3c/wcag21/pull/125>.
Contextual information <https://rawgit.com/w3c/wcag21/FPWD_review/guidelines/index.html#dfn-contextual-information> and author settable properties <https://rawgit.com/w3c/wcag21/FPWD_review/guidelines/index.html#dfn-author-settable-properties> of regions, critical features <https://rawgit.com/w3c/wcag21/FPWD_review/guidelines/index.html#dfn-critical-features> and important information <https://rawgit.com/w3c/wcag21/FPWD_review/guidelines/index.html#dfn-important-information>are programmatically determinable so that personalization <https://rawgit.com/w3c/wcag21/FPWD_review/guidelines/index.html#dfn-personalization> is available. Exception: Information does not need to be exposed when there is not a standardized technique <https://rawgit.com/w3c/wcag21/FPWD_review/guidelines/index.html#dfn-standardized-technique> of exposing it in the technology or the platform. standardized technique Proposed part of a W3C standard, the standard of the native platform, or a WCAG technique (please note: other success criterion have better definitions for this term) I think we should create a standardized technique eh? Gregg Gregg C Vanderheiden [email protected]
_______________________________________________ Architecture mailing list [email protected] http://lists.gpii.net/mailman/listinfo/architecture
