WCAG 2.2 uses the same conformance model as WCAG 2.0. It is intended that sites that conform to WCAG 2.2 also conform to WCAG 2.0 and WCAG 2.1, which means they meet the requirements of any policies that reference WCAG 2.0 or WCAG 2.1, while also better meeting the needs of users on the current Web.
+WCAG 2.2 uses the same conformance model as WCAG 2.0. It is intended that sites that conform to WCAG 2.2 also conform to WCAG 2.0 and WCAG 2.1, which means they meet the requirements of any policies that reference WCAG 2.0 or WCAG 2.1, while also better meeting the needs of users on the current web.
Success criteria within this specification which the Working Group has identified possible implications for privacy, either by providing protections for end users or which are important for website providers to take in to consideration when implementing features designed to protect user privacy, are listed below. This list reflects the current understanding of the Working Group but other Success criteria may have privacy implications that the Working Group is not aware of at the time of publishing.
+Success criteria within this specification which the Working Group has identified possible implications for privacy, either by providing protections for end users or which are important for website providers to take in to consideration when implementing features designed to protect user privacy, are listed below. This list reflects the current understanding of the Working Group but other success criteria may have privacy implications that the Working Group is not aware of at the time of publishing.
Success criteria within this specification that may relate to privacy are:
Success criteria within this specification which the Working Group has identified possible implications for security, either by providing protections for end users or which are important for website providers to take in to consideration when implementing features designed to protect user security, are listed below. This list reflects the current understanding of the Working Group but other Success criteria may have security implications that the Working Group is not aware of at the time of publishing.
+Success criteria within this specification which the Working Group has identified possible implications for security, either by providing protections for end users or which are important for website providers to take in to consideration when implementing features designed to protect user security, are listed below. This list reflects the current understanding of the Working Group but other success criteria may have security implications that the Working Group is not aware of at the time of publishing.
Success criteria within this specification that may relate to security are:
text or number by which software can identify the function of a component within Web +
text or number by which software can identify the function of a component within web content
diff --git a/guidelines/terms/20/technology.html b/guidelines/terms/20/technology.html index 5a32eaf78f..e7d1cc6138 100644 --- a/guidelines/terms/20/technology.html +++ b/guidelines/terms/20/technology.html @@ -10,7 +10,7 @@Web content technologies may include markup languages, data formats, or programming languages that authors may use alone or in combination to create end-user experiences - that range from static web pages to synchronized media presentations to dynamic Web + that range from static web pages to synchronized media presentations to dynamic web applications.