From e169f4e62695e1bcd14c236e2cae6c0a235ae8f7 Mon Sep 17 00:00:00 2001 From: rmontgomery Date: Thu, 7 Nov 2024 12:54:39 -0500 Subject: [PATCH 01/49] first changes --- guidelines/index.html | 770 +++++++++++++++++++++--------------------- 1 file changed, 393 insertions(+), 377 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 958a032..d3e70c8 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -11,7 +11,7 @@

W3C Accessibility Guidelines (WCAG) 3.0 will provide a wide range of recommendations for making web content more accessible to users with disabilities. Following these guidelines will address many of the needs of users with blindness, low vision and other vision impairments; deafness and hearing loss; limited movement and dexterity; speech disabilities; sensory disorders; cognitive and learning disabilities; and combinations of these. These guidelines address accessibility of web content on desktops, laptops, tablets, mobile devices, wearable devices, and other web of things devices. The guidelines apply to various types of web content including static, dynamic, interactive, and streaming content; visual and auditory media; virtual and augmented reality; and alternative access presentation and control. These guidelines also address related web tools such as user agents (browsers and assistive technologies), content management systems, authoring tools, and testing tools.

-

Each guideline in this standard provides information on accessibility practices that address documented user needs of people with disabilities. Guidelines are supported by multiple outcomes to determine whether the need has been met. Guidelines are also supported by technology-specific methods to meet each outcome.

+

Each guideline in this standard provides information on accessibility practices that address documented user needs of people with disabilities. Guidelines are supported by multiple requirements and assertions to determine whether the need has been met. Guidelines are also supported by technology-specific methods to meet each outcome or assertion.

This specification is expected to be updated regularly to keep pace with changing technology by updating and adding methods, outcomes, and guidelines to address new needs as technologies evolve. For entities that make formal claims of conformance to these guidelines, several levels of conformance are available to address the diverse nature of digital content and the type of testing that is performed.

See WCAG 3 Introduction for an introduction and links to WCAG technical and educational material.

@@ -78,7 +78,8 @@

Section status levels

Guidelines

Summary -

The following guidelines are being considered for WCAG 3. They are currently a list of topics which we expect to explore more thoroughly in future drafts. The list includes current WCAG 2 guidance and additional requirements. The list will change in future drafts.

+

The following guidelines are being considered for WCAG 3. They are currently a list of topics which we expect to explore more thoroughly in future drafts. The list includes current WCAG 2 guidance and additional requirements. The list will change in future drafts.

+

Unless otherwise stated, requirements assume the content described is provided both visually and programmatically.

@@ -94,9 +95,10 @@

Guidelines

Please consider the following questions when reviewing this list of outcomes:

- From 5e86ac39a22c86b72531697bbee4033f6de9bb36 Mon Sep 17 00:00:00 2001 From: rmontgomery Date: Fri, 8 Nov 2024 12:17:16 -0500 Subject: [PATCH 02/49] updates to guidelines and css --- guidelines/guidelines.css | 12 +-- guidelines/index.html | 157 ++++++++++++++++++++++++-------------- 2 files changed, 105 insertions(+), 64 deletions(-) diff --git a/guidelines/guidelines.css b/guidelines/guidelines.css index ccdbeea..6ffdbfa 100644 --- a/guidelines/guidelines.css +++ b/guidelines/guidelines.css @@ -42,25 +42,25 @@ summary::after { a.internalDFN[title]:hover, .internalDFN[title]:active, a.internalDFN[title]:focus { cursor: help; } -.outcome h4 { +.provision h4, .provision h5 { font-style: normal; font-weight: normal; font-size: 100%; color: #005A9C; } -.guideline-text, .outcome-text { - font-size: 11 0%; +.guideline-text, provision-text { + font-size: 110%; margin-top: 0; margin-bottom: 0; text-indent: 50px; } -.guideline h3, .outcome h4 { +.guideline h3, .provision h4, .provision h5 { width: 100%; margin-bottom: 0; margin-top: .4em; } -.guideline h3 { -font-size: 120%; +.guideline h3, .guideline h4 { +font-size: 110%; color: black; } diff --git a/guidelines/index.html b/guidelines/index.html index 919dc82..386aa7e 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -113,23 +113,24 @@

Guidelines

Animation and movement

+

Avoid physical harm

Users do not experience physical harm from content.

-

Audio shifting

+
Audio shifting

Audio shifting designed to create a perception of motion is avoided; or can be paused or prevented.

Needs additional research

-

Flashing and strobing

+
Flashing and strobing

Flashing or strobing beyond thresholds defined by safety standards are avoided; or can be paused or prevented.

-

Motion

+
Motion

Visual motion and pseudo-motion that lasts longer than 5 seconds is avoided; or can be paused or prevented.

Needs additional research

-

Motion from Interaction

+
Motion from Interaction

Visual motion and pseudo-motion triggered by interaction is avoided; or can be prevented, unless the animation is essential to the functionality or the information being conveyed.

Needs additional research

@@ -137,31 +138,28 @@

Motion from Interaction

-

Errors

+

Error handling

-

Users know about errors when they occur and know what to do to fix them.

+

Correct mistakes

+

Users know about and can correct mistakes.

-

Allow automated entry

-

Automated input from user agents, 3rd party tools, or copy-and-paste is supported.

-
-
-

Error association

+
Error association

Error notifications are programmatically associated with the error source.

-

Error identification

+
Error identification

Errors are visually identifiable without relying on only text, only color, or only symbols.

-

Error notification

+
Error notification

Error notifications are provided when an error occurs that describe the error and either provide instructions to fix the error or state that the system is at fault.

-

Persistent error notification

+
Persistent error notification

Error notifications persist until the user dismisses them or the error is resolved.

-

Visible error

+
Visible error

Error notifications are visually collocated with the source of the error within the viewport, or provide a link to the source of the error which, when activated, moves the viewport to the error.

Needs additional research

@@ -170,54 +168,109 @@

Visible error

-

Processes and task completion

-
+

Process and task completion

+
+

Unnecessary steps

+

Users can complete tasks without unnecessary steps.

+
+

Cognitive tasks

+

Users can complete tasks without needing to memorize nor complete advanced cognitive tasks.

+
+

Allow automated entry

+

Automated input from user agents, 3rd party tools, or copy-and-paste is supported.

+
+

Users can complete tasks without needing to memorize nor complete advanced cognitive tasks.

+
+

No cognitive tests

+

Tasks, including login/authentication, can be completed without puzzles, calculations, or other cognitive tests (essential exceptions would apply).

+
+
+

No memorization

+

Tasks can be completed without memorizing and recalling information from previous stages of the process.

+

Needs additional research

+
+
+ +

Adequate time

-

Enough time is provided to read and use content.

-

Needs additional research

+

Users have enough time to read and use content.

+
+
+
Adjust timing at start
+

For each process with a time-limit, a mechanism exists to disable or extend the limit before the time-limit starts.

+
+
+
Adjust timing at timeout
+

For each process with a time-limit, a mechanism exists to disable or extend the time-limit at timeout.

+
+
+
Disable timeout
+

For each process with a time-limit, a mechanism exists to disable the limit.

+
+
-
-

Action required

-

The interface indicates when user input or action is required to proceed.

+ +
+

Unnecessary steps

+

Users can complete tasks without unnecessary steps.

+
+

Optional information

+

Processes can be completed without being forced to read or understand unnecessary content.

+
+
+

Optional input

+

Processes can be completed without entering unnecessary information.

+
+
-

Avoid manipulation

-

Tasks can be completed without navigating misinformation or redirections.

+

Misinformation

+

Processes can be completed without navigating misinformation or redirections.

Needs additional research

-

Go back in process

-

The interface supports stepping backwards in a process and returning to the current point without data loss.

+

Preselections

+

Preselected options are visible by default during process completion without additional interactions.

-

Inform at start

-

Information needed to complete a multi-step process is provided at the start of the process, including: -

  • estimated time or number of steps it might take,
    • -
  • details of any resources needed to perform the task, and
    • -
  • overview of the process and next step.
-

+

Deceptive controls

+

Interactive components are not deceptively designed.

+

Needs additional research

-

No cognitive tests

-

Tasks, including login/authentication, can be completed without puzzles, calculations, or other cognitive tests (essential exceptions would apply).

+

Exploitive behaviors

+

Process completion does not include exploitive behaviors.

+

Needs additional research

-

No memorization

-

Tasks can be completed without memorizing and recalling information from previous stages of the process.

+

Redirection

+

A mechanism is available to prevent fraudulent redirection or alert users they are exiting the site.

Needs additional research

-
+
+ +
-

Optimized processes

-

Tasks can be completed without reading or understanding unnecessary content.

+

Action required

+

The interface indicates when user input or action is required to proceed.

+ + +
-

Optional information

-

Tasks can be completed without entering unnecessary information.

+

Go back in process

+

The interface supports stepping backwards in a process and returning to the current point without data loss.

-

Preselections

-

Preselections are visible during task completion.

+

Inform at start

+

Information needed to complete a multi-step process is provided at the start of the process, including: +

  • estimated time or number of steps it might take,
    • +
  • details of any resources needed to perform the task, and
    • +
  • overview of the process and next step.
+

+ + +

Save progress

Data entry and other task completion processes allow saving and resuming from the current step in the task.

@@ -372,11 +425,7 @@

Control importance

Control updates

Changes to control or input name, roles, values or states are visually and programmatically indicated.

-
-

Deceptive controls

-

Controls and interactions are not deceptively designed (invisible, incorrectly labeled, placement, etc.).

-

Needs additional research

-
+

Distinguishable controls

Controls are visually distinct from static content and include visual cues on how to use them.

@@ -649,16 +698,8 @@

Disability information privacy

Disability information is not disclosed to or used by third parties and algorithms (including AI).

Needs additional research

-
-

Exploitive behaviors

-

Task completion does not include exploitive behaviors.

-

Needs additional research

-
-
-

Redirection

-

A mechanism is available to prevent fraudulent redirection or alert users they are exiting the site.

-

Needs additional research

-
+ +

Sensitive information

Prompts to hide and remove sensitive information from observers are available.

From 5c1f599ec9b19429425a66655a1e82c00c0575cb Mon Sep 17 00:00:00 2001 From: rachaelbradley Date: Mon, 11 Nov 2024 07:51:29 -0500 Subject: [PATCH 03/49] guideline updates --- guidelines/index.html | 501 ++++++++++++++++++++++++++++-------------- 1 file changed, 332 insertions(+), 169 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 386aa7e..281d596 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -121,7 +121,7 @@
Audio shifting

Needs additional research

-
Flashing and strobing
+
Flashing

Flashing or strobing beyond thresholds defined by safety standards are avoided; or can be paused or prevented.

@@ -144,7 +144,7 @@

Correct mistakes

Users know about and can correct mistakes.

Error association
-

Error notifications are programmatically associated with the error source.

+

Error notifications are programmatically associated with the error source so that users can access the error information while focused on the source of the error.

Error identification
@@ -152,10 +152,10 @@
Error identification
Error notification
-

Error notifications are provided when an error occurs that describe the error and either provide instructions to fix the error or state that the system is at fault.

+

Errors that can be automatically detected are identified and described to the user.

-
Persistent error notification
+
Persistent errors

Error notifications persist until the user dismisses them or the error is resolved.

@@ -170,23 +170,19 @@
Visible error

Process and task completion

-

Unnecessary steps

-

Users can complete tasks without unnecessary steps.

-
-

Cognitive tasks

+

Avoid cognitive tasks

Users can complete tasks without needing to memorize nor complete advanced cognitive tasks.

-

Allow automated entry

-

Automated input from user agents, 3rd party tools, or copy-and-paste is supported.

+
Allow automated entry
+

Automated input from user agents, 3rd party tools, or copy-and-paste is not prevented.

-

Users can complete tasks without needing to memorize nor complete advanced cognitive tasks.

-

No cognitive tests

-

Tasks, including login/authentication, can be completed without puzzles, calculations, or other cognitive tests (essential exceptions would apply).

+
No cognitive tests
+

Processes, including login/authentication, can be completed without puzzles, calculations, or other cognitive tests (essential exceptions would apply).

-

No memorization

-

Tasks can be completed without memorizing and recalling information from previous stages of the process.

+
No memorization
+

Processes can be completed without memorizing and recalling information from previous stages of the process.

Needs additional research

@@ -195,7 +191,6 @@

No memorization

Adequate time

Users have enough time to read and use content.

-
Adjust timing at start

For each process with a time-limit, a mechanism exists to disable or extend the limit before the time-limit starts.

@@ -208,7 +203,6 @@
Disable timeout

For each process with a time-limit, a mechanism exists to disable the limit.

-

Unnecessary steps

@@ -223,15 +217,9 @@

Optional input

-
-

Misinformation

-

Processes can be completed without navigating misinformation or redirections.

-

Needs additional research

-
-
-

Preselections

-

Preselected options are visible by default during process completion without additional interactions.

-
+
+

Avoid deception

+

Users do not encounter deception when completing tasks, unless essential to the task.

Deceptive controls

Interactive components are not deceptively designed.

@@ -243,243 +231,435 @@

Exploitive behaviors

Needs additional research

-

Redirection

+
Misinformation
+

Processes can be completed without navigating misinformation or redirections.

+

Needs additional research

+
+
+
Preselections
+

Preselected options are visible by default during process completion without additional interactions.

+
+
+
Redirection

A mechanism is available to prevent fraudulent redirection or alert users they are exiting the site.

Needs additional research

-
- +
+
+
+

Retain information

+

Users do not have to reenter information or redo work.

-

Action required

-

The interface indicates when user input or action is required to proceed.

+
Go back in process
+

In a multistep process, the interface supports stepping backwards in a process and returning to the current point without data loss.

+
+
Redundant entry
+

Information previously entered by or provided to the user that is required to be entered again in the same process is either auto-populated, or available for the user to select.

+
+
+
Save progress
+

Data entry and other task completion processes allow saving and resuming from the current step in the task.

+
+
- - +
+

Complete tasks

+

Users understand how to complete tasks.

-

Go back in process

-

The interface supports stepping backwards in a process and returning to the current point without data loss.

+
Action required
+

In a process, the interface indicates when user input or action is required to procceed to the next step. c

-

Inform at start

+
Inform at start of process

Information needed to complete a multi-step process is provided at the start of the process, including: -

  • estimated time or number of steps it might take,
    • +
    • number of steps it might take (if known in advance),
    • details of any resources needed to perform the task, and
    • overview of the process and next step.

+
+
Steps and instructions
+

The steps and instructions needed to complete a multistep process are available

+
+
+
+
+

Image and media alternatives

+
+

Image alternatives

+

Users have equivalent alternatives for images.

+ +

Foundational

+

For each image: +

    +
  1. Would removing the image impact how people understand the page? + +
    2. -
    -

    Save progress

    -

    Data entry and other task completion processes allow saving and resuming from the current step in the task.

    +
  2. Is the image presented in a way that is available to user agents and assistive technology? + +
    3. + +
  3. Is an equivalent text alternative available for the image? + +
    4. +
+

+ +
+
Decorative image
+

Decorative image is programmatically hidden.

+
+
+
Content image
+

Equivalent text alternative is available for image that conveys content.

+
+
Detectable image
+

Image is programmatically detectable.

+
+ + +

Supplemental

-

Steps and direction

-

The steps and directions needed to complete a process are visually and programmatically indicated.

+
Image role
+

The role and importance of the image is programmatically indicated.

-

Task completion documentation

-

For tasks where labels and instructions cannot provide sufficient instructions for completion, detailed documentation on task completion is available.

-

Needs additional research

+
Image type
+

The type of image (photo, icon, etc.) is indicated.

-
- -
-

Image and media alternatives

-

AI editable

+
Editable Alternatives

Auto generated text descriptions are editable by content creator.

Needs additional research

+ +

Assertions

-

Audio alternative in preferred language

-

Equivalent audio alternatives are available in the preferred language.

+
Style Guide
+

Text alternatives follow an organizational style guide.

+
+ +
+

Media alternatives

+

Users have equivalent alternatives for media content.

-

Audio descriptions

-

Equivalent visual alternatives are available as synchronized audio in the media.

+
Audio descriptions
+

Where there is visual content in media, there is an equivalent synchronized audio track.

-

Captions

-

Equivalent audio alternatives are available as synchronized captions in the media.

+
Captions
+

Where there is audio content in media, there are equivalent synchronized captions.

-

Complex image alternative

-

Equivalent text alternatives are available for complex images.

+
Descriptive transcripts
+

A transcript is available whenever audio or visual alternatives are used.

-

Context in image alternative

-

Image alternatives include context.

+
Findable media alternatives
+

Media that has the desired media alternatives (captions, audio descriptions, and descriptive transcripts) can be found. (Needs additional research).

Needs additional research

-

Decorative image alternative

-

Equivalent descriptive text alternatives are available for decorative images.

Preferred language +

Equivalent audio alternatives are available in the preferred language.

Needs additional research

-

Descriptive transcripts

-

Equivalent audio and visual alternatives to audio and video alternatives are available in descriptive transcripts.

+

Non-verbal cues

+

Media alternatives explain nonverbal cues, such as tone of voice, facial expressions, body gestures, or music with emotional meaning.

+

Needs additional research

+
+ + +
+

Nontext alternatives

+

Users have alternatives available for non-text, non-image content that conveys context or meaning.

-

Finding media alternatives

-

Media that has the desired media alternatives (captions, audio descriptions, and descriptive transcripts) can be found.

+
Nontext content
+

Equivalent text alternatives are available for non-text, non-image content that conveys context or meaning.

Needs additional research

+
+ +
+

Figure captions

+

Users can view figure captions even if not focused at figure.

+
-

Identify autogenerated text

-

Auto generated text alternatives are identified.

+
Persistent captions
+

Figure captions persist or can be made to persist even if the focus moves away.

Needs additional research

+
+ +
+

Single Sense

+

Users have content that does not rely on a single sense or perception.

-

Image alternatives

-

Equivalent text alternatives are available for images that convey content.

+
Use of hue
+

Information conveyed by graphical elements does not rely on hue.

+

Needs additional research

-

Image role

-

The role and importance of images are programmatically indicated.

+
Use of visual depth
+

Information conveyed with visual depth is also conveyed programmatically and/or through text.

Needs additional research

-

Image type

-

The type of image (photo, icon, etc.) is indicated.

-

Needs additional research

+
Use of sound
+

Information conveyed with sound is also conveyed programmatically and/or through text.

-

Images-of-Text alternatives

-

Equivalent text alternatives are available for images of text.

+
Use of spatial audio
+

Information that is conveyed with spatial audio is also conveyed programmatically and/or through text.

+
+
+
+ +
+

Interactive components

+
+

Keyboard Focus Appearance

+

Users have a visual indicator for the Keyboard Focus that is sufficient for them.

+ +

Foundational

+ +

For each focusable item: +

    +
  1. Is the user-agent default focus indicator used? + +
    2. + +
  2. Is the user-agent default focus indicator used, and meets contrast across backgrounds? + +
    3. + +
  3. Is the focus indicator defined by the author? + +
    4. +
+

+ +
+
Custom indicator
+

A custom focus indicator is used with sufficient size, change of contrast, adjacent contrast, distinct style and adjacecy.

+
+
+
Default indicator
+

The platform’s default indicator is used, and where the backgrounds are changed, the indicator contrast is checked.

+
+
+
User agent default indicator
+

Focusable item uses the user agent default indicator.

+ +

Supplemental

-

Non-text alternatives

-

Equivalent text alternatives are available for non-text, non-image content that conveys context or meaning.

+
Supplimentary indicators
+

@@

+ +

Assertions

-

Non-verbal cues

-

Media alternatives explain nonverbal cues, such as tone of voice, facial expressions, body gestures, or music with emotional meaning.

-

Needs additional research

+
Style Guide
+

Focus indicators follow an organizational style guide.

+
+
+ +
+

Pointer Focus Appearance

+

Users have a visual indicator for the Pointer Focus that is sufficient for them.

+
+
Pointer visible
+

There is a visible indicator of pointer focus.

+
+ +
+

Navigating content

+

Users can determine where they are and move through content (including interactive elements) in a systematic and meaningful way regardless of input or movement method.

-

Persistent figure captions

-

Figure captions persist or can be made to persist.

-

Needs additional research

+
Focus in viewport
+

The focus does not move to a position outside the current viewport, unless a mechanism is available to return to the previous focus point.

-

Use of color

-

Information is not conveyed with color alone.

+
Focus retention
+

A user can focus on a content “area,” such as a modal or pop-up, then resume their view of all content using a limited number of steps.

-

Use of visual depth

-

Information is not conveyed with visual depth alone.

-

Needs additional research

+
Keyboard focus order
+

The keyboard focus moves sequentially through content in an order and way that preserves meaning and operability.

-

Use of sound

-

Information is not conveyed with sound alone.

+
Restore focus
+

When the focus is moved by the content into a temporary change of view (e.g. a modal), the focus is restored to its previous location when the view is restored.

-

Use of spatial audio

-

Information is not conveyed with spatial audio alone.

-
+
Relevant focus
+

The focus order does not include repetitive, hidden, or static elements.

+
-
-

Interactive components

+

Expected behavior

+

Users have interactive components that behave as expected.

-

Behavior of controls

-

Controls and inputs with the same functionality behave consistently.

+
Consistent Interaction
+

Interactive components with the same functionality behave consistently.

-

Change focus with pointer device

-

Selecting an element with a ‘pointer’ sets the focus to that element.

+
Consistent labels
+

Interactive components with the same functionality have consistent labels.

-

Control labels

-

Controls have visible labels that identify the purpose of the controls.

+
Consistent visual design
+

Interactive components that have similar function and behavior have a consistent visual design.

+
+
+
Control location
+

Interactive components are visually and programmatically located in conventional locations.

+

Needs additional research

+
+
+
Conventions
+

Interactive components follow established conventions.

+

Needs additional research

+
+
+
Familiar component
+

Conventional interactive components are used.

+
+ + +
+

Control information

+

Users have information about interactive components that is identifiable and usable visually and using assistive technology.

+
-

Conventions

-

Controls follow established conventions.

+
Control importance
+

The importance of interactive components is indicated.

Needs additional research

-

Consistent labels

-

Controls and inputs with the same functionality have consistent labels.

+
Control labels
+

Interactive components have visible labels that identify the purpose of the component.

-

Matching labels

-

Controls and inputs with the same functionality have consistent labels.

+
Control updates
+

Changes to interactive components’ names, roles, values or states are visually and programmatically indicated.

-

Field constraints

+
Distinguishable controls
+

Interactive components are visually distinguishable without interaction from static content and include visual cues on how to use them.

+
+
+
Field constraints

Field constraints and conditions (required line length, date format, password format, etc) are available.

-

Control importance

-

The importance of controls is visually and programmatically indicated.

-

Needs additional research

+
Input labels
+

Inputs have visible labels that identify the purpose of the input.

-

Control updates

-

Changes to control or input name, roles, values or states are visually and programmatically indicated.

+
Labels match
+

The programmatic name includes the visual label.

-
-

Distinguishable controls

-

Controls are visually distinct from static content and include visual cues on how to use them.

+
Name, role, value, state
+

Accurate names, roles, values, and states are available for interactive components.

+
+
+ + +
+

Input / Operation

+
+

Input Operation

+

Users can use different input techniques and combinations and switch between them.

-

Hover information

-

Components which trigger a 'change of context' are indicated, or the change of context can be reversed.

+
Concurrent inputs
+

Any input modality available on a platform can be used concurrently.

-

Interaction indicators contrast

-

Interaction indicators meet a ‘minimum contrast ratio text’ and meet a minimum thickness.

-

Needs additional research

+
Hover information
+

Users can dismiss additional content (triggered by hover) without moving the pointer, unless the additional content communicates an input error or does not obscure or replace other content.

-

Input control

+
Input control

Interactive components are available to all navigation and input methods.

+
+ +
+

Content changes

+

Users are aware of changes to content or context.

-

Name, role, value, state

-

Accurate names, roles, values, and states are available for interactive components.

+
Notify about change
+

Changes in content and updates notify users, regardless of the update speed. +

-

Non-Text contrast

-

Visual information required to identify user interface components and states meet a ‘minimum contrast ratio test’, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author.

-

Needs additional research

+
Notify on change
+

Notification is provided when viewing content that was previously viewed is changed.

-

Notify on change

-

Notification is provided when previously viewed content changes.

+
Inform before activation
+

Interactive components that can alter the order of content convey their purpose prior to activation, and convey their impact on content order when activated.

-

Notify before activation

-

Controls that can alter the order of content convey their purpose prior to activation, and convey their impact on content order when activated.

+
Reverse change of context
+

Components that trigger a 'change of context' are indicated, or the change of context can be reversed.

+
+ +
+

Target size

+

Users are not required to accurately position a pointer in order to view or operate content.

-

Restore focus

-

The focus or point of regard is restored to its previous location after a temporary change of view.

+
Target size minimum
+

The combined target size and spacing to adjacent targets is at least 24x24 pixels +

-

Relevant focus

-

The focus order does not include repetitive, hidden, or static elements.

+
Target size optimum
+

The combined target size and spacing to adjacent targets is at least 48x48 pixels.

+
+ + + +
-

Target size

-

All functionality can be used without needing to accurately position a pointer.

+

Interaction indicators contrast

+

Interaction indicators meet a ‘minimum contrast ratio text’ and meet a minimum thickness.

+

Needs additional research

-

Visual design of controls

-

Controls that have similar function and behavior have a consistent visual design.

-
+

Non-Text contrast

+

Visual information required to identify user interface components and states meet a ‘minimum contrast ratio test’, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author.

+

Needs additional research

+
-
-

Input / operation

+ + +

Comparable keyboard effort

The number of input commands required to complete a task using the keyboard is similar to the number of input commands when using other input modalities.

@@ -489,10 +669,6 @@

Comparable keyboard effort

Consistent keyboard interaction

Keyboard interface interactions are consistent.

-
-

Focus in viewport

-

The focus does not move to a position outside the current viewport, unless a mechanism is available to return to the previous focus point.

-

Gestures & dragging

Every function that can be operated by a pointer, can be operated by a ‘single pointer input’ or a sequence of single pointer inputs, without limitations on timing for input.

@@ -501,10 +677,7 @@

Gestures & dragging

Keyboard commands

Application keyboard commands do not conflict with platform commands, and the user is informed of non-standard commands.

-
-

Keyboard focus location

-

The keyboard focus is visually indicated.

-
+

Keyboard only

All functionality can be performed through the keyboard interface only, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

@@ -513,6 +686,10 @@

Keyboard only

No keyboard trap

If keyboard focus can be moved to an interactive component, then the keyboard focus can be moved away from that component.

+
+

Change focus with pointer device

+

Selecting an element with a ‘pointer’ sets the focus to that element.

+

Pointer-agnostic

Functionality which supports pointers can be used by any pointing device supported by the platform.

@@ -546,10 +723,7 @@

Use without body movement

Use without device movement

All functionality can be done without needing to move the hardware device.

-
-

Varied inputs

-

Any input modality available on a platform can be used concurrently.

-
+
@@ -580,11 +754,7 @@

Consistent order

Content orientation

Content orientation allows the user to read the language presented without changing head position.

-
-

Control location

-

Controls are visually and programmatically located in an expected location.

-

Needs additional research

-
+

Current location

The current location within the view, multi-step process, and product is visually and programmatically indicated.

@@ -603,10 +773,6 @@

Distinguishable sections

Familiar components and layout

Common components and layouts are used.

-
-

Focus retention

-

A user can focus on a content “area,” such as a modal or pop-up, then resume their view of all content using a limited number of steps.

-

Indicate 3rd party content

Third party content (AI, Advertising, etc.) is visually and programmatically indicated.

@@ -621,10 +787,7 @@

Interface redesign

Multistep process

Provides context that orients the user in a site or multi-step process.

-
-

Notification of change

-

Changes in content and updates notify users, regardless of the update speed.

-
+

Order of content

Related information is grouped together within a visual and programmatic structure.

From 809a32d15438cd87c28f6fced9ea105358bd8c08 Mon Sep 17 00:00:00 2001 From: rachaelbradley Date: Mon, 11 Nov 2024 11:31:31 -0500 Subject: [PATCH 04/49] Finished guideline updates --- guidelines/index.html | 645 ++++++++++++++++++++++++------------------ 1 file changed, 366 insertions(+), 279 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 281d596..17341b7 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -430,7 +430,7 @@
Use of spatial audio

Interactive components

Keyboard Focus Appearance

-

Users have a visual indicator for the Keyboard Focus that is sufficient for them.

+

Users can see which element has keyboard focus.

Foundational

@@ -447,8 +447,7 @@

Keyboard Focus Appearance

  • Is the focus indicator defined by the author? -
    • .
      • -
    • Yes, indicator must meet Custom focus indicators. Stop.
      • + @@ -482,7 +481,7 @@
      Style Guide

      Pointer Focus Appearance

      -

      Users have a visual indicator for the Pointer Focus that is sufficient for them.

      +

      Users can see the location of the pointer focus.

      Pointer visible

      There is a visible indicator of pointer focus.

      @@ -534,6 +533,7 @@
      Control location

      Interactive components are visually and programmatically located in conventional locations.

      Needs additional research

      +
      Conventions

      Interactive components follow established conventions.

      @@ -543,6 +543,9 @@
      Conventions
      Familiar component

      Conventional interactive components are used.

      +
      Reliable positioning
      +

      Interactive components retain their position unless a user changes the viewport or moves the component.

      +
      @@ -576,7 +579,7 @@
      Input labels

      Inputs have visible labels that identify the purpose of the input.

    • -
    Labels match
    +
    Label in name

    The programmatic name includes the visual label.

    @@ -642,506 +645,590 @@
    Target size optimum
    - - - +
    +

    Keyboard operation

    +

    Users can navigate and operate content using only the keyboard focus.

    -

    Interaction indicators contrast

    -

    Interaction indicators meet a ‘minimum contrast ratio text’ and meet a minimum thickness.

    +
    Comparable keyboard effort
    +

    The number of input commands required to complete a task using the keyboard is similar to the number of input commands when using other input modalities.

    Needs additional research

    -

    Non-Text contrast

    -

    Visual information required to identify user interface components and states meet a ‘minimum contrast ratio test’, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author.

    -

    Needs additional research

    -
    -
    - - - - -
    -

    Comparable keyboard effort

    -

    The number of input commands required to complete a task using the keyboard is similar to the number of input commands when using other input modalities.

    -

    Needs additional research

    +
    Conflicting keyboard commands
    +

    Authored keyboard commands do not conflict with platform commands or they can be remapped.

    -

    Consistent keyboard interaction

    -

    Keyboard interface interactions are consistent.

    +
    Consistent keyboard interaction
    +

    Keyboard interface interactions are consistent.

    -

    Gestures & dragging

    -

    Every function that can be operated by a pointer, can be operated by a ‘single pointer input’ or a sequence of single pointer inputs, without limitations on timing for input.

    +
    Keyboard mode
    +

    If the keyboard is non-hardware (such as a virtual keyboard), the keyboard input mode is indicated.

    -

    Keyboard commands

    -

    Application keyboard commands do not conflict with platform commands, and the user is informed of non-standard commands.

    +
    Keyboard only
    +

    All functionality must be accessible through the keyboard, except when a task requires input based on the user's specific input action.

    -
    -

    Keyboard only

    -

    All functionality can be performed through the keyboard interface only, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

    +
    No keyboard trap
    +

    If keyboard focus can be moved to an interactive component, then the keyboard focus can be moved away from that component, or the component can be dismissed, with focus returning to the previous point.

    -

    No keyboard trap

    -

    If keyboard focus can be moved to an interactive component, then the keyboard focus can be moved away from that component.

    +
    Non-standard commands
    +

    The user is informed of non-standard authored keyboard commands.

    +
    + +
    +

    Gestures

    +

    Users are not required to use gestures or dragging to view or operate content.

    -

    Change focus with pointer device

    -

    Selecting an element with a ‘pointer’ sets the focus to that element.

    +
    Change focus with pointer device
    +

    Selecting an interactive component with a ‘pointer’ sets the focus to that element.

    -

    Pointer-agnostic

    -

    Functionality which supports pointers can be used by any pointing device supported by the platform.

    +
    Complex pointer inputs
    +

    Every function that can be operated by a pointer, can be operated by a ‘single pointer input’ or a sequence of single pointer inputs without requiring certain timing.

    -

    Pointer cancellation

    -

    Pointer cancellation is consistent.

    +
    Pointer-agnostic
    +

    Functionality which supports pointers is available to any pointer device supported by the platform.

    -

    Pointer location

    -

    Users are able to determine where the pointer is located.

    +
    Pointer cancellation
    +

    The method of pointer cancellation is consistent.

    -

    Specific pressure

    -

    Click activation using a pointer device does not require applying a specific pressure.

    +
    Specific pressure
    +

    Where specific pressures are used, they can be adjusted and/or disabled without loss of function.

    Needs additional research

    -

    Speed insensitive

    -

    Use of a pointer does not require a particular speed of pointer movement or click activation.

    +
    Speed insensitive
    +

    Where specific speeds are used, they can be adjusted and/or disabled without loss of function.

    +

    Needs additional research

    +
    + +
    +

    Motion input

    +

    Users are not required to move their bodies or devices to operate functionality.

    -

    Keyboard mode

    -

    The keyboard input mode is indicated.

    +
    Use without body movement
    +

    All functionality that requires full or gross body movement may also be accomplished with a standard input device.

    -

    Use without body movement

    -

    All functionality can be done without needing to move their body, except for accessibility supported input devices.

    +
    Use without device movement
    +

    All functionality can be completed without reorienting or repositioning hardware devices.

    -

    Use without device movement

    -

    All functionality can be done without needing to move the hardware device.

    -
    - +
    Interactive component contrast
    +

    Visual information required to identify user interface components and states meet a ‘minimum contrast ratio test’, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author.

    +

    Needs additional research

    +
    + - -
    +

    Layout

    +
    +

    Relationships

    +

    Users can determine relationships between content both visually and using assistive technologies.

    -

    Clear navigation

    -

    Navigation elements are visually and programmatically differentiated from static content.

    -
    -
    -

    Clear relationships

    +
    Clear relationships

    The relationships between parts of the content is clearly indicated.

    -

    Clear starting point

    +
    Clear starting point

    The starting point or home is visually and programmatically labeled.

    -

    Citation

    -

    The source of the interface and primary content is visually and programmatically indicated.

    +
    Distinguishable relationships
    +

    Relationships that convey meaning between pieces of content are programmatically determinable. Note: Examples of relationships include items positioned next to each other, arranged in a hierarchy, or visually grouped.

    Needs additional research

    -

    Consistent order

    -

    The order of content and interactions remain consistent throughout a workflow.

    -
    -
    -

    Content orientation

    -

    Content orientation allows the user to read the language presented without changing head position.

    -
    - -
    -

    Current location

    -

    The current location within the view, multi-step process, and product is visually and programmatically indicated.

    -
    -
    -

    Distinguishable relationships

    -

    Meaningful associations between distinct pieces of content are programmatically determinable.

    -

    Needs additional research

    -
    -
    -

    Distinguishable sections

    +
    Distinguishable sections

    Sections are visually and programmatically distinguishable.

    Needs additional research

    +
    + + +
    +

    Recognizable layouts

    +

    Users have consistent and recognizable layouts available.

    -

    Familiar components and layout

    -

    Common components and layouts are used.

    +
    Consistent order
    +

    The relative order of content and interactions remain consistent throughout a workflow. Note: Relative order means that content can be added or removed, but repeated items are in the same order relative to each other.

    -

    Indicate 3rd party content

    -

    Third party content (AI, Advertising, etc.) is visually and programmatically indicated.

    -

    Needs additional research

    +
    Familiar layout
    +

    Conventional layouts are available.

    -

    Interface redesign

    -

    When interfaces dramatically change (due to redesign), a mechanism to learn the new interface or revert to the older design is available.

    -

    Needs additional research

    +
    Information about options
    +

    Information required to understand options is visually and programmatically associated with the options.

    -

    Multistep process

    -

    Provides context that orients the user in a site or multi-step process.

    +
    Related information
    +

    Related information is grouped together within a visual and programmatic structure.

    +
    +
    +

    Orientation

    +

    Users can determine their location in content both visually and using assistive technologies.

    -

    Order of content

    -

    Related information is grouped together within a visual and programmatic structure.

    +
    Current location
    +

    The current location within the view, multi-step process, and product is visually and programmatically indicated.

    +

    Needs additional research

    -

    Organized content

    +
    Multistep process

    Provides context that orients the user in a site or multi-step process.

    -
    -

    Related information

    -

    Information required to understand options is adjacent to the options.

    -
    -

    Reliable positioning

    -

    Interactive components retain their position unless a user changes the viewport or moves the component.

    +
    +
    Contextual information
    +

    Provide contextual information to help the user orient within the product.

    +
    + +
    +

    Structure

    +

    Users can understand and navigate through the content using structure.

    -

    Section headers

    -

    Sections of content have well structured, understandable visual and programmatic headings.

    -
    +
    Section labels
    +

    Major sections of content have within them well structured, understandable visual and programmatic headings.

    +
    -

    Section length

    -

    Content is organized into short sections of related content.

    +
    Section length
    +

    Content is organized into short sections of related content.

    Needs additional research

    -

    Section purpose

    +
    Section purpose

    The purpose of each section of the content is clearly indicated.

    -

    Visual stimulation

    -

    Use does not cause visual overstimulation.

    -

    Needs additional research

    -
    +
    Single idea
    +

    The number of concepts within a segment of text is minimized.

    +
    -

    White spacing

    +
    White spacing

    Whitespace separates chunks of content.

    +
    +
    Title
    +

    Content has a title or high-level description.

    +
    +
    +
    Lists
    +

    Three or more items of related data are presented as bulleted or numbered lists.

    +
    +
    +
    Numbered steps
    +

    Steps in a multi-step process are numbered.

    +
    -
    -

    Consistency across views

    +
    + +
    +

    Consistency across views

    +
    +

    Navigation

    +

    Users have consistent and alternative methods for navigation.

    -

    Consistent navigation

    +
    Consistent navigation

    Navigation elements remain consistent across views within the product.

    -

    Multiple ways

    +
    Multiple ways

    The product provides at least two ways of navigating and finding information (Search, Scan, Site Map, Menu Structure, Breadcrumbs, contextual links, etc).

    -

    Persistent navigation

    -

    Navigation features remain available, regardless of screen size and magnification (responsive design).

    +
    Persistent navigation
    +

    Navigation features are available regardless of screen size and magnification (responsive design)

    -
    -

    Policy and Protection

    -
    -

    Algorithm bias

    -

    Algorithms (including AI) used are not biased against people with disabilities.

    +
    +

    Policy and Protection

    +
    +

    Third Party Content

    +

    Users understand who created the content.

    +
    +
    Citation
    +

    The author or source of the primary content is visually and programmatically indicated.

    Needs additional research

    -
    -

    Clear agreement

    -

    The interface clearly indicates when a user is entering an agreement or submitting data.

    +
    Indicate 3rd party content
    +

    Third party content (AI, Advertising, etc.) is visually and programmatically indicated.

    Needs additional research

    -

    Disability information privacy

    -

    Disability information is not disclosed to or used by third parties and algorithms (including AI).

    +
    Obscuring primary content
    +

    Advertising and other third-party content that obscures the primary content can be moved or removed without interacting with the advertising or third-party content.

    Needs additional research

    +
    - -
    -

    Sensitive information

    -

    Prompts to hide and remove sensitive information from observers are available.

    -

    Needs additional research

    -
    +
    +

    Security and Privacy

    +

    Users’ safety, security or privacy are not decreased by accessibility measures.

    -

    Social media algorithm

    -

    A mechanism is available to understand and control social media algorithms.

    +
    Clear agreement
    +

    The interface indicates when a user is entering an agreement or submitting data.

    Needs additional research

    -
    -
    - -
    -

    Text and Wording

    -
    -

    Acronyms and abbreviations

    -

    The expanded form or meaning of abbreviations and acronyms is available.

    -
    -
    -

    Ambiguous numerical formatting

    -

    Alternative formats for ambiguous number formats are available.

    -

    Ambiguous pronunciation

    -

    All letters and diacritics needed to phonetically read words are available.

    +
    Disability information privacy
    +

    Disability information is not disclosed to or used by third parties and algorithms (including AI).

    +

    Needs additional research

    -

    Appropriate tone

    -

    The language and tone used is respectful and appropriate to the topic or subject matter.

    +
    Sensitive information
    +

    Prompts to hide and remove sensitive information from observers are available.

    Needs additional research

    -
    -
    -

    Conveying importance without sizing

    -

    When font size conveys meaning (such as headings), the text maintains its meaning and purpose when text is resized.

    -

    Double negatives

    -

    Content does not include double negatives to express a positive unless it is standard usage for that language or dialect.

    -
    -
    -

    Figurative language

    -

    Explanations for figurative and non-literal language [such as jokes, sarcasm, hyperbole, metaphors, similes, and idioms] are available.

    +
    Risk statements
    +

    Clear explanations of the risks and consequences of choices, including use, are stated.

    +

    Needs additional research

    +
    + +
    +

    Algorithms

    +

    Users are not disadvantaged by algorithms.

    -

    Interface Verbosity

    -

    The interface avoids overwhelming verbosity.

    +
    Algorithm bias
    +

    Algorithms (including AI) used are not biased against people with disabilities.

    Needs additional research

    -

    Lists

    -

    Three or more items of related data are presented as bulleted or numbered lists.

    -
    +
    Social media algorithm
    +

    A mechanism is available to understand and control social media algorithms.

    +

    Needs additional research

    +
    +
    +
    + +
    +

    Text and Wording

    +
    +

    @@

    +

    Users can read visually rendered text.

    -

    Maximum text contrast

    -

    The rendered text against its background meets a maximum ‘contrast ratio test’ for its text appearance and use.

    +
    Maximum text contrast
    +

    The rendered text against its background meets a maximum ‘contrast ratio test’ for its text appearance.

    Needs additional research

    +
    +
    Minimum text contrast
    +

    The rendered text against its background meets a minimum 'contrast ratio test' for its text appearance.

    +

    Needs additional research

    +
    -

    Minimum text contrast

    -

    The rendered text against its background meets a minimum ‘contrast ratio test’ for its text appearance and use.

    +
    Text size
    +

    The rendered text meets a minimum font size and weight.

    Needs additional research

    -

    Numbered steps

    -

    Steps in a multi-step process are numbered.

    +
    Text style
    +

    The rendered text does not use a decorative or cursive font face.

    +
    + +
    +

    Text-to-speech

    +

    Users can access text content and its meaning with text-to-speech tools.

    -

    Risk statements

    -

    Clear explanations of the risks and consequences of choices, including use, are stated.

    +
    Text-to-speech supported
    +

    Text content can be converted into speech.

    Needs additional research

    +
    +
    +
    Human language
    +

    The human language of the view and content within the view is programmatically available.

    -

    Semantic text appearance

    +
    Semantic text appearance

    Meaning conveyed by text appearance is programmatically available.

    Needs additional research

    -
    -
    -

    Sentence voice

    -

    The voice used is easiest to understand in context.

    -

    Needs additional research

    +
    + +
    +

    Clear language

    +

    Users can access clear language content.

    -

    Single idea

    -

    Each segment of text [such as sentence, paragraph, bullet] presents one concept.

    +
    Acronyms and abbreviations
    +

    The expanded form or meaning of abbreviations and acronyms is available.

    -

    Summary

    -

    Access to a plain-language summary, abstract, or executive summaries is available.

    +
    Ambiguous numbers
    +

    Alternative formats for ambiguous number formats are available.

    -

    Supplements to numerical concepts

    -

    Text or visual alternatives are available for numerical concepts.

    +
    Ambiguous pronunciation
    +

    All letters and diacritics needed to identify (phonetically read) words are available.

    -

    Text minimum

    -

    The rendered text meets a minimum font size and weight.

    +
    Appropriate tone
    +

    The language and tone used is respectful and appropriate to the topic or subject matter.

    Needs additional research

    -

    Text style

    -

    The rendered text does not use a decorative or cursive font face.

    -
    +
    Double negatives
    +

    Content does not include double negatives to express a positive unless it is standard usage for that language or dialect.

    +
    -

    Text-to-speech supported

    -

    Text content can be converted into speech.

    -

    Needs additional research

    +
    Figurative language
    +

    Explanations for figurative and non-literal language [such as jokes, sarcasm, hyperbole, metaphors, similes, and idioms] are available.

    -

    Title

    -

    Content has a title or high-level description.

    +
    Sentence voice
    +

    The voice used is easiest to understand in context.

    +

    Needs additional research

    -

    Topic sentence

    -

    Each paragraph of text begins with a topic sentence stating the aim or purpose.

    +
    Topic sentence
    +

    For text intended to inform the user, each paragraph of text begins with a topic sentence stating the aim or purpose.

    -

    Uncommon words

    +
    Uncommon words

    Definitions for uncommon or new words are available.

    Needs additional research

    -

    Unnecessary words or phrases

    +
    Unnecessary words or phrases

    Sentences are concise, without unnecessary filler words and phrases.

    -

    Verb tense

    +
    Verb tense

    The verb tense used is easiest to understand in context.

    Needs additional research

    +
    -
    -

    Help and feedback

    +
    +

    Help and feedback

    +
    +

    Help available

    +

    Users have help available.

    -

    Consistent help

    -

    Help is labeled consistently and provided in a consistent visual and programmatic location.

    +
    Consistent help
    +

    Help is labeled consistently and available in a consistent visual and programmatic location.

    Needs additional research

    -

    Contextual help

    +
    Contextual help

    Contextual help is available.

    -

    Conversational support

    -

    Conversational support is available that allows both text and verbal communication.

    +
    Conversational support
    +

    Conversational support allowing both text and verbal modes is available.

    -

    Data visualization help

    -

    Help understanding and using data visualizations is available.

    +
    Data visualizations
    +

    Help is available to understand and use data visualizations.

    Needs additional research

    -
    -
    -

    Feedback mechanism

    -

    Feedback can be provided.

    -
    +
    -

    Help using new interfaces

    -

    Help using new or changed interfaces is available.

    +
    New interfaces
    +

    When interfaces dramatically change (due to redesign), a mechanism to learn the new interface or revert to the older design is available.

    Needs additional research

    -

    Personalizable help

    -

    Adaptable/personalizable help is available.

    +
    Personalizable help
    +

    Help is adaptable and personalizable.

    Needs additional research

    -

    Sensory characteristics

    -

    Instructions and help do not rely on sensory characteristics.

    +
    Support available
    +

    Accessible support is available during data entry, task completion and search.

    +

    Needs additional research

    +
    +
    + +
    +

    Supplemental content

    +

    Users have supplemental content available.

    +
    +
    Number supplements
    +

    Text or visual alternatives are available for numerical concepts.

    -

    Supplements to text

    +
    Text supplements

    Visual illustrations, pictures, and images are available to help explain complex ideas, events, and processes.

    Needs additional research

    +
    + +
    +

    Feedback

    +

    Users can provide feedback to authors.

    -

    Support available

    -

    Accessible support during data entry, task completion and search is available.

    -

    Needs additional research

    -
    -
    +
    Feedback mechanism
    +

    A mechanism is available to provide feedback to authors.

    +
    +
    +
    -
    -

    User Control

    +
    +

    User Control

    +
    +

    Control Text

    +

    Users can control text presentation.

    -

    Adjust color

    +
    Adjust color

    Text and background colors can be customized.

    -

    Alternative presentation

    -

    Complex information or instructions for complex processes are available in multiple presentation formats.

    -

    Needs additional research

    +
    Adjust background
    +

    Patterns, designs or images placed behind text are avoided or can be removed by the user.

    -

    AT control

    -

    Content can be controlled using assistive and adaptive technology.

    +
    Font size meaning
    +

    When font size conveys visual meaning (such as headings), the text maintains its meaning and purpose when text is resized.

    +
    +
    +
    Text Customization
    +

    Users can change the text style (like font and size) and the layout (such as spacing and single column) to fit their needs.

    +
    + +
    +

    Adjustable viewport

    +

    Users can transform size and orientation if content presentation to make it viewable and usable.

    -

    Audio control

    -

    Audio can be turned off, independent of the system audio, while allowing video to play.

    -
    +
    Orientation
    +

    Content orientation allows the user to read the language presented without changing head or body position.

    +
    -

    Caption control

    -

    The position and formatting of captions can be changed.

    -
    +
    Reflow
    +

    Content can be viewed in multiple viewport sizes, orientations, and zoom levels -- without loss of content, functionality, meaningful relationships, and with scrolling only occurring in one direction.

    +
    +
    + +
    +

    Transform content

    +

    Users can transform content to make it understandable.

    -

    Chunk content

    -

    Large amounts of data can be broken into smaller chunks.

    +
    Alternative presentation
    +

    Complex information or instructions for complex processes are available in multiple presentation formats.

    +

    Needs additional research

    -

    Clear background

    -

    Patterns, designs or images placed behind text are avoided or can be removed.

    +
    Content markup
    +

    Role and priority of content is programmatically determinable.

    -

    Control interruptions

    -

    The timing and positioning of notifications and other interruptions can be changed, suppressed or saved, except interruptions involving an emergency.

    +
    Summary
    +

    Access to a plain-language summary, abstract, or executive summaries is available.

    -

    Disturbing content

    -

    Warnings about content that may be emotionally disturbing are available and the content can be hidden.

    +
    Transform content
    +

    Content can be transformed to make its purpose clearer.

    Needs additional research

    +
    + +
    +

    Media control

    +

    Users can control media and media alternative.

    -

    Haptic stimulation

    -

    Haptic feedback can be reduced or turned off.

    -

    Needs additional research

    -
    +
    Adjust captions
    +

    The position and formatting of captions can be changed.

    +
    -

    Interactive audio alternative

    -

    The ability to look up terms within audio alternatives is available.

    +
    Audio control
    +

    Audio can be turned off, while still playing the video, and without affecting the system sound.

    +
    +
    +
    Interactive audio alternative
    +

    Alternatives for audio include the ability to search and look up terms.

    Needs additional research

    -

    Media alternative control

    +
    Media alternative control

    Captions and audio descriptions can be turned on and off.

    -

    Media chapters

    +
    Media chapters

    Media can be navigated by chapters.

    Needs additional research

    -
    -
    -

    Preferences apply to printing.

    -

    Printing respects user’s content presentation preferences.

    -

    Needs additional research

    + + + +
    +

    Control interruptions

    +

    Users can control interruptions.

    -

    Reflow

    -

    Content can be viewed in multiple size viewports, orientations, and zoom levels without loss of content, functionality and meaningful relationships and with scrolling only occurring in 1 direction.

    +
    Control notifications
    +

    The timing and positioning of notifications and other interruptions can be changed, suppressed or saved, except interruptions involving an emergency.

    +
    + +
    +

    Control possible harm

    +

    Users can control potential sources of harm.

    -

    Text Customization

    -

    Text appearance [font, size, etc] and layout [spacing, single column] can be customized by the user.

    +
    Disturbing content
    +

    Warnings are available about content that may be emotionally disturbing, and the disturbing content can be hidden.

    +

    Needs additional research

    -

    3rd party content presentation

    -

    Advertising and other third-party content that obscures the primary content can be moved or removed before interacting with it.

    +
    Haptic stimulation
    +

    Haptic feedback can be reduced or turned off.

    +

    Needs additional research

    +
    +
    +
    Triggers
    +

    Warnings are available about triggering content, and the warnings and triggering content can be hidden.

    Needs additional research

    -

    Transform content

    -

    Content can be transformed to make its purpose clearer.

    +
    Verbosity
    +

    Overwhelming wordiness can be reduced or turned off.

    Needs additional research

    -

    Triggers

    -

    Triggering content is indicated and the content and trigger warnings can be hidden.

    +
    Visual stimulation
    +

    Visual stimulation from combinations of density, color, movement, etc. can be reduced or turned off.

    Needs additional research

    +
    + +
    +

    User Agent Support

    +

    Users can control content settings from their User Agents including Assistive Technology.

    +
    +
    Assistive technology control
    +

    Content can be controlled using assistive and adaptive technology.

    +
    +
    +
    Printing
    +

    Printing respects user’s content presentation preferences.

    +

    Needs additional research

    +
    -

    User settings

    -

    User settings are honored when using or reviewing content.

    +
    User settings
    +

    User settings are honored.

    -

    Virtual cursor

    -

    Assistive technologies can access content and interactions when mechanisms that convey alternative points of regard or focus (i.e. virtual cursor) are used.

    +
    Virtual cursor
    +

    Assistive technologies can access content and interactions when using mechanisms that convey alternative points of regard or focus (i.e. virtual cursor).

    -
    + +

    Conformance

    From f8fb9cc4edc6ded55ebf81a092d4a62428594000 Mon Sep 17 00:00:00 2001 From: rachaelbradley Date: Mon, 11 Nov 2024 12:45:14 -0500 Subject: [PATCH 05/49] editorial fixes --- guidelines/index.html | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 17341b7..ea15af8 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -593,7 +593,7 @@
    Name, role, value, state

    Input / Operation

    -

    Input Operation

    +

    Input pperation

    Users can use different input techniques and combinations and switch between them.

    Concurrent inputs
    @@ -856,7 +856,7 @@
    Persistent navigation

    Policy and Protection

    -

    Third Party Content

    +

    Third party content

    Users understand who created the content.

    Citation
    @@ -919,7 +919,7 @@
    Social media algorithm

    Text and Wording

    -

    @@

    +

    Text appearance

    Users can read visually rendered text.

    Maximum text contrast
    @@ -1048,6 +1048,10 @@
    Personalizable help

    Help is adaptable and personalizable.

    Needs additional research

    +
    +

    Sensory characteristics

    +

    Instructions and help do not rely on sensory characteristics.

    +
    Support available

    Accessible support is available during data entry, task completion and search.

    @@ -1082,7 +1086,7 @@
    Feedback mechanism

    User Control

    -

    Control Text

    +

    Control text

    Users can control text presentation.

    Adjust color
    @@ -1097,7 +1101,7 @@
    Font size meaning

    When font size conveys visual meaning (such as headings), the text maintains its meaning and purpose when text is resized.

    -
    Text Customization
    +
    Text customization

    Users can change the text style (like font and size) and the layout (such as spacing and single column) to fit their needs.

    From 16601b9bc5d0d441174b1611b915e94eb3cbd4d1 Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 12 Nov 2024 10:40:03 +0000 Subject: [PATCH 06/49] Fix sections and spacing --- guidelines/index.html | 376 +++++++++++++++++++++--------------------- 1 file changed, 188 insertions(+), 188 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index ea15af8..0ef905c 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -115,21 +115,21 @@

    Animation and movement

    Avoid physical harm

    Users do not experience physical harm from content.

    -
    +
    Audio shifting

    Audio shifting designed to create a perception of motion is avoided; or can be paused or prevented.

    Needs additional research

    -
    +
    Flashing

    Flashing or strobing beyond thresholds defined by safety standards are avoided; or can be paused or prevented.

    -
    +
    Motion

    Visual motion and pseudo-motion that lasts longer than 5 seconds is avoided; or can be paused or prevented.

    Needs additional research

    -
    +
    Motion from Interaction

    Visual motion and pseudo-motion triggered by interaction is avoided; or can be prevented, unless the animation is essential to the functionality or the information being conveyed.

    Needs additional research

    @@ -142,23 +142,23 @@

    Error handling

    Correct mistakes

    Users know about and can correct mistakes.

    -
    +
    Error association

    Error notifications are programmatically associated with the error source so that users can access the error information while focused on the source of the error.

    -
    +
    Error identification

    Errors are visually identifiable without relying on only text, only color, or only symbols.

    -
    +
    Error notification

    Errors that can be automatically detected are identified and described to the user.

    -
    +
    Persistent errors

    Error notifications persist until the user dismisses them or the error is resolved.

    -
    +
    Visible error

    Error notifications are visually collocated with the source of the error within the viewport, or provide a link to the source of the error which, when activated, moves the viewport to the error.

    Needs additional research

    @@ -172,15 +172,15 @@

    Process and task completion

    Avoid cognitive tasks

    Users can complete tasks without needing to memorize nor complete advanced cognitive tasks.

    -
    +
    Allow automated entry

    Automated input from user agents, 3rd party tools, or copy-and-paste is not prevented.

    -
    +
    No cognitive tests

    Processes, including login/authentication, can be completed without puzzles, calculations, or other cognitive tests (essential exceptions would apply).

    -
    +
    No memorization

    Processes can be completed without memorizing and recalling information from previous stages of the process.

    Needs additional research

    @@ -190,15 +190,15 @@
    No memorization

    Adequate time

    Users have enough time to read and use content.

    -
    +
    Adjust timing at start

    For each process with a time-limit, a mechanism exists to disable or extend the limit before the time-limit starts.

    -
    +
    Adjust timing at timeout

    For each process with a time-limit, a mechanism exists to disable or extend the time-limit at timeout.

    -
    +
    Disable timeout

    For each process with a time-limit, a mechanism exists to disable the limit.

    @@ -207,11 +207,11 @@
    Disable timeout

    Unnecessary steps

    Users can complete tasks without unnecessary steps.

    -
    +

    Optional information

    Processes can be completed without being forced to read or understand unnecessary content.

    -
    +

    Optional input

    Processes can be completed without entering unnecessary information.

    @@ -220,26 +220,26 @@

    Optional input

    Avoid deception

    Users do not encounter deception when completing tasks, unless essential to the task.

    -
    +

    Deceptive controls

    Interactive components are not deceptively designed.

    Needs additional research

    -
    +

    Exploitive behaviors

    Process completion does not include exploitive behaviors.

    Needs additional research

    -
    +
    Misinformation

    Processes can be completed without navigating misinformation or redirections.

    Needs additional research

    -
    +
    Preselections

    Preselected options are visible by default during process completion without additional interactions.

    -
    +
    Redirection

    A mechanism is available to prevent fraudulent redirection or alert users they are exiting the site.

    Needs additional research

    @@ -249,15 +249,15 @@
    Redirection

    Retain information

    Users do not have to reenter information or redo work.

    -
    +
    Go back in process

    In a multistep process, the interface supports stepping backwards in a process and returning to the current point without data loss.

    -
    +
    Redundant entry

    Information previously entered by or provided to the user that is required to be entered again in the same process is either auto-populated, or available for the user to select.

    -
    +
    Save progress

    Data entry and other task completion processes allow saving and resuming from the current step in the task.

    @@ -266,11 +266,11 @@
    Save progress

    Complete tasks

    Users understand how to complete tasks.

    -
    +
    Action required

    In a process, the interface indicates when user input or action is required to procceed to the next step. c

    -
    +
    Inform at start of process

    Information needed to complete a multi-step process is provided at the start of the process, including:

    • number of steps it might take (if known in advance),
      • @@ -278,7 +278,7 @@
      Inform at start of process
    • overview of the process and next step.

    -
    +
    Steps and instructions

    The steps and instructions needed to complete a multistep process are available

    @@ -312,37 +312,37 @@

    Image alternatives

    -
    +
    Decorative image

    Decorative image is programmatically hidden.

    -
    +
    Content image

    Equivalent text alternative is available for image that conveys content.

    -
    +
    Detectable image

    Image is programmatically detectable.

    Supplemental

    -
    +
    Image role

    The role and importance of the image is programmatically indicated.

    -
    +
    Image type

    The type of image (photo, icon, etc.) is indicated.

    -
    +
    Editable Alternatives

    Auto generated text descriptions are editable by content creator.

    Needs additional research

    Assertions

    -
    +
    Style Guide

    Text alternatives follow an organizational style guide.

    @@ -351,29 +351,29 @@
    Style Guide

    Media alternatives

    Users have equivalent alternatives for media content.

    -
    +
    Audio descriptions

    Where there is visual content in media, there is an equivalent synchronized audio track.

    -
    +
    Captions

    Where there is audio content in media, there are equivalent synchronized captions.

    -
    +
    Descriptive transcripts

    A transcript is available whenever audio or visual alternatives are used.

    -
    +
    Findable media alternatives

    Media that has the desired media alternatives (captions, audio descriptions, and descriptive transcripts) can be found. (Needs additional research).

    Needs additional research

    -
    +
    Preferred language

    Equivalent audio alternatives are available in the preferred language.

    Needs additional research

    -
    +

    Non-verbal cues

    Media alternatives explain nonverbal cues, such as tone of voice, facial expressions, body gestures, or music with emotional meaning.

    Needs additional research

    @@ -384,7 +384,7 @@

    Non-verbal cues

    Nontext alternatives

    Users have alternatives available for non-text, non-image content that conveys context or meaning.

    -
    +
    Nontext content

    Equivalent text alternatives are available for non-text, non-image content that conveys context or meaning.

    Needs additional research

    @@ -395,7 +395,7 @@
    Nontext content

    Figure captions

    Users can view figure captions even if not focused at figure.

    -
    +
    Persistent captions

    Figure captions persist or can be made to persist even if the focus moves away.

    Needs additional research

    @@ -405,21 +405,21 @@
    Persistent captions

    Single Sense

    Users have content that does not rely on a single sense or perception.

    -
    +
    Use of hue

    Information conveyed by graphical elements does not rely on hue.

    Needs additional research

    -
    +
    Use of visual depth

    Information conveyed with visual depth is also conveyed programmatically and/or through text.

    Needs additional research

    -
    +
    Use of sound

    Information conveyed with sound is also conveyed programmatically and/or through text.

    -
    +
    Use of spatial audio

    Information that is conveyed with spatial audio is also conveyed programmatically and/or through text.

    @@ -453,27 +453,27 @@

    Keyboard Focus Appearance

    -
    +
    Custom indicator

    A custom focus indicator is used with sufficient size, change of contrast, adjacent contrast, distinct style and adjacecy.

    -
    +
    Default indicator

    The platform’s default indicator is used, and where the backgrounds are changed, the indicator contrast is checked.

    -
    +
    User agent default indicator

    Focusable item uses the user agent default indicator.

    Supplemental

    -
    +
    Supplimentary indicators

    @@

    Assertions

    -
    +
    Style Guide

    Focus indicators follow an organizational style guide.

    @@ -482,7 +482,7 @@
    Style Guide

    Pointer Focus Appearance

    Users can see the location of the pointer focus.

    -
    +
    Pointer visible

    There is a visible indicator of pointer focus.

    @@ -491,23 +491,23 @@
    Pointer visible

    Navigating content

    Users can determine where they are and move through content (including interactive elements) in a systematic and meaningful way regardless of input or movement method.

    -
    +
    Focus in viewport

    The focus does not move to a position outside the current viewport, unless a mechanism is available to return to the previous focus point.

    -
    +
    Focus retention

    A user can focus on a content “area,” such as a modal or pop-up, then resume their view of all content using a limited number of steps.

    -
    +
    Keyboard focus order

    The keyboard focus moves sequentially through content in an order and way that preserves meaning and operability.

    -
    +
    Restore focus

    When the focus is moved by the content into a temporary change of view (e.g. a modal), the focus is restored to its previous location when the view is restored.

    -
    +
    Relevant focus

    The focus order does not include repetitive, hidden, or static elements.

    @@ -516,30 +516,30 @@
    Relevant focus

    Expected behavior

    Users have interactive components that behave as expected.

    -
    +
    Consistent Interaction

    Interactive components with the same functionality behave consistently.

    -
    +
    Consistent labels

    Interactive components with the same functionality have consistent labels.

    -
    +
    Consistent visual design

    Interactive components that have similar function and behavior have a consistent visual design.

    -
    +
    Control location

    Interactive components are visually and programmatically located in conventional locations.

    Needs additional research

    -
    -
    +
    +
    Conventions

    Interactive components follow established conventions.

    Needs additional research

    -
    +
    Familiar component

    Conventional interactive components are used.

    @@ -553,36 +553,36 @@
    Reliable positioning

    Control information

    Users have information about interactive components that is identifiable and usable visually and using assistive technology.

    -
    +
    Control importance

    The importance of interactive components is indicated.

    Needs additional research

    -
    +
    Control labels

    Interactive components have visible labels that identify the purpose of the component.

    -
    +
    Control updates

    Changes to interactive components’ names, roles, values or states are visually and programmatically indicated.

    -
    +
    Distinguishable controls

    Interactive components are visually distinguishable without interaction from static content and include visual cues on how to use them.

    -
    +
    Field constraints

    Field constraints and conditions (required line length, date format, password format, etc) are available.

    -
    +
    Input labels

    Inputs have visible labels that identify the purpose of the input.

    -
    +
    Label in name

    The programmatic name includes the visual label.

    -
    +
    Name, role, value, state

    Accurate names, roles, values, and states are available for interactive components.

    @@ -595,15 +595,15 @@

    Input / Operation

    Input pperation

    Users can use different input techniques and combinations and switch between them.

    -
    +
    Concurrent inputs

    Any input modality available on a platform can be used concurrently.

    -
    +
    Hover information

    Users can dismiss additional content (triggered by hover) without moving the pointer, unless the additional content communicates an input error or does not obscure or replace other content.

    -
    +
    Input control

    Interactive components are available to all navigation and input methods.

    @@ -612,20 +612,20 @@
    Input control

    Content changes

    Users are aware of changes to content or context.

    -
    +
    Notify about change

    Changes in content and updates notify users, regardless of the update speed.

    -
    +
    Notify on change

    Notification is provided when viewing content that was previously viewed is changed.

    -
    +
    Inform before activation

    Interactive components that can alter the order of content convey their purpose prior to activation, and convey their impact on content order when activated.

    -
    +
    Reverse change of context

    Components that trigger a 'change of context' are indicated, or the change of context can be reversed.

    @@ -634,12 +634,12 @@
    Reverse change of context

    Target size

    Users are not required to accurately position a pointer in order to view or operate content.

    -
    +
    Target size minimum

    The combined target size and spacing to adjacent targets is at least 24x24 pixels

    -
    +
    Target size optimum

    The combined target size and spacing to adjacent targets is at least 48x48 pixels.

    @@ -648,32 +648,32 @@
    Target size optimum

    Keyboard operation

    Users can navigate and operate content using only the keyboard focus.

    -
    +
    Comparable keyboard effort

    The number of input commands required to complete a task using the keyboard is similar to the number of input commands when using other input modalities.

    Needs additional research

    -
    +
    Conflicting keyboard commands

    Authored keyboard commands do not conflict with platform commands or they can be remapped.

    -
    +
    Consistent keyboard interaction

    Keyboard interface interactions are consistent.

    -
    +
    Keyboard mode

    If the keyboard is non-hardware (such as a virtual keyboard), the keyboard input mode is indicated.

    -
    +
    Keyboard only

    All functionality must be accessible through the keyboard, except when a task requires input based on the user's specific input action.

    -
    +
    No keyboard trap

    If keyboard focus can be moved to an interactive component, then the keyboard focus can be moved away from that component, or the component can be dismissed, with focus returning to the previous point.

    -
    +
    Non-standard commands

    The user is informed of non-standard authored keyboard commands.

    @@ -682,28 +682,28 @@
    Non-standard commands

    Gestures

    Users are not required to use gestures or dragging to view or operate content.

    -
    +
    Change focus with pointer device

    Selecting an interactive component with a ‘pointer’ sets the focus to that element.

    -
    +
    Complex pointer inputs

    Every function that can be operated by a pointer, can be operated by a ‘single pointer input’ or a sequence of single pointer inputs without requiring certain timing.

    -
    +
    Pointer-agnostic

    Functionality which supports pointers is available to any pointer device supported by the platform.

    -
    +
    Pointer cancellation

    The method of pointer cancellation is consistent.

    -
    +
    Specific pressure

    Where specific pressures are used, they can be adjusted and/or disabled without loss of function.

    Needs additional research

    -
    +
    Speed insensitive

    Where specific speeds are used, they can be adjusted and/or disabled without loss of function.

    Needs additional research

    @@ -713,15 +713,15 @@
    Speed insensitive

    Motion input

    Users are not required to move their bodies or devices to operate functionality.

    -
    +
    Use without body movement

    All functionality that requires full or gross body movement may also be accomplished with a standard input device.

    -
    +
    Use without device movement

    All functionality can be completed without reorienting or repositioning hardware devices.

    -
    +
    Interactive component contrast

    Visual information required to identify user interface components and states meet a ‘minimum contrast ratio test’, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author.

    Needs additional research

    @@ -730,24 +730,24 @@
    Interactive component contrast
    -

    Layout

    +

    Layout

    Relationships

    Users can determine relationships between content both visually and using assistive technologies.

    -
    +
    Clear relationships

    The relationships between parts of the content is clearly indicated.

    -
    +
    Clear starting point

    The starting point or home is visually and programmatically labeled.

    -
    +
    Distinguishable relationships

    Relationships that convey meaning between pieces of content are programmatically determinable. Note: Examples of relationships include items positioned next to each other, arranged in a hierarchy, or visually grouped.

    Needs additional research

    -
    +
    Distinguishable sections

    Sections are visually and programmatically distinguishable.

    Needs additional research

    @@ -758,19 +758,19 @@
    Distinguishable sections

    Recognizable layouts

    Users have consistent and recognizable layouts available.

    -
    +
    Consistent order

    The relative order of content and interactions remain consistent throughout a workflow. Note: Relative order means that content can be added or removed, but repeated items are in the same order relative to each other.

    -
    +
    Familiar layout

    Conventional layouts are available.

    -
    +
    Information about options

    Information required to understand options is visually and programmatically associated with the options.

    -
    +
    Related information

    Related information is grouped together within a visual and programmatic structure.

    @@ -779,17 +779,16 @@
    Related information

    Orientation

    Users can determine their location in content both visually and using assistive technologies.

    -
    +
    Current location

    The current location within the view, multi-step process, and product is visually and programmatically indicated.

    Needs additional research

    -
    +
    Multistep process

    Provides context that orients the user in a site or multi-step process.

    -
    -
    +
    Contextual information

    Provide contextual information to help the user orient within the product.

    @@ -798,36 +797,36 @@
    Contextual information

    Structure

    Users can understand and navigate through the content using structure.

    -
    +
    Section labels

    Major sections of content have within them well structured, understandable visual and programmatic headings.

    -
    +
    Section length

    Content is organized into short sections of related content.

    Needs additional research

    -
    +
    Section purpose

    The purpose of each section of the content is clearly indicated.

    -
    +
    Single idea

    The number of concepts within a segment of text is minimized.

    -
    +
    White spacing

    Whitespace separates chunks of content.

    -
    +
    Title

    Content has a title or high-level description.

    -
    +
    Lists

    Three or more items of related data are presented as bulleted or numbered lists.

    -
    +
    Numbered steps

    Steps in a multi-step process are numbered.

    @@ -837,38 +836,39 @@
    Numbered steps

    Consistency across views

    -

    Navigation

    +

    Consistency

    Users have consistent and alternative methods for navigation.

    -
    +
    Consistent navigation

    Navigation elements remain consistent across views within the product.

    -
    +
    Multiple ways

    The product provides at least two ways of navigating and finding information (Search, Scan, Site Map, Menu Structure, Breadcrumbs, contextual links, etc).

    -
    +
    Persistent navigation

    Navigation features are available regardless of screen size and magnification (responsive design)

    -
    +
    +

    Policy and Protection

    -

    Third party content

    -

    Users understand who created the content.

    -
    +

    Content source

    +

    Users can determine when content is provided by a Third Party

    +
    Citation

    The author or source of the primary content is visually and programmatically indicated.

    Needs additional research

    -
    +
    Indicate 3rd party content

    Third party content (AI, Advertising, etc.) is visually and programmatically indicated.

    Needs additional research

    -
    +
    Obscuring primary content

    Advertising and other third-party content that obscures the primary content can be moved or removed without interacting with the advertising or third-party content.

    Needs additional research

    @@ -878,22 +878,22 @@
    Obscuring primary content

    Security and Privacy

    Users’ safety, security or privacy are not decreased by accessibility measures.

    -
    +
    Clear agreement

    The interface indicates when a user is entering an agreement or submitting data.

    Needs additional research

    -
    +
    Disability information privacy

    Disability information is not disclosed to or used by third parties and algorithms (including AI).

    Needs additional research

    -
    +
    Sensitive information

    Prompts to hide and remove sensitive information from observers are available.

    Needs additional research

    -
    +
    Risk statements

    Clear explanations of the risks and consequences of choices, including use, are stated.

    Needs additional research

    @@ -903,12 +903,12 @@
    Risk statements

    Algorithms

    Users are not disadvantaged by algorithms.

    -
    +
    Algorithm bias

    Algorithms (including AI) used are not biased against people with disabilities.

    Needs additional research

    -
    +
    Social media algorithm

    A mechanism is available to understand and control social media algorithms.

    Needs additional research

    @@ -921,7 +921,7 @@

    Text and Wording

    Text appearance

    Users can read visually rendered text.

    -
    +
    Maximum text contrast

    The rendered text against its background meets a maximum ‘contrast ratio test’ for its text appearance.

    Needs additional research

    @@ -931,12 +931,12 @@
    Minimum text contrast

    The rendered text against its background meets a minimum 'contrast ratio test' for its text appearance.

    Needs additional research

    -
    +
    Text size

    The rendered text meets a minimum font size and weight.

    Needs additional research

    -
    +
    Text style

    The rendered text does not use a decorative or cursive font face.

    @@ -945,16 +945,16 @@
    Text style

    Text-to-speech

    Users can access text content and its meaning with text-to-speech tools.

    -
    +
    Text-to-speech supported

    Text content can be converted into speech.

    Needs additional research

    -
    +
    Human language

    The human language of the view and content within the view is programmatically available.

    -
    +
    Semantic text appearance

    Meaning conveyed by text appearance is programmatically available.

    Needs additional research

    @@ -964,50 +964,50 @@
    Semantic text appearance

    Clear language

    Users can access clear language content.

    -
    +
    Acronyms and abbreviations

    The expanded form or meaning of abbreviations and acronyms is available.

    -
    +
    Ambiguous numbers

    Alternative formats for ambiguous number formats are available.

    -
    +
    Ambiguous pronunciation

    All letters and diacritics needed to identify (phonetically read) words are available.

    -
    +
    Appropriate tone

    The language and tone used is respectful and appropriate to the topic or subject matter.

    Needs additional research

    -
    +
    Double negatives

    Content does not include double negatives to express a positive unless it is standard usage for that language or dialect.

    -
    +
    Figurative language

    Explanations for figurative and non-literal language [such as jokes, sarcasm, hyperbole, metaphors, similes, and idioms] are available.

    -
    +
    Sentence voice

    The voice used is easiest to understand in context.

    Needs additional research

    -
    +
    Topic sentence

    For text intended to inform the user, each paragraph of text begins with a topic sentence stating the aim or purpose.

    -
    +
    Uncommon words

    Definitions for uncommon or new words are available.

    Needs additional research

    -
    +
    Unnecessary words or phrases

    Sentences are concise, without unnecessary filler words and phrases.

    -
    +
    Verb tense

    The verb tense used is easiest to understand in context.

    Needs additional research

    @@ -1020,39 +1020,39 @@

    Help and feedback

    Help available

    Users have help available.

    -
    +
    Consistent help

    Help is labeled consistently and available in a consistent visual and programmatic location.

    Needs additional research

    -
    +
    Contextual help

    Contextual help is available.

    -
    +
    Conversational support

    Conversational support allowing both text and verbal modes is available.

    -
    +
    Data visualizations

    Help is available to understand and use data visualizations.

    Needs additional research

    -
    +
    New interfaces

    When interfaces dramatically change (due to redesign), a mechanism to learn the new interface or revert to the older design is available.

    Needs additional research

    -
    +
    Personalizable help

    Help is adaptable and personalizable.

    Needs additional research

    -
    +

    Sensory characteristics

    Instructions and help do not rely on sensory characteristics.

    -
    +
    Support available

    Accessible support is available during data entry, task completion and search.

    Needs additional research

    @@ -1062,11 +1062,11 @@
    Support available

    Supplemental content

    Users have supplemental content available.

    -
    +
    Number supplements

    Text or visual alternatives are available for numerical concepts.

    -
    +
    Text supplements

    Visual illustrations, pictures, and images are available to help explain complex ideas, events, and processes.

    Needs additional research

    @@ -1076,7 +1076,7 @@
    Text supplements

    Feedback

    Users can provide feedback to authors.

    -
    +
    Feedback mechanism

    A mechanism is available to provide feedback to authors.

    @@ -1088,19 +1088,19 @@

    User Control

    Control text

    Users can control text presentation.

    -
    +
    Adjust color

    Text and background colors can be customized.

    -
    +
    Adjust background

    Patterns, designs or images placed behind text are avoided or can be removed by the user.

    -
    +
    Font size meaning

    When font size conveys visual meaning (such as headings), the text maintains its meaning and purpose when text is resized.

    -
    +
    Text customization

    Users can change the text style (like font and size) and the layout (such as spacing and single column) to fit their needs.

    @@ -1109,11 +1109,11 @@
    Text customization

    Adjustable viewport

    Users can transform size and orientation if content presentation to make it viewable and usable.

    -
    +
    Orientation

    Content orientation allows the user to read the language presented without changing head or body position.

    -
    +
    Reflow

    Content can be viewed in multiple viewport sizes, orientations, and zoom levels -- without loss of content, functionality, meaningful relationships, and with scrolling only occurring in one direction.

    @@ -1122,20 +1122,20 @@
    Reflow

    Transform content

    Users can transform content to make it understandable.

    -
    +
    Alternative presentation

    Complex information or instructions for complex processes are available in multiple presentation formats.

    Needs additional research

    -
    +
    Content markup

    Role and priority of content is programmatically determinable.

    -
    +
    Summary

    Access to a plain-language summary, abstract, or executive summaries is available.

    -
    +
    Transform content

    Content can be transformed to make its purpose clearer.

    Needs additional research

    @@ -1145,24 +1145,24 @@
    Transform content

    Media control

    Users can control media and media alternative.

    -
    +
    Adjust captions

    The position and formatting of captions can be changed.

    -
    +
    Audio control

    Audio can be turned off, while still playing the video, and without affecting the system sound.

    -
    +
    Interactive audio alternative

    Alternatives for audio include the ability to search and look up terms.

    Needs additional research

    -
    +
    Media alternative control

    Captions and audio descriptions can be turned on and off.

    -
    +
    Media chapters

    Media can be navigated by chapters.

    Needs additional research

    @@ -1173,7 +1173,7 @@
    Media chapters

    Control interruptions

    Users can control interruptions.

    -
    +
    Control notifications

    The timing and positioning of notifications and other interruptions can be changed, suppressed or saved, except interruptions involving an emergency.

    @@ -1182,27 +1182,27 @@
    Control notifications

    Control possible harm

    Users can control potential sources of harm.

    -
    +
    Disturbing content

    Warnings are available about content that may be emotionally disturbing, and the disturbing content can be hidden.

    Needs additional research

    -
    +
    Haptic stimulation

    Haptic feedback can be reduced or turned off.

    Needs additional research

    -
    +
    Triggers

    Warnings are available about triggering content, and the warnings and triggering content can be hidden.

    Needs additional research

    -
    +
    Verbosity

    Overwhelming wordiness can be reduced or turned off.

    Needs additional research

    -
    +
    Visual stimulation

    Visual stimulation from combinations of density, color, movement, etc. can be reduced or turned off.

    Needs additional research

    @@ -1212,20 +1212,20 @@
    Visual stimulation

    User Agent Support

    Users can control content settings from their User Agents including Assistive Technology.

    -
    +
    Assistive technology control

    Content can be controlled using assistive and adaptive technology.

    -
    +
    Printing

    Printing respects user’s content presentation preferences.

    Needs additional research

    -
    +
    User settings

    User settings are honored.

    -
    +
    Virtual cursor

    Assistive technologies can access content and interactions when using mechanisms that convey alternative points of regard or focus (i.e. virtual cursor).

    From ce7b91431843aeea184b6dc66a130f0596bece6a Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 12 Nov 2024 10:55:29 +0000 Subject: [PATCH 07/49] Improve indentation --- guidelines/guidelines.css | 21 +++++++++------------ 1 file changed, 9 insertions(+), 12 deletions(-) diff --git a/guidelines/guidelines.css b/guidelines/guidelines.css index 6ffdbfa..b3eb3b8 100644 --- a/guidelines/guidelines.css +++ b/guidelines/guidelines.css @@ -48,11 +48,18 @@ a.internalDFN[title]:hover, .internalDFN[title]:active, a.internalDFN[title]:foc font-size: 100%; color: #005A9C; } + +.guideline { + margin-left: 2em; +} + +.guideline .provision { + margin-left: 2em; +} + .guideline-text, provision-text { font-size: 110%; margin-top: 0; - margin-bottom: 0; - text-indent: 50px; } .guideline h3, .provision h4, .provision h5 { width: 100%; @@ -66,7 +73,6 @@ color: black; .guideline p { margin-top: 0; - text-indent: 50px; } h2, h3, h4 { @@ -89,15 +95,6 @@ h5, h6 { font-size: 100%; color: #005A9C; } -.rating-table, .rating-table th, .rating-table td { - border: 1px solid black; - vertical-align: top; - border-collapse: collapse; - padding: 5px; -} -.rating-table th[scope=row] { - white-space: nowrap; -} caption { font-style: normal !important; font-weight: bold; From e959182225448281a4d1e46dd011a67d8bf3c393 Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 12 Nov 2024 10:57:04 +0000 Subject: [PATCH 08/49] Remove "End of note" paragraph @alastc @rachaelbradley I am not sure why this was introduced. My personal design view is that it adds clutter but I am not sure if it is in response to a specific need? --- guidelines/guidelines.js | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/guidelines/guidelines.js b/guidelines/guidelines.js index 0fbef6d..c8ea699 100644 --- a/guidelines/guidelines.js +++ b/guidelines/guidelines.js @@ -122,12 +122,12 @@ function addSummaryMarkers() { } function addNoteMarkers() { - document.querySelectorAll(".note").forEach(function(node){ - var el = document.createElement("p"); - el.className = "summaryEnd"; - el.innerHTML = "End of note"; - node.appendChild(el); - }) + // document.querySelectorAll(".note").forEach(function(node){ + // var el = document.createElement("p"); + // el.className = "summaryEnd"; + // el.innerHTML = "End of note"; + // node.appendChild(el); + // }) } var statusLabels = { From 6ed75ca6883feb486be0b4ef85610b48ecdf3b2d Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 12 Nov 2024 10:59:09 +0000 Subject: [PATCH 09/49] Revert "Remove "End of note" paragraph" This reverts commit e959182225448281a4d1e46dd011a67d8bf3c393. --- guidelines/guidelines.js | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/guidelines/guidelines.js b/guidelines/guidelines.js index c8ea699..0fbef6d 100644 --- a/guidelines/guidelines.js +++ b/guidelines/guidelines.js @@ -122,12 +122,12 @@ function addSummaryMarkers() { } function addNoteMarkers() { - // document.querySelectorAll(".note").forEach(function(node){ - // var el = document.createElement("p"); - // el.className = "summaryEnd"; - // el.innerHTML = "End of note"; - // node.appendChild(el); - // }) + document.querySelectorAll(".note").forEach(function(node){ + var el = document.createElement("p"); + el.className = "summaryEnd"; + el.innerHTML = "End of note"; + node.appendChild(el); + }) } var statusLabels = { From e24faa16231ef54daaffc806536c94a0e24f1f96 Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 12 Nov 2024 11:01:33 +0000 Subject: [PATCH 10/49] Remove centering for end of note summary --- guidelines/guidelines.css | 1 - 1 file changed, 1 deletion(-) diff --git a/guidelines/guidelines.css b/guidelines/guidelines.css index b3eb3b8..604dfef 100644 --- a/guidelines/guidelines.css +++ b/guidelines/guidelines.css @@ -26,7 +26,6 @@ summary::after { content: url(img/summary.svg); } .summaryEnd { - text-align: center; font-weight: bold; } From 0f2ff74f61b684060f59787e95f7024651abaccb Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 12 Nov 2024 11:10:45 +0000 Subject: [PATCH 11/49] Tidy up Fix missing
    s --- guidelines/index.html | 1946 ++++++++++++++++++++--------------------- 1 file changed, 972 insertions(+), 974 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 0ef905c..f5353b2 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -115,25 +115,25 @@

    Animation and movement

    Avoid physical harm

    Users do not experience physical harm from content.

    -
    -
    Audio shifting
    -

    Audio shifting designed to create a perception of motion is avoided; or can be paused or prevented.

    -

    Needs additional research

    -
    -
    -
    Flashing
    -

    Flashing or strobing beyond thresholds defined by safety standards are avoided; or can be paused or prevented.

    -
    -
    -
    Motion
    -

    Visual motion and pseudo-motion that lasts longer than 5 seconds is avoided; or can be paused or prevented.

    -

    Needs additional research

    -
    -
    -
    Motion from Interaction
    -

    Visual motion and pseudo-motion triggered by interaction is avoided; or can be prevented, unless the animation is essential to the functionality or the information being conveyed.

    -

    Needs additional research

    -
    +
    +
    Audio shifting
    +

    Audio shifting designed to create a perception of motion is avoided; or can be paused or prevented.

    +

    Needs additional research

    +
    +
    +
    Flashing
    +

    Flashing or strobing beyond thresholds defined by safety standards are avoided; or can be paused or prevented.

    +
    +
    +
    Motion
    +

    Visual motion and pseudo-motion that lasts longer than 5 seconds is avoided; or can be paused or prevented.

    +

    Needs additional research

    +
    +
    +
    Motion from Interaction
    +

    Visual motion and pseudo-motion triggered by interaction is avoided; or can be prevented, unless the animation is essential to the functionality or the information being conveyed.

    +

    Needs additional research

    +
    @@ -142,31 +142,30 @@

    Error handling

    Correct mistakes

    Users know about and can correct mistakes.

    -
    -
    Error association
    -

    Error notifications are programmatically associated with the error source so that users can access the error information while focused on the source of the error.

    -
    -
    -
    Error identification
    -

    Errors are visually identifiable without relying on only text, only color, or only symbols.

    -
    -
    -
    Error notification
    -

    Errors that can be automatically detected are identified and described to the user.

    -
    -
    -
    Persistent errors
    -

    Error notifications persist until the user dismisses them or the error is resolved.

    -
    -
    -
    Visible error
    -

    Error notifications are visually collocated with the source of the error within the viewport, or provide a link to the source of the error which, when activated, moves the viewport to the error.

    -

    Needs additional research

    -
    +
    +
    Error association
    +

    Error notifications are programmatically associated with the error source so that users can access the error information while focused on the source of the error.

    +
    +
    +
    Error identification
    +

    Errors are visually identifiable without relying on only text, only color, or only symbols.

    +
    +
    +
    Error notification
    +

    Errors that can be automatically detected are identified and described to the user.

    +
    +
    +
    Persistent errors
    +

    Error notifications persist until the user dismisses them or the error is resolved.

    +
    +
    +
    Visible error
    +

    Error notifications are visually collocated with the source of the error within the viewport, or provide a link to the source of the error which, when activated, moves the viewport to the error.

    +

    Needs additional research

    +
    -

    Process and task completion

    @@ -176,33 +175,33 @@

    Avoid cognitive tasks

    Allow automated entry

    Automated input from user agents, 3rd party tools, or copy-and-paste is not prevented.

    -
    -
    No cognitive tests
    -

    Processes, including login/authentication, can be completed without puzzles, calculations, or other cognitive tests (essential exceptions would apply).

    -
    -
    -
    No memorization
    -

    Processes can be completed without memorizing and recalling information from previous stages of the process.

    -

    Needs additional research

    -
    +
    +
    No cognitive tests
    +

    Processes, including login/authentication, can be completed without puzzles, calculations, or other cognitive tests (essential exceptions would apply).

    +
    +
    +
    No memorization
    +

    Processes can be completed without memorizing and recalling information from previous stages of the process.

    +

    Needs additional research

    +

    Adequate time

    Users have enough time to read and use content.

    -
    Adjust timing at start
    -

    For each process with a time-limit, a mechanism exists to disable or extend the limit before the time-limit starts.

    -
    -
    -
    Adjust timing at timeout
    -

    For each process with a time-limit, a mechanism exists to disable or extend the time-limit at timeout.

    -
    -
    -
    Disable timeout
    -

    For each process with a time-limit, a mechanism exists to disable the limit.

    -
    +
    Adjust timing at start
    +

    For each process with a time-limit, a mechanism exists to disable or extend the limit before the time-limit starts.

    +
    +
    +
    Adjust timing at timeout
    +

    For each process with a time-limit, a mechanism exists to disable or extend the time-limit at timeout.

    +
    +
    Disable timeout
    +

    For each process with a time-limit, a mechanism exists to disable the limit.

    +
    +

    Unnecessary steps

    @@ -220,1020 +219,1019 @@

    Optional input

    Avoid deception

    Users do not encounter deception when completing tasks, unless essential to the task.

    -
    -

    Deceptive controls

    -

    Interactive components are not deceptively designed.

    -

    Needs additional research

    -
    -
    -

    Exploitive behaviors

    -

    Process completion does not include exploitive behaviors.

    -

    Needs additional research

    -
    -
    -
    Misinformation
    -

    Processes can be completed without navigating misinformation or redirections.

    -

    Needs additional research

    -
    -
    -
    Preselections
    -

    Preselected options are visible by default during process completion without additional interactions.

    -
    -
    -
    Redirection
    -

    A mechanism is available to prevent fraudulent redirection or alert users they are exiting the site.

    -

    Needs additional research

    -
    -
    +
    +

    Deceptive controls

    +

    Interactive components are not deceptively designed.

    +

    Needs additional research

    +
    +
    +

    Exploitive behaviors

    +

    Process completion does not include exploitive behaviors.

    +

    Needs additional research

    +
    +
    +
    Misinformation
    +

    Processes can be completed without navigating misinformation or redirections.

    +

    Needs additional research

    +
    +
    +
    Preselections
    +

    Preselected options are visible by default during process completion without additional interactions.

    +
    +
    +
    Redirection
    +

    A mechanism is available to prevent fraudulent redirection or alert users they are exiting the site.

    +

    Needs additional research

    +
    +
    -
    -

    Retain information

    -

    Users do not have to reenter information or redo work.

    -
    -
    Go back in process
    -

    In a multistep process, the interface supports stepping backwards in a process and returning to the current point without data loss.

    -
    -
    -
    Redundant entry
    -

    Information previously entered by or provided to the user that is required to be entered again in the same process is either auto-populated, or available for the user to select.

    -
    -
    -
    Save progress
    -

    Data entry and other task completion processes allow saving and resuming from the current step in the task.

    +
    +

    Retain information

    +

    Users do not have to reenter information or redo work.

    +
    +
    Go back in process
    +

    In a multistep process, the interface supports stepping backwards in a process and returning to the current point without data loss.

    +
    +
    +
    Redundant entry
    +

    Information previously entered by or provided to the user that is required to be entered again in the same process is either auto-populated, or available for the user to select.

    +
    +
    +
    Save progress
    +

    Data entry and other task completion processes allow saving and resuming from the current step in the task.

    +
    -
    -
    -

    Complete tasks

    -

    Users understand how to complete tasks.

    -
    -
    Action required
    -

    In a process, the interface indicates when user input or action is required to procceed to the next step. c

    -
    -
    -
    Inform at start of process
    -

    Information needed to complete a multi-step process is provided at the start of the process, including: -

    • number of steps it might take (if known in advance),
      • -
    • details of any resources needed to perform the task, and
      • -
    • overview of the process and next step.
    -

    -
    -
    -
    Steps and instructions
    -

    The steps and instructions needed to complete a multistep process are available

    +
    +

    Complete tasks

    +

    Users understand how to complete tasks.

    +
    +
    Action required
    +

    In a process, the interface indicates when user input or action is required to procceed to the next step. c

    +
    +
    +
    Inform at start of process
    +

    Information needed to complete a multi-step process is provided at the start of the process, including: +

    • number of steps it might take (if known in advance),
      • +
    • details of any resources needed to perform the task, and
      • +
    • overview of the process and next step.
    +

    +
    +
    +
    Steps and instructions
    +

    The steps and instructions needed to complete a multistep process are available

    +
    -
    - -
    -

    Image and media alternatives

    -
    -

    Image alternatives

    -

    Users have equivalent alternatives for images.

    - -

    Foundational

    - -

    For each image: -

      -
    1. Would removing the image impact how people understand the page? - -
      2. - -
    2. Is the image presented in a way that is available to user agents and assistive technology? - -
      3. - -
    3. Is an equivalent text alternative available for the image? - -
      4. -
    -

    - -
    -
    Decorative image
    -

    Decorative image is programmatically hidden.

    -
    -
    -
    Content image
    -

    Equivalent text alternative is available for image that conveys content.

    -
    -
    -
    Detectable image
    -

    Image is programmatically detectable.

    -
    +
    +

    Image and media alternatives

    +
    +

    Image alternatives

    +

    Users have equivalent alternatives for images.

    + +

    Foundational

    -

    Supplemental

    -
    -
    Image role
    -

    The role and importance of the image is programmatically indicated.

    -
    -
    -
    Image type
    -

    The type of image (photo, icon, etc.) is indicated.

    -
    -
    -
    Editable Alternatives
    -

    Auto generated text descriptions are editable by content creator.

    -

    Needs additional research

    -
    +

    For each image: +

      +
    1. Would removing the image impact how people understand the page? + +
      2. -

      Assertions

      -
      -
      Style Guide
      -

      Text alternatives follow an organizational style guide.

      -
      -
    +
  • Is the image presented in a way that is available to user agents and assistive technology? + +
    • -
    -

    Media alternatives

    -

    Users have equivalent alternatives for media content.

    -
    -
    Audio descriptions
    -

    Where there is visual content in media, there is an equivalent synchronized audio track.

    -
    -
    -
    Captions
    -

    Where there is audio content in media, there are equivalent synchronized captions.

    -
    -
    -
    Descriptive transcripts
    -

    A transcript is available whenever audio or visual alternatives are used.

    -
    -
    -
    Findable media alternatives
    -

    Media that has the desired media alternatives (captions, audio descriptions, and descriptive transcripts) can be found. (Needs additional research).

    -

    Needs additional research

    -
    -
    -
    Preferred language
    -

    Equivalent audio alternatives are available in the preferred language.

    -

    Needs additional research

    -
    -
    -

    Non-verbal cues

    -

    Media alternatives explain nonverbal cues, such as tone of voice, facial expressions, body gestures, or music with emotional meaning.

    -

    Needs additional research

    -
    -
    +
  • Is an equivalent text alternative available for the image? + +
    • + +

    +
    +
    Decorative image
    +

    Decorative image is programmatically hidden.

    +
    +
    +
    Content image
    +

    Equivalent text alternative is available for image that conveys content.

    +
    +
    +
    Detectable image
    +

    Image is programmatically detectable.

    +
    -
    -

    Nontext alternatives

    -

    Users have alternatives available for non-text, non-image content that conveys context or meaning.

    -
    -
    Nontext content
    -

    Equivalent text alternatives are available for non-text, non-image content that conveys context or meaning.

    -

    Needs additional research

    -
    -
    -
    -

    Figure captions

    -

    Users can view figure captions even if not focused at figure.

    +

    Supplemental

    +
    +
    Image role
    +

    The role and importance of the image is programmatically indicated.

    +
    +
    +
    Image type
    +

    The type of image (photo, icon, etc.) is indicated.

    +
    +
    +
    Editable Alternatives
    +

    Auto generated text descriptions are editable by content creator.

    +

    Needs additional research

    +
    -
    -
    Persistent captions
    -

    Figure captions persist or can be made to persist even if the focus moves away.

    -

    Needs additional research

    -
    -
    - -
    -

    Single Sense

    -

    Users have content that does not rely on a single sense or perception.

    -
    -
    Use of hue
    -

    Information conveyed by graphical elements does not rely on hue.

    -

    Needs additional research

    -
    -
    -
    Use of visual depth
    -

    Information conveyed with visual depth is also conveyed programmatically and/or through text.

    -

    Needs additional research

    -
    -
    -
    Use of sound
    -

    Information conveyed with sound is also conveyed programmatically and/or through text.

    +

    Assertions

    +
    +
    Style Guide
    +

    Text alternatives follow an organizational style guide.

    +
    -
    -
    Use of spatial audio
    -

    Information that is conveyed with spatial audio is also conveyed programmatically and/or through text.

    -
    -
    -
    -
    -

    Interactive components

    -
    -

    Keyboard Focus Appearance

    -

    Users can see which element has keyboard focus.

    - -

    Foundational

    - -

    For each focusable item: -

      -
    1. Is the user-agent default focus indicator used? - -
      2. - -
    2. Is the user-agent default focus indicator used, and meets contrast across backgrounds? - -
      3. - -
    3. Is the focus indicator defined by the author? - -
      4. -
    -

    - -
    -
    Custom indicator
    -

    A custom focus indicator is used with sufficient size, change of contrast, adjacent contrast, distinct style and adjacecy.

    -
    -
    -
    Default indicator
    -

    The platform’s default indicator is used, and where the backgrounds are changed, the indicator contrast is checked.

    -
    -
    -
    User agent default indicator
    -

    Focusable item uses the user agent default indicator.

    +
    +

    Media alternatives

    +

    Users have equivalent alternatives for media content.

    +
    +
    Audio descriptions
    +

    Where there is visual content in media, there is an equivalent synchronized audio track.

    +
    +
    +
    Captions
    +

    Where there is audio content in media, there are equivalent synchronized captions.

    +
    +
    +
    Descriptive transcripts
    +

    A transcript is available whenever audio or visual alternatives are used.

    +
    +
    +
    Findable media alternatives
    +

    Media that has the desired media alternatives (captions, audio descriptions, and descriptive transcripts) can be found. (Needs additional research).

    +

    Needs additional research

    +
    +
    +
    Preferred language
    +

    Equivalent audio alternatives are available in the preferred language.

    +

    Needs additional research

    +
    +
    +

    Non-verbal cues

    +

    Media alternatives explain nonverbal cues, such as tone of voice, facial expressions, body gestures, or music with emotional meaning.

    +

    Needs additional research

    +
    -

    Supplemental

    -
    -
    Supplimentary indicators
    -

    @@

    -
    - -

    Assertions

    -
    -
    Style Guide
    -

    Focus indicators follow an organizational style guide.

    -
    -
    -
    -

    Pointer Focus Appearance

    -

    Users can see the location of the pointer focus.

    -
    -
    Pointer visible
    -

    There is a visible indicator of pointer focus.

    +
    +

    Nontext alternatives

    +

    Users have alternatives available for non-text, non-image content that conveys context or meaning.

    +
    +
    Nontext content
    +

    Equivalent text alternatives are available for non-text, non-image content that conveys context or meaning.

    +

    Needs additional research

    +
    -
    -
    -

    Navigating content

    -

    Users can determine where they are and move through content (including interactive elements) in a systematic and meaningful way regardless of input or movement method.

    -
    -
    Focus in viewport
    -

    The focus does not move to a position outside the current viewport, unless a mechanism is available to return to the previous focus point.

    -
    -
    -
    Focus retention
    -

    A user can focus on a content “area,” such as a modal or pop-up, then resume their view of all content using a limited number of steps.

    -
    -
    -
    Keyboard focus order
    -

    The keyboard focus moves sequentially through content in an order and way that preserves meaning and operability.

    -
    -
    -
    Restore focus
    -

    When the focus is moved by the content into a temporary change of view (e.g. a modal), the focus is restored to its previous location when the view is restored.

    -
    -
    -
    Relevant focus
    -

    The focus order does not include repetitive, hidden, or static elements.

    -
    -
    +
    +

    Figure captions

    +

    Users can view figure captions even if not focused at figure.

    -
    -

    Expected behavior

    -

    Users have interactive components that behave as expected.

    -
    -
    Consistent Interaction
    -

    Interactive components with the same functionality behave consistently.

    -
    -
    -
    Consistent labels
    -

    Interactive components with the same functionality have consistent labels.

    -
    -
    -
    Consistent visual design
    -

    Interactive components that have similar function and behavior have a consistent visual design.

    -
    -
    -
    Control location
    -

    Interactive components are visually and programmatically located in conventional locations.

    -

    Needs additional research

    -
    -
    -
    -
    Conventions
    -

    Interactive components follow established conventions.

    -

    Needs additional research

    -
    -
    -
    Familiar component
    -

    Conventional interactive components are used.

    +
    +
    Persistent captions
    +

    Figure captions persist or can be made to persist even if the focus moves away.

    +

    Needs additional research

    +
    -
    Reliable positioning
    -

    Interactive components retain their position unless a user changes the viewport or moves the component.

    + +
    +

    Single Sense

    +

    Users have content that does not rely on a single sense or perception.

    +
    +
    Use of hue
    +

    Information conveyed by graphical elements does not rely on hue.

    +

    Needs additional research

    +
    +
    +
    Use of visual depth
    +

    Information conveyed with visual depth is also conveyed programmatically and/or through text.

    +

    Needs additional research

    +
    +
    +
    Use of sound
    +

    Information conveyed with sound is also conveyed programmatically and/or through text.

    +
    +
    +
    Use of spatial audio
    +

    Information that is conveyed with spatial audio is also conveyed programmatically and/or through text.

    +
    -
    -

    Control information

    -

    Users have information about interactive components that is identifiable and usable visually and using assistive technology.

    - -
    -
    Control importance
    -

    The importance of interactive components is indicated.

    -

    Needs additional research

    -
    -
    -
    Control labels
    -

    Interactive components have visible labels that identify the purpose of the component.

    -
    -
    -
    Control updates
    -

    Changes to interactive components’ names, roles, values or states are visually and programmatically indicated.

    -
    -
    -
    Distinguishable controls
    -

    Interactive components are visually distinguishable without interaction from static content and include visual cues on how to use them.

    -
    -
    -
    Field constraints
    -

    Field constraints and conditions (required line length, date format, password format, etc) are available.

    -
    -
    -
    Input labels
    -

    Inputs have visible labels that identify the purpose of the input.

    -
    -
    -
    Label in name
    -

    The programmatic name includes the visual label.

    -
    -
    -
    Name, role, value, state
    -

    Accurate names, roles, values, and states are available for interactive components.

    -
    -
    -
    +

    Interactive components

    +
    +

    Keyboard Focus Appearance

    +

    Users can see which element has keyboard focus.

    + +

    Foundational

    +

    For each focusable item: +

      +
    1. Is the user-agent default focus indicator used? + +
      2. -
      -

      Input / Operation

      -
      -

      Input pperation

      -

      Users can use different input techniques and combinations and switch between them.

      -
      -
      Concurrent inputs
      -

      Any input modality available on a platform can be used concurrently.

      -
      -
      -
      Hover information
      -

      Users can dismiss additional content (triggered by hover) without moving the pointer, unless the additional content communicates an input error or does not obscure or replace other content.

      -
      -
      -
      Input control
      -

      Interactive components are available to all navigation and input methods.

      -
      -
      +
    2. Is the user-agent default focus indicator used, and meets contrast across backgrounds? + +
      3. -
      -

      Content changes

      -

      Users are aware of changes to content or context.

      -
      -
      Notify about change
      -

      Changes in content and updates notify users, regardless of the update speed. +

    3. Is the focus indicator defined by the author? + +
      4. +

    -
    -
    -
    Notify on change
    -

    Notification is provided when viewing content that was previously viewed is changed.

    -
    -
    -
    Inform before activation
    -

    Interactive components that can alter the order of content convey their purpose prior to activation, and convey their impact on content order when activated.

    -
    -
    -
    Reverse change of context
    -

    Components that trigger a 'change of context' are indicated, or the change of context can be reversed.

    -
    -
    -
    -

    Target size

    -

    Users are not required to accurately position a pointer in order to view or operate content.

    -
    -
    Target size minimum
    -

    The combined target size and spacing to adjacent targets is at least 24x24 pixels -

    -
    -
    -
    Target size optimum
    -

    The combined target size and spacing to adjacent targets is at least 48x48 pixels.

    -
    -
    +
    +
    Custom indicator
    +

    A custom focus indicator is used with sufficient size, change of contrast, adjacent contrast, distinct style and adjacecy.

    +
    +
    +
    Default indicator
    +

    The platform’s default indicator is used, and where the backgrounds are changed, the indicator contrast is checked.

    +
    +
    +
    User agent default indicator
    +

    Focusable item uses the user agent default indicator.

    +
    -
    -

    Keyboard operation

    -

    Users can navigate and operate content using only the keyboard focus.

    -
    -
    Comparable keyboard effort
    -

    The number of input commands required to complete a task using the keyboard is similar to the number of input commands when using other input modalities.

    -

    Needs additional research

    -
    -
    -
    Conflicting keyboard commands
    -

    Authored keyboard commands do not conflict with platform commands or they can be remapped.

    -
    -
    -
    Consistent keyboard interaction
    -

    Keyboard interface interactions are consistent.

    -
    -
    -
    Keyboard mode
    -

    If the keyboard is non-hardware (such as a virtual keyboard), the keyboard input mode is indicated.

    -
    -
    -
    Keyboard only
    -

    All functionality must be accessible through the keyboard, except when a task requires input based on the user's specific input action.

    -
    -
    -
    No keyboard trap
    -

    If keyboard focus can be moved to an interactive component, then the keyboard focus can be moved away from that component, or the component can be dismissed, with focus returning to the previous point.

    -
    -
    -
    Non-standard commands
    -

    The user is informed of non-standard authored keyboard commands.

    +

    Supplemental

    +
    +
    Supplimentary indicators
    +

    @@

    +
    + +

    Assertions

    +
    +
    Style Guide
    +

    Focus indicators follow an organizational style guide.

    +
    -
    -
    -

    Gestures

    -

    Users are not required to use gestures or dragging to view or operate content.

    -
    -
    Change focus with pointer device
    -

    Selecting an interactive component with a ‘pointer’ sets the focus to that element.

    -
    -
    -
    Complex pointer inputs
    -

    Every function that can be operated by a pointer, can be operated by a ‘single pointer input’ or a sequence of single pointer inputs without requiring certain timing.

    -
    -
    -
    Pointer-agnostic
    -

    Functionality which supports pointers is available to any pointer device supported by the platform.

    -
    -
    -
    Pointer cancellation
    -

    The method of pointer cancellation is consistent.

    -
    -
    -
    Specific pressure
    -

    Where specific pressures are used, they can be adjusted and/or disabled without loss of function.

    -

    Needs additional research

    -
    -
    -
    Speed insensitive
    -

    Where specific speeds are used, they can be adjusted and/or disabled without loss of function.

    -

    Needs additional research

    +
    +

    Pointer Focus Appearance

    +

    Users can see the location of the pointer focus.

    +
    +
    Pointer visible
    +

    There is a visible indicator of pointer focus.

    +
    -
    -
    -

    Motion input

    -

    Users are not required to move their bodies or devices to operate functionality.

    -
    -
    Use without body movement
    -

    All functionality that requires full or gross body movement may also be accomplished with a standard input device.

    -
    -
    -
    Use without device movement
    -

    All functionality can be completed without reorienting or repositioning hardware devices.

    +
    +

    Navigating content

    +

    Users can determine where they are and move through content (including interactive elements) in a systematic and meaningful way regardless of input or movement method.

    +
    +
    Focus in viewport
    +

    The focus does not move to a position outside the current viewport, unless a mechanism is available to return to the previous focus point.

    +
    +
    +
    Focus retention
    +

    A user can focus on a content “area,” such as a modal or pop-up, then resume their view of all content using a limited number of steps.

    +
    +
    +
    Keyboard focus order
    +

    The keyboard focus moves sequentially through content in an order and way that preserves meaning and operability.

    +
    +
    +
    Restore focus
    +

    When the focus is moved by the content into a temporary change of view (e.g. a modal), the focus is restored to its previous location when the view is restored.

    +
    +
    +
    Relevant focus
    +

    The focus order does not include repetitive, hidden, or static elements.

    +
    -
    -
    Interactive component contrast
    -

    Visual information required to identify user interface components and states meet a ‘minimum contrast ratio test’, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author.

    -

    Needs additional research

    -
    -
    -
    -
    -

    Layout

    -
    -

    Relationships

    -

    Users can determine relationships between content both visually and using assistive technologies.

    -
    -
    Clear relationships
    -

    The relationships between parts of the content is clearly indicated.

    -
    -
    -
    Clear starting point
    -

    The starting point or home is visually and programmatically labeled.

    -
    -
    -
    Distinguishable relationships
    -

    Relationships that convey meaning between pieces of content are programmatically determinable. Note: Examples of relationships include items positioned next to each other, arranged in a hierarchy, or visually grouped.

    -

    Needs additional research

    -
    -
    -
    Distinguishable sections
    -

    Sections are visually and programmatically distinguishable.

    -

    Needs additional research

    +
    +

    Expected behavior

    +

    Users have interactive components that behave as expected.

    +
    +
    Consistent Interaction
    +

    Interactive components with the same functionality behave consistently.

    +
    +
    +
    Consistent labels
    +

    Interactive components with the same functionality have consistent labels.

    +
    +
    +
    Consistent visual design
    +

    Interactive components that have similar function and behavior have a consistent visual design.

    +
    +
    +
    Control location
    +

    Interactive components are visually and programmatically located in conventional locations.

    +

    Needs additional research

    +
    +
    +
    +
    Conventions
    +

    Interactive components follow established conventions.

    +

    Needs additional research

    +
    +
    +
    Familiar component
    +

    Conventional interactive components are used.

    +
    +
    Reliable positioning
    +

    Interactive components retain their position unless a user changes the viewport or moves the component.

    +
    -
    -
    -

    Recognizable layouts

    -

    Users have consistent and recognizable layouts available.

    -
    -
    Consistent order
    -

    The relative order of content and interactions remain consistent throughout a workflow. Note: Relative order means that content can be added or removed, but repeated items are in the same order relative to each other.

    -
    -
    -
    Familiar layout
    -

    Conventional layouts are available.

    -
    -
    -
    Information about options
    -

    Information required to understand options is visually and programmatically associated with the options.

    -
    -
    -
    Related information
    -

    Related information is grouped together within a visual and programmatic structure.

    -
    -
    +
    +

    Control information

    +

    Users have information about interactive components that is identifiable and usable visually and using assistive technology.

    -
    -

    Orientation

    -

    Users can determine their location in content both visually and using assistive technologies.

    -
    -
    Current location
    -

    The current location within the view, multi-step process, and product is visually and programmatically indicated.

    -

    Needs additional research

    -
    -
    -
    Multistep process
    -

    Provides context that orients the user in a site or multi-step process.

    -
    -
    -
    Contextual information
    -

    Provide contextual information to help the user orient within the product.

    +
    +
    Control importance
    +

    The importance of interactive components is indicated.

    +

    Needs additional research

    +
    +
    +
    Control labels
    +

    Interactive components have visible labels that identify the purpose of the component.

    +
    +
    +
    Control updates
    +

    Changes to interactive components’ names, roles, values or states are visually and programmatically indicated.

    +
    +
    +
    Distinguishable controls
    +

    Interactive components are visually distinguishable without interaction from static content and include visual cues on how to use them.

    +
    +
    +
    Field constraints
    +

    Field constraints and conditions (required line length, date format, password format, etc) are available.

    +
    +
    +
    Input labels
    +

    Inputs have visible labels that identify the purpose of the input.

    +
    +
    +
    Label in name
    +

    The programmatic name includes the visual label.

    +
    +
    +
    Name, role, value, state
    +

    Accurate names, roles, values, and states are available for interactive components.

    +
    -
    -

    Structure

    -

    Users can understand and navigate through the content using structure.

    -
    -
    Section labels
    -

    Major sections of content have within them well structured, understandable visual and programmatic headings.

    -
    -
    -
    Section length
    -

    Content is organized into short sections of related content.

    -

    Needs additional research

    -
    -
    -
    Section purpose
    -

    The purpose of each section of the content is clearly indicated.

    -
    -
    -
    Single idea
    -

    The number of concepts within a segment of text is minimized.

    -
    -
    -
    White spacing
    -

    Whitespace separates chunks of content.

    -
    -
    -
    Title
    -

    Content has a title or high-level description.

    -
    -
    -
    Lists
    -

    Three or more items of related data are presented as bulleted or numbered lists.

    -
    -
    -
    Numbered steps
    -

    Steps in a multi-step process are numbered.

    +
    +

    Input / Operation

    +
    +

    Input pperation

    +

    Users can use different input techniques and combinations and switch between them.

    +
    +
    Concurrent inputs
    +

    Any input modality available on a platform can be used concurrently.

    +
    +
    +
    Hover information
    +

    Users can dismiss additional content (triggered by hover) without moving the pointer, unless the additional content communicates an input error or does not obscure or replace other content.

    +
    +
    +
    Input control
    +

    Interactive components are available to all navigation and input methods.

    +
    -
    -
    -
    -

    Consistency across views

    -
    -

    Consistency

    -

    Users have consistent and alternative methods for navigation.

    -
    -
    Consistent navigation
    -

    Navigation elements remain consistent across views within the product.

    -
    -
    -
    Multiple ways
    -

    The product provides at least two ways of navigating and finding information (Search, Scan, Site Map, Menu Structure, Breadcrumbs, contextual links, etc).

    +
    +

    Content changes

    +

    Users are aware of changes to content or context.

    +
    +
    Notify about change
    +

    Changes in content and updates notify users, regardless of the update speed. +

    +
    +
    +
    Notify on change
    +

    Notification is provided when viewing content that was previously viewed is changed.

    +
    +
    +
    Inform before activation
    +

    Interactive components that can alter the order of content convey their purpose prior to activation, and convey their impact on content order when activated.

    +
    +
    +
    Reverse change of context
    +

    Components that trigger a 'change of context' are indicated, or the change of context can be reversed.

    +
    -
    -
    Persistent navigation
    -

    Navigation features are available regardless of screen size and magnification (responsive design)

    + +
    +

    Target size

    +

    Users are not required to accurately position a pointer in order to view or operate content.

    +
    +
    Target size minimum
    +

    The combined target size and spacing to adjacent targets is at least 24x24 pixels +

    +
    +
    +
    Target size optimum
    +

    The combined target size and spacing to adjacent targets is at least 48x48 pixels.

    +
    -
    -
    -
    -

    Policy and Protection

    -
    -

    Content source

    -

    Users can determine when content is provided by a Third Party

    -
    -
    Citation
    -

    The author or source of the primary content is visually and programmatically indicated.

    -

    Needs additional research

    +
    +

    Keyboard operation

    +

    Users can navigate and operate content using only the keyboard focus.

    +
    +
    Comparable keyboard effort
    +

    The number of input commands required to complete a task using the keyboard is similar to the number of input commands when using other input modalities.

    +

    Needs additional research

    +
    +
    +
    Conflicting keyboard commands
    +

    Authored keyboard commands do not conflict with platform commands or they can be remapped.

    +
    +
    +
    Consistent keyboard interaction
    +

    Keyboard interface interactions are consistent.

    +
    +
    +
    Keyboard mode
    +

    If the keyboard is non-hardware (such as a virtual keyboard), the keyboard input mode is indicated.

    +
    +
    +
    Keyboard only
    +

    All functionality must be accessible through the keyboard, except when a task requires input based on the user's specific input action.

    +
    +
    +
    No keyboard trap
    +

    If keyboard focus can be moved to an interactive component, then the keyboard focus can be moved away from that component, or the component can be dismissed, with focus returning to the previous point.

    +
    +
    +
    Non-standard commands
    +

    The user is informed of non-standard authored keyboard commands.

    +
    -
    -
    Indicate 3rd party content
    -

    Third party content (AI, Advertising, etc.) is visually and programmatically indicated.

    -

    Needs additional research

    + +
    +

    Gestures

    +

    Users are not required to use gestures or dragging to view or operate content.

    +
    +
    Change focus with pointer device
    +

    Selecting an interactive component with a ‘pointer’ sets the focus to that element.

    +
    +
    +
    Complex pointer inputs
    +

    Every function that can be operated by a pointer, can be operated by a ‘single pointer input’ or a sequence of single pointer inputs without requiring certain timing.

    +
    +
    +
    Pointer-agnostic
    +

    Functionality which supports pointers is available to any pointer device supported by the platform.

    +
    +
    +
    Pointer cancellation
    +

    The method of pointer cancellation is consistent.

    +
    +
    +
    Specific pressure
    +

    Where specific pressures are used, they can be adjusted and/or disabled without loss of function.

    +

    Needs additional research

    +
    +
    +
    Speed insensitive
    +

    Where specific speeds are used, they can be adjusted and/or disabled without loss of function.

    +

    Needs additional research

    +
    -
    -
    Obscuring primary content
    -

    Advertising and other third-party content that obscures the primary content can be moved or removed without interacting with the advertising or third-party content.

    -

    Needs additional research

    + +
    +

    Motion input

    +

    Users are not required to move their bodies or devices to operate functionality.

    +
    +
    Use without body movement
    +

    All functionality that requires full or gross body movement may also be accomplished with a standard input device.

    +
    +
    +
    Use without device movement
    +

    All functionality can be completed without reorienting or repositioning hardware devices.

    +
    +
    +
    Interactive component contrast
    +

    Visual information required to identify user interface components and states meet a ‘minimum contrast ratio test’, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author.

    +

    Needs additional research

    +
    -
    -

    Security and Privacy

    -

    Users’ safety, security or privacy are not decreased by accessibility measures.

    -
    -
    Clear agreement
    -

    The interface indicates when a user is entering an agreement or submitting data.

    -

    Needs additional research

    -
    -
    -
    Disability information privacy
    -

    Disability information is not disclosed to or used by third parties and algorithms (including AI).

    -

    Needs additional research

    +
    +

    Layout

    +
    +

    Relationships

    +

    Users can determine relationships between content both visually and using assistive technologies.

    +
    +
    Clear relationships
    +

    The relationships between parts of the content is clearly indicated.

    +
    +
    +
    Clear starting point
    +

    The starting point or home is visually and programmatically labeled.

    +
    +
    +
    Distinguishable relationships
    +

    Relationships that convey meaning between pieces of content are programmatically determinable. Note: Examples of relationships include items positioned next to each other, arranged in a hierarchy, or visually grouped.

    +

    Needs additional research

    +
    +
    +
    Distinguishable sections
    +

    Sections are visually and programmatically distinguishable.

    +

    Needs additional research

    +
    -
    -
    Sensitive information
    -

    Prompts to hide and remove sensitive information from observers are available.

    -

    Needs additional research

    -
    -
    -
    Risk statements
    -

    Clear explanations of the risks and consequences of choices, including use, are stated.

    -

    Needs additional research

    + + +
    +

    Recognizable layouts

    +

    Users have consistent and recognizable layouts available.

    +
    +
    Consistent order
    +

    The relative order of content and interactions remain consistent throughout a workflow. Note: Relative order means that content can be added or removed, but repeated items are in the same order relative to each other.

    +
    +
    +
    Familiar layout
    +

    Conventional layouts are available.

    +
    +
    +
    Information about options
    +

    Information required to understand options is visually and programmatically associated with the options.

    +
    +
    +
    Related information
    +

    Related information is grouped together within a visual and programmatic structure.

    +
    -
    -
    -

    Algorithms

    -

    Users are not disadvantaged by algorithms.

    -
    -
    Algorithm bias
    -

    Algorithms (including AI) used are not biased against people with disabilities.

    -

    Needs additional research

    +
    +

    Orientation

    +

    Users can determine their location in content both visually and using assistive technologies.

    +
    +
    Current location
    +

    The current location within the view, multi-step process, and product is visually and programmatically indicated.

    +

    Needs additional research

    +
    +
    +
    Multistep process
    +

    Provides context that orients the user in a site or multi-step process.

    +
    +
    +
    Contextual information
    +

    Provide contextual information to help the user orient within the product.

    +
    -
    -
    Social media algorithm
    -

    A mechanism is available to understand and control social media algorithms.

    -

    Needs additional research

    -
    -
    -
    -
    -

    Text and Wording

    -

    Text appearance

    -

    Users can read visually rendered text.

    -
    -
    Maximum text contrast
    -

    The rendered text against its background meets a maximum ‘contrast ratio test’ for its text appearance.

    -

    Needs additional research

    +

    Structure

    +

    Users can understand and navigate through the content using structure.

    +
    +
    Section labels
    +

    Major sections of content have within them well structured, understandable visual and programmatic headings.

    +
    +
    +
    Section length
    +

    Content is organized into short sections of related content.

    +

    Needs additional research

    +
    +
    +
    Section purpose
    +

    The purpose of each section of the content is clearly indicated.

    +
    +
    +
    Single idea
    +

    The number of concepts within a segment of text is minimized.

    +
    +
    +
    White spacing
    +

    Whitespace separates chunks of content.

    +
    +
    +
    Title
    +

    Content has a title or high-level description.

    +
    +
    +
    Lists
    +

    Three or more items of related data are presented as bulleted or numbered lists.

    +
    +
    +
    Numbered steps
    +

    Steps in a multi-step process are numbered.

    +
    -
    -
    Minimum text contrast
    -

    The rendered text against its background meets a minimum 'contrast ratio test' for its text appearance.

    -

    Needs additional research

    -
    -
    -
    Text size
    -

    The rendered text meets a minimum font size and weight.

    -

    Needs additional research

    -
    -
    -
    Text style
    -

    The rendered text does not use a decorative or cursive font face.

    -
    -
    -

    Text-to-speech

    -

    Users can access text content and its meaning with text-to-speech tools.

    -
    -
    Text-to-speech supported
    -

    Text content can be converted into speech.

    -

    Needs additional research

    -
    +
    +

    Consistency across views

    +
    +

    Consistency

    +

    Users have consistent and alternative methods for navigation.

    -
    Human language
    -

    The human language of the view and content within the view is programmatically available.

    -
    -
    -
    Semantic text appearance
    -

    Meaning conveyed by text appearance is programmatically available.

    -

    Needs additional research

    +
    Consistent navigation
    +

    Navigation elements remain consistent across views within the product.

    +
    +
    +
    Multiple ways
    +

    The product provides at least two ways of navigating and finding information (Search, Scan, Site Map, Menu Structure, Breadcrumbs, contextual links, etc).

    +
    +
    +
    Persistent navigation
    +

    Navigation features are available regardless of screen size and magnification (responsive design)

    +
    -
    -

    Clear language

    -

    Users can access clear language content.

    -
    -
    Acronyms and abbreviations
    -

    The expanded form or meaning of abbreviations and acronyms is available.

    -
    -
    -
    Ambiguous numbers
    -

    Alternative formats for ambiguous number formats are available.

    -
    -
    -
    Ambiguous pronunciation
    -

    All letters and diacritics needed to identify (phonetically read) words are available.

    -
    -
    -
    Appropriate tone
    -

    The language and tone used is respectful and appropriate to the topic or subject matter.

    -

    Needs additional research

    -
    -
    -
    Double negatives
    -

    Content does not include double negatives to express a positive unless it is standard usage for that language or dialect.

    -
    -
    -
    Figurative language
    -

    Explanations for figurative and non-literal language [such as jokes, sarcasm, hyperbole, metaphors, similes, and idioms] are available.

    -
    -
    -
    Sentence voice
    -

    The voice used is easiest to understand in context.

    -

    Needs additional research

    -
    -
    -
    Topic sentence
    -

    For text intended to inform the user, each paragraph of text begins with a topic sentence stating the aim or purpose.

    -
    -
    -
    Uncommon words
    -

    Definitions for uncommon or new words are available.

    -

    Needs additional research

    -
    -
    -
    Unnecessary words or phrases
    -

    Sentences are concise, without unnecessary filler words and phrases.

    -
    -
    -
    Verb tense
    -

    The verb tense used is easiest to understand in context.

    -

    Needs additional research

    +
    +

    Policy and Protection

    +
    +

    Content source

    +

    Users can determine when content is provided by a Third Party

    +
    +
    Citation
    +

    The author or source of the primary content is visually and programmatically indicated.

    +

    Needs additional research

    +
    +
    +
    Indicate 3rd party content
    +

    Third party content (AI, Advertising, etc.) is visually and programmatically indicated.

    +

    Needs additional research

    +
    +
    +
    Obscuring primary content
    +

    Advertising and other third-party content that obscures the primary content can be moved or removed without interacting with the advertising or third-party content.

    +

    Needs additional research

    +
    -
    -
    -
    -

    Help and feedback

    -
    -

    Help available

    -

    Users have help available.

    -
    -
    Consistent help
    -

    Help is labeled consistently and available in a consistent visual and programmatic location.

    -

    Needs additional research

    -
    -
    -
    Contextual help
    -

    Contextual help is available.

    -
    -
    -
    Conversational support
    -

    Conversational support allowing both text and verbal modes is available.

    -
    -
    -
    Data visualizations
    -

    Help is available to understand and use data visualizations.

    -

    Needs additional research

    -
    -
    -
    New interfaces
    -

    When interfaces dramatically change (due to redesign), a mechanism to learn the new interface or revert to the older design is available.

    -

    Needs additional research

    -
    -
    -
    Personalizable help
    -

    Help is adaptable and personalizable.

    -

    Needs additional research

    -
    -
    -

    Sensory characteristics

    -

    Instructions and help do not rely on sensory characteristics.

    +
    +

    Security and Privacy

    +

    Users’ safety, security or privacy are not decreased by accessibility measures.

    +
    +
    Clear agreement
    +

    The interface indicates when a user is entering an agreement or submitting data.

    +

    Needs additional research

    +
    +
    +
    Disability information privacy
    +

    Disability information is not disclosed to or used by third parties and algorithms (including AI).

    +

    Needs additional research

    +
    +
    +
    Sensitive information
    +

    Prompts to hide and remove sensitive information from observers are available.

    +

    Needs additional research

    +
    +
    +
    Risk statements
    +

    Clear explanations of the risks and consequences of choices, including use, are stated.

    +

    Needs additional research

    +
    -
    -
    Support available
    -

    Accessible support is available during data entry, task completion and search.

    -

    Needs additional research

    + +
    +

    Algorithms

    +

    Users are not disadvantaged by algorithms.

    +
    +
    Algorithm bias
    +

    Algorithms (including AI) used are not biased against people with disabilities.

    +

    Needs additional research

    +
    +
    +
    Social media algorithm
    +

    A mechanism is available to understand and control social media algorithms.

    +

    Needs additional research

    +
    -
    -

    Supplemental content

    -

    Users have supplemental content available.

    -
    -
    Number supplements
    -

    Text or visual alternatives are available for numerical concepts.

    +
    +

    Text and Wording

    +
    +

    Text appearance

    +

    Users can read visually rendered text.

    +
    +
    Maximum text contrast
    +

    The rendered text against its background meets a maximum ‘contrast ratio test’ for its text appearance.

    +

    Needs additional research

    +
    +
    +
    Minimum text contrast
    +

    The rendered text against its background meets a minimum 'contrast ratio test' for its text appearance.

    +

    Needs additional research

    +
    +
    +
    Text size
    +

    The rendered text meets a minimum font size and weight.

    +

    Needs additional research

    +
    +
    +
    Text style
    +

    The rendered text does not use a decorative or cursive font face.

    +
    -
    -
    Text supplements
    -

    Visual illustrations, pictures, and images are available to help explain complex ideas, events, and processes.

    -

    Needs additional research

    + +
    +

    Text-to-speech

    +

    Users can access text content and its meaning with text-to-speech tools.

    +
    +
    Text-to-speech supported
    +

    Text content can be converted into speech.

    +

    Needs additional research

    +
    +
    +
    Human language
    +

    The human language of the view and content within the view is programmatically available.

    +
    +
    +
    Semantic text appearance
    +

    Meaning conveyed by text appearance is programmatically available.

    +

    Needs additional research

    +
    -
    -
    -

    Feedback

    -

    Users can provide feedback to authors.

    -
    -
    Feedback mechanism
    -

    A mechanism is available to provide feedback to authors.

    +
    +

    Clear language

    +

    Users can access clear language content.

    +
    +
    Acronyms and abbreviations
    +

    The expanded form or meaning of abbreviations and acronyms is available.

    +
    +
    +
    Ambiguous numbers
    +

    Alternative formats for ambiguous number formats are available.

    +
    +
    +
    Ambiguous pronunciation
    +

    All letters and diacritics needed to identify (phonetically read) words are available.

    +
    +
    +
    Appropriate tone
    +

    The language and tone used is respectful and appropriate to the topic or subject matter.

    +

    Needs additional research

    +
    +
    +
    Double negatives
    +

    Content does not include double negatives to express a positive unless it is standard usage for that language or dialect.

    +
    +
    +
    Figurative language
    +

    Explanations for figurative and non-literal language [such as jokes, sarcasm, hyperbole, metaphors, similes, and idioms] are available.

    +
    +
    +
    Sentence voice
    +

    The voice used is easiest to understand in context.

    +

    Needs additional research

    +
    +
    +
    Topic sentence
    +

    For text intended to inform the user, each paragraph of text begins with a topic sentence stating the aim or purpose.

    +
    +
    +
    Uncommon words
    +

    Definitions for uncommon or new words are available.

    +

    Needs additional research

    +
    +
    +
    Unnecessary words or phrases
    +

    Sentences are concise, without unnecessary filler words and phrases.

    +
    +
    +
    Verb tense
    +

    The verb tense used is easiest to understand in context.

    +

    Needs additional research

    +
    -
    -
    -

    User Control

    -
    -

    Control text

    -

    Users can control text presentation.

    -
    -
    Adjust color
    -

    Text and background colors can be customized.

    -
    -
    -
    Adjust background
    -

    Patterns, designs or images placed behind text are avoided or can be removed by the user.

    -
    -
    -
    Font size meaning
    -

    When font size conveys visual meaning (such as headings), the text maintains its meaning and purpose when text is resized.

    -
    -
    -
    Text customization
    -

    Users can change the text style (like font and size) and the layout (such as spacing and single column) to fit their needs.

    +
    +

    Help and feedback

    +
    +

    Help available

    +

    Users have help available.

    +
    +
    Consistent help
    +

    Help is labeled consistently and available in a consistent visual and programmatic location.

    +

    Needs additional research

    +
    +
    +
    Contextual help
    +

    Contextual help is available.

    +
    +
    +
    Conversational support
    +

    Conversational support allowing both text and verbal modes is available.

    +
    +
    +
    Data visualizations
    +

    Help is available to understand and use data visualizations.

    +

    Needs additional research

    +
    +
    +
    New interfaces
    +

    When interfaces dramatically change (due to redesign), a mechanism to learn the new interface or revert to the older design is available.

    +

    Needs additional research

    +
    +
    +
    Personalizable help
    +

    Help is adaptable and personalizable.

    +

    Needs additional research

    +
    +
    +

    Sensory characteristics

    +

    Instructions and help do not rely on sensory characteristics.

    +
    +
    +
    Support available
    +

    Accessible support is available during data entry, task completion and search.

    +

    Needs additional research

    +
    -
    -
    -

    Adjustable viewport

    -

    Users can transform size and orientation if content presentation to make it viewable and usable.

    -
    -
    Orientation
    -

    Content orientation allows the user to read the language presented without changing head or body position.

    -
    -
    -
    Reflow
    -

    Content can be viewed in multiple viewport sizes, orientations, and zoom levels -- without loss of content, functionality, meaningful relationships, and with scrolling only occurring in one direction.

    +
    +

    Supplemental content

    +

    Users have supplemental content available.

    +
    +
    Number supplements
    +

    Text or visual alternatives are available for numerical concepts.

    +
    +
    +
    Text supplements
    +

    Visual illustrations, pictures, and images are available to help explain complex ideas, events, and processes.

    +

    Needs additional research

    +
    -
    -
    -

    Transform content

    -

    Users can transform content to make it understandable.

    -
    -
    Alternative presentation
    -

    Complex information or instructions for complex processes are available in multiple presentation formats.

    -

    Needs additional research

    -
    -
    -
    Content markup
    -

    Role and priority of content is programmatically determinable.

    -
    -
    -
    Summary
    -

    Access to a plain-language summary, abstract, or executive summaries is available.

    -
    -
    -
    Transform content
    -

    Content can be transformed to make its purpose clearer.

    -

    Needs additional research

    +
    +

    Feedback

    +

    Users can provide feedback to authors.

    +
    +
    Feedback mechanism
    +

    A mechanism is available to provide feedback to authors.

    +
    -
    -

    Media control

    -

    Users can control media and media alternative.

    -
    -
    Adjust captions
    -

    The position and formatting of captions can be changed.

    +
    +

    User Control

    +
    +

    Control text

    +

    Users can control text presentation.

    +
    +
    Adjust color
    +

    Text and background colors can be customized.

    +
    +
    +
    Adjust background
    +

    Patterns, designs or images placed behind text are avoided or can be removed by the user.

    +
    +
    +
    Font size meaning
    +

    When font size conveys visual meaning (such as headings), the text maintains its meaning and purpose when text is resized.

    +
    +
    +
    Text customization
    +

    Users can change the text style (like font and size) and the layout (such as spacing and single column) to fit their needs.

    +
    -
    -
    Audio control
    -

    Audio can be turned off, while still playing the video, and without affecting the system sound.

    + +
    +

    Adjustable viewport

    +

    Users can transform size and orientation if content presentation to make it viewable and usable.

    +
    +
    Orientation
    +

    Content orientation allows the user to read the language presented without changing head or body position.

    +
    +
    +
    Reflow
    +

    Content can be viewed in multiple viewport sizes, orientations, and zoom levels -- without loss of content, functionality, meaningful relationships, and with scrolling only occurring in one direction.

    +
    -
    -
    Interactive audio alternative
    -

    Alternatives for audio include the ability to search and look up terms.

    -

    Needs additional research

    + +
    +

    Transform content

    +

    Users can transform content to make it understandable.

    +
    +
    Alternative presentation
    +

    Complex information or instructions for complex processes are available in multiple presentation formats.

    +

    Needs additional research

    +
    +
    +
    Content markup
    +

    Role and priority of content is programmatically determinable.

    +
    +
    +
    Summary
    +

    Access to a plain-language summary, abstract, or executive summaries is available.

    +
    +
    +
    Transform content
    +

    Content can be transformed to make its purpose clearer.

    +

    Needs additional research

    +
    -
    -
    Media alternative control
    -

    Captions and audio descriptions can be turned on and off.

    + +
    +

    Media control

    +

    Users can control media and media alternative.

    +
    +
    Adjust captions
    +

    The position and formatting of captions can be changed.

    +
    +
    +
    Audio control
    +

    Audio can be turned off, while still playing the video, and without affecting the system sound.

    +
    +
    +
    Interactive audio alternative
    +

    Alternatives for audio include the ability to search and look up terms.

    +

    Needs additional research

    +
    +
    +
    Media alternative control
    +

    Captions and audio descriptions can be turned on and off.

    +
    +
    +
    Media chapters
    +

    Media can be navigated by chapters.

    +

    Needs additional research

    +
    -
    -
    Media chapters
    -

    Media can be navigated by chapters.

    -

    Needs additional research

    -
    -
    -
    -

    Control interruptions

    -

    Users can control interruptions.

    -
    -
    Control notifications
    -

    The timing and positioning of notifications and other interruptions can be changed, suppressed or saved, except interruptions involving an emergency.

    +
    +

    Control interruptions

    +

    Users can control interruptions.

    +
    +
    Control notifications
    +

    The timing and positioning of notifications and other interruptions can be changed, suppressed or saved, except interruptions involving an emergency.

    +
    -
    -
    -

    Control possible harm

    -

    Users can control potential sources of harm.

    -
    -
    Disturbing content
    -

    Warnings are available about content that may be emotionally disturbing, and the disturbing content can be hidden.

    -

    Needs additional research

    -
    -
    -
    Haptic stimulation
    -

    Haptic feedback can be reduced or turned off.

    -

    Needs additional research

    -
    -
    -
    Triggers
    -

    Warnings are available about triggering content, and the warnings and triggering content can be hidden.

    -

    Needs additional research

    -
    -
    -
    Verbosity
    -

    Overwhelming wordiness can be reduced or turned off.

    -

    Needs additional research

    +
    +

    Control possible harm

    +

    Users can control potential sources of harm.

    +
    +
    Disturbing content
    +

    Warnings are available about content that may be emotionally disturbing, and the disturbing content can be hidden.

    +

    Needs additional research

    +
    +
    +
    Haptic stimulation
    +

    Haptic feedback can be reduced or turned off.

    +

    Needs additional research

    +
    +
    +
    Triggers
    +

    Warnings are available about triggering content, and the warnings and triggering content can be hidden.

    +

    Needs additional research

    +
    +
    +
    Verbosity
    +

    Overwhelming wordiness can be reduced or turned off.

    +

    Needs additional research

    +
    +
    +
    Visual stimulation
    +

    Visual stimulation from combinations of density, color, movement, etc. can be reduced or turned off.

    +

    Needs additional research

    +
    -
    -
    Visual stimulation
    -

    Visual stimulation from combinations of density, color, movement, etc. can be reduced or turned off.

    -

    Needs additional research

    -
    -
    -
    -

    User Agent Support

    -

    Users can control content settings from their User Agents including Assistive Technology.

    -
    -
    Assistive technology control
    -

    Content can be controlled using assistive and adaptive technology.

    -
    -
    -
    Printing
    -

    Printing respects user’s content presentation preferences.

    -

    Needs additional research

    -
    -
    -
    User settings
    -

    User settings are honored.

    +
    +

    User Agent Support

    +

    Users can control content settings from their User Agents including Assistive Technology.

    +
    +
    Assistive technology control
    +

    Content can be controlled using assistive and adaptive technology.

    +
    +
    +
    Printing
    +

    Printing respects user’s content presentation preferences.

    +

    Needs additional research

    +
    +
    +
    User settings
    +

    User settings are honored.

    +
    +
    +
    Virtual cursor
    +

    Assistive technologies can access content and interactions when using mechanisms that convey alternative points of regard or focus (i.e. virtual cursor).

    +
    -
    -
    Virtual cursor
    -

    Assistive technologies can access content and interactions when using mechanisms that convey alternative points of regard or focus (i.e. virtual cursor).

    -
    - -
    +

    Conformance

    Summary From 8185ad3e4867f30b604ba563030a26e21a16a33a Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 12 Nov 2024 11:23:57 +0000 Subject: [PATCH 12/49] Update editors --- guidelines/guidelines.js | 7 ------- guidelines/respec-config.js | 37 ++++++++++++------------------------- 2 files changed, 12 insertions(+), 32 deletions(-) diff --git a/guidelines/guidelines.js b/guidelines/guidelines.js index 0fbef6d..d64d770 100644 --- a/guidelines/guidelines.js +++ b/guidelines/guidelines.js @@ -303,12 +303,6 @@ function outputJson() { function loadDoc(path) { } -function authorToPM() { - document.querySelectorAll("div.head dt").forEach(function(node){ - if (node.textContent.trim() == "Authors:" || node.textContent.trim() == "Author:") node.textContent = "Project Manager:"; - }); -} - function moveStatusFilterToToc() { var button = document.querySelector('#status-filter'); var button_parent = button.parentNode; @@ -329,7 +323,6 @@ function preRespec() { // scripts after Respec has run function postRespec() { - authorToPM(); addOutcomeMarkers(); adjustNormativity(); termTitles(); diff --git a/guidelines/respec-config.js b/guidelines/respec-config.js index 5df15ce..87d9ec1 100644 --- a/guidelines/respec-config.js +++ b/guidelines/respec-config.js @@ -29,12 +29,6 @@ var respecConfig = { // editors, add as many as you like // only "name" is required editors:[ { - name: "Jeanne Spellman", - mailto: "jspellman@spellmanconsulting.com", - company: "TetraLogical", - companyURI: "https://tetralogical.com/", - w3cid: 42417 - }, { name: "Rachael Bradley Montgomery", mailto: "rmontgomery@loc.gov", company: "Library of Congress", @@ -58,27 +52,20 @@ var respecConfig = { company: "W3C", companyURI: "https://www.w3.org/", w3cid: 71819 - }], - formerEditors: [{ - name: "Michael Cooper", - mailto: "cooper@w3.org", - company: "W3C", - companyURI: "https://www.w3.org/", - w3cid: 34017 }, { - name: "Shawn Lauriat", - mailto: "lauriat@google.com", - company: "Google, Inc.", - companyURI: "https://www.google.com/", - w3cid: 90646 + name: "Jeanne Spellman", + mailto: "jspellman@spellmanconsulting.com", + company: "TetraLogical", + companyURI: "https://tetralogical.com/", + w3cid: 42417 + }, { + name: "Francis Storr", + mailto: "francis.storr@intel.com", + company: "Intel Corporation", + companyURI: "https://tetralogical.com/", + w3cid: 90883 }], - authors: [{ - name: "Wilco Fiers", - mailto: "wilco.fiers@deque.com", - company: "Deque Systems, Inc.", - companyURI: "https://www.deque.com/", - w3cid: 43334 - }], + // authors, add as many as you like. // This is optional, uncomment if you have authors as well as editors. From 500de0694e495c77518eff14bd86666426aabece Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 12 Nov 2024 11:54:05 +0000 Subject: [PATCH 13/49] Removing Explainer material --- guidelines/index.html | 434 ++---------------------------------- guidelines/respec-config.js | 7 + 2 files changed, 28 insertions(+), 413 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index f5353b2..7ec1c18 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -1235,400 +1235,47 @@
    Virtual cursor

    Conformance

    Summary -

    You might want to make a claim that your content or product meets the WCAG 3 guidelines. If it does meet the guidelines, we call this “conformance.” To conform to WCAG 3, your test results must show that your project is accessible.

    -

    If you want to make a formal conformance claim, you must use the process described in this document. However, conformance claims are not required and your content can conform to WCAG 3, even if you don’t want to make a claim. You can still use this process to test your project’s accessibility.

    +

    You might want to make a claim that your content or product meets the WCAG 3 guidelines. If it does meet the guidelines, we call this “conformance”.

    +

    If you want to make a formal conformance claim, you must use the process described in this document. Conformance claims are not required and your content can conform to WCAG 3, even if you don’t want to make a claim.

    There are two types of content in this document:

    • Normative: what you must do to meet the guidelines.
    • Non-normative: advice to help you meet the guidelines. This is also called informative.
    -

    There are a variety of ways to say what is required in WCAG 3. We are experimenting with different approaches. Once we have developed enough guidelines, we will test how well each works. Here are some of the ideas for WCAG 3 requirements:

    -
      -
    • Two ways of evaluating accessibility: -
      • Outcomes are statements that can be tested.
        • -
      • Assertions and procedures are statements that you used an accessible way to create the content that is hard to test. Assertions are new and we are trying different rules for how they can work.
        • -
      • -
    • Outcomes have two (2) types of tests: -
        -
      • Quantifiable tests: Tests where there is a high degree of consistency between test results from different testers. Examples include testing whether certain properties exist in the content or if they match a value specified by the requirement.
        • - -
      • Qualitative tests: Tests that rely on a qualitative evaluation based on existing criteria. Test results may vary between testers who understand the criteria. An example is evaluating the quality of a requirement such as alternative text.
        • -
      • -
    • Tests can be applied to four (4) different scopes: -
        -
      • Item: A component or unit of content. Examples include a drop down menu, a media player, a phrase, or an image.
        • -
      • View: All content visually and programmatically available without a user-initiated substantive change.
        • -
      • User process: Series of user actions, and the distinct items and interactive views that support the actions, where each action is required to complete an activity.
        • -
      • Product: The aggregate of all related items, user processes, and views.
        • -
      • -
    • Three different levels show how accessible the content is: bronze, silver, or gold level.
      • -
    • Issue severity allows different rules for accessibility problems. Rules for problems that block people from using the content are stronger than rules for minor problems.
      • -
    • Adjectival ratings allow testers to grade content using words (fail, pass, great) or numbers (1,2,3). This provides a scale that may better match what people with disabilities go through to use it.
      • -
    • Percentages are used instead of requiring that accessibility be perfect or you fail.
      • -
    • Pre-assessment conditions are tests that coders can use to see if they are ready to start accessibility testing. This is to help coders, not to make a new level of requirements.
      • -
    -

    We intend to address the following topics in the future, but for now, you can skip them.

    -
      -
    • Conforming alternative version - whether WCAG 3 will allow having inaccessible content if there is also an accessible version.
      • -
    • Only accessibility-supported ways of using technologies - this is a complicated topic about different assistive technologies, their features, and the languages they are available in.
      • -
    • Defining conformance scope - WCAG 2.x defines scope as a web page. WCAG 3 will have a broader scope to include the modern web and applications.
      • -
    • Conformance requirements - what someone has to do to meet WCAG 3.
      • -
    • Conformance claims – how to make a statement that you meet WCAG 3.
      • -
    - +

    We are experimenting with different conformance approaches for WCAG 3. Once we have developed enough guidelines, we will test how well each works.

    -
    -

    Normative requirements

    -

    In addition to this section, the Guidelines and Conformance sections in WCAG 3 provide normative content and define requirements that impact conformance claims. Introductory material, appendices, sections marked as non-normative, diagrams, examples, and notes are informative (non-normative). Non-normative material provides advisory information to help interpret the guidelines but does not create requirements that impact a conformance claim.

    -

    The key words MAY, MUST, MUST NOT, NOT RECOMMENDED, RECOMMENDED, SHOULD, and SHOULD NOT in this document are to be interpreted as described in BCP 14 [[RFC2119]] [[RFC8174]] when, and only when, they appear in all capitals, as shown here.

    -
    -
    -

    Approaches to conformance

    -

    WCAG 3 will include a new conformance model to address a wider range of user needs, test a wider range of technologies and support new approaches to testing. We are exploring several approaches to conformance. After studying the comments on the previous draft, these are the concepts that showed promise. We are giving an overview in this draft, but we continue to test the combination of the concepts.

    -

    There are several goals for this new conformance model:

    -
      -
    1. Develop a model that encourages web sites to continue to improve accessibility (vs. stopping at the previous AA level);
      2. -
    2. Better reflect the lived experience of people with disabilities, who successfully use sites that have some content that does not meet WCAG 2.0 AA, or who encounter barriers with sites that meet WCAG 2.0 AA; and
      3. -
    3. Allow for bugs and oversight by content authors, provided the impact of them upon users with disabilities is not substantial.
      4. -
    -

    The proposed approaches can fit together in a variety of ways. We will be testing these approaches and others for validity, reliability, sensitivity, adequacy, complexity and equity. We welcome suggestions on ways to improve these approaches to better meet these criteria and concerns about how they might affect accessibility. The working group plans to select from or even replace these options based on feedback, prototyping, and testing.

    -

    There are two main approaches to evaluating accessibility that are promising. There are also detailed ideas that support these approaches. The two main approaches are:

    -
      -
    • Outcomes with tests: Outcomes are verifiable statements that allow testers to reliably determine if the content being evaluated satisfies the user needs identified in the Guideline. Outcomes are addressed in Section 3.3.1 Outcomes. Tests are addressed in Section 3.3.2 Testing Outcomes.
      • -
    • Assertions and procedures: - Assertions are attributable statements by a person or organization that they followed a procedure to improve accessibility. Assertions are addressed in Section 3.4.1 Assertions.
      • -
    -

    There are additional ideas that support these two approaches and can be used or combined in many different ways.

    -
      -
    • Conformance levels: Bronze, Silver, and Gold levels continue to receive positive feedback as an approach for overall conformance rating.
      • -
    • Issue severity: Outcomes may allow for the concept of varying severity. High severity issues are those which prevent users from completing user processes (tasks).
      • -
    • Adjectival ratings: Adjectival Ratings allow testers to grade a test, outcome, or guideline by an adjective rating (such as fail, pass, exemplary) or a numeric rating (such as 1-5) that potentially can be closer to the lived experience of a person with a disability.
      • -
    • Pre-assessment checks: Pre-Assessment checks are tests or criteria that implementers can use to determine if they are ready to assess conformance. The intent is to help organizations prepare for conformance testing, not to create a new level of conformance.
      • -
    -

    The details of these approaches change as we assemble them into a coherent whole. This draft gives a high level overview of these approaches so we can give an update and receive feedback on the individual approaches we are considering.

    - -
    -

    As we continue developing conformance, we seek input on the following:

    -
      -
    • Which option has the best chance of adoption and why?
      • -
    • How well do these approaches support regulatory needs?
      • -
    • How will these approaches be integrated into a conformance model (including levels or scores)?
      • -
    - -

    Next steps include:

    -
      -
    • Further refine options,
      • -
    • Test the validity, reliability, sensitivity, adequacy, complexity and equity of the various models using these approaches, and
      • -
    • Write sample guidelines to test out each option.
      • -
    -
    -
    - -
    -

    Outcomes and methods

    -
    -

    As we continue developing outcomes and methods, we seek input on how well the approach to outcomes, assertions and tests defined here supports additional requirements not addressed in 2.2.

    - -

    Next steps include:

    -
      -
    • Get feedback from designers, developers, and other communities on wording choice,
      • -
    • Finalize names and descriptions of scope and tests,
      • -
    • Develop detailed examples of methods and tests,
      • -
    • As we develop example outcomes and methods, further explore conditions and how multiple measurements might be used to meet an outcome.
      • -
    • Address all GitHub issues under test types and terminology milestone.
      • -
    -
    - -
    -

    Outcomes

    -

    Outcomes are verifiable statements that allow testers to reliably determine if the content being evaluated satisfies the user needs identified in the Guideline. All outcomes and assertions that relate to a Guideline will be listed together to encourage adoption of higher levels of accessibility.

    -

    Each outcome is associated with at least one method. Methods are informative and kept in how to documents. Each method contains techniques for meeting the outcome, examples, resources, and sets of tests for evaluating the outcome. Methods can apply to a specific technology, such as HTML, or can be more generic where the advice applies no matter what technology, such as the methods supporting the Clear Language guideline.

    - -

    Outcomes are written so that testers can determine the accessibility of technologies based solely on the outcome, even when methods do not yet exist for those technologies.

    -
    -
    -

    Testing outcomes

    - -
    -
    Types of tests
    -

    WCAG 3 includes two (2) types of tests which are evaluated:

    -
      -
    • Quantifiable tests: Tests where there is a high degree of consistency between test results from different testers. Examples include testing whether certain properties exist in the content or if they match a value specified by the requirement.
      • - -
    • Qualitative tests: Tests that rely on a qualitative evaluation based on existing criteria. Test results may vary between testers who understand the criteria. One example is evaluating the quality of alternative text used to meet a requirement for alternative text.
      • -
    - -

    Most tests have prescribed ways to meet the test. In some cases, the ways to meet the test will change based on a specific condition being met (example: the human language of the content).

    - -

    Although content may satisfy all outcomes using quantifiable and qualitative tests, the content may not always be usable by people with a wide variety of disabilities. The assertions (see Section 3.4.1 Assertions) are designed to address this problem.

    - -
    -
    Quantifiable tests
    -

    Quantifiable tests rely on measuring properties of the content based on nominal values. The test results are objectively verifiable, and avoid variation of test results between different testers. Values are quantifiable. They could be boolean (true/false), for example to check the presence of titles, text alternatives, and accessible names. Other values could include numerical thresholds; for example, to check color luminosity ratios.

    -

    Each method using quantifiable tests includes:

    -
      -
    • the values being tested; and
      • -
    • an algorithm to measure the properties of the content based on the values.
      • -
    - - -
    - -
    -
    Qualitative tests
    -

    Qualitative tests rely on evaluating content based on a set of defined qualities and exceptions. The set of qualities and exceptions limit the scope of decisions, to minimize variation of test results arrived at by different testers. Still, some level of qualitative assessment is required, therefore the accuracy of the test results also depends on the knowledge and context of the testers to some degree.

    -

    Each method using qualitative tests includes:

    -
      -
    • the defined qualities being tested; and
      • -
    • guidance on evaluating how well the content meets the defined qualities.
      • -
    - - -
    -
    -
    -
    Test scopes
    -

    Testing outcomes use items, views, user processes, and the product to define what is being tested.

    - -

    Items are the smallest testable unit. They may be interactive components such as a drop down menu, a link, or a media player. They may also be units of content such as a word, a phrase, a label or error message, an icon, or an image.

    - -

    Views include all content visually and programmatically available without a substantive change. Conceptually, views correspond to the definition of a web page as used in WCAG 2, but are not restricted to content meeting that definition. For example, a view could be considered a “screen” in a mobile app or a layer of web content – such as a modal.

    - -

    User processes are a series of user actions, and the distinct interactive views and items that support the actions, where each action is required to complete an activity. A user process may include a subset of items in a view or a group of views.

    -

    Examples of a process include:

    -
      -
    • Logging into a web site and being recognized as an authenticated user;
      • -
    • Ordering an item, in which case the process includes the entire set of tasks from searching for the item, adding it to the shopping cart, paying for it, and receiving confirmation;
      • -
    • Submitting tax information, from start to end of the process; and
      • -
    • Interacting with other users in a virtual reality environment.
      • -
    -

    A process is comprised of one or more views or subsets of views. Only the part of the views that support the user process are included in a test of the user process.

    - -

    The product is the combination of items, views, and user processes that collectively comprise the web site, set of web pages, web app, etc.

    -
    -
    -
    Conditions
    -

    Some tests only apply in certain situations. Testing may occasionally require determining and referencing which specifications are being tested. Methods will note whether a test always applies or under what conditions a test applies. Both quantitative and qualitative tests can be conditional.

    - - - - +

    The most basic level of conformance will require meeting all of the Foundational Requirements. This set will be somewhat comparable to WCAG 2.2 Level AA.

    -
    -
    -
    -
    -

    Assertions and procedures

    -
    -

    As we continue developing this content, we seek input on the following:

    -
      -
    • Can assertions be used to record accessibility work that is - not required in the guidelines? This could include advance work on guidance not yet - added to the guidelines.
      • -
    • What optional supporting documentation should organizations provide with an assertion?
      • -
    • Is there a need for WCAG 3 to require proof of an assertion, and if so, what documentation should be required as proof?
      • -
    • Should assertions be dated, expire, or be reviewed on a regular basis?
      • -
    • Can steps in a procedure duplicate tests in other parts of the guidelines? If so, how should those be handled?
      • -
    • Can assertions exist outside of conformance? For example, can they be used as an internal benchmark rather than for a claim of conformance?
      • -
    • Can assertions be used at the most basic level of conformance? If so, how?
      • -
    • How can small organizations use assertions without unrealistic burden?
      • -
    • As written, outcomes and assertions are at the same level. Would moving assertions to the test level be more effective?
      • -
    • The AGWG is considering whether and how assertions can be applied to the Bronze level.
      • -
    • The AGWG is considering what will qualify as a procedure in WCAG 3. A procedure may be limited to guidance: -
      • approved by AGWG and listed in WCAG,
        • -
      • that references publicly published guidance, or
        • -
      • that meets criteria specified in WCAG
      - or it may be any process that an organization uses to improve accessibility. Comments or criticism of these alternatives is welcome.
      • -
    -

    Next steps include:

    -
    • Better define procedure,
      • -
    • Develop detailed examples of methods and test,
      • -
    • Test the accuracy, reliability, repeatability, etc. of this approach
    -
    - - -
    -

    Assertions

    -

    An assertion is a formal claim of fact, attributed to a person or organization. In WCAG 3, an [=assertion=] is an attributable and documented statement of fact regarding procedures practiced in the development and maintenance of the content or product to improve accessibility.

    -
    - -
    -

    Using assertions

    -

    Assertions may supplement [=methods=] in one or more outcomes. Assertions should only be used on outcomes and guidelines that allow assertions. Organizations can make an assertion that they followed a procedure to claim conformance. Results when testing assertions are true/false - the organization making the assertion either provided the required documentation or it did not.

    - -

    Procedures used in assertions may be implemented at the organization level, during design and development, or during testing.

    - -

    Examples of procedures that may be used during implementation might include:

    -
    • Training,
      • -
    • FTE (Full Time Equivalent) assignments,
      • -
    • Skills testing,
      • -
    • Coordination and documentation of accessibility processes, or
      • -
    • Setting the priority for remediation.
    - -

    Examples of procedures that may be used to evaluate accessibility might include:

    -
    • Usability testing,
      • -
    • Heuristic evaluation, or
      • -
    • Assistive technology testing.
    - -
    - -
    -

    Documenting assertions

    - -

    Assertions must be documented as part of the conformance claim process. The required information may also be made available through the web site.

    - -

    Assertions might include the following information:

    -
    • The statement being asserted,
      • -
    • The date of the assertion,
      • -
    • The date or date range the procedure was completed,
      • -
    • The scope of the assertion,
      • -
    • Contact information for the person or group making the assertion, and
      • -
    • The outcome(s) or guideline(s) supported by the assertion.
    - -

    An alternative to specifying assertions at the outcome or guideline level might be to require the assertion apply to the scope of the conformance claim.

    -
    +

    Higher levels of conformance will be defined and met using Supplemental Requirements and Assertions. AG will be exploring whether meeting the higher levels would work best based on points, percentages, or predefined sets of provisions (modules).

    -
    -

    Supporting documentation for assertions

    -

    WCAG recommends maintaining additional information that an organization can use to improve or validate procedures and assertions. WCAG will not require organizations to provide supporting documentation to conform.

    -
    - -
    -

    Testing assertions

    -

    The quality of an assertion can be tested based on how well the assertion meets the documentation requirements for assertions (See Documenting Assertions). Conforming to WCAG does not require testing supporting documentation; however, organizations may decide to adopt additional documentation requirements based on the procedure being asserted.

    -
    -
    -
    -

    Conformance levels

    +

    Other conformance concepts AG continues to explore the following include conformance levels, issue severity, adjectival ratings and pre-assessment checks.

    -

    WCAG 3 defines three levels of conformance: bronze, silver, and gold. While it is easy to replicate the WCAG 2 A, AA, AAA by renaming the levels, there is an opportunity to improve accessibility for people with disabilities by using a more advanced approach.

    -

    Bronze is the minimum conformance level. Content that does not meet the requirements of the bronze level does not conform to WCAG 3. To reach Bronze level, the scope claimed in the conformance statement must pass a subset of outcomes and assertions. The subset will require enough outcomes and assertions to improve equity across functional needs.

    + See [[[?WCAG3-explainer]]] for more information. -

    Silver level incentivizes organizations to go further to improve accessibility. One possibility that we are examining is that Silver level points can accumulate even prior to completing bronze but are not usable until Bronze is achieved. The goal is to encourage organizations to go beyond the minimum, especially where organizations want to be recognized for their efforts to go beyond minimum accessibility.

    - -

    Gold level identifies measures we want to include for those organizations that do achieve Silver so that some can stand out as exemplary, cutting edge, and role models. There are a number of ideas that will be developed further once more of the conformance structure is solidified.

    -
    -
    -

    Issue severity

    -
    -

    Severity rating could contribute towards scoring and prioritization.

    -

    As we continue developing this content, we seek input on the following:

    -
      -
    1. Is every issue critical to someone, making this concept invalid?
      2. -
    2. How best to assign severity, particularly if testers have different ideas on what is critical?
      3. -
    3. How do we incorporate context/process/task? Is that part of scoping, or issue severity? Both are important to the end result.
      4. -
    4. What to do with non-critical issues?
      5. -
    5. If included, how will situations where severity depends on context be handled?
      6. -
    6. Can the matrix inform designation of functional categories? For example, the Text Alternative Available outcome.
      7. -
    7. How will issue severity fit into levels? For example:
        -
      • “Bronze” could be an absence of any critical or high issues;
        • -
      • “Silver” could be an absence of any critical, high, or medium issues.
        • -
      -
      8. -
    8. How to account for cumulative issues becoming critical?
      9. -
    9. Would another approach be more effective, for example assigning critical issues after testing is complete based on task or type of task rather than by test?
      10. -
    -

    Next steps include:

    -
      -
    • Testing the assumption that some failures cause a greater impact to users than others or whether all guidelines and contexts are important to some individuals.
      • -
    • Explore whether the concept of issue severity can be applied consistently and effectively.
      • -
    -
    -

    Outcomes may allow for the concept of varying severity. High severity issues are those which prevent users from completing user processes (tasks).

    -

    Tests could include critical issues. Each test could have a category of severity, so some tests will be flagged as causing a critical issue.

    -
    - -
    -

    Adjectival ratings

    -

    Adjectival Ratings allow test results to go beyond Pass or Fail to show progress towards a goal or exceeding a goal. Example of Possible adjectival ratings are:

    -
      -
    • Fail, Pass, Exceptional; or
      • -
    • Fail, Progress, Pass, Better, Exceptional.
      • -
    -

    Outcomes or guidelines could be evaluated using adjectival ratings on both directly quantifiable outcomes and qualitative measures that are asserted. Outcomes might be assigned an adjectival rating based on methods used to meet the outcome and issue severity. Guidelines might be assigned an adjectival rating based on the outcomes and assertions completed under the guideline.

    -
    - -
    -

    Percentages

    -
    -

    We are exploring whether percentages could apply to Bronze but have not found a model to date where this works without adding complexity and time needed for testing.

    -

    As we continue developing this content, we seek input on the following:

    -
      -
    • How can percentages be used in a way that is equitable across disabilities?
      • -
    -
    -

    In this approach, percentage of outcomes and assertions passed or percentage passed at a certain adjectival rating might be used to conform to Silver and Gold levels.

    -
    - -
    -

    Pre-assessment checks

    -

    Pre-Assessment checks are tests or criteria that implementers can use to determine if they are ready to assess conformance. The intent of specifying these would be to help implementers prepare for conformance testing, not to create a new level of conformance. Examples of pre-assessment checks might be:

    -
      -
    • The video player used has the ability to display captions and support multiple audio tracks,
      • -
    • All non-text elements on a page have an accessible name.
      • -
    -
    -
    -

    Only accessibility-supported ways of using technologies

    -
    -

    The intent is for the responsibility of meeting requirements to vary depending on the level of conformance.

    -

    At the basic/lower levels of conformance assumptions can be made by authors that many requirements can be met by user-agents and assistive technology. At higher levels of conformance the author may need to meet a requirement, or check that available user-agents do meet the requirements, or a combination of both.

    - -

    This approach means the working group will ensure that methods and techniques included do have reasonably wide and international support from user-agents, and there are sufficient techniques to meet each outcome.

    +
    +

    Only accessibility-supported ways of using technologies

    -

    The intent is that WCAG 3 will use a content-management-system to support tagging of methods/techniques with support information. There should also be a process where interested parties can provide information

    +

    The concept of "accessibility-supported" is to account for the variety of user-agents and scenarios. How does an author know that a particular technique for meeting a guideline will work in practice with user-agents that are used by real people?

    -

    Informative documentation that will be associated with this section includes:

    -
      -
    • How to assess which assistive technologies you should support, for the "accessibility support set". This could be taken up by regulators to provide this information for a region.
      • -
    +

    The intent is for the responsibility of testing with user-agents to vary depending on the level of conformance.

    -

    The exception is still being discussed to avoid people using that scenario when not appropriate.

    +

    At the foundational level of conformance assumptions can be made by authors that methods and techniques provided by WCAG 3 work. At higher levels of conformance the author may need to test that a technique works, or check that available user-agents meet the requirement, or a combination of both.

    -

    We continue to explore how the WCAG 2 concept of accessibility-supported fits into proposed conformance models.

    +

    This approach means the working group will ensure that methods and techniques included do have reasonably wide and international support from user-agents, and there are sufficient techniques to meet each outcome.

    -
    -

    Author responsibility for accessibility support (or "Assistive Technology Support") varies by conformance level.

    -
    - -

    Pre-requisite / Baseline conformance / Bronze

    -

    At lower levels of conformance authors can assume the methods and techniques provided by WCAG 3 will be sufficient to meet that level of conformance.

    +

    The intent is that WCAG 3 will use a content-management-system to support tagging of methods/techniques with support information. There should also be a process where interested parties can provide information.

    -

    The techniques provided as part of WCAG 3 documentation are marked at this level, and can be assumed to work.

    -
    - -
    -

    Enhanced / Silver

    -

    Part of claiming conformance at higher levels includes defining which user-agents and assistive technologies you test for support, your "accessibility support set".

    -

    Methods and techniques at the higher levels of conformance include some information about Assistive Technology compatibility. If the provided coverage is not sufficient for your "accessibility support set", or you need to use a different technique to meet the outcome, the author is responsible for testing that their technique works for the "accessibility support set".

    -
    +

    An "accessibility support set" is used at higher levels of conformance to define which user-agents and assistive technologies you test with. It would be included in a conformance claim, and enables authors to use techniques that are not provided with WCAG 3.

    -
    -

    Exceptions (at Enhanced / Silver level)

    -

    If there is a particular assistive technology which is in your "accessibility support set", and it has had a bug for more than 2 years, the author can claim an exception. In circumstances where most technologies support a technique but one does not for significant time, authors can still claim conformance.

    -
    +

    An exception for long-present bugs in assistive technology is still under discussion.

    - -
    +
    +

    Defining conformance scope

    When evaluating the accessibility of content, WCAG 3 requires the outcomes apply to a specific scope. While the scope can be an all content within a digital product, it is usually one or more sub-sets of the whole. Reasons for this include:

    @@ -1643,45 +1290,6 @@

    Defining conformance scope

    Conformance is defined only for processes and views. However, a conformance claim may be made to cover one process and view, a series of processes and views, or multiple related processes and views. All unique steps in a process MUST be represented in the set of views. Views outside of the process MAY also be included in the scope.

    We recognize that representative sampling is an important strategy that large and complex sites use to assess accessibility. While it is not addressed within this document at this time, our intent is to later address it within this document or in a separate document before the guidelines reach the Candidate Recommendation stage. We welcome your suggestions and feedback about the best way to incorporate representative sampling in WCAG 3.

    -
    -

    Conformance requirements

    -

    For technology to conform to WCAG 3, the following conformance requirements apply:

    -
      -
    1. Conformance level - Content MUST meet the requirements of the selected conformance level.
      2. -
    -
    -
    -

    Conformance claims

    -

    Conformance claims are not required. Authors can conform to WCAG 3 without making a claim. The material below describes how to make a conformance claim if that option is chosen.

    -

    Required components of a conformance claim

    A conformance claim MUST include the following information:

      -
    1. Date of the claim;
      2. -
    2. Guidelines title, version and URI - W3C Accessibility Guidelines 3.0 at https://www.w3.org/TR/wcag-3.0/
      3. -
    3. Conformance level satisfied: (bronze, silver, or gold);
      4. -
    4. A concise description of the views and processes, such as a list of URIs for which the claim is made, including any state changes which lead to a new view; and
      5. -
    5. The technology including the hardware, software, and assistive technology used to test the claim.
      6. -
    -
    -
    -

    Example conformance claim

    -

    On 12 August 2020, the following 10 views and 2 processes conform to WCAG 3 at a bronze level. Processes were selected because they are the most common activities on the web site and include 4 unique views. The other 6 views are the most commonly used.

    - -

    These were tested using Firefox and Chrome on a Windows platform. The assistive technology used included JAWS and Dragon.

    -
    -
    -
    -

    Conforming alternative version

    -

    We continue to explore how the WCAG 2 concept of conforming alternative versions fit into proposed conformance models.

    -

    User-generated content

    diff --git a/guidelines/respec-config.js b/guidelines/respec-config.js index 87d9ec1..56c7cc6 100644 --- a/guidelines/respec-config.js +++ b/guidelines/respec-config.js @@ -98,6 +98,13 @@ var respecConfig = { postProcess: [postRespec], localBiblio: { + "WCAG3-explainer": { + "title": "Explainer for W3C Accessibility Guidelines (WCAG) 3.0", + "publisher": "World Wide Web Consortium", + "date": "8 November 2024", + "href": "https://www.w3.org/TR/wcag-3.0-explainer-20241108/" + }, + "508-criteria": { "title": "Section 508 Functional Performance Criteria", "publisher": "United States Access Board", From d828051b48449669e839d688505e5eb91953a4fd Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 12 Nov 2024 12:03:33 +0000 Subject: [PATCH 14/49] Tidying up references --- guidelines/index.html | 5 ++--- guidelines/respec-config.js | 7 +++++++ 2 files changed, 9 insertions(+), 3 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 7ec1c18..8845d67 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -1463,12 +1463,11 @@

    Security Considerations

    Guidelines development methodology

    Summary -

    WCAG 3 includes some of the information from WCAG 2, guidelines for tools to create web content (ATAG), and guidelines for browsers, media players, and similar software (UAAG). The WCAG 3 design is based on research. You can read more about the Requirements for WCAG 3.0. -

    +

    WCAG 3 includes some of the information from WCAG 2, guidelines for tools to create web content (ATAG), and guidelines for browsers, media players, and similar software (UAAG). The WCAG 3 design is based on research. You can read more about the [[[?WCAG3-requirements]]].

    Relationship to other W3C guidelines

    -

    The Web Content Accessibility Guidelines (WCAG) 2.0 [[WCAG20]] were designed to be technology neutral, and have stayed relevant for over 10 years. The Authoring Tool Accessibility Guidelines (ATAG) 2.0 [[ATAG20]] provide guidance for various types of software that assist people in writing accessible content. User Agent Accessibility Guidelines (UAAG) 2.0 [[UAAG20]] offers useful guidance to user agent developers and has been implemented on an individual success criterion basis.

    +

    The [[[WCAG20]]] were designed to be technology neutral, and have stayed relevant for over 10 years. The [[[ATAG20]]] provide guidance for various types of software that assist people in writing accessible content. [[[UAAG20]]] offers useful guidance to user agent developers and has been implemented on an individual success criterion basis.

    These guidelines have normative guidance for content and helpful implementation advice for authoring tools, user agents, and assistive technologies.

    • WCAG 3 incorporates but may not be all encompassing of WCAG 2, ATAG, and UAAG.
      • diff --git a/guidelines/respec-config.js b/guidelines/respec-config.js index 56c7cc6..d222784 100644 --- a/guidelines/respec-config.js +++ b/guidelines/respec-config.js @@ -98,6 +98,13 @@ var respecConfig = { postProcess: [postRespec], localBiblio: { + "WCAG3-requirements": { + "title": "Requirements for WCAG 3.0", + "publisher": "World Wide Web Consortium", + "date": "8 November 2024", + "href": "https://www.w3.org/TR/wcag-3.0-requirements-20241108/" + }, + "WCAG3-explainer": { "title": "Explainer for W3C Accessibility Guidelines (WCAG) 3.0", "publisher": "World Wide Web Consortium", From e6ad2a2be62574ba9bba18362f7d95cbf6e387e5 Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 12 Nov 2024 12:04:16 +0000 Subject: [PATCH 15/49] Removing Goals and requirements The requirements are linked to, although this could probably be cleaned up. --- guidelines/index.html | 6 ------ 1 file changed, 6 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 8845d67..926b903 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -1475,12 +1475,6 @@

      Relationship to other W3C guidelines

    For more details about differences from previous guidelines, see Appendix: Differences From WCAG 2.

    -
    -

    Goals and requirements

    -

    The goal of WCAG 3 and supporting documents is to make digital products including web, ePub, PDF, applications, mobile apps, and other emerging technologies more accessible and usable to people with disabilities. It is the intention for WCAG 3 to meet this goal by supporting a wider set of user needs, using new approaches to testing, and allowing more frequent maintenance of guidelines to keep pace with accelerating technology change. The hope is that WCAG 3 will make it significantly easier for both beginners and experts to create accessible digital products that support the needs of people with disabilities.

    - -

    Research and design work performed by the Silver Task Force identified key requirements needed to improve upon the existing WCAG 2 structure. These requirements, presented in the Requirements for WCAG 3 document, shaped the guidelines that follow and should be taken into account when evaluating and updating the guidelines.

    -

    Differences from WCAG 2

    From 1f152a7f27b45564561ad7a82a2aae082db06ca6 Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 12 Nov 2024 16:00:02 +0000 Subject: [PATCH 16/49] Move UGC to Explainer --- guidelines/index.html | 32 -------------------------------- 1 file changed, 32 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 926b903..10c12e6 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -1291,38 +1291,6 @@

    Defining conformance scope

    We recognize that representative sampling is an important strategy that large and complex sites use to assess accessibility. While it is not addressed within this document at this time, our intent is to later address it within this document or in a separate document before the guidelines reach the Candidate Recommendation stage. We welcome your suggestions and feedback about the best way to incorporate representative sampling in WCAG 3.

    -
    -

    User-generated content

    -
    - Summary -

    User-generated content is content written by the public and customers. WCAG 3.0 may use different advice or steps for user-generated content to improve accessibility than for content created by the publisher. WCAG 3.0 proposes that organizations identify user-generated content and identify the steps taken to encourage accessibility.

    -
    -
    -

    It remains to be determined how to address user-generated content that has accessibility issues; and to define what minimum thresholds might be acceptable. We expect WCAG 3 to provide this guidance within individual guidelines and outcomes and to support testing for conformance. The working group is looking at alternative requirements to apply to user-generated content guideline by guideline, and is seeking feedback on what would serve as reasonable requirements on how to best support accessibility in user-generated content with known (or anticipated) accessibility issues.

    -

    One example would be “alternative text”. The Authoring Tool Accessibility Guidelines (ATAG) has specific guidance for providing a mechanism for alternative text. The ATAG 2.0 Guideline B.2.3 - “Assist authors with managing alternative content for non-text content” could be adapted to provide specific, guideline-related guidance for user generated alternative text.

    -

    The working group intends to more thoroughly address the contents and the location of an accessibility statement in a future draft.

    -
    -

    Web content publishers may include content provided by the users of their digital products. We refer to such content as “user-generated content”.

    -

    Examples of user-generated content include:

    -
      -
    • social media postings and comments,
      • -
    • uploaded photographs, or
      • -
    • uploaded videos or other multimedia.
      • -
    -

    User-generated content is provided for publication by visitors where the content platform specifically welcomes and encourages it. User-generated content is content that is submitted through a user interface designed specifically for members of the public and customers. Use of the same user interface as an authoring tool for publication of content by agents of the publisher (such as employees, contractors, or authorized volunteers) acting on behalf of the publisher does not make that content user-generated content. The purpose of the user-generated content conformance section is to allow WCAG 3 outcomes and methods to require additional or different steps to improve the accessibility of user-generated content.

    -

    An important part of WCAG conformance is the specific guidance that is associated with individual WCAG 3 guidelines and outcomes. Not all WCAG 3 guidelines will have unique outcomes and testing for user-generated content. Unless user-generated content requirements are specified in a particular guideline, that guideline applies as written whether or not the content is user generated.

    - - -

    The web content publisher should identify all locations of user-generated content (such as commentary on hosted content, product descriptions for consumer to consumer for sale listings, and restaurant reviews) and perform standard accessibility evaluation analysis for each. If there are no accessibility issues, the user-generated content is fully conforming.

    -
    -

    Steps to conform

    -

    If accessibility issues are identified, or if the web site author wants to proactively address potential accessibility issues that might arise from user-generated content, then all of the following must be indicated alongside the user-generated content or in an accessibility statement published on the web site or product that is linked from the view or page in a consistent location:

    -
      -
    1. Clearly identify where user-generated content can be found on the publisher’s digital product (perhaps by id href);
      2. -
    2. Clearly identify the steps taken to encourage accessibility in user-generated content such as prompting the user for alternative text for their uploaded images before they are accepted and prohibiting text attributes except as they are part of semantic markup such as strong, headings, etc.;
      3. -
    -
    -

    Glossary

    From 176a5033320c1cc4fcf546e8fa9718776db35ee5 Mon Sep 17 00:00:00 2001 From: Kevin White Date: Wed, 13 Nov 2024 11:15:55 +0000 Subject: [PATCH 17/49] Update to introduction and sotd Bit of a tidy up and added in links to each outcome group --- guidelines/index.html | 49 ++++++++++++++++++++++++++++++------------- 1 file changed, 35 insertions(+), 14 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 10c12e6..8aaf000 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -16,26 +16,32 @@

    See WCAG 3 Introduction for an introduction and links to WCAG technical and educational material.

    +

    This is an update to the W3C Accessibility Guidelines (WCAG) 3.0. It includes a restructuring of the guidelines and first draft decision trees for two outcomes: Image alternatives and Keyboard Focus Appearance.

    To comment, file an issue in the W3C wcag3 GitHub repository. The Working Group requests that public comments be filed as new issues, one issue per discrete comment. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, send email to public-agwg-comments@w3.org (comment archive). In-progress updates to the guidelines can be viewed in the public editors’ draft.

    Introduction

    Summary -
      -
    • W3C Accessibility Guidelines (WCAG) 3.0 shows ways to make web content and apps usable by people with disabilities. WCAG 3 is a newer standard than the Web Content Accessibility Guidelines (WCAG) 2.
      • -
    • WCAG 3 doesn’t replace WCAG 2. WCAG 2 is used around the world and will still be required by different countries for a long time to come.
      • -
    • Meeting WCAG 2 at AA level means you will be close to meeting WCAG 3.0, but there may be differences.
      • -
    • We have developed labels for sections to tell you how confident we are that the content will not change. This lets you tell whether we are trying out an idea or whether we have put a lot of work into the topic and we don’t expect it to change. There are 5 levels: -
        -
      • Placeholder - we are thinking about the topic and plan to work on it in the next few months.
        • -
      • Exploratory - we have started work on this topic but still have many questions.
        • -
      • Developing - we have general agreement, but not all the details are worked out.
        • -
      • Refining - we think we have a good idea and want public feedback about it. We are ready to have a few people try it out and see how well it works.
        • -
      • Mature - we think it is ready to publish and we want to know if we missed any rare examples.
        • -
      -
      • -
    +
      +
    • W3C Accessibility Guidelines (WCAG) 3.0 shows ways to make web content and apps usable by people with + disabilities. WCAG 3 is a newer standard than the Web Content Accessibility Guidelines (WCAG) 2.
      • +
    • WCAG 3 doesn’t replace WCAG 2. WCAG 2 is used around the world and will still be required by different + countries for a long time to come.
      • +
    • Meeting WCAG 2 at AA level means you will be close to meeting WCAG 3.0, but there may be differences.
      • +
    • We have developed labels for sections to tell you how confident we are that the content will not change. + This lets you tell whether we are trying out an idea or whether we have put a lot of work into the topic and + we don’t expect it to change. There are 5 levels: +
        +
      • Placeholder - we are thinking about the topic and plan to work on it in the next few months.
        • +
      • Exploratory - we have started work on this topic but still have many questions.
        • +
      • Developing - we have general agreement, but not all the details are worked out.
        • +
      • Refining - we think we have a good idea and want public feedback about it. We are ready to have a + few people try it out and see how well it works.
        • +
      • Mature - we think it is ready to publish and we want to know if we missed any rare examples.
        • +
      +
      • +

    What’s new in this version of WCAG 3?

    @@ -48,6 +54,21 @@

    Introduction

    We did not make changes to conformance related sections and we did not publish an updated WCAG 3 Explainer.

    +

    The outcomes are grouped into the following sections:

    +

    About WCAG 3

    From 097843087e5b5bd013cda28cf55c92a074e7f721 Mon Sep 17 00:00:00 2001 From: Kevin White Date: Wed, 13 Nov 2024 11:25:33 +0000 Subject: [PATCH 18/49] Update references --- guidelines/index.html | 43 +++---------------------------------------- 1 file changed, 3 insertions(+), 40 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 8aaf000..4e84fa9 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -81,7 +81,7 @@

    About WCAG 3

    Section status levels

    -

    As part of the WCAG 3 drafting process each normative section of this document is given a status. This status is used to indicate how far along in the development this section is, how ready it is for experimental adoption, and what kind of feedback the Accessibility Guidelines Working Group is looking for.

    +

    As part of the WCAG 3 drafting process each normative section of this document is given a status. This status is used to indicate how far along in the development this section is, how ready it is for experimental adoption, and what kind of feedback the Accessibility Guidelines Working Group is looking for.

    • Placeholder: This content is temporary. It showcases the type of content or section to expect here. All of this is expected to be replaced. No feedback is needed on placeholder content.
    • Exploratory: The working group is exploring what direction to take with this section. This content is not refined, details and definitions may be missing. Feedback should be about the proposed direction.
      • @@ -1261,7 +1261,7 @@

      Conformance

      There are two types of content in this document:

      • Normative: what you must do to meet the guidelines.
        • -
      • Non-normative: advice to help you meet the guidelines. This is also called informative.
        • +
      • Non-normative: advice to help you meet the guidelines. This is also called informative.

      We are experimenting with different conformance approaches for WCAG 3. Once we have developed enough guidelines, we will test how well each works.

    @@ -1317,12 +1317,6 @@

    Defining conformance scope

    Glossary

    Many of the terms defined here have common meanings. When terms appear with a link to the definition, the meaning is as formally defined here. When terms appear without a link to the definition, their meaning is not explicitly related to the formal definition here. These definitions are in progress and may evolve as the document evolves.

    -
    Adequacy
    -
    -

    Adequacy is subtle metric, but important to WCAG 3 proposals. Adequacy describes if the formulas being used to process and score the accessibility testing results are using such a small interval that small changes in accessibility do not cause large changes in scoring. Benchmarking Web Accessibility Metrics, Vigo, Lopes, O Connor, Brajnik, Yesilada 2011.

    -
    -
    Adjectival Ratings
    -

    A system to report evaluation results as a set of human-understandable adjectives.

    Assertion

    A formal claim of fact, attributed to a person or organization. An attributable and documented statement of fact regarding procedures practiced in the development and maintenance of the content or product to improve accessibility.

    Automated @@ -1333,12 +1327,6 @@

    Glossary

    experience. [=Semi-automated evaluation=] allows machines to guide humans to areas that need inspection. The emerging field of testing conducted via machine learning is not included in this definition.

    -
    Best Practice
    -

    Methods which are not required and meet a higher requirement than methods required to conform to Bronze.

    -
    Complexity
    -
    -

    Complexity refers to the resources required to accomplish the conformance testing. These could be crawler time, or time for human judgment testing. This would be a useful metric to have to answer the question of how much time WCAG 3 takes to test as compared to WCAG 2. Benchmarking Web Accessibility Metrics, Vigo, Lopes, O Connor, Brajnik, Yesilada 2011.

    -
    Conformance

    Satisfying all the requirements of the guidelines. Conformance is an important part of following the guidelines even when not making a formal Conformance Claim.

    @@ -1348,10 +1336,6 @@

    Glossary

    To declare something outdated and in the process of being phased out, usually in favor of a specified replacement.

    Deprecated documents are no longer recommended for use and may cease to exist in the future.

    -
    Equity
    -
    -

    Equity is the outcome of processes and actions that ensure the spectrum of human reality obtains what is needed to participate, not solely access. As equity relates to WCAG it is about the impact the standards/guidelines have on people with disabilities, along with actually including people with disabilities in the work.

    -
    Evaluation
    The process of examining content for conformance to these guidelines.
    @@ -1377,7 +1361,7 @@

    Glossary

    involves inspection of content features, by contrast with user testing which directly tests the experience of users with content.

    -
    Informative
    +
    Informative

    Content provided for information purposes and not required for conformance.

    @@ -1400,11 +1384,6 @@

    Glossary

    Process

    A sequence of steps that need to be completed to accomplish an activity / task from end-to-end.

    -
    Reliability
    -
    -

    The reproducibility and consistency of scores i.e. the extent to which they are the same when evaluations of the same resources are carried out in different contexts (different tools, different people, different goals, different time). This would be particularly useful to ensure that similar results are achieved by different testers. It would also be useful to see if different testers would select the same path or off-path decisions. Representative sampling tests also fit in this category. - Benchmarking Web Accessibility Metrics, Vigo, Lopes, O Connor, Brajnik, Yesilada 2011.

    -
    Semi-Automated Evaluation

    Evaluation conducted using machines to guide humans to areas that need @@ -1412,32 +1391,16 @@

    Glossary

    Semi-automated evaluation involves components of automated evaluation and human evaluation.

    -
    Sensitivity
    -
    -

    Sensitivity of a metric is related to the extent that changes in the output of the metric are quantitatively related to changes of the accessibility of the web site being analyzed. This metric is useful for determining if the conformance proposal captures the impact of the severity of accessibility barriers on the final score and if different disabilities are treated equally by the proposal. Benchmarking Web Accessibility Metrics, Vigo, Lopes, O Connor, Brajnik, Yesilada 2011.

    -
    -
    Set of Tests
    -
    -

    A group of tests that supports a method.

    -
    Test

    Mechanism to evaluate implementation of a method.

    -
    Technique
    -
    -

    Technology-specific approach to follow a method.

    -
    User need

    The end goal a user has when starting a process through digital means.

    User testing

    Evaluation of content by observation of how users with specific functional needs are able to complete a process and how the content meets the relevant outcomes.

    -
    Validity
    -
    -

    The extent to which the measurements obtained by a metric reflect the accessibility of the web site to which it is applied. Does the rating that a web site or digital product achieve in any conformance proposal actually reflect the rating that it should get? Benchmarking Web Accessibility Metrics, Vigo, Lopes, O Connor, Brajnik, Yesilada 2011. Accessed on 29 July 2020

    -
    From c8112d7e3ec10205be1330e5f773df6c1f123ca2 Mon Sep 17 00:00:00 2001 From: rmontgomery Date: Fri, 15 Nov 2024 15:51:35 -0500 Subject: [PATCH 19/49] editorial updates to align with explainer --- guidelines/index.html | 115 ++++++++++++------------------------------ 1 file changed, 31 insertions(+), 84 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 4e84fa9..2df7509 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -11,12 +11,12 @@

    W3C Accessibility Guidelines (WCAG) 3.0 will provide a wide range of recommendations for making web content more accessible to users with disabilities. Following these guidelines will address many of the needs of users with blindness, low vision and other vision impairments; deafness and hearing loss; limited movement and dexterity; speech disabilities; sensory disorders; cognitive and learning disabilities; and combinations of these. These guidelines address accessibility of web content on desktops, laptops, tablets, mobile devices, wearable devices, and other web of things devices. The guidelines apply to various types of web content including static, dynamic, interactive, and streaming content; visual and auditory media; virtual and augmented reality; and alternative access presentation and control. These guidelines also address related web tools such as user agents (browsers and assistive technologies), content management systems, authoring tools, and testing tools.

    -

    Each guideline in this standard provides information on accessibility practices that address documented user needs of people with disabilities. Guidelines are supported by multiple requirements and assertions to determine whether the need has been met. Guidelines are also supported by technology-specific methods to meet each outcome or assertion.

    -

    This specification is expected to be updated regularly to keep pace with changing technology by updating and adding methods, outcomes, and guidelines to address new needs as technologies evolve. For entities that make formal claims of conformance to these guidelines, several levels of conformance are available to address the diverse nature of digital content and the type of testing that is performed.

    +

    Each guideline in this standard provides information on accessibility practices that address documented user needs of people with disabilities. Guidelines are supported by multiple requirements and assertions to determine whether the need has been met. Guidelines are also supported by technology-specific methods to meet each requirement or assertion.

    +

    This specification is expected to be updated regularly to keep pace with changing technology by updating and adding methods, requirements, and guidelines to address new needs as technologies evolve. For entities that make formal claims of conformance to these guidelines, several levels of conformance are available to address the diverse nature of digital content and the type of testing that is performed.

    See WCAG 3 Introduction for an introduction and links to WCAG technical and educational material.

    -

    This is an update to the W3C Accessibility Guidelines (WCAG) 3.0. It includes a restructuring of the guidelines and first draft decision trees for two outcomes: Image alternatives and Keyboard Focus Appearance.

    +

    This is an update to the W3C Accessibility Guidelines (WCAG) 3.0. It includes a restructuring of the guidelines and first draft decision trees for three Guidelines: Image alternatives, Keyboard Focus Appearance and Implied meaningful.

    To comment, file an issue in the W3C wcag3 GitHub repository. The Working Group requests that public comments be filed as new issues, one issue per discrete comment. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, send email to public-agwg-comments@w3.org (comment archive). In-progress updates to the guidelines can be viewed in the public editors’ draft.

    @@ -45,16 +45,20 @@

    Introduction

    What’s new in this version of WCAG 3?

    -

    This draft includes an updated list of the potential outcomes which we are exploring. The list of outcomes is longer than a listing of Success Criteria in WCAG 2.2 because the intent at this stage is to be as inclusive as possible of potential outcomes. The final set of outcomes in WCAG 3 will be different than what is in this draft. Outcomes will be added, combined, and removed. We also expect changes to the text of the Outcomes. Only some of the Outcomes will be required at the base level of conformance.

    +

    This draft includes an updated list of the potential Guidelines and Requirements which we are exploring. The list of Requirements is longer than the list of Success Criteria in WCAG 2.2. This is because: +

    • the intent at this stage is to be as inclusive as possible of potential Requirements, and
      • +
    • WCAG 3 Requirements are more granular than WCAG 2 Success Criteria.
    + The final set of Requirements in WCAG 3 will be different than what is in this draft. Requirements will be added, combined, and removed. + We also expect changes to the text of the Requirements. Only some of the Requirements will be used to meet the base level of conformance.

    The purpose of publishing this initial list is to:

    • better understand the scope of needs,
    • request assistance in identifying gaps, and
      • -
    • request assistance locating and conducting research to validate or invalidate the outcomes listed.
    +
  • request assistance locating and conducting research to validate or invalidate the requirements listed.

    • We did not make changes to conformance related sections and we did not publish an updated WCAG 3 Explainer.

    -

    The outcomes are grouped into the following sections:

    +

    The Requirements are grouped into the following sections:

    • Animation and movement
    • Error handling
      • @@ -72,10 +76,10 @@

      Introduction

      About WCAG 3

      -

      This specification presents a new model and guidelines to make web content and applications accessible to people with disabilities. The W3C Accessibility Guidelines (WCAG) 3.0 support a wide set of user needs, use new approaches to testing, and allow frequent maintenance of guidelines and related content to keep pace with accelerating technology change. WCAG 3 supports this evolution by focusing on the functional needs of users. These needs are then supported by outcomes and technology-specific methods to meet those needs. 

      +

      This specification presents a new model and guidelines to make web content and applications accessible to people with disabilities. The W3C Accessibility Guidelines (WCAG) 3.0 support a wide set of user needs, use new approaches to testing, and allow frequent maintenance of guidelines and related content to keep pace with accelerating technology change. WCAG 3 supports this evolution by focusing on the functional needs of users. These needs are then supported by guidelines written as outcome statements, requirments, assertions, and technology-specific methods to meet those needs. 

      WCAG 3 is a successor to Web Content Accessibility Guidelines 2.2 [[WCAG22]] and previous versions, but does not deprecate WCAG 2. It will also incorporate content from and partially extend User Agent Accessibility Guidelines 2.0 [[UAAG20]] and Authoring Tool Accessibility Guidelines 2.0 [[ATAG20]]. These earlier versions provided a flexible model that kept them relevant for over 15 years. However, changing technology and changing needs of people with disabilities have led to the need for a new model to address content accessibility more comprehensively and flexibly.

      There are many differences between WCAG 2 and WCAG 3. The WCAG 3 guidelines address accessibility of web content on desktops, laptops, tablets, mobile devices, wearable devices, and other web of things devices. The guidelines apply to various types of web content including static, dynamic, interactive, and streaming content; visual and auditory media; virtual and augmented reality; and alternative access presentation and control. These guidelines also address related web tools such as user agents (browsers and assistive technologies), content management systems, authoring tools, and testing tools.

      -

      Each guideline in this standard provides information on accessibility practices that address documented user needs of people with disabilities. Guidelines are supported by multiple outcomes to determine whether the need has been met. Guidelines are also supported by technology-specific methods to meet each outcome.

      +

      Each guideline in this standard provides information on accessibility practices that address documented user needs of people with disabilities. Guidelines are supported by multiple requirements to determine whether the need has been met. Guidelines are also supported by technology-specific methods to meet each requirement.

      Content that conforms to WCAG 2.2 A and AA is expected to meet most of the minimum conformance level of this new standard but, since WCAG 3 includes additional tests and different scoring mechanics, additional work will be needed to reach full conformance. Since the new standard will use a different conformance model, the Accessibility Guidelines Working Group expects that some organizations may wish to continue using WCAG 2, while others may wish to migrate to the new standard. For those that wish to migrate to the new standard, the Working Group will provide transition support materials, which may use mapping and other approaches to facilitate migration.

      @@ -105,20 +109,20 @@

      Guidelines

      -

      The individuals and organizations that use WCAG vary widely and include web designers and developers, policy makers, purchasing agents, teachers, and students. To meet the varying needs of this audience, several layers of guidance will be provided including functional categories of disabilities, general guidelines, outcomes that can be tested, a rich collection of methods, resource links, and code samples.

      +

      The individuals and organizations that use WCAG vary widely and include web designers and developers, policy makers, purchasing agents, teachers, and students. To meet the varying needs of this audience, several layers of guidance will be provided including guidelines written as outcome statements, requirements that can be tested, assertions, a rich collection of methods, resource links, and code samples.

      -

      The following guidelines are an initial list of potential outcomes that the working group will be exploring. The goal is to guide the next phase of work. They should be considered drafts and should not be considered as final content of WCAG 3.

      +

      The following list is an initial set of potential guidelines and requirements that the working group will be exploring. The goal is to guide the next phase of work. They should be considered drafts and should not be considered as final content of WCAG 3.

      -

      Ordinarily, exploratory content includes editor's notes listing concerns and questions for each item. Because this Guidelines section is very early in the process of working on WCAG 3.0, this editor's note covers the content of the entire section. Please consider all items in the list as exploratory at this point. It is a list of all possible topics for consideration. Not all items listed will become requirements.

      +

      Ordinarily, exploratory content includes editor's notes listing concerns and questions for each item. Because this Guidelines section is very early in the process of working on WCAG 3.0, this editor's note covers most of the content in thi section. Unless otherwise noted, all items in the list as exploratory at this point. It is a list of all possible topics for consideration. Not all items listed will be included in the final version of WCAG 3.0.

      -

      The outcomes listed below came from analysis of user needs that the Working Group has been studying, examining, and researching. They have not been refined and do not include essential exceptions or methods. Some outcomes may be best addressed by authoring tools or at the platform level. Many outcomes need additional work to better define the scope and to ensure they apply correctly to multiple languages, cultures, and writing systems. We will address these questions as we further explore each outcome.

      +

      The guidelines and requirements listed below came from analysis of user needs that the Working Group has been studying, examining, and researching. They have not been refined and do not include essential exceptions or methods. Some requirements may be best addressed by authoring tools or at the platform level. Many requirements need additional work to better define the scope and to ensure they apply correctly to multiple languages, cultures, and writing systems. We will address these questions as we further explore each requirement.

      -

      Please consider the following questions when reviewing this list of outcomes:

      +

      Please consider the following questions when reviewing this list of requirements:

        -
      • Does the structure proposed here and exemplified in the three developing outcomes help explain the relationship of requirements?
        • -
      • What requirements are needed to make web content accessible and are missing from this list?
        • +
      • Does the structure proposed here and exemplified in the three developing guidelines help explain the relationship of requirements?
        • +
      • What requirements that are needed to make web content accessible and are missing from this list?
      • What research supports or refutes these requirements?

      @@ -126,7 +130,7 @@

      Guidelines

      Additional Research

      One goal of publishing this list is to identify gaps in current research and request assistance filling those gaps.

      -

      Editor's notes indicate the outcomes within this list where the working group has not found enough research to fully validate the guidance and create methods to support it or additional work is needed to evaluate existing research. If you know of existing research or if you are interested in conducting research in this area, please file a GitHub issue or send email to public-agwg-comments@w3.org (comment archive).

      +

      Editor's notes indicate the requirements within this list where the working group has not found enough research to fully validate the guidance and create methods to support it or additional work is needed to evaluate existing research. If you know of existing research or if you are interested in conducting research in this area, please file a GitHub issue or send email to public-agwg-comments@w3.org (comment archive).

      @@ -1287,7 +1291,7 @@

      Only accessibility-supported ways of using technologies

      At the foundational level of conformance assumptions can be made by authors that methods and techniques provided by WCAG 3 work. At higher levels of conformance the author may need to test that a technique works, or check that available user-agents meet the requirement, or a combination of both.

      -

      This approach means the working group will ensure that methods and techniques included do have reasonably wide and international support from user-agents, and there are sufficient techniques to meet each outcome.

      +

      This approach means the working group will ensure that methods and techniques included do have reasonably wide and international support from user-agents, and there are sufficient techniques to meet each requirement.

      The intent is that WCAG 3 will use a content-management-system to support tagging of methods/techniques with support information. There should also be a process where interested parties can provide information.

      @@ -1299,7 +1303,7 @@

      Only accessibility-supported ways of using technologies

      Defining conformance scope

      -

      When evaluating the accessibility of content, WCAG 3 requires the outcomes apply to a specific scope. While the scope can be an all content within a digital product, it is usually one or more sub-sets of the whole. Reasons for this include:

      +

      When evaluating the accessibility of content, WCAG 3 requires the guidelines apply to a specific scope. While the scope can be an all content within a digital product, it is usually one or more sub-sets of the whole. Reasons for this include:

      • Large amounts of content are impractical to evaluate comprehensively using anything beyond automated evaluation of items;
      • In many cases, content changes frequently, causing evaluation to be accurate only for a specific moment in time;
        • @@ -1348,8 +1352,8 @@

        Glossary

        Guideline
        -

        High-level, plain-language content used to organize outcomes.

        -

        Guidelines provide a high-level, plain-language version of the content for managers, policy makers, individuals who are new to accessibility, and other individuals who need to understand the concepts but not dive into the technical details. They provide an easy-to-understand way of organizing and presenting the outcomes so that non-experts can learn about and understand the concepts. Each guideline includes a unique, descriptive name along with a high-level plain-language summary. Guidelines address functional needs on specific topics, such as contrast, forms, readability, and more. Guidelines group related outcomes and are technology-independent.

        +

        High-level, plain-language outcome statements used to organize requirements.

        +

        Guidelines provide a high-level, plain-language outcome statements for managers, policy makers, individuals who are new to accessibility, and other individuals who need to understand the concepts but not dive into the technical details. They provide an easy-to-understand way of organizing and presenting the requirements so that non-experts can learn about and understand the concepts. Each guideline includes a unique, descriptive name along with a high-level plain-language summary. Guidelines address functional needs on specific topics, such as contrast, forms, readability, and more. Guidelines group related requirements and are technology-independent.

        Human evaluation
        @@ -1367,23 +1371,23 @@

        Glossary

        Method
        -

        Detailed information, either technology-specific or technology-agnostic, on ways to meet the outcome as well as tests and scoring information.

        +

        Detailed information, either technology-specific or technology-agnostic, on ways to meet the requirement as well as tests and scoring information.

        Normative

        Content whose instructions are required for conformance.

        -
        Outcome
        -
        -

        Result of practices that reduce or eliminate barriers that people with disabilities experience.

        -

        See Outcomes.

        -
        Point of Regard

        The position in rendered content that the user is presumed to be viewing. The dimensions of the point of regard can vary. For example,it can be a two-dimensional area (e.g. content rendered through a two-dimensional graphical viewport), or a point (e.g. a moment during an audio rendering or a cursor position in a graphical rendering), or a range of text (e.g. focused text), or a two-dimensional area (e.g. content rendered through a two-dimensional graphical viewport). The point of regard is almost always within the viewport, but it can exceed the spatial or temporal dimensions of the viewport (see the definition of rendered content for more information about viewport dimensions). The point of regard can also refer to a particular moment in time for content that changes over time (e.g. an audio-only presentation). User agents can determine the point of regard in a number of ways, including based on viewport position in content, keyboard focus, and selection.

        Process

        A sequence of steps that need to be completed to accomplish an activity / task from end-to-end.

        +
        Requirement
        +
        +

        Result of practices that reduce or eliminate barriers that people with disabilities experience.

        +

        See Requirements.

        +
        Semi-Automated Evaluation

        Evaluation conducted using machines to guide humans to areas that need @@ -1399,7 +1403,7 @@

        Glossary

        The end goal a user has when starting a process through digital means.

        User testing
        -

        Evaluation of content by observation of how users with specific functional needs are able to complete a process and how the content meets the relevant outcomes.

        +

        Evaluation of content by observation of how users with specific functional needs are able to complete a process and how the content meets the relevant requirements.

      @@ -1411,63 +1415,6 @@

      Privacy Considerations

      Security Considerations

      The content of this document has not matured enough to identify security considerations. Reviewers of this draft should consider whether requirements of the conformance model could impact security.

    -
    -

    Guidelines development methodology

    -
    - Summary -

    WCAG 3 includes some of the information from WCAG 2, guidelines for tools to create web content (ATAG), and guidelines for browsers, media players, and similar software (UAAG). The WCAG 3 design is based on research. You can read more about the [[[?WCAG3-requirements]]].

    -
    -
    -

    Relationship to other W3C guidelines

    -

    The [[[WCAG20]]] were designed to be technology neutral, and have stayed relevant for over 10 years. The [[[ATAG20]]] provide guidance for various types of software that assist people in writing accessible content. [[[UAAG20]]] offers useful guidance to user agent developers and has been implemented on an individual success criterion basis.

    -

    These guidelines have normative guidance for content and helpful implementation advice for authoring tools, user agents, and assistive technologies.

    -
      -
    • WCAG 3 incorporates but may not be all encompassing of WCAG 2, ATAG, and UAAG.
      • -
    • WCAG 3 is not backward compatible with WCAG 2, ATAG 2.0, and UAAG 2.0.
      • -
    -

    For more details about differences from previous guidelines, see Appendix: Differences From WCAG 2.

    -
    -
    -
    -

    Differences from WCAG 2

    -
    -

    Outcomes

    -

    Outcomes are different from WCAG 2 success criteria. Compared to success criteria, outcomes are written to be:

    -
      -
    • In plain language; 
      • -
    • More understandable by people who are not experts in technology;
      • -
    • More user-need oriented instead of technology oriented;
      • -
    • More granular, so there will be more of them; and
      • -
    • More flexible to allow more tests than the true/false statements of WCAG 2. 
      • -
    -

    The design of outcomes allows more varied needs of people with disabilities than could have been included in WCAG 2. 

    -

    Methods map approximately to WCAG 2 Techniques documents.

    -
    -
    -

    Approximate mapping of WCAG 2 and WCAG 3 documentation

    - - - - - - - - - - - - - - - - - - - - -
    WCAG 2 WCAG 3
    Success CriteriaOutcomes
    TechniquesMethods
    UnderstandingHow-to
    -
    -

    Change log

    This section shows substantive changes made in WCAG 3 since the First Public Working Draft was published in 21 January 2021 . From 45d26b6a993f4f4e8a07ac9962ae085b9a33569f Mon Sep 17 00:00:00 2001 From: rmontgomery Date: Fri, 15 Nov 2024 16:34:15 -0500 Subject: [PATCH 20/49] Updates to questions --- guidelines/index.html | 31 ++++++++++++------------------- 1 file changed, 12 insertions(+), 19 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 2df7509..f3f8187 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -16,7 +16,7 @@

    See WCAG 3 Introduction for an introduction and links to WCAG technical and educational material.

    -

    This is an update to the W3C Accessibility Guidelines (WCAG) 3.0. It includes a restructuring of the guidelines and first draft decision trees for three Guidelines: Image alternatives, Keyboard Focus Appearance and Implied meaningful.

    +

    This is an update to the W3C Accessibility Guidelines (WCAG) 3.0. It includes a restructuring of the guidelines and first draft decision trees for three Guidelines: Image alternatives, Keyboard Focus Appearance and Implied meaning.

    To comment, file an issue in the W3C wcag3 GitHub repository. The Working Group requests that public comments be filed as new issues, one issue per discrete comment. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, send email to public-agwg-comments@w3.org (comment archive). In-progress updates to the guidelines can be viewed in the public editors’ draft.

    @@ -51,12 +51,16 @@

    Introduction

    The final set of Requirements in WCAG 3 will be different than what is in this draft. Requirements will be added, combined, and removed. We also expect changes to the text of the Requirements. Only some of the Requirements will be used to meet the base level of conformance.

    -

    The purpose of publishing this initial list is to: -

    • better understand the scope of needs,
      • -
    • request assistance in identifying gaps, and
      • -
    • request assistance locating and conducting research to validate or invalidate the requirements listed.
    -

    -

    We did not make changes to conformance related sections and we did not publish an updated WCAG 3 Explainer.

    +

    The purpose of this update is to demonstrate a potential structure for guidelines and indicate the current direction of the WCAG 3.0 conformance. Please consider the following questions when reviewing this draft: +

    • What requirements that are needed to make web content accessible and are missing from this list?
      • +
    • What research supports or refutes these requirements?
      • +
    • Three guidelines have moved from exploratory to developing: Image alternatives, Keyboard Focus Appearance and Implied Meaning. Does grouping related requirements and assertions together and using a decision tree + structure for foundational requirements make the guidelines easier to understand and use?
      • +
    • The conformance section explains the conformance approach the Accessibilty Guidelines Working Group is considering. While many details remain to be worked out, do you have concerns or comments about the general approach?
      • +

    + +

    To provide feedback, please file a GitHub issue or send email to public-agwg-comments@w3.org (comment archive).

    +

    The Requirements are grouped into the following sections:

      @@ -113,21 +117,10 @@

      Guidelines

      The following list is an initial set of potential guidelines and requirements that the working group will be exploring. The goal is to guide the next phase of work. They should be considered drafts and should not be considered as final content of WCAG 3.

      -

      Ordinarily, exploratory content includes editor's notes listing concerns and questions for each item. Because this Guidelines section is very early in the process of working on WCAG 3.0, this editor's note covers most of the content in thi section. Unless otherwise noted, all items in the list as exploratory at this point. It is a list of all possible topics for consideration. Not all items listed will be included in the final version of WCAG 3.0.

      +

      Ordinarily, exploratory content includes editor's notes listing concerns and questions for each item. Because this Guidelines section is very early in the process of working on WCAG 3.0, this editor's note covers most of the content in this section. Unless otherwise noted, all items in the list as exploratory at this point. It is a list of all possible topics for consideration. Not all items listed will be included in the final version of WCAG 3.0.

      The guidelines and requirements listed below came from analysis of user needs that the Working Group has been studying, examining, and researching. They have not been refined and do not include essential exceptions or methods. Some requirements may be best addressed by authoring tools or at the platform level. Many requirements need additional work to better define the scope and to ensure they apply correctly to multiple languages, cultures, and writing systems. We will address these questions as we further explore each requirement.

      -

      Please consider the following questions when reviewing this list of requirements:

      - - -
        -
      • Does the structure proposed here and exemplified in the three developing guidelines help explain the relationship of requirements?
        • -
      • What requirements that are needed to make web content accessible and are missing from this list?
        • -
      • What research supports or refutes these requirements?
        • -

      - -

      To provide feedback, please file a GitHub issue or send email to public-agwg-comments@w3.org (comment archive).

      -

      Additional Research

      One goal of publishing this list is to identify gaps in current research and request assistance filling those gaps.

      Editor's notes indicate the requirements within this list where the working group has not found enough research to fully validate the guidance and create methods to support it or additional work is needed to evaluate existing research. If you know of existing research or if you are interested in conducting research in this area, please file a GitHub issue or send email to public-agwg-comments@w3.org (comment archive).

      From 4796ec6830b3a0fdd958fe7e43a2073a3453e537 Mon Sep 17 00:00:00 2001 From: rmontgomery Date: Fri, 15 Nov 2024 16:50:56 -0500 Subject: [PATCH 21/49] Editorial changes to questions --- guidelines/index.html | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index f3f8187..76491a6 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -50,17 +50,6 @@

      Introduction

    • WCAG 3 Requirements are more granular than WCAG 2 Success Criteria.
    The final set of Requirements in WCAG 3 will be different than what is in this draft. Requirements will be added, combined, and removed. We also expect changes to the text of the Requirements. Only some of the Requirements will be used to meet the base level of conformance.

    - -

    The purpose of this update is to demonstrate a potential structure for guidelines and indicate the current direction of the WCAG 3.0 conformance. Please consider the following questions when reviewing this draft: -

    • What requirements that are needed to make web content accessible and are missing from this list?
      • -
    • What research supports or refutes these requirements?
      • -
    • Three guidelines have moved from exploratory to developing: Image alternatives, Keyboard Focus Appearance and Implied Meaning. Does grouping related requirements and assertions together and using a decision tree - structure for foundational requirements make the guidelines easier to understand and use?
      • -
    • The conformance section explains the conformance approach the Accessibilty Guidelines Working Group is considering. While many details remain to be worked out, do you have concerns or comments about the general approach?
      • -

    - -

    To provide feedback, please file a GitHub issue or send email to public-agwg-comments@w3.org (comment archive).

    -

    The Requirements are grouped into the following sections:

    +

    The purpose of this update is to demonstrate a potential structure for guidelines and indicate the current direction of the WCAG 3.0 conformance. Please consider the following questions when reviewing this draft: +

    • What requirements needed to make web content accessible are missing from this list?
      • +
    • What research supports or refutes the requirements marked as needing additional research?
      • +
    • Three guidelines (Image alternatives, Keyboard Focus Appearance and Implied Meaning) have moved from exploratory to developing and demonstrate a potential structure. Does grouping related requirements and assertions together and using a decision tree + for foundational requirements make the guidelines easier to understand and use?
      • +
    • The conformance section explains the approach the Accessibilty Guidelines Working Group is considering for WCAG 3. While many details still need to be worked out, do you have constructive comments about the proposed approach for WCAG 3?
      • +

    + +

    To provide feedback, please file a GitHub issue or send email to public-agwg-comments@w3.org (comment archive).

    +

    About WCAG 3

    This specification presents a new model and guidelines to make web content and applications accessible to people with disabilities. The W3C Accessibility Guidelines (WCAG) 3.0 support a wide set of user needs, use new approaches to testing, and allow frequent maintenance of guidelines and related content to keep pace with accelerating technology change. WCAG 3 supports this evolution by focusing on the functional needs of users. These needs are then supported by guidelines written as outcome statements, requirments, assertions, and technology-specific methods to meet those needs. 

    From 9982cfb8db86998c7effb9ae0f136e24f1cb441d Mon Sep 17 00:00:00 2001 From: Alastair Campbell Date: Tue, 19 Nov 2024 09:51:10 +0000 Subject: [PATCH 22/49] but comma Co-authored-by: Hidde de Vries <160571138+hidde-logius@users.noreply.github.com> --- guidelines/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guidelines/index.html b/guidelines/index.html index 76491a6..3182700 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -34,7 +34,7 @@

    Introduction

    we don’t expect it to change. There are 5 levels:
    • Placeholder - we are thinking about the topic and plan to work on it in the next few months.
      • -
    • Exploratory - we have started work on this topic but still have many questions.
      • +
    • Exploratory - we have started work on this topic, but still have many questions.
    • Developing - we have general agreement, but not all the details are worked out.
    • Refining - we think we have a good idea and want public feedback about it. We are ready to have a few people try it out and see how well it works.
      • From 6ee1064cabc2cd187aaf8dcc00c902d84faf9dbc Mon Sep 17 00:00:00 2001 From: Alastair Campbell Date: Tue, 19 Nov 2024 09:58:29 +0000 Subject: [PATCH 23/49] Working group capitalisation and lists tidy --- guidelines/index.html | 32 +++++++++++++++++++------------- 1 file changed, 19 insertions(+), 13 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 3182700..a41ecf5 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -91,10 +91,10 @@

      Section status levels

      As part of the WCAG 3 drafting process each normative section of this document is given a status. This status is used to indicate how far along in the development this section is, how ready it is for experimental adoption, and what kind of feedback the Accessibility Guidelines Working Group is looking for.

      • Placeholder: This content is temporary. It showcases the type of content or section to expect here. All of this is expected to be replaced. No feedback is needed on placeholder content.
        • -
      • Exploratory: The working group is exploring what direction to take with this section. This content is not refined, details and definitions may be missing. Feedback should be about the proposed direction.
        • +
      • Exploratory: The Working Group is exploring what direction to take with this section. This content is not refined, details and definitions may be missing. Feedback should be about the proposed direction.
      • Developing: There is rough agreement on what is needed for this section, although not all high-level concerns have been settled. Details have been filled, but are yet to be worked out. Feedback should be focused on ensuring the sections are usable and reasonable in a broad sense.
        • -
      • Refining: The working group has reach consensus on this section. It is ready for broad public review and experimental adoption. Feedback should be focused on the feasibility and implementability.
        • -
      • Mature: Content is believed by the working group to be ready for recommendation. Feedback should be focused on edge case scenarios the working group may not have anticipated.
        • +
      • Refining: The Working Group has reach consensus on this section. It is ready for broad public review and experimental adoption. Feedback should be focused on the feasibility and implementability.
        • +
      • Mature: Content is believed by the Working Group to be ready for recommendation. Feedback should be focused on edge case scenarios the Working Group may not have anticipated.
    @@ -114,7 +114,7 @@

    Guidelines

    The individuals and organizations that use WCAG vary widely and include web designers and developers, policy makers, purchasing agents, teachers, and students. To meet the varying needs of this audience, several layers of guidance will be provided including guidelines written as outcome statements, requirements that can be tested, assertions, a rich collection of methods, resource links, and code samples.

    -

    The following list is an initial set of potential guidelines and requirements that the working group will be exploring. The goal is to guide the next phase of work. They should be considered drafts and should not be considered as final content of WCAG 3.

    +

    The following list is an initial set of potential guidelines and requirements that the Working Group will be exploring. The goal is to guide the next phase of work. They should be considered drafts and should not be considered as final content of WCAG 3.

    Ordinarily, exploratory content includes editor's notes listing concerns and questions for each item. Because this Guidelines section is very early in the process of working on WCAG 3.0, this editor's note covers most of the content in this section. Unless otherwise noted, all items in the list as exploratory at this point. It is a list of all possible topics for consideration. Not all items listed will be included in the final version of WCAG 3.0.

    @@ -122,7 +122,7 @@

    Guidelines

    Additional Research

    One goal of publishing this list is to identify gaps in current research and request assistance filling those gaps.

    -

    Editor's notes indicate the requirements within this list where the working group has not found enough research to fully validate the guidance and create methods to support it or additional work is needed to evaluate existing research. If you know of existing research or if you are interested in conducting research in this area, please file a GitHub issue or send email to public-agwg-comments@w3.org (comment archive).

    +

    Editor's notes indicate the requirements within this list where the Working Group has not found enough research to fully validate the guidance and create methods to support it or additional work is needed to evaluate existing research. If you know of existing research or if you are interested in conducting research in this area, please file a GitHub issue or send email to public-agwg-comments@w3.org (comment archive).

    @@ -453,18 +453,24 @@

    Keyboard Focus Appearance

    For each focusable item:

    1. Is the user-agent default focus indicator used? - +
    2. Is the user-agent default focus indicator used, and meets contrast across backgrounds? - +
    3. Is the focus indicator defined by the author? - +

    @@ -1233,7 +1239,7 @@
    Assistive technology control
    Printing
    -

    Printing respects user’s content presentation preferences.

    +

    Printing respects user's content presentation preferences.

    Needs additional research

    @@ -1283,7 +1289,7 @@

    Only accessibility-supported ways of using technologies

    At the foundational level of conformance assumptions can be made by authors that methods and techniques provided by WCAG 3 work. At higher levels of conformance the author may need to test that a technique works, or check that available user-agents meet the requirement, or a combination of both.

    -

    This approach means the working group will ensure that methods and techniques included do have reasonably wide and international support from user-agents, and there are sufficient techniques to meet each requirement.

    +

    This approach means the Working Group will ensure that methods and techniques included do have reasonably wide and international support from user-agents, and there are sufficient techniques to meet each requirement.

    The intent is that WCAG 3 will use a content-management-system to support tagging of methods/techniques with support information. There should also be a process where interested parties can provide information.

    From 06fee925153a39d38c7b76dd7213b737c696ba0e Mon Sep 17 00:00:00 2001 From: Alastair Campbell Date: Tue, 19 Nov 2024 10:00:08 +0000 Subject: [PATCH 24/49] Update guidelines/index.html Co-authored-by: Hidde de Vries <160571138+hidde-logius@users.noreply.github.com> --- guidelines/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guidelines/index.html b/guidelines/index.html index a41ecf5..95d9dbc 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -194,7 +194,7 @@
    Allow automated entry
    No cognitive tests
    -

    Processes, including login/authentication, can be completed without puzzles, calculations, or other cognitive tests (essential exceptions would apply).

    +

    Processes, including authentication, can be completed without puzzles, calculations, or other cognitive tests (essential exceptions would apply).

    No memorization
    From 97a588fb73c2bc3951e23511dceeb8eb952822a2 Mon Sep 17 00:00:00 2001 From: Alastair Campbell Date: Tue, 19 Nov 2024 10:00:47 +0000 Subject: [PATCH 25/49] Update guidelines/index.html Co-authored-by: Hidde de Vries <160571138+hidde-logius@users.noreply.github.com> --- guidelines/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guidelines/index.html b/guidelines/index.html index 95d9dbc..d15e9bf 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -477,7 +477,7 @@

    Keyboard Focus Appearance

    Custom indicator
    -

    A custom focus indicator is used with sufficient size, change of contrast, adjacent contrast, distinct style and adjacecy.

    +

    A custom focus indicator is used with sufficient size, change of contrast, adjacent contrast, distinct style and adjacency.

    Default indicator
    From 93aa0873d33f4b12da53059d9bf0032db3ebc339 Mon Sep 17 00:00:00 2001 From: rmontgomery Date: Tue, 19 Nov 2024 09:26:27 -0500 Subject: [PATCH 26/49] Add implied meaning --- guidelines/index.html | 40 +++++++++++++++++++++++++++++++++------- 1 file changed, 33 insertions(+), 7 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index d15e9bf..9355be9 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -307,7 +307,7 @@

    Image and media alternatives

    Image alternatives

    Users have equivalent alternatives for images.

    -

    Foundational

    +

    Foundational Requirements

    For each image:

      @@ -342,7 +342,7 @@
      Detectable image
    -

    Supplemental

    +

    Supplemental Requirements

    Image role

    The role and importance of the image is programmatically indicated.

    @@ -448,7 +448,7 @@

    Interactive components

    Keyboard Focus Appearance

    Users can see which element has keyboard focus.

    -

    Foundational

    +

    Foundational Requirements

    For each focusable item:

      @@ -488,7 +488,7 @@
      User agent default indicator

      Focusable item uses the user agent default indicator.

    -

    Supplemental

    +

    Supplemental Requirements

    Supplimentary indicators

    @@

    @@ -1006,9 +1006,35 @@
    Appropriate tone
    Double negatives

    Content does not include double negatives to express a positive unless it is standard usage for that language or dialect.

    -
    -
    Figurative language
    -

    Explanations for figurative and non-literal language [such as jokes, sarcasm, hyperbole, metaphors, similes, and idioms] are available.

    +
    +
    Implied Meaning
    +

    Users can access the literal meaning of text.

    +

    Foundational Requirements

    +

    For each item of non-literal text: +

      +
    1. Is the non-literal text presented in a way that is available to user agents, including assistive technology (AT)? + +
      2. + +
    2. Does the available user agent, including assistive technology, sufficiently Explain non-literal text or provide a literal alternative? +
      • Yes, pass. Stop.
        • +
      • No, continue.
      +
      3. + +
    3. Does the publisher sufficiently explain the non-literal text or provide a literal alternative? + +
      4. +
    +

    +

    Exceptions

    +
    • If the purpose is to showcase works of art, such as a poetry journal but if the purpose is to educate students about + pieces of art, then the exception would not apply.
    +
    +
    Literal text
    +

    Explain non-literal text or provide a literal alternative

    +
    Sentence voice
    From d0b483a5c39dc908d90147f584787b1178570187 Mon Sep 17 00:00:00 2001 From: rmontgomery Date: Tue, 19 Nov 2024 09:44:24 -0500 Subject: [PATCH 27/49] Adding editor's note to Glosssary --- guidelines/index.html | 2 ++ 1 file changed, 2 insertions(+) diff --git a/guidelines/index.html b/guidelines/index.html index 9355be9..d05bd17 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -1344,6 +1344,8 @@

    Defining conformance scope

    Glossary

    Many of the terms defined here have common meanings. When terms appear with a link to the definition, the meaning is as formally defined here. When terms appear without a link to the definition, their meaning is not explicitly related to the formal definition here. These definitions are in progress and may evolve as the document evolves.

    +

    This glossary includes terms used by content that has reached the developing stage or at a higher level. The definitions themselves include a maturity level and may mature at a differet pace than the content that refers to them. We have not yet, but inted to, work with other taskforces and groups to harmonize terminology as much as is possible.

    +
    Assertion

    A formal claim of fact, attributed to a person or organization. An attributable and documented statement of fact regarding procedures practiced in the development and maintenance of the content or product to improve accessibility.

    From 1024eb0640c7c6934a04f58cd4b68fed16df4a8b Mon Sep 17 00:00:00 2001 From: rmontgomery Date: Tue, 19 Nov 2024 09:46:58 -0500 Subject: [PATCH 28/49] editorial fix to glossary editor's note --- guidelines/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guidelines/index.html b/guidelines/index.html index d05bd17..d3d899e 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -1344,7 +1344,7 @@

    Defining conformance scope

    Glossary

    Many of the terms defined here have common meanings. When terms appear with a link to the definition, the meaning is as formally defined here. When terms appear without a link to the definition, their meaning is not explicitly related to the formal definition here. These definitions are in progress and may evolve as the document evolves.

    -

    This glossary includes terms used by content that has reached the developing stage or at a higher level. The definitions themselves include a maturity level and may mature at a differet pace than the content that refers to them. We have not yet, but inted to, work with other taskforces and groups to harmonize terminology as much as is possible.

    +

    This glossary includes terms used by content that has reached a maturity level of Developing or higher. The definitions themselves include a maturity level and may mature at a differet pace than the content that refers to them. The AGWG will work with other taskforces and groups to harmonize terminology across documents as much as is possible.

    Assertion
    From 72328a6d749d094d4ce439b496aa851122a28a4c Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 19 Nov 2024 15:11:43 +0000 Subject: [PATCH 29/49] Update glossary references --- guidelines/index.html | 314 ++++++++++++++++++++++++++---------------- 1 file changed, 197 insertions(+), 117 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index d15e9bf..9ed5cc6 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -107,7 +107,7 @@

    Guidelines

    Summary

    The following guidelines are being considered for WCAG 3. They are currently a list of topics which we expect to explore more thoroughly in future drafts. The list includes current WCAG 2 guidance and additional requirements. The list will change in future drafts.

    -

    Unless otherwise stated, requirements assume the content described is provided both visually and programmatically.

    +

    Unless otherwise stated, requirements assume the content described is provided both visually and programmatically.

    @@ -131,7 +131,7 @@

    Guidelines

    Animation and movement

    Avoid physical harm

    -

    Users do not experience physical harm from content.

    +

    Users do not experience physical harm from content.

    Audio shifting

    Audio shifting designed to create a perception of motion is avoided; or can be paused or prevented.

    @@ -161,7 +161,7 @@

    Correct mistakes

    Users know about and can correct mistakes.

    Error association
    -

    Error notifications are programmatically associated with the error source so that users can access the error information while focused on the source of the error.

    +

    Error notifications are programmatically associated with the error source so that users can access the error information while focused on the source of the error.

    Error identification
    @@ -205,7 +205,7 @@
    No memorization

    Adequate time

    -

    Users have enough time to read and use content.

    +

    Users have enough time to read and use content.

    Adjust timing at start

    For each process with a time-limit, a mechanism exists to disable or extend the limit before the time-limit starts.

    @@ -225,7 +225,7 @@

    Unnecessary steps

    Users can complete tasks without unnecessary steps.

    Optional information

    -

    Processes can be completed without being forced to read or understand unnecessary content.

    +

    Processes can be completed without being forced to read or understand unnecessary content.

    Optional input

    @@ -309,20 +309,20 @@

    Image alternatives

    Foundational

    -

    For each image: +

    For each image:

      -
    1. Would removing the image impact how people understand the page? +
    2. Would removing the image impact how people understand the page?
      3. -
    3. Is the image presented in a way that is available to user agents and assistive technology? -
    @@ -330,30 +330,30 @@

    Image alternatives

    Decorative image
    -

    Decorative image is programmatically hidden.

    +

    Decorative image is programmatically hidden.

    Content image
    -

    Equivalent text alternative is available for image that conveys content.

    +

    Equivalent text alternative is available for image that conveys content.

    Detectable image
    -

    Image is programmatically detectable.

    +

    Image is programmatically detectable.

    Supplemental

    Image role
    -

    The role and importance of the image is programmatically indicated.

    +

    The role and importance of the image is programmatically indicated.

    Image type
    -

    The type of image (photo, icon, etc.) is indicated.

    +

    The type of image (photo, icon, etc.) is indicated.

    Editable Alternatives
    -

    Auto generated text descriptions are editable by content creator.

    +

    Auto generated text descriptions are editable by content creator.

    Needs additional research

    @@ -366,14 +366,14 @@
    Style Guide

    Media alternatives

    -

    Users have equivalent alternatives for media content.

    +

    Users have equivalent alternatives for media content.

    Audio descriptions
    -

    Where there is visual content in media, there is an equivalent synchronized audio track.

    +

    Where there is visual content in media, there is an equivalent synchronized audio track.

    Captions
    -

    Where there is audio content in media, there are equivalent synchronized captions.

    +

    Where there is audio content in media, there are equivalent synchronized captions.

    Descriptive transcripts
    @@ -399,10 +399,10 @@

    Non-verbal cues

    Nontext alternatives

    -

    Users have alternatives available for non-text, non-image content that conveys context or meaning.

    +

    Users have alternatives available for non-text, non-image content that conveys context or meaning.

    Nontext content
    -

    Equivalent text alternatives are available for non-text, non-image content that conveys context or meaning.

    +

    Equivalent text alternatives are available for non-text, non-image content that conveys context or meaning.

    Needs additional research

    @@ -420,7 +420,7 @@
    Persistent captions

    Single Sense

    -

    Users have content that does not rely on a single sense or perception.

    +

    Users have content that does not rely on a single sense or perception.

    Use of hue

    Information conveyed by graphical elements does not rely on hue.

    @@ -428,16 +428,16 @@
    Use of hue
    Use of visual depth
    -

    Information conveyed with visual depth is also conveyed programmatically and/or through text.

    +

    Information conveyed with visual depth is also conveyed programmatically and/or through text.

    Needs additional research

    Use of sound
    -

    Information conveyed with sound is also conveyed programmatically and/or through text.

    +

    Information conveyed with sound is also conveyed programmatically and/or through text.

    Use of spatial audio
    -

    Information that is conveyed with spatial audio is also conveyed programmatically and/or through text.

    +

    Information that is conveyed with spatial audio is also conveyed programmatically and/or through text.

    @@ -446,7 +446,7 @@
    Use of spatial audio

    Interactive components

    Keyboard Focus Appearance

    -

    Users can see which element has keyboard focus.

    +

    Users can see which element has keyboard focus.

    Foundational

    @@ -512,22 +512,22 @@
    Pointer visible

    Navigating content

    -

    Users can determine where they are and move through content (including interactive elements) in a systematic and meaningful way regardless of input or movement method.

    +

    Users can determine where they are and move through content (including interactive elements) in a systematic and meaningful way regardless of input or movement method.

    Focus in viewport

    The focus does not move to a position outside the current viewport, unless a mechanism is available to return to the previous focus point.

    Focus retention
    -

    A user can focus on a content “area,” such as a modal or pop-up, then resume their view of all content using a limited number of steps.

    +

    A user can focus on a content “area,” such as a modal or pop-up, then resume their view of all content using a limited number of steps.

    Keyboard focus order
    -

    The keyboard focus moves sequentially through content in an order and way that preserves meaning and operability.

    +

    The keyboard focus moves sequentially through content in an order and way that preserves meaning and operability.

    Restore focus
    -

    When the focus is moved by the content into a temporary change of view (e.g. a modal), the focus is restored to its previous location when the view is restored.

    +

    When the focus is moved by the content into a temporary change of view (e.g. a modal), the focus is restored to its previous location when the view is restored.

    Relevant focus
    @@ -552,7 +552,7 @@
    Consistent visual design
    Control location
    -

    Interactive components are visually and programmatically located in conventional locations.

    +

    Interactive components are visually and programmatically located in conventional locations.

    Needs additional research

    @@ -586,11 +586,11 @@
    Control labels
    Control updates
    -

    Changes to interactive components’ names, roles, values or states are visually and programmatically indicated.

    +

    Changes to interactive components’ names, roles, values or states are visually and programmatically indicated.

    Distinguishable controls
    -

    Interactive components are visually distinguishable without interaction from static content and include visual cues on how to use them.

    +

    Interactive components are visually distinguishable without interaction from static content and include visual cues on how to use them.

    Field constraints
    @@ -622,7 +622,7 @@
    Concurrent inputs
    Hover information
    -

    Users can dismiss additional content (triggered by hover) without moving the pointer, unless the additional content communicates an input error or does not obscure or replace other content.

    +

    Users can dismiss additional content (triggered by hover) without moving the pointer, unless the additional content communicates an input error or does not obscure or replace other content.

    Input control
    @@ -632,19 +632,19 @@
    Input control

    Content changes

    -

    Users are aware of changes to content or context.

    +

    Users are aware of changes to content or context.

    Notify about change
    -

    Changes in content and updates notify users, regardless of the update speed. +

    Changes in content and updates notify users, regardless of the update speed.

    Notify on change
    -

    Notification is provided when viewing content that was previously viewed is changed.

    +

    Notification is provided when viewing content that was previously viewed is changed.

    Inform before activation
    -

    Interactive components that can alter the order of content convey their purpose prior to activation, and convey their impact on content order when activated.

    +

    Interactive components that can alter the order of content convey their purpose prior to activation, and convey their impact on content order when activated.

    Reverse change of context
    @@ -654,7 +654,7 @@
    Reverse change of context

    Target size

    -

    Users are not required to accurately position a pointer in order to view or operate content.

    +

    Users are not required to accurately position a pointer in order to view or operate content.

    Target size minimum

    The combined target size and spacing to adjacent targets is at least 24x24 pixels @@ -692,7 +692,7 @@

    Keyboard only
    No keyboard trap
    -

    If keyboard focus can be moved to an interactive component, then the keyboard focus can be moved away from that component, or the component can be dismissed, with focus returning to the previous point.

    +

    If keyboard focus can be moved to an interactive component, then the keyboard focus can be moved away from that component, or the component can be dismissed, with focus returning to the previous point.

    Non-standard commands
    @@ -702,14 +702,14 @@
    Non-standard commands

    Gestures

    -

    Users are not required to use gestures or dragging to view or operate content.

    +

    Users are not required to use gestures or dragging to view or operate content.

    Change focus with pointer device
    -

    Selecting an interactive component with a ‘pointer’ sets the focus to that element.

    +

    Selecting an interactive component with a pointer sets the focus to that element.

    Complex pointer inputs
    -

    Every function that can be operated by a pointer, can be operated by a ‘single pointer input’ or a sequence of single pointer inputs without requiring certain timing.

    +

    Every function that can be operated by a pointer, can be operated by a single pointer input or a sequence of single pointer inputs without requiring certain timing.

    Pointer-agnostic
    @@ -744,7 +744,7 @@
    Use without device movement
    Interactive component contrast
    -

    Visual information required to identify user interface components and states meet a ‘minimum contrast ratio test’, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author.

    +

    Visual information required to identify user interface components and states meet a minimum contrast ratio test, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author.

    Needs additional research

    @@ -754,23 +754,23 @@
    Interactive component contrast

    Layout

    Relationships

    -

    Users can determine relationships between content both visually and using assistive technologies.

    +

    Users can determine relationships between content both visually and using assistive technologies.

    Clear relationships
    -

    The relationships between parts of the content is clearly indicated.

    +

    The relationships between parts of the content is clearly indicated.

    Clear starting point
    -

    The starting point or home is visually and programmatically labeled.

    +

    The starting point or home is visually and programmatically labeled.

    Distinguishable relationships
    -

    Relationships that convey meaning between pieces of content are programmatically determinable. Note: Examples of relationships include items positioned next to each other, arranged in a hierarchy, or visually grouped.

    +

    Relationships that convey meaning between pieces of content are programmatically determinable. Note: Examples of relationships include items positioned next to each other, arranged in a hierarchy, or visually grouped.

    Needs additional research

    Distinguishable sections
    -

    Sections are visually and programmatically distinguishable.

    +

    Sections are visually and programmatically distinguishable.

    Needs additional research

    @@ -781,7 +781,7 @@

    Recognizable layouts

    Users have consistent and recognizable layouts available.

    Consistent order
    -

    The relative order of content and interactions remain consistent throughout a workflow. Note: Relative order means that content can be added or removed, but repeated items are in the same order relative to each other.

    +

    The relative order of content and interactions remain consistent throughout a workflow. Note: Relative order means that content can be added or removed, but repeated items are in the same order relative to each other.

    Familiar layout
    @@ -789,7 +789,7 @@
    Familiar layout
    Information about options
    -

    Information required to understand options is visually and programmatically associated with the options.

    +

    Information required to understand options is visually and programmatically associated with the options.

    Related information
    @@ -799,10 +799,10 @@
    Related information

    Orientation

    -

    Users can determine their location in content both visually and using assistive technologies.

    +

    Users can determine their location in content both visually and using assistive technologies.

    Current location
    -

    The current location within the view, multi-step process, and product is visually and programmatically indicated.

    +

    The current location within the view, multi-step process, and is visually and programmatically indicated.

    Needs additional research

    @@ -811,25 +811,25 @@
    Multistep process
    Contextual information
    -

    Provide contextual information to help the user orient within the product.

    +

    Provide contextual information to help the user orient within the product.

    Structure

    -

    Users can understand and navigate through the content using structure.

    +

    Users can understand and navigate through the content using structure.

    Section labels
    -

    Major sections of content have within them well structured, understandable visual and programmatic headings.

    +

    Major sections of content have within them well structured, understandable visual and programmatic headings.

    Section length
    -

    Content is organized into short sections of related content.

    +

    Content is organized into short sections of related content.

    Needs additional research

    Section purpose
    -

    The purpose of each section of the content is clearly indicated.

    +

    The purpose of each section of the content is clearly indicated.

    Single idea
    @@ -837,15 +837,15 @@
    Single idea
    White spacing
    -

    Whitespace separates chunks of content.

    +

    Whitespace separates chunks of content.

    Title
    -

    Content has a title or high-level description.

    +

    Content has a title or high-level description.

    Lists
    -

    Three or more items of related data are presented as bulleted or numbered lists.

    +

    Three or more items of related data are presented as bulleted or numbered lists.

    Numbered steps
    @@ -861,11 +861,11 @@

    Consistency

    Users have consistent and alternative methods for navigation.

    Consistent navigation
    -

    Navigation elements remain consistent across views within the product.

    +

    Navigation elements remain consistent across views within the product.

    Multiple ways
    -

    The product provides at least two ways of navigating and finding information (Search, Scan, Site Map, Menu Structure, Breadcrumbs, contextual links, etc).

    +

    The product provides at least two ways of navigating and finding information (Search, Scan, Site Map, Menu Structure, Breadcrumbs, contextual links, etc).

    Persistent navigation
    @@ -878,20 +878,20 @@
    Persistent navigation

    Policy and Protection

    Content source

    -

    Users can determine when content is provided by a Third Party

    +

    Users can determine when content is provided by a Third Party

    Citation
    -

    The author or source of the primary content is visually and programmatically indicated.

    +

    The author or source of the primary content is visually and programmatically indicated.

    Needs additional research

    Indicate 3rd party content
    -

    Third party content (AI, Advertising, etc.) is visually and programmatically indicated.

    +

    Third party content (AI, Advertising, etc.) is visually and programmatically indicated.

    Needs additional research

    Obscuring primary content
    -

    Advertising and other third-party content that obscures the primary content can be moved or removed without interacting with the advertising or third-party content.

    +

    Advertising and other third-party content that obscures the primary content can be moved or removed without interacting with the advertising or third-party content.

    Needs additional research

    @@ -944,7 +944,7 @@

    Text appearance

    Users can read visually rendered text.

    Maximum text contrast
    -

    The rendered text against its background meets a maximum ‘contrast ratio test’ for its text appearance.

    +

    The rendered text against its background meets a maximum contrast ratio test for its text appearance.

    Needs additional research

    @@ -965,26 +965,26 @@
    Text style

    Text-to-speech

    -

    Users can access text content and its meaning with text-to-speech tools.

    +

    Users can access text content and its meaning with text-to-speech tools.

    Text-to-speech supported
    -

    Text content can be converted into speech.

    +

    Text content can be converted into speech.

    Needs additional research

    Human language
    -

    The human language of the view and content within the view is programmatically available.

    +

    The human language of the view and content within the view is programmatically available.

    Semantic text appearance
    -

    Meaning conveyed by text appearance is programmatically available.

    +

    Meaning conveyed by text appearance is programmatically available.

    Needs additional research

    Clear language

    -

    Users can access clear language content.

    +

    Users can access clear language content.

    Acronyms and abbreviations

    The expanded form or meaning of abbreviations and acronyms is available.

    @@ -1004,11 +1004,11 @@
    Appropriate tone
    Double negatives
    -

    Content does not include double negatives to express a positive unless it is standard usage for that language or dialect.

    +

    Content does not include double negatives to express a positive unless it is standard usage for that language or dialect.

    Figurative language
    -

    Explanations for figurative and non-literal language [such as jokes, sarcasm, hyperbole, metaphors, similes, and idioms] are available.

    +

    Explanations for figurative and non-literal language [such as jokes, sarcasm, hyperbole, metaphors, similes, and idioms] are available.

    Sentence voice
    @@ -1082,7 +1082,7 @@
    Support available

    Supplemental content

    -

    Users have supplemental content available.

    +

    Users have supplemental content available.

    Number supplements

    Text or visual alternatives are available for numerical concepts.

    @@ -1129,20 +1129,20 @@
    Text customization

    Adjustable viewport

    -

    Users can transform size and orientation if content presentation to make it viewable and usable.

    +

    Users can transform size and orientation of content presentation to make it viewable and usable.

    Orientation

    Content orientation allows the user to read the language presented without changing head or body position.

    Reflow
    -

    Content can be viewed in multiple viewport sizes, orientations, and zoom levels -- without loss of content, functionality, meaningful relationships, and with scrolling only occurring in one direction.

    +

    Content can be viewed in multiple viewport sizes, orientations, and zoom levels -- without loss of content, functionality, meaningful relationships, and with scrolling only occurring in one direction.

    Transform content

    -

    Users can transform content to make it understandable.

    +

    Users can transform content to make it understandable.

    Alternative presentation

    Complex information or instructions for complex processes are available in multiple presentation formats.

    @@ -1150,7 +1150,7 @@
    Alternative presentation
    Content markup
    -

    Role and priority of content is programmatically determinable.

    +

    Role and priority of content is programmatically determinable.

    Summary
    @@ -1158,7 +1158,7 @@
    Summary
    Transform content
    -

    Content can be transformed to make its purpose clearer.

    +

    Content can be transformed to make its purpose clearer.

    Needs additional research

    @@ -1205,7 +1205,7 @@

    Control possible harm

    Users can control potential sources of harm.

    Disturbing content
    -

    Warnings are available about content that may be emotionally disturbing, and the disturbing content can be hidden.

    +

    Warnings are available about content that may be emotionally disturbing, and the disturbing content can be hidden.

    Needs additional research

    @@ -1215,7 +1215,7 @@
    Haptic stimulation
    Triggers
    -

    Warnings are available about triggering content, and the warnings and triggering content can be hidden.

    +

    Warnings are available about triggering content, and the warnings and triggering content can be hidden.

    Needs additional research

    @@ -1232,14 +1232,14 @@
    Visual stimulation

    User Agent Support

    -

    Users can control content settings from their User Agents including Assistive Technology.

    +

    Users can control content settings from their User Agents including Assistive Technology.

    Assistive technology control
    -

    Content can be controlled using assistive and adaptive technology.

    +

    Content can be controlled using assistive and adaptive technology.

    Printing
    -

    Printing respects user's content presentation preferences.

    +

    Printing respects user's content presentation preferences.

    Needs additional research

    @@ -1248,7 +1248,7 @@
    User settings
    Virtual cursor
    -

    Assistive technologies can access content and interactions when using mechanisms that convey alternative points of regard or focus (i.e. virtual cursor).

    +

    Assistive technologies can access content and interactions when using mechanisms that convey alternative points of regard or focus (i.e. virtual cursor).

    @@ -1258,7 +1258,7 @@
    Virtual cursor

    Conformance

    Summary -

    You might want to make a claim that your content or product meets the WCAG 3 guidelines. If it does meet the guidelines, we call this “conformance”.

    +

    You might want to make a claim that your content or product meets the WCAG 3 guidelines. If it does meet the guidelines, we call this “conformance”.

    If you want to make a formal conformance claim, you must use the process described in this document. Conformance claims are not required and your content can conform to WCAG 3, even if you don’t want to make a claim.

    There are two types of content in this document:

      @@ -1301,7 +1301,7 @@

      Only accessibility-supported ways of using technologies

      Defining conformance scope

      -

      When evaluating the accessibility of content, WCAG 3 requires the guidelines apply to a specific scope. While the scope can be an all content within a digital product, it is usually one or more sub-sets of the whole. Reasons for this include:

      +

      When evaluating the accessibility of content, WCAG 3 requires the guidelines apply to a specific scope. While the scope can be an all content within a digital product, it is usually one or more sub-sets of the whole. Reasons for this include:

      • Large amounts of content are impractical to evaluate comprehensively using anything beyond automated evaluation of items;
      • In many cases, content changes frequently, causing evaluation to be accurate only for a specific moment in time;
        • @@ -1310,7 +1310,7 @@

        Defining conformance scope

      WCAG 3 therefore defines two ways to scope content: views and processes. Evaluation is done on one or more complete views or processes, and conformance is determined on the basis of one or more complete views or processes.

      -

      Conformance is defined only for processes and views. However, a conformance claim may be made to cover one process and view, a series of processes and views, or multiple related processes and views. All unique steps in a process MUST be represented in the set of views. Views outside of the process MAY also be included in the scope.

      +

      Conformance is defined only for processes and views. However, a conformance claim may be made to cover one process and view, a series of processes and views, or multiple related processes and views. All unique steps in a process MUST be represented in the set of views. Views outside of the process MAY also be included in the scope.

      We recognize that representative sampling is an important strategy that large and complex sites use to assess accessibility. While it is not addressed within this document at this time, our intent is to later address it within this document or in a separate document before the guidelines reach the Candidate Recommendation stage. We welcome your suggestions and feedback about the best way to incorporate representative sampling in WCAG 3.

    @@ -1320,7 +1320,7 @@

    Glossary

    Many of the terms defined here have common meanings. When terms appear with a link to the definition, the meaning is as formally defined here. When terms appear without a link to the definition, their meaning is not explicitly related to the formal definition here. These definitions are in progress and may evolve as the document evolves.

    Assertion
    -

    A formal claim of fact, attributed to a person or organization. An attributable and documented statement of fact regarding procedures practiced in the development and maintenance of the content or product to improve accessibility.

    +

    A formal claim of fact, attributed to a person or organization. An attributable and documented statement of fact regarding procedures practiced in the development and maintenance of the content or product to improve accessibility.

    Automated evaluation

    Evaluation conducted using software tools, typically evaluating code-level features and applying @@ -1332,18 +1332,36 @@

    Glossary

    Conformance

    Satisfying all the requirements of the guidelines. Conformance is an important part of following the guidelines even when not making a formal Conformance Claim.

    -

    See Conformance.

    +

    See Conformance.

    + +
    Content
    +
    +
    +

    To be defined.

    +
    +
    +
    Decorative image
    +
    +
    +

    To be defined.

    +
    +
    Deprecate

    To declare something outdated and in the process of being phased out, usually in favor of a specified replacement.

    Deprecated documents are no longer recommended for use and may cease to exist in the future.

    +
    Element
    +
    +
    +

    To be defined.

    +
    +
    Evaluation
    -
    The process of examining content for conformance to these - guidelines.
    -
    Different approaches to evaluation include automated evaluation, - semi-automated evaluation, human evaluation, and user - testing.
    +
    +

    The process of examining content for conformance to these guidelines.

    +

    Different approaches to evaluation include automated evaluation, semi-automated evaluation, human evaluation, and user testing.

    +
    Functional need

    A statement that describes a specific gap in one’s ability, or a specific mismatch between ability and the designed environment or context.

    @@ -1355,32 +1373,74 @@

    Glossary

    Human evaluation
    -

    Evaluation conducted by a human, typically to apply human judgement to tests - that cannot be fully automatically evaluated.

    -

    Human evaluation is contrasted with automated evaluation which is done entirely by - machine, though it includes semi-automated evaluation which allows - machines to guide humans to areas that need inspection. Human evaluation - involves inspection of content features, by contrast with user - testing which directly tests the experience of users with - content.

    +

    Evaluation conducted by a human, typically to apply human judgement to tests that cannot be fully automatically evaluated.

    +

    Human evaluation is contrasted with automated evaluation which is done entirely by machine, though it includes semi-automated evaluation which allows machines to guide humans to areas that need inspection. Human evaluation involves inspection of content features, by contrast with user testing which directly tests the experience of users with content.

    + +
    Image
    +
    +
    +

    To be defined.

    +
    +
    +
    Image role
    +
    +
    +

    To be defined.

    +
    +
    +
    Image type
    +
    +
    +

    To be defined.

    +
    +
    Informative
    -

    Content provided for information purposes and not required for conformance.

    +

    Content provided for information purposes and not required for conformance.

    +
    +
    Interactive component
    +
    +
    +

    To be defined.

    +
    +
    + +
    Items
    +
    +

    The smallest testable unit for testing scope. They could be interactive components such as a drop down menu, a link, or a media player. They could also be units of content such as a phrase, a paragraph, a label or error message, an icon, or an image.

    Method

    Detailed information, either technology-specific or technology-agnostic, on ways to meet the requirement as well as tests and scoring information.

    +
    Non-literal language
    +
    +
    +

    To be defined.

    +
    +
    Normative
    -

    Content whose instructions are required for conformance.

    +

    Content whose instructions are required for conformance.

    Point of Regard

    - The position in rendered content that the user is presumed to be viewing. The dimensions of the point of regard can vary. For example,it can be a two-dimensional area (e.g. content rendered through a two-dimensional graphical viewport), or a point (e.g. a moment during an audio rendering or a cursor position in a graphical rendering), or a range of text (e.g. focused text), or a two-dimensional area (e.g. content rendered through a two-dimensional graphical viewport). The point of regard is almost always within the viewport, but it can exceed the spatial or temporal dimensions of the viewport (see the definition of rendered content for more information about viewport dimensions). The point of regard can also refer to a particular moment in time for content that changes over time (e.g. an audio-only presentation). User agents can determine the point of regard in a number of ways, including based on viewport position in content, keyboard focus, and selection.

    + The position in rendered content that the user is presumed to be viewing. The dimensions of the point of regard can vary. For example,it can be a two-dimensional area (e.g. content rendered through a two-dimensional graphical viewport), or a point (e.g. a moment during an audio rendering or a cursor position in a graphical rendering), or a range of text (e.g. focused text), or a two-dimensional area (e.g. content rendered through a two-dimensional graphical viewport). The point of regard is almost always within the viewport, but it can exceed the spatial or temporal dimensions of the viewport (see the definition of rendered content for more information about viewport dimensions). The point of regard can also refer to a particular moment in time for content that changes over time (e.g. an audio-only presentation). User agents can determine the point of regard in a number of ways, including based on viewport position in content, keyboard focus, and selection.

    +
    Process
    -

    A sequence of steps that need to be completed to accomplish an activity / task from - end-to-end.

    +
    +

    A sequence of steps that need to be completed to accomplish an activity / task from end-to-end.

    +
    +
    Product
    +
    +

    Testing scope that is a combination of all items, views, and task flows that comprise the web site, set of web pages, web app, etc.

    +
    +
    Programmatically determinable
    +
    +
    +

    To be defined.

    +
    +
    Requirement

    Result of practices that reduce or eliminate barriers that people with disabilities experience.

    @@ -1388,20 +1448,40 @@

    Glossary

    Semi-Automated Evaluation
    -

    Evaluation conducted using machines to guide humans to areas that need - inspection.

    -

    Semi-automated evaluation involves components of automated evaluation - and human evaluation.

    +

    Evaluation conducted using machines to guide humans to areas that need inspection.

    +

    Semi-automated evaluation involves components of automated evaluation and human evaluation.

    +
    +
    Task flow
    +
    +

    Testing scope that includes a series views that support a specified user activity. A task flow may include a subset of items in a view or a group of views. Only the part of the views that support the user activity are included in a test of the task flow.

    Test

    Mechanism to evaluate implementation of a method.

    +
    User agent
    +
    +
    +

    To be defined.

    +
    +
    User need
    -

    The end goal a user has when starting a process through digital means.

    +
    +

    The end goal a user has when starting a process through digital means.

    +
    User testing
    -

    Evaluation of content by observation of how users with specific functional needs are able to complete a process and how the content meets the relevant requirements.

    +

    Evaluation of content by observation of how users with specific functional needs are able to complete a process and how the content meets the relevant requirements.

    +
    +
    Views
    +
    +

    Testing scope that includes all content visually and programmatically available without a significant change. Conceptually, views correspond to the definition of a web page as used in WCAG 2, but are not restricted to content meeting that definition. For example, a view could be considered a “screen” in a mobile app or a layer of web content, such as a modal dialog.

    +
    +
    Web technologies
    +
    +
    +

    To be defined.

    +
    From 3875e28d9a4c9d033a851e28024950e8fc27eeb8 Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 19 Nov 2024 15:18:02 +0000 Subject: [PATCH 30/49] Update "non-literal text" references --- guidelines/index.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index c9fc357..b5052f0 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -1010,7 +1010,7 @@
    Double negatives
    Implied Meaning

    Users can access the literal meaning of text.

    Foundational Requirements

    -

    For each item of non-literal text: +

    For each item of non-literal text:

    1. Is the non-literal text presented in a way that is available to user agents, including assistive technology (AT)?
      • Yes, item meets Accessible text, continue.
        • @@ -1033,7 +1033,7 @@
        Implied Meaning
        pieces of art, then the exception would not apply.
      Literal text
      -

      Explain non-literal text or provide a literal alternative

      +

      Explain non-literal text or provide a literal alternative

    @@ -1441,7 +1441,7 @@

    Glossary

    Detailed information, either technology-specific or technology-agnostic, on ways to meet the requirement as well as tests and scoring information.

    -
    Non-literal language
    +
    Non-literal text

    To be defined.

    From f29a7392d5872f9428a959c879919c4ad8062056 Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 19 Nov 2024 15:21:47 +0000 Subject: [PATCH 31/49] Definition for non-literal text --- guidelines/index.html | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index b5052f0..8edb896 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -1443,9 +1443,8 @@

    Glossary

    Non-literal text
    -
    -

    To be defined.

    -
    +

    Non-literal text uses words or phrases in a way that goes beyond their standard or dictionary meaning to express deeper, more complex ideas. This is also called figurative language. To understand it, users have to interpret the implied meaning behind the words, rather than just their literal or direct meaning.

    +

    Examples: Allusions, hyperbole, idioms, irony, jokes, litotes, metaphors, metonymies, onomatopoeias, oxymorons, personification, puns, sarcasm, and similes. More detailed examples are available in the Methods section.

    Normative
    From 96f971e78b2d8056408e973ed01c362eeead168b Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 19 Nov 2024 15:30:02 +0000 Subject: [PATCH 32/49] Fixes to glossary --- guidelines/index.html | 29 +++++++++++++++++++++++------ 1 file changed, 23 insertions(+), 6 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 8edb896..29e847c 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -744,7 +744,7 @@
    Use without device movement
    Interactive component contrast
    -

    Visual information required to identify user interface components and states meet a minimum contrast ratio test, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author.

    +

    Visual information required to identify user interface components and states meet a minimum contrast ratio test, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author.

    Needs additional research

    @@ -944,12 +944,12 @@

    Text appearance

    Users can read visually rendered text.

    Maximum text contrast
    -

    The rendered text against its background meets a maximum contrast ratio test for its text appearance.

    +

    The rendered text against its background meets a maximum contrast ratio test for its text appearance.

    Needs additional research

    Minimum text contrast
    -

    The rendered text against its background meets a minimum 'contrast ratio test' for its text appearance.

    +

    The rendered text against its background meets a minimum contrast ratio test for its text appearance.

    Needs additional research

    @@ -1368,6 +1368,12 @@

    Glossary

    To be defined.

    +
    Contrast ratio test
    +
    +
    +

    To be defined.

    +
    +
    Decorative image
    @@ -1450,6 +1456,12 @@

    Glossary

    Content whose instructions are required for conformance.

    +
    Pointer
    +
    +
    +

    To be defined.

    +
    +
    Point of Regard

    The position in rendered content that the user is presumed to be viewing. The dimensions of the point of regard can vary. For example,it can be a two-dimensional area (e.g. content rendered through a two-dimensional graphical viewport), or a point (e.g. a moment during an audio rendering or a cursor position in a graphical rendering), or a range of text (e.g. focused text), or a two-dimensional area (e.g. content rendered through a two-dimensional graphical viewport). The point of regard is almost always within the viewport, but it can exceed the spatial or temporal dimensions of the viewport (see the definition of rendered content for more information about viewport dimensions). The point of regard can also refer to a particular moment in time for content that changes over time (e.g. an audio-only presentation). User agents can determine the point of regard in a number of ways, including based on viewport position in content, keyboard focus, and selection.

    @@ -1462,7 +1474,7 @@

    Glossary

    Testing scope that is a combination of all items, views, and task flows that comprise the web site, set of web pages, web app, etc.

    -
    Programmatically determinable
    +
    Programmatically determinable

    To be defined.

    @@ -1471,13 +1483,18 @@

    Glossary

    Requirement

    Result of practices that reduce or eliminate barriers that people with disabilities experience.

    -

    See Requirements.

    Semi-Automated Evaluation

    Evaluation conducted using machines to guide humans to areas that need inspection.

    Semi-automated evaluation involves components of automated evaluation and human evaluation.

    +
    Single pointer input
    +
    +
    +

    To be defined.

    +
    +
    Task flow

    Testing scope that includes a series views that support a specified user activity. A task flow may include a subset of items in a view or a group of views. Only the part of the views that support the user activity are included in a test of the task flow.

    @@ -1498,7 +1515,7 @@

    Glossary

    User testing
    -

    Evaluation of content by observation of how users with specific functional needs are able to complete a process and how the content meets the relevant requirements.

    +

    Evaluation of content by observation of how users with specific functional needs are able to complete a process and how the content meets the relevant requirements.

    Views
    From a5d5f0cf3f18b83aae390a04e1745364ac8e9283 Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 19 Nov 2024 15:59:35 +0000 Subject: [PATCH 33/49] Update headings and structure for images --- guidelines/index.html | 99 +++++++++++++++++++++++-------------------- 1 file changed, 53 insertions(+), 46 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 29e847c..24a17ac 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -301,66 +301,73 @@
    Steps and instructions
    -
    +

    Image and media alternatives

    Image alternatives

    Users have equivalent alternatives for images.

    -

    Foundational Requirements

    +
    +
    Foundational Requirements
    -

    For each image: -

      -
    1. Would removing the image impact how people understand the page? - -
      2. +

      For each image: +

        +
      1. Would removing the image impact how people understand the page? + +
        2. -
      2. Is the image presented in a way that is available to user agents and assistive technology? - -
        3. +
      3. Is the image presented in a way that is available to user agents and assistive technology? + +
        4. -
      4. Is an equivalent text alternative available for the image? - -
        5. -
      -

      +
    2. Is an equivalent text alternative available for the image? + +
      3. +
    +

    -
    -
    Decorative image
    -

    Decorative image is programmatically hidden.

    -
    -
    -
    Content image
    -

    Equivalent text alternative is available for image that conveys content.

    -
    -
    -
    Detectable image
    -

    Image is programmatically detectable.

    +
    +
    Decorative image
    +

    Decorative image is programmatically hidden.

    +
    +
    +
    Content image
    +

    Equivalent text alternative is available for image that conveys content.

    +
    +
    +
    Detectable image
    +

    Image is programmatically detectable.

    +
    -

    Supplemental Requirements

    -
    -
    Image role
    -

    The role and importance of the image is programmatically indicated.

    -
    -
    -
    Image type
    -

    The type of image (photo, icon, etc.) is indicated.

    -
    -
    -
    Editable Alternatives
    -

    Auto generated text descriptions are editable by content creator.

    -

    Needs additional research

    +
    +
    Supplemental Requirements
    + +
    +
    Image role
    +

    The role and importance of the image is programmatically indicated.

    +
    +
    +
    Image type
    +

    The type of image (photo, icon, etc.) is indicated.

    +
    +
    +
    Editable Alternatives
    +

    Auto generated text descriptions are editable by content creator.

    +

    Needs additional research

    +
    -

    Assertions

    -
    -
    Style Guide
    -

    Text alternatives follow an organizational style guide.

    +
    +
    Assertions
    +
    +
    Style Guide
    +

    Text alternatives follow an organizational style guide.

    +
    From aca28667978b11eacd25a7b2b2bf586f196c5820 Mon Sep 17 00:00:00 2001 From: rmontgomery Date: Tue, 19 Nov 2024 11:01:04 -0500 Subject: [PATCH 34/49] editorial fix --- guidelines/index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 24a17ac..924aed3 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -1020,7 +1020,7 @@
    Implied Meaning

    For each item of non-literal text:

    1. Is the non-literal text presented in a way that is available to user agents, including assistive technology (AT)? -
      2. @@ -1030,7 +1030,7 @@
      Implied Meaning
    2. Does the publisher sufficiently explain the non-literal text or provide a literal alternative? -
    From 280546682a1ba83eb00b0ba22b15f7eb52ef6225 Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 19 Nov 2024 16:12:19 +0000 Subject: [PATCH 35/49] Headings and structure for focus and implied meaning --- guidelines/index.html | 151 ++++++++++++++++++++++++------------------ 1 file changed, 86 insertions(+), 65 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 924aed3..3b96280 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -455,56 +455,62 @@

    Interactive components

    Keyboard Focus Appearance

    Users can see which element has keyboard focus.

    -

    Foundational Requirements

    - -

    For each focusable item: -

      -
    1. Is the user-agent default focus indicator used? - -
      2. +
      +
      Foundational Requirements
      -
    2. Is the user-agent default focus indicator used, and meets contrast across backgrounds? - -
      3. +

      For each focusable item: +

        +
      1. Is the user-agent default focus indicator used? + +
        2. -
      2. Is the focus indicator defined by the author? - -
        3. -
      -

      +
    3. Is the user-agent default focus indicator used, and meets contrast across backgrounds? + +
      4. -
      -
      Custom indicator
      -

      A custom focus indicator is used with sufficient size, change of contrast, adjacent contrast, distinct style and adjacency.

      -
      -
      -
      Default indicator
      -

      The platform’s default indicator is used, and where the backgrounds are changed, the indicator contrast is checked.

      -
      -
      -
      User agent default indicator
      -

      Focusable item uses the user agent default indicator.

      +
    4. Is the focus indicator defined by the author? + +
      5. +
    +

    + +
    +
    Custom indicator
    +

    A custom focus indicator is used with sufficient size, change of contrast, adjacent contrast, distinct style and adjacency.

    +
    +
    +
    Default indicator
    +

    The platform’s default indicator is used, and where the backgrounds are changed, the indicator contrast is checked.

    +
    +
    +
    User agent default indicator
    +

    Focusable item uses the user agent default indicator.

    +
    -

    Supplemental Requirements

    -
    -
    Supplimentary indicators
    -

    @@

    +
    +
    Supplemental Requirements
    +
    +
    Supplimentary indicators
    +

    @@

    +
    - -

    Assertions

    -
    -
    Style Guide
    -

    Focus indicators follow an organizational style guide.

    + +
    +
    Assertions
    +
    +
    Style Guide
    +

    Focus indicators follow an organizational style guide.

    +
    @@ -1016,33 +1022,48 @@
    Double negatives
    Implied Meaning

    Users can access the literal meaning of text.

    -

    Foundational Requirements

    -

    For each item of non-literal text: + +

    +
    Foundational Requirements
    +

    For each item of non-literal text:

      -
    1. Is the non-literal text presented in a way that is available to user agents, including assistive technology (AT)? - +
    2. Is the non-literal text presented in a way that is available to user agents, including assistive technology + (AT)? + +
      3. - -
    3. Does the available user agent, including assistive technology, sufficiently Explain non-literal text or provide a literal alternative? -
      • Yes, pass. Stop.
        • -
      • No, continue.
      + +
    4. Does the available user agent, including assistive technology, sufficiently Explain non-literal text or + provide a literal alternative? +
        +
      • Yes, pass. Stop.
        • +
      • No, continue.
        • +
      5. - -
    5. Does the publisher sufficiently explain the non-literal text or provide a literal alternative? - + +
    6. Does the publisher sufficiently explain the non-literal text or provide a literal alternative? +
    -

    -

    Exceptions

    -
    • If the purpose is to showcase works of art, such as a poetry journal but if the purpose is to educate students about - pieces of art, then the exception would not apply.
    -
    -
    Literal text
    -

    Explain non-literal text or provide a literal alternative

    -
    +

    +

    Exceptions

    +
      +
    • If the purpose is to showcase works of art, such as a poetry journal but if the purpose is to educate students + about + pieces of art, then the exception would not apply.
      • +
    +
    +
    +
    Literal text
    +

    Explain non-literal text or provide a literal alternative

    +
    +
    Sentence voice

    The voice used is easiest to understand in context.

    From 3e2d458ccc2eb8cc7401342892c32e5b6ff6422b Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 19 Nov 2024 16:20:41 +0000 Subject: [PATCH 36/49] Qualify UAAG and ATAG potential inclusions --- guidelines/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guidelines/index.html b/guidelines/index.html index 3b96280..ec43284 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -80,7 +80,7 @@

    Introduction

    About WCAG 3

    This specification presents a new model and guidelines to make web content and applications accessible to people with disabilities. The W3C Accessibility Guidelines (WCAG) 3.0 support a wide set of user needs, use new approaches to testing, and allow frequent maintenance of guidelines and related content to keep pace with accelerating technology change. WCAG 3 supports this evolution by focusing on the functional needs of users. These needs are then supported by guidelines written as outcome statements, requirments, assertions, and technology-specific methods to meet those needs. 

    -

    WCAG 3 is a successor to Web Content Accessibility Guidelines 2.2 [[WCAG22]] and previous versions, but does not deprecate WCAG 2. It will also incorporate content from and partially extend User Agent Accessibility Guidelines 2.0 [[UAAG20]] and Authoring Tool Accessibility Guidelines 2.0 [[ATAG20]]. These earlier versions provided a flexible model that kept them relevant for over 15 years. However, changing technology and changing needs of people with disabilities have led to the need for a new model to address content accessibility more comprehensively and flexibly.

    +

    WCAG 3 is a successor to Web Content Accessibility Guidelines 2.2 [[WCAG22]] and previous versions, but does not deprecate WCAG 2. It will also incorporate some content from and partially extend User Agent Accessibility Guidelines 2.0 [[UAAG20]] and Authoring Tool Accessibility Guidelines 2.0 [[ATAG20]]. These earlier versions provided a flexible model that kept them relevant for over 15 years. However, changing technology and changing needs of people with disabilities have led to the need for a new model to address content accessibility more comprehensively and flexibly.

    There are many differences between WCAG 2 and WCAG 3. The WCAG 3 guidelines address accessibility of web content on desktops, laptops, tablets, mobile devices, wearable devices, and other web of things devices. The guidelines apply to various types of web content including static, dynamic, interactive, and streaming content; visual and auditory media; virtual and augmented reality; and alternative access presentation and control. These guidelines also address related web tools such as user agents (browsers and assistive technologies), content management systems, authoring tools, and testing tools.

    Each guideline in this standard provides information on accessibility practices that address documented user needs of people with disabilities. Guidelines are supported by multiple requirements to determine whether the need has been met. Guidelines are also supported by technology-specific methods to meet each requirement.

    Content that conforms to WCAG 2.2 A and AA is expected to meet most of the minimum conformance level of this new standard but, since WCAG 3 includes additional tests and different scoring mechanics, additional work will be needed to reach full conformance. Since the new standard will use a different conformance model, the Accessibility Guidelines Working Group expects that some organizations may wish to continue using WCAG 2, while others may wish to migrate to the new standard. For those that wish to migrate to the new standard, the Working Group will provide transition support materials, which may use mapping and other approaches to facilitate migration.

    From 12aef7485858f8479cfd138e95b3e6f04f345170 Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 19 Nov 2024 17:02:31 +0000 Subject: [PATCH 37/49] Allow for status in definitions and put some in --- guidelines/guidelines.js | 21 +++++++++++++++------ guidelines/index.html | 26 +++++++++++++------------- 2 files changed, 28 insertions(+), 19 deletions(-) diff --git a/guidelines/guidelines.js b/guidelines/guidelines.js index d64d770..4fb8613 100644 --- a/guidelines/guidelines.js +++ b/guidelines/guidelines.js @@ -141,13 +141,22 @@ var statusLabels = { function addStatusMarkers() { var statusKeys = Object.keys(statusLabels); statusKeys.forEach(function (status) { - var selector = '[data-status="' + status + '"] > .header-wrapper'; - var headings = document.querySelectorAll(selector); + var headingSelector = '[data-status="' + status + '"] > .header-wrapper'; + var headings = document.querySelectorAll(headingSelector); headings.forEach(function (heading) { - var statusMarker = document.createElement("span"); - statusMarker.classList.add("status-marker"); - statusMarker.innerHTML = sentenceCase(status); - heading.firstElementChild.insertAdjacentElement('beforeend', statusMarker); + var statusMarker = document.createElement("span"); + statusMarker.classList.add("status-marker"); + statusMarker.innerHTML = sentenceCase(status); + heading.firstElementChild.insertAdjacentElement('beforeend', statusMarker); + }); + + var dfnSelector = '[data-status="' + status + '"] > dfn'; + var dfns = document.querySelectorAll(dfnSelector); + dfns.forEach(function (dfn) { + var statusMarker = document.createElement("span"); + statusMarker.classList.add("status-marker"); + statusMarker.innerHTML = sentenceCase(status); + dfn.insertAdjacentElement('beforeend', statusMarker); }) }); } diff --git a/guidelines/index.html b/guidelines/index.html index ec43284..42e0225 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -1375,7 +1375,7 @@

    Glossary

    This glossary includes terms used by content that has reached a maturity level of Developing or higher. The definitions themselves include a maturity level and may mature at a differet pace than the content that refers to them. The AGWG will work with other taskforces and groups to harmonize terminology across documents as much as is possible.

    -
    Assertion
    +
    Assertion

    A formal claim of fact, attributed to a person or organization. An attributable and documented statement of fact regarding procedures practiced in the development and maintenance of the content or product to improve accessibility.

    Automated evaluation
    @@ -1385,7 +1385,7 @@

    Glossary

    experience. [=Semi-automated evaluation=] allows machines to guide humans to areas that need inspection. The emerging field of testing conducted via machine learning is not included in this definition.

    -
    Conformance
    +
    Conformance

    Satisfying all the requirements of the guidelines. Conformance is an important part of following the guidelines even when not making a formal Conformance Claim.

    See Conformance.

    @@ -1408,7 +1408,7 @@

    Glossary

    To be defined.

    -
    Deprecate
    +
    Deprecate

    To declare something outdated and in the process of being phased out, usually in favor of a specified replacement.

    Deprecated documents are no longer recommended for use and may cease to exist in the future.

    @@ -1424,11 +1424,11 @@

    Glossary

    The process of examining content for conformance to these guidelines.

    Different approaches to evaluation include automated evaluation, semi-automated evaluation, human evaluation, and user testing.

    -
    Functional need
    +
    Functional need

    A statement that describes a specific gap in one’s ability, or a specific mismatch between ability and the designed environment or context.

    -
    Guideline
    +
    Guideline

    High-level, plain-language outcome statements used to organize requirements.

    Guidelines provide a high-level, plain-language outcome statements for managers, policy makers, individuals who are new to accessibility, and other individuals who need to understand the concepts but not dive into the technical details. They provide an easy-to-understand way of organizing and presenting the requirements so that non-experts can learn about and understand the concepts. Each guideline includes a unique, descriptive name along with a high-level plain-language summary. Guidelines address functional needs on specific topics, such as contrast, forms, readability, and more. Guidelines group related requirements and are technology-independent.

    @@ -1456,7 +1456,7 @@

    Glossary

    To be defined.

    -
    Informative
    +
    Informative

    Content provided for information purposes and not required for conformance.

    @@ -1467,11 +1467,11 @@

    Glossary

    -
    Items
    +
    Items

    The smallest testable unit for testing scope. They could be interactive components such as a drop down menu, a link, or a media player. They could also be units of content such as a phrase, a paragraph, a label or error message, an icon, or an image.

    -
    Method
    +
    Method

    Detailed information, either technology-specific or technology-agnostic, on ways to meet the requirement as well as tests and scoring information.

    @@ -1480,7 +1480,7 @@

    Glossary

    Non-literal text uses words or phrases in a way that goes beyond their standard or dictionary meaning to express deeper, more complex ideas. This is also called figurative language. To understand it, users have to interpret the implied meaning behind the words, rather than just their literal or direct meaning.

    Examples: Allusions, hyperbole, idioms, irony, jokes, litotes, metaphors, metonymies, onomatopoeias, oxymorons, personification, puns, sarcasm, and similes. More detailed examples are available in the Methods section.

    -
    Normative
    +
    Normative

    Content whose instructions are required for conformance.

    @@ -1498,7 +1498,7 @@

    Glossary

    A sequence of steps that need to be completed to accomplish an activity / task from end-to-end.

    -
    Product
    +
    Product

    Testing scope that is a combination of all items, views, and task flows that comprise the web site, set of web pages, web app, etc.

    @@ -1523,11 +1523,11 @@

    Glossary

    To be defined.

    -
    Task flow
    +
    Task flow

    Testing scope that includes a series views that support a specified user activity. A task flow may include a subset of items in a view or a group of views. Only the part of the views that support the user activity are included in a test of the task flow.

    -
    Test
    +
    Test

    Mechanism to evaluate implementation of a method.

    @@ -1545,7 +1545,7 @@

    Glossary

    Evaluation of content by observation of how users with specific functional needs are able to complete a process and how the content meets the relevant requirements.

    -
    Views
    +
    View

    Testing scope that includes all content visually and programmatically available without a significant change. Conceptually, views correspond to the definition of a web page as used in WCAG 2, but are not restricted to content meeting that definition. For example, a view could be considered a “screen” in a mobile app or a layer of web content, such as a modal dialog.

    From f7b5e23971120105fbc1ba08442c83081f933f3f Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 19 Nov 2024 17:05:16 +0000 Subject: [PATCH 38/49] Mark developing definitions --- guidelines/index.html | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 42e0225..8cdb8d6 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -1375,7 +1375,7 @@

    Glossary

    This glossary includes terms used by content that has reached a maturity level of Developing or higher. The definitions themselves include a maturity level and may mature at a differet pace than the content that refers to them. The AGWG will work with other taskforces and groups to harmonize terminology across documents as much as is possible.

    -
    Assertion
    +
    Assertion

    A formal claim of fact, attributed to a person or organization. An attributable and documented statement of fact regarding procedures practiced in the development and maintenance of the content or product to improve accessibility.

    Automated evaluation
    @@ -1385,7 +1385,7 @@

    Glossary

    experience. [=Semi-automated evaluation=] allows machines to guide humans to areas that need inspection. The emerging field of testing conducted via machine learning is not included in this definition.

    -
    Conformance
    +
    Conformance

    Satisfying all the requirements of the guidelines. Conformance is an important part of following the guidelines even when not making a formal Conformance Claim.

    See Conformance.

    @@ -1408,7 +1408,7 @@

    Glossary

    To be defined.

    -
    Deprecate
    +
    Deprecate

    To declare something outdated and in the process of being phased out, usually in favor of a specified replacement.

    Deprecated documents are no longer recommended for use and may cease to exist in the future.

    @@ -1424,11 +1424,11 @@

    Glossary

    The process of examining content for conformance to these guidelines.

    Different approaches to evaluation include automated evaluation, semi-automated evaluation, human evaluation, and user testing.

    -
    Functional need
    +
    Functional need

    A statement that describes a specific gap in one’s ability, or a specific mismatch between ability and the designed environment or context.

    -
    Guideline
    +
    Guideline

    High-level, plain-language outcome statements used to organize requirements.

    Guidelines provide a high-level, plain-language outcome statements for managers, policy makers, individuals who are new to accessibility, and other individuals who need to understand the concepts but not dive into the technical details. They provide an easy-to-understand way of organizing and presenting the requirements so that non-experts can learn about and understand the concepts. Each guideline includes a unique, descriptive name along with a high-level plain-language summary. Guidelines address functional needs on specific topics, such as contrast, forms, readability, and more. Guidelines group related requirements and are technology-independent.

    @@ -1456,7 +1456,7 @@

    Glossary

    To be defined.

    -
    Informative
    +
    Informative

    Content provided for information purposes and not required for conformance.

    @@ -1467,11 +1467,11 @@

    Glossary

    -
    Items
    +
    Items

    The smallest testable unit for testing scope. They could be interactive components such as a drop down menu, a link, or a media player. They could also be units of content such as a phrase, a paragraph, a label or error message, an icon, or an image.

    -
    Method
    +
    Method

    Detailed information, either technology-specific or technology-agnostic, on ways to meet the requirement as well as tests and scoring information.

    @@ -1480,7 +1480,7 @@

    Glossary

    Non-literal text uses words or phrases in a way that goes beyond their standard or dictionary meaning to express deeper, more complex ideas. This is also called figurative language. To understand it, users have to interpret the implied meaning behind the words, rather than just their literal or direct meaning.

    Examples: Allusions, hyperbole, idioms, irony, jokes, litotes, metaphors, metonymies, onomatopoeias, oxymorons, personification, puns, sarcasm, and similes. More detailed examples are available in the Methods section.

    -
    Normative
    +
    Normative

    Content whose instructions are required for conformance.

    @@ -1498,7 +1498,7 @@

    Glossary

    A sequence of steps that need to be completed to accomplish an activity / task from end-to-end.

    -
    Product
    +
    Product

    Testing scope that is a combination of all items, views, and task flows that comprise the web site, set of web pages, web app, etc.

    @@ -1523,11 +1523,11 @@

    Glossary

    To be defined.

    -
    Task flow
    +
    Task flow

    Testing scope that includes a series views that support a specified user activity. A task flow may include a subset of items in a view or a group of views. Only the part of the views that support the user activity are included in a test of the task flow.

    -
    Test
    +
    Test

    Mechanism to evaluate implementation of a method.

    @@ -1545,7 +1545,7 @@

    Glossary

    Evaluation of content by observation of how users with specific functional needs are able to complete a process and how the content meets the relevant requirements.

    -
    View
    +
    View

    Testing scope that includes all content visually and programmatically available without a significant change. Conceptually, views correspond to the definition of a web page as used in WCAG 2, but are not restricted to content meeting that definition. For example, a view could be considered a “screen” in a mobile app or a layer of web content, such as a modal dialog.

    From 29d0cbb23ce8a8d7e964a77a1d3689cd3e47f35b Mon Sep 17 00:00:00 2001 From: rmontgomery Date: Tue, 19 Nov 2024 12:28:36 -0500 Subject: [PATCH 39/49] Editorial fixes from meeting --- .../current-contributors.html | 40 ++++++------- guidelines/index.html | 56 +++++++++---------- 2 files changed, 48 insertions(+), 48 deletions(-) diff --git a/guidelines/acknowledgements/current-contributors.html b/guidelines/acknowledgements/current-contributors.html index 9269bb7..ff26e0c 100644 --- a/guidelines/acknowledgements/current-contributors.html +++ b/guidelines/acknowledgements/current-contributors.html @@ -20,53 +20,53 @@

    Contributors to the development of this document

  • Gez Lemon (TetraLogical Services Ltd)
  • Giacomo Petri (UsableNet)
  • Glenda Sims (Deque Systems, Inc.)
    • -
  • Graham Ritchie (Invited Experts)
    • -
  • Gregg Vanderheiden (Invited Experts)
    • +
  • Graham Ritchie (Invited Expert)
    • +
  • Gregg Vanderheiden (Invited Expert)
  • Gundula Niemann (SAP SE)
  • Hidde de Vries (Logius)
  • JaEun Jemma Ku (University of Illinois)
    • -
  • Jake Abma (Invited Experts)
    • -
  • Jan Jaap de Groot (Invited Experts)
    • -
  • Jan McSorley (Invited Experts)
    • -
  • Janina Sajka (Invited Experts)
    • +
  • Jake Abma (Invited Expert)
    • +
  • Jan Jaap de Groot (Invited Expert)
    • +
  • Jan McSorley (Invited Expert)
    • +
  • Janina Sajka (Invited Expert)
  • Jaunita George (Navy Federal Credit Union)
  • Jeanne Spellman (TetraLogical Services Ltd)
    • -
  • Jennifer Delisi (Invited Experts)
    • +
  • Jennifer Delisi (Invited Expert)
  • Jennifer Strickland (MITRE Corporation)
    • -
  • John Kirkwood (Invited Experts)
    • -
  • John Rochford (Invited Experts)
    • +
  • John Kirkwood (Invited Expert)
    • +
  • John Rochford (Invited Expert)
  • John Toles (Rhonda Weiss Center for Accessible IDEA Data)
  • Jon Avila (Level Access)
  • Julie Rawe (Understood)
  • Kimberly McGee (SAP SE)
    • -
  • Laura Carlson (Invited Experts)
    • +
  • Laura Carlson (Invited Expert)
  • Len Beasley (CVS Pharmacy, Inc.)
  • Léonie Watson (TetraLogical Services Ltd)
    • -
  • Lisa Seeman-Kestenbaum (Invited Experts)
    • +
  • Lisa Seeman-Kestenbaum (Invited Expert)
  • Lori Oakley (Oracle Corporation)
    • -
  • Makoto Ueki (Invited Experts)
    • +
  • Makoto Ueki (Invited Expert)
  • Mary Ann Jawili (Adobe)
  • Mary Jo Mueller (IBM Corporation)
  • Matt Garrish (DAISY Consortium)
  • Melanie Philipp (Deque Systems, Inc.)
    • -
  • Mike Beganyi (Invited Experts)
    • +
  • Mike Beganyi (Invited Expert)
  • Mike Gower (IBM Corporation)
  • Nina Krauß (SAP SE)
  • Patrick Lauke (TetraLogical Services Ltd)
    • -
  • Poornima Badhan Subramanian (Invited Experts)
    • +
  • Poornima Badhan Subramanian (Invited Expert)
  • Rachael Bradley Montgomery (Library of Congress)
  • Rain Breaw Michaels (Google LLC)
    • -
  • Roberto Scano (Invited Experts)
    • -
  • Sarah Horton (Invited Experts)
    • +
  • Roberto Scano (Invited Expert)
    • +
  • Sarah Horton (Invited Expert)
  • Scott O'Hara (Microsoft Corporation)
  • Shadi Abou-Zahra (Amazon)
    • -
  • Shawn Thompson (Invited Experts)
    • -
  • Sheri Byrne-Haber (Invited Experts)
    • +
  • Shawn Thompson (Invited Expert)
    • +
  • Sheri Byrne-Haber (Invited Expert)
  • Steve Faulkner (TetraLogical Services Ltd)
  • Tananda Darling (SAP SE)
  • Theo Hale (Microsoft Corporation)
    • -
  • Tiffany Burtin (Invited Experts)
    • -
  • Todd Libby (Invited Experts)
    • +
  • Tiffany Burtin (Invited Expert)
    • +
  • Todd Libby (Invited Expert)
  • Wendy Reid (Rakuten Group, Inc.)
  • Wilco Fiers (Deque Systems, Inc.)
    • diff --git a/guidelines/index.html b/guidelines/index.html index 8cdb8d6..553789e 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -13,7 +13,7 @@

    W3C Accessibility Guidelines (WCAG) 3.0 will provide a wide range of recommendations for making web content more accessible to users with disabilities. Following these guidelines will address many of the needs of users with blindness, low vision and other vision impairments; deafness and hearing loss; limited movement and dexterity; speech disabilities; sensory disorders; cognitive and learning disabilities; and combinations of these. These guidelines address accessibility of web content on desktops, laptops, tablets, mobile devices, wearable devices, and other web of things devices. The guidelines apply to various types of web content including static, dynamic, interactive, and streaming content; visual and auditory media; virtual and augmented reality; and alternative access presentation and control. These guidelines also address related web tools such as user agents (browsers and assistive technologies), content management systems, authoring tools, and testing tools.

    Each guideline in this standard provides information on accessibility practices that address documented user needs of people with disabilities. Guidelines are supported by multiple requirements and assertions to determine whether the need has been met. Guidelines are also supported by technology-specific methods to meet each requirement or assertion.

    This specification is expected to be updated regularly to keep pace with changing technology by updating and adding methods, requirements, and guidelines to address new needs as technologies evolve. For entities that make formal claims of conformance to these guidelines, several levels of conformance are available to address the diverse nature of digital content and the type of testing that is performed.

    -

    See WCAG 3 Introduction for an introduction and links to WCAG technical and educational material.

    +

    See WCAG 3.0 Introduction for an introduction and links to WCAG technical and educational material.

    This is an update to the W3C Accessibility Guidelines (WCAG) 3.0. It includes a restructuring of the guidelines and first draft decision trees for three Guidelines: Image alternatives, Keyboard Focus Appearance and Implied meaning.

    @@ -25,8 +25,8 @@

    Introduction

    Summary
    • W3C Accessibility Guidelines (WCAG) 3.0 shows ways to make web content and apps usable by people with - disabilities. WCAG 3 is a newer standard than the Web Content Accessibility Guidelines (WCAG) 2.
      • -
    • WCAG 3 doesn’t replace WCAG 2. WCAG 2 is used around the world and will still be required by different + disabilities. WCAG 3.0 is a newer standard than the Web Content Accessibility Guidelines (WCAG) 2.
      • +
    • WCAG 3.0 doesn’t replace WCAG 2. WCAG 2 is used around the world and will still be required by different countries for a long time to come.
    • Meeting WCAG 2 at AA level means you will be close to meeting WCAG 3.0, but there may be differences.
    • We have developed labels for sections to tell you how confident we are that the content will not change. @@ -43,12 +43,12 @@

      Introduction

    -

    What’s new in this version of WCAG 3?

    +

    What’s new in this version of WCAG 3.0?

    This draft includes an updated list of the potential Guidelines and Requirements which we are exploring. The list of Requirements is longer than the list of Success Criteria in WCAG 2.2. This is because:

    • the intent at this stage is to be as inclusive as possible of potential Requirements, and
      • -
    • WCAG 3 Requirements are more granular than WCAG 2 Success Criteria.
    - The final set of Requirements in WCAG 3 will be different than what is in this draft. Requirements will be added, combined, and removed. +
  • WCAG 3.0 Requirements are more granular than WCAG 2 Success Criteria.
    • + The final set of Requirements in WCAG 3.0 will be different than what is in this draft. Requirements will be added, combined, and removed. We also expect changes to the text of the Requirements. Only some of the Requirements will be used to meet the base level of conformance.

    The Requirements are grouped into the following sections:

    @@ -72,23 +72,23 @@

    Introduction

  • What research supports or refutes the requirements marked as needing additional research?
  • Three guidelines (Image alternatives, Keyboard Focus Appearance and Implied Meaning) have moved from exploratory to developing and demonstrate a potential structure. Does grouping related requirements and assertions together and using a decision tree for foundational requirements make the guidelines easier to understand and use?
    • -
  • The conformance section explains the approach the Accessibilty Guidelines Working Group is considering for WCAG 3. While many details still need to be worked out, do you have constructive comments about the proposed approach for WCAG 3?
    • +
  • The conformance section explains the approach the Accessibilty Guidelines Working Group is considering for WCAG 3.0. While many details still need to be worked out, do you have constructive comments about the proposed approach for WCAG 3.0?

    • To provide feedback, please file a GitHub issue or send email to public-agwg-comments@w3.org (comment archive).

    -

    About WCAG 3

    -

    This specification presents a new model and guidelines to make web content and applications accessible to people with disabilities. The W3C Accessibility Guidelines (WCAG) 3.0 support a wide set of user needs, use new approaches to testing, and allow frequent maintenance of guidelines and related content to keep pace with accelerating technology change. WCAG 3 supports this evolution by focusing on the functional needs of users. These needs are then supported by guidelines written as outcome statements, requirments, assertions, and technology-specific methods to meet those needs. 

    -

    WCAG 3 is a successor to Web Content Accessibility Guidelines 2.2 [[WCAG22]] and previous versions, but does not deprecate WCAG 2. It will also incorporate some content from and partially extend User Agent Accessibility Guidelines 2.0 [[UAAG20]] and Authoring Tool Accessibility Guidelines 2.0 [[ATAG20]]. These earlier versions provided a flexible model that kept them relevant for over 15 years. However, changing technology and changing needs of people with disabilities have led to the need for a new model to address content accessibility more comprehensively and flexibly.

    -

    There are many differences between WCAG 2 and WCAG 3. The WCAG 3 guidelines address accessibility of web content on desktops, laptops, tablets, mobile devices, wearable devices, and other web of things devices. The guidelines apply to various types of web content including static, dynamic, interactive, and streaming content; visual and auditory media; virtual and augmented reality; and alternative access presentation and control. These guidelines also address related web tools such as user agents (browsers and assistive technologies), content management systems, authoring tools, and testing tools.

    +

    About WCAG 3.0

    +

    This specification presents a new model and guidelines to make web content and applications accessible to people with disabilities. The W3C Accessibility Guidelines (WCAG) 3.0 support a wide set of user needs, use new approaches to testing, and allow frequent maintenance of guidelines and related content to keep pace with accelerating technology change. WCAG 3.0 supports this evolution by focusing on the functional needs of users. These needs are then supported by guidelines written as outcome statements, requirments, assertions, and technology-specific methods to meet those needs. 

    +

    WCAG 3.0 is a successor to Web Content Accessibility Guidelines 2.2 [[WCAG22]] and previous versions, but does not deprecate WCAG 2. It will also incorporate some content from and partially extend User Agent Accessibility Guidelines 2.0 [[UAAG20]] and Authoring Tool Accessibility Guidelines 2.0 [[ATAG20]]. These earlier versions provided a flexible model that kept them relevant for over 15 years. However, changing technology and changing needs of people with disabilities have led to the need for a new model to address content accessibility more comprehensively and flexibly.

    +

    There are many differences between WCAG 2 and WCAG 3.0. The WCAG 3.0 guidelines address accessibility of web content on desktops, laptops, tablets, mobile devices, wearable devices, and other web of things devices. The guidelines apply to various types of web content including static, dynamic, interactive, and streaming content; visual and auditory media; virtual and augmented reality; and alternative access presentation and control. These guidelines also address related web tools such as user agents (browsers and assistive technologies), content management systems, authoring tools, and testing tools.

    Each guideline in this standard provides information on accessibility practices that address documented user needs of people with disabilities. Guidelines are supported by multiple requirements to determine whether the need has been met. Guidelines are also supported by technology-specific methods to meet each requirement.

    -

    Content that conforms to WCAG 2.2 A and AA is expected to meet most of the minimum conformance level of this new standard but, since WCAG 3 includes additional tests and different scoring mechanics, additional work will be needed to reach full conformance. Since the new standard will use a different conformance model, the Accessibility Guidelines Working Group expects that some organizations may wish to continue using WCAG 2, while others may wish to migrate to the new standard. For those that wish to migrate to the new standard, the Working Group will provide transition support materials, which may use mapping and other approaches to facilitate migration.

    +

    Content that conforms to WCAG 2.2 A and AA is expected to meet most of the minimum conformance level of this new standard but, since WCAG 3.0 includes additional tests and different scoring mechanics, additional work will be needed to reach full conformance. Since the new standard will use a different conformance model, the Accessibility Guidelines Working Group expects that some organizations may wish to continue using WCAG 2, while others may wish to migrate to the new standard. For those that wish to migrate to the new standard, the Working Group will provide transition support materials, which may use mapping and other approaches to facilitate migration.

    Section status levels

    -

    As part of the WCAG 3 drafting process each normative section of this document is given a status. This status is used to indicate how far along in the development this section is, how ready it is for experimental adoption, and what kind of feedback the Accessibility Guidelines Working Group is looking for.

    +

    As part of the WCAG 3.0 drafting process each normative section of this document is given a status. This status is used to indicate how far along in the development this section is, how ready it is for experimental adoption, and what kind of feedback the Accessibility Guidelines Working Group is looking for.

    • Placeholder: This content is temporary. It showcases the type of content or section to expect here. All of this is expected to be replaced. No feedback is needed on placeholder content.
    • Exploratory: The Working Group is exploring what direction to take with this section. This content is not refined, details and definitions may be missing. Feedback should be about the proposed direction.
      • @@ -106,7 +106,7 @@

      Section status levels

      Guidelines

      Summary -

      The following guidelines are being considered for WCAG 3. They are currently a list of topics which we expect to explore more thoroughly in future drafts. The list includes current WCAG 2 guidance and additional requirements. The list will change in future drafts.

      +

      The following guidelines are being considered for WCAG 3.0. They are currently a list of topics which we expect to explore more thoroughly in future drafts. The list includes current WCAG 2 guidance and additional requirements. The list will change in future drafts.

      Unless otherwise stated, requirements assume the content described is provided both visually and programmatically.

      @@ -114,7 +114,7 @@

      Guidelines

      The individuals and organizations that use WCAG vary widely and include web designers and developers, policy makers, purchasing agents, teachers, and students. To meet the varying needs of this audience, several layers of guidance will be provided including guidelines written as outcome statements, requirements that can be tested, assertions, a rich collection of methods, resource links, and code samples.

      -

      The following list is an initial set of potential guidelines and requirements that the Working Group will be exploring. The goal is to guide the next phase of work. They should be considered drafts and should not be considered as final content of WCAG 3.

      +

      The following list is an initial set of potential guidelines and requirements that the Working Group will be exploring. The goal is to guide the next phase of work. They should be considered drafts and should not be considered as final content of WCAG 3.0.

      Ordinarily, exploratory content includes editor's notes listing concerns and questions for each item. Because this Guidelines section is very early in the process of working on WCAG 3.0, this editor's note covers most of the content in this section. Unless otherwise noted, all items in the list as exploratory at this point. It is a list of all possible topics for consideration. Not all items listed will be included in the final version of WCAG 3.0.

      @@ -1312,14 +1312,14 @@
      Virtual cursor

      Conformance

      Summary -

      You might want to make a claim that your content or product meets the WCAG 3 guidelines. If it does meet the guidelines, we call this “conformance”.

      -

      If you want to make a formal conformance claim, you must use the process described in this document. Conformance claims are not required and your content can conform to WCAG 3, even if you don’t want to make a claim.

      +

      You might want to make a claim that your content or product meets the WCAG 3.0 guidelines. If it does meet the guidelines, we call this “conformance”.

      +

      If you want to make a formal conformance claim, you must use the process described in this document. Conformance claims are not required and your content can conform to WCAG 3.0, even if you don’t want to make a claim.

      There are two types of content in this document:

      • Normative: what you must do to meet the guidelines.
      • Non-normative: advice to help you meet the guidelines. This is also called informative.
      -

      We are experimenting with different conformance approaches for WCAG 3. Once we have developed enough guidelines, we will test how well each works.

      +

      We are experimenting with different conformance approaches for WCAG 3.0. Once we have developed enough guidelines, we will test how well each works.

      WCAG 3.0 will use a different conformance model than WCAG 2.2 in order to meet its requirements. Developing and vetting the conformance model is a large portion of the work AG needs to complete over the next few years. Drafts will include maturity models for public review and comment.

      @@ -1341,13 +1341,13 @@

      Only accessibility-supported ways of using technologies

      The intent is for the responsibility of testing with user-agents to vary depending on the level of conformance.

      -

      At the foundational level of conformance assumptions can be made by authors that methods and techniques provided by WCAG 3 work. At higher levels of conformance the author may need to test that a technique works, or check that available user-agents meet the requirement, or a combination of both.

      +

      At the foundational level of conformance assumptions can be made by authors that methods and techniques provided by WCAG 3.0 work. At higher levels of conformance the author may need to test that a technique works, or check that available user-agents meet the requirement, or a combination of both.

      This approach means the Working Group will ensure that methods and techniques included do have reasonably wide and international support from user-agents, and there are sufficient techniques to meet each requirement.

      -

      The intent is that WCAG 3 will use a content-management-system to support tagging of methods/techniques with support information. There should also be a process where interested parties can provide information.

      +

      The intent is that WCAG 3.0 will use a content-management-system to support tagging of methods/techniques with support information. There should also be a process where interested parties can provide information.

      -

      An "accessibility support set" is used at higher levels of conformance to define which user-agents and assistive technologies you test with. It would be included in a conformance claim, and enables authors to use techniques that are not provided with WCAG 3.

      +

      An "accessibility support set" is used at higher levels of conformance to define which user-agents and assistive technologies you test with. It would be included in a conformance claim, and enables authors to use techniques that are not provided with WCAG 3.0.

      An exception for long-present bugs in assistive technology is still under discussion.

      @@ -1355,17 +1355,17 @@

      Only accessibility-supported ways of using technologies

      Defining conformance scope

      -

      When evaluating the accessibility of content, WCAG 3 requires the guidelines apply to a specific scope. While the scope can be an all content within a digital product, it is usually one or more sub-sets of the whole. Reasons for this include:

      +

      When evaluating the accessibility of content, WCAG 3.0 requires the guidelines apply to a specific scope. While the scope can be an all content within a digital product, it is usually one or more sub-sets of the whole. Reasons for this include:

      • Large amounts of content are impractical to evaluate comprehensively using anything beyond automated evaluation of items;
      • In many cases, content changes frequently, causing evaluation to be accurate only for a specific moment in time;
      • Some content is more important to the majority of users than other content; and
      • Content that mostly meets the requirements but has problems can interfere with the user’s ability to complete a process.
      -

      WCAG 3 therefore defines two ways to scope content: views and processes. Evaluation is done on one or more complete views or processes, and conformance is determined on the basis of one or more complete views or processes.

      +

      WCAG 3.0 therefore defines two ways to scope content: views and processes. Evaluation is done on one or more complete views or processes, and conformance is determined on the basis of one or more complete views or processes.

      Conformance is defined only for processes and views. However, a conformance claim may be made to cover one process and view, a series of processes and views, or multiple related processes and views. All unique steps in a process MUST be represented in the set of views. Views outside of the process MAY also be included in the scope.

      -

      We recognize that representative sampling is an important strategy that large and complex sites use to assess accessibility. While it is not addressed within this document at this time, our intent is to later address it within this document or in a separate document before the guidelines reach the Candidate Recommendation stage. We welcome your suggestions and feedback about the best way to incorporate representative sampling in WCAG 3.

      +

      We recognize that representative sampling is an important strategy that large and complex sites use to assess accessibility. While it is not addressed within this document at this time, our intent is to later address it within this document or in a separate document before the guidelines reach the Candidate Recommendation stage. We welcome your suggestions and feedback about the best way to incorporate representative sampling in WCAG 3.0.

    @@ -1567,9 +1567,9 @@

    Security Considerations

    Change log

    -

    This section shows substantive changes made in WCAG 3 since the First Public Working Draft was published in 21 January 2021 . +

    This section shows substantive changes made in WCAG 3.0 since the First Public Working Draft was published in 21 January 2021 . -

    The full commit history to WCAG 3 and commit history to Silver is available. +

    The full commit history to WCAG 3.0 and commit history to Silver is available.

      @@ -1577,12 +1577,12 @@

      Change log

    • 2021-12-07: Add Project Manager
      • -
    • 2023-07-24: Changed approach to WCAG 3 based feedback and removed old material that was not consistent with the new appraoch. Added WCAG 3 Guideline placeholders to indicate maturity level. +
    • 2023-07-24: Changed approach to WCAG 3.0 based feedback and removed old material that was not consistent with the new appraoch. Added WCAG 3.0 Guideline placeholders to indicate maturity level.
    • 2024-03-15: Updated placeholder guidelines with exploratory guidelines.
    • 2024-??-??: Updated placeholder guidelines; added 3 developing guidelines and accessibility supported; and - moved explanatory content to the Explainer for WCAG 3.0r + moved explanatory content to the Explainer for WCAG 3.0
    From 1201f68036ea20e3d4edc20f44a33fa461d7af72 Mon Sep 17 00:00:00 2001 From: rmontgomery Date: Tue, 19 Nov 2024 12:50:55 -0500 Subject: [PATCH 40/49] fixes to spelling errors --- guidelines/index.html | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 553789e..4b3a281 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -72,14 +72,14 @@

    Introduction

  • What research supports or refutes the requirements marked as needing additional research?
  • Three guidelines (Image alternatives, Keyboard Focus Appearance and Implied Meaning) have moved from exploratory to developing and demonstrate a potential structure. Does grouping related requirements and assertions together and using a decision tree for foundational requirements make the guidelines easier to understand and use?
    • -
  • The conformance section explains the approach the Accessibilty Guidelines Working Group is considering for WCAG 3.0. While many details still need to be worked out, do you have constructive comments about the proposed approach for WCAG 3.0?
    • +
  • The conformance section explains the approach the Accessibility Guidelines Working Group is considering for WCAG 3.0. While many details still need to be worked out, do you have constructive comments about the proposed approach for WCAG 3.0?

    • To provide feedback, please file a GitHub issue or send email to public-agwg-comments@w3.org (comment archive).

    About WCAG 3.0

    -

    This specification presents a new model and guidelines to make web content and applications accessible to people with disabilities. The W3C Accessibility Guidelines (WCAG) 3.0 support a wide set of user needs, use new approaches to testing, and allow frequent maintenance of guidelines and related content to keep pace with accelerating technology change. WCAG 3.0 supports this evolution by focusing on the functional needs of users. These needs are then supported by guidelines written as outcome statements, requirments, assertions, and technology-specific methods to meet those needs. 

    +

    This specification presents a new model and guidelines to make web content and applications accessible to people with disabilities. The W3C Accessibility Guidelines (WCAG) 3.0 support a wide set of user needs, use new approaches to testing, and allow frequent maintenance of guidelines and related content to keep pace with accelerating technology change. WCAG 3.0 supports this evolution by focusing on the functional needs of users. These needs are then supported by guidelines written as outcome statements, requirements, assertions, and technology-specific methods to meet those needs. 

    WCAG 3.0 is a successor to Web Content Accessibility Guidelines 2.2 [[WCAG22]] and previous versions, but does not deprecate WCAG 2. It will also incorporate some content from and partially extend User Agent Accessibility Guidelines 2.0 [[UAAG20]] and Authoring Tool Accessibility Guidelines 2.0 [[ATAG20]]. These earlier versions provided a flexible model that kept them relevant for over 15 years. However, changing technology and changing needs of people with disabilities have led to the need for a new model to address content accessibility more comprehensively and flexibly.

    There are many differences between WCAG 2 and WCAG 3.0. The WCAG 3.0 guidelines address accessibility of web content on desktops, laptops, tablets, mobile devices, wearable devices, and other web of things devices. The guidelines apply to various types of web content including static, dynamic, interactive, and streaming content; visual and auditory media; virtual and augmented reality; and alternative access presentation and control. These guidelines also address related web tools such as user agents (browsers and assistive technologies), content management systems, authoring tools, and testing tools.

    Each guideline in this standard provides information on accessibility practices that address documented user needs of people with disabilities. Guidelines are supported by multiple requirements to determine whether the need has been met. Guidelines are also supported by technology-specific methods to meet each requirement.

    @@ -93,7 +93,7 @@

    Section status levels

  • Placeholder: This content is temporary. It showcases the type of content or section to expect here. All of this is expected to be replaced. No feedback is needed on placeholder content.
  • Exploratory: The Working Group is exploring what direction to take with this section. This content is not refined, details and definitions may be missing. Feedback should be about the proposed direction.
  • Developing: There is rough agreement on what is needed for this section, although not all high-level concerns have been settled. Details have been filled, but are yet to be worked out. Feedback should be focused on ensuring the sections are usable and reasonable in a broad sense.
    • -
  • Refining: The Working Group has reach consensus on this section. It is ready for broad public review and experimental adoption. Feedback should be focused on the feasibility and implementability.
    • +
  • Refining: The Working Group has reach consensus on this section. It is ready for broad public review and experimental adoption. Feedback should be focused on the feasibility of implementation.
  • Mature: Content is believed by the Working Group to be ready for recommendation. Feedback should be focused on edge case scenarios the Working Group may not have anticipated.
    • @@ -147,7 +147,7 @@
    Motion

    Needs additional research

    -
    Motion from Interaction
    +
    Motion from interaction

    Visual motion and pseudo-motion triggered by interaction is avoided; or can be prevented, unless the animation is essential to the functionality or the information being conveyed.

    Needs additional research

    @@ -176,7 +176,7 @@
    Persistent errors

    Error notifications persist until the user dismisses them or the error is resolved.

    -
    Visible error
    +
    Visible errors

    Error notifications are visually collocated with the source of the error within the viewport, or provide a link to the source of the error which, when activated, moves the viewport to the error.

    Needs additional research

    @@ -284,7 +284,7 @@

    Complete tasks

    Users understand how to complete tasks.

    Action required
    -

    In a process, the interface indicates when user input or action is required to procceed to the next step. c

    +

    In a process, the interface indicates when user input or action is required to proceed to the next step. c

    Inform at start of process
    @@ -500,7 +500,7 @@
    User agent default indicator
    Supplemental Requirements
    -
    Supplimentary indicators
    +
    Supplementary indicators

    @@

    @@ -607,7 +607,7 @@
    Distinguishable controls
    Field constraints
    -

    Field constraints and conditions (required line length, date format, password format, etc) are available.

    +

    Field constraints and conditions (required line length, date format, password format, etc.) are available.

    Input labels
    @@ -627,7 +627,7 @@
    Name, role, value, state

    Input / Operation

    -

    Input pperation

    +

    Input Operation

    Users can use different input techniques and combinations and switch between them.

    Concurrent inputs
    @@ -815,7 +815,7 @@

    Orientation

    Users can determine their location in content both visually and using assistive technologies.

    Current location
    -

    The current location within the view, multi-step process, and is visually and programmatically indicated.

    +

    The current location within the view, multi-step process, and product is visually and programmatically indicated.

    Needs additional research

    @@ -878,7 +878,7 @@
    Consistent navigation
    Multiple ways
    -

    The product provides at least two ways of navigating and finding information (Search, Scan, Site Map, Menu Structure, Breadcrumbs, contextual links, etc).

    +

    The product provides at least two ways of navigating and finding information (Search, Scan, Site Map, Menu Structure, Breadcrumbs, contextual links, etc.).

    Persistent navigation
    @@ -1372,7 +1372,7 @@

    Defining conformance scope

    Glossary

    Many of the terms defined here have common meanings. When terms appear with a link to the definition, the meaning is as formally defined here. When terms appear without a link to the definition, their meaning is not explicitly related to the formal definition here. These definitions are in progress and may evolve as the document evolves.

    -

    This glossary includes terms used by content that has reached a maturity level of Developing or higher. The definitions themselves include a maturity level and may mature at a differet pace than the content that refers to them. The AGWG will work with other taskforces and groups to harmonize terminology across documents as much as is possible.

    +

    This glossary includes terms used by content that has reached a maturity level of Developing or higher. The definitions themselves include a maturity level and may mature at a different pace than the content that refers to them. The AGWG will work with other taskforces and groups to harmonize terminology across documents as much as is possible.

    Assertion
    @@ -1492,7 +1492,7 @@

    Glossary

    Point of Regard

    - The position in rendered content that the user is presumed to be viewing. The dimensions of the point of regard can vary. For example,it can be a two-dimensional area (e.g. content rendered through a two-dimensional graphical viewport), or a point (e.g. a moment during an audio rendering or a cursor position in a graphical rendering), or a range of text (e.g. focused text), or a two-dimensional area (e.g. content rendered through a two-dimensional graphical viewport). The point of regard is almost always within the viewport, but it can exceed the spatial or temporal dimensions of the viewport (see the definition of rendered content for more information about viewport dimensions). The point of regard can also refer to a particular moment in time for content that changes over time (e.g. an audio-only presentation). User agents can determine the point of regard in a number of ways, including based on viewport position in content, keyboard focus, and selection.

    + The position in rendered content that the user is presumed to be viewing. The dimensions of the point of regard can vary. For example, it can be a two-dimensional area (e.g. content rendered through a two-dimensional graphical viewport), or a point (e.g. a moment during an audio rendering or a cursor position in a graphical rendering), or a range of text (e.g. focused text), or a two-dimensional area (e.g. content rendered through a two-dimensional graphical viewport). The point of regard is almost always within the viewport, but it can exceed the spatial or temporal dimensions of the viewport (see the definition of rendered content for more information about viewport dimensions). The point of regard can also refer to a particular moment in time for content that changes over time (e.g. an audio-only presentation). User agents can determine the point of regard in a number of ways, including based on viewport position in content, keyboard focus, and selection.

    Process
    From d731295cc7b9b45b381db06450206f78a8272b68 Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 19 Nov 2024 17:52:42 +0000 Subject: [PATCH 41/49] Style changes to improve blocking --- guidelines/guidelines.css | 26 +++++++++++++++++++++++--- 1 file changed, 23 insertions(+), 3 deletions(-) diff --git a/guidelines/guidelines.css b/guidelines/guidelines.css index 604dfef..d871bdd 100644 --- a/guidelines/guidelines.css +++ b/guidelines/guidelines.css @@ -26,7 +26,16 @@ summary::after { content: url(img/summary.svg); } .summaryEnd { - font-weight: bold; + border: 0; + clip: rect(1px, 1px, 1px, 1px); + clip-path: inset(50%); + height: 1px; + margin: -1px; + overflow: hidden; + padding: 0; + position: absolute; + width: 1px; + word-wrap: normal !important; } /* removing for readability @@ -49,11 +58,11 @@ a.internalDFN[title]:hover, .internalDFN[title]:active, a.internalDFN[title]:foc } .guideline { - margin-left: 2em; + margin-left: 4rem; } .guideline .provision { - margin-left: 2em; + margin-left: 4rem; } .guideline-text, provision-text { @@ -173,4 +182,15 @@ a[href].status-link { text-indent: 0px; font-weight: bolder; font-size: .75em; +} + +section { + margin-bottom: 2rem; +} +#guidelines > section { + margin-bottom: 4rem; +} + +#guidelines :is(h2, h3, h4, h5, h6) { + margin-top: 1rem; } \ No newline at end of file From 3921215644416f15ec9f253a03adef1337f323df Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 19 Nov 2024 18:14:52 +0000 Subject: [PATCH 42/49] Clarify question text --- guidelines/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guidelines/index.html b/guidelines/index.html index 553789e..2727451 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -68,7 +68,7 @@

    Introduction

    The purpose of this update is to demonstrate a potential structure for guidelines and indicate the current direction of the WCAG 3.0 conformance. Please consider the following questions when reviewing this draft: -

    • What requirements needed to make web content accessible are missing from this list?
      • +
      • What requirements are missing from this list to make web content accessible?
      • What research supports or refutes the requirements marked as needing additional research?
      • Three guidelines (Image alternatives, Keyboard Focus Appearance and Implied Meaning) have moved from exploratory to developing and demonstrate a potential structure. Does grouping related requirements and assertions together and using a decision tree for foundational requirements make the guidelines easier to understand and use?
        • From f263b9de0a54f72889a43fe5ed59126db30c2eaa Mon Sep 17 00:00:00 2001 From: Kevin White Date: Tue, 19 Nov 2024 18:23:39 +0000 Subject: [PATCH 43/49] Update questions --- guidelines/index.html | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 2727451..1c84a69 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -70,8 +70,12 @@

        Introduction

        The purpose of this update is to demonstrate a potential structure for guidelines and indicate the current direction of the WCAG 3.0 conformance. Please consider the following questions when reviewing this draft:

        • What requirements are missing from this list to make web content accessible?
        • What research supports or refutes the requirements marked as needing additional research?
          • -
        • Three guidelines (Image alternatives, Keyboard Focus Appearance and Implied Meaning) have moved from exploratory to developing and demonstrate a potential structure. Does grouping related requirements and assertions together and using a decision tree - for foundational requirements make the guidelines easier to understand and use?
          • +
        • Three guidelines (Image alternatives, Keyboard Focus Appearance and Implied Meaning) have moved from exploratory to developing and demonstrate a potential structure. Do the following make the guidelines easier to understand and use: +
            +
          • Grouping related requirements and assertions?
            • +
          • Using a decision tree for foundational requirements?
            • +
          +
        • The conformance section explains the approach the Accessibilty Guidelines Working Group is considering for WCAG 3.0. While many details still need to be worked out, do you have constructive comments about the proposed approach for WCAG 3.0?

        From 8c7d32bda2ca0d6ec2f0e41c91d4725878050cb6 Mon Sep 17 00:00:00 2001 From: Alastair Campbell Date: Tue, 19 Nov 2024 18:27:30 +0000 Subject: [PATCH 44/49] Hidde comment on focus-management --- guidelines/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guidelines/index.html b/guidelines/index.html index 553789e..532f9aa 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -540,7 +540,7 @@
        Keyboard focus order
    Restore focus
    -

    When the focus is moved by the content into a temporary change of view (e.g. a modal), the focus is restored to its previous location when the view is restored.

    +

    When the focus is moved by the content into a temporary change of view (e.g. a modal), the focus is restored to its previous location when returned from the temporary change of view.

    Relevant focus
    From bd47e288b7ff3d13cb88ca347e0d38f13db10cb2 Mon Sep 17 00:00:00 2001 From: Kevin White Date: Wed, 20 Nov 2024 12:31:33 +0000 Subject: [PATCH 45/49] Remove redundant JS --- guidelines/guidelines.js | 108 +-------------------------------------- 1 file changed, 1 insertion(+), 107 deletions(-) diff --git a/guidelines/guidelines.js b/guidelines/guidelines.js index 4fb8613..cea80c9 100644 --- a/guidelines/guidelines.js +++ b/guidelines/guidelines.js @@ -34,78 +34,6 @@ function pathToName(path) { return sentenceCase(path.replace(/-/g, " ")); } -function linkHowTo() { - var howtoBaseURI = "https://www.w3.org/WAI/GL/WCAG3/" + new Date().getFullYear() + "/how-tos/"; - //if (respecConfig.specStatus == "ED") understandingBaseURI = "../../understanding/"; - //else understandingBaseURI = "https://www.w3.org/WAI/WCAG" + version + "/Understanding/"; - document.querySelectorAll('.guideline').forEach(function(node){ - //this is brittle, depends on how respec does the heading - var heading = textNoDescendant(findHeading(node)); - var pathFrag = titleToPathFrag(heading); - var htm = "

    Learn how to meet guideline \"" + heading + "\"

    "; - node.querySelector("p.guideline-text").insertAdjacentHTML("afterend", htm); - }) -} - -function linkOutcome() { - var outcomeBaseURI = "https://www.w3.org/WAI/GL/WCAG3/" + new Date().getFullYear() + "/outcomes/"; - //if (respecConfig.specStatus == "ED") understandingBaseURI = "../../understanding/"; - //else understandingBaseURI = "https://www.w3.org/WAI/WCAG" + version + "/Understanding/"; - document.querySelectorAll('.outcome').forEach(function(node){ - //this is brittle, depends on how respec does the heading - var heading = textNoDescendant(findHeading(node)); - var pathFrag = titleToPathFrag(heading); - var el = document.createElement("p"); - el.innerHTML = " Outcome details and methods for \"" + heading + "\""; - node.insertBefore(el, node.querySelector("details")); - - node.classList.add("notoc"); - }) -} - -function addOutcomeMarkers() { - document.querySelectorAll('.outcome').forEach(function(node){ - var outcomeText = node.querySelector("p"); - outcomeText.innerHTML = "Outcome: " + outcomeText.innerHTML; - /* - var insertion = document.createElement("p"); - insertion.classList.add("inserted"); - insertion.innerHTML = " (outcome for " + textNoDescendant(parentHeader) + ")"; - outcomeHeader.insertAdjacentElement("afterend", insertion); - */ - }) -} - -function addCategoryMarkers() { - document.querySelectorAll('.categories').forEach(function(node){ - var parentHeader = findHeading(node.parentElement); - var sectionHeader = node.querySelector('summary'); - sectionHeader.innerHTML = "Functional categories for " + textNoDescendant(parentHeader) + ""; - }) -} - -function addErrorMarkers() { - document.querySelectorAll('.errors').forEach(function(node){ - var parentHeader = findHeading(node.parentElement); - var errorHeader = node.querySelector('summary'); - errorHeader.innerHTML = "Critical errors for " + textNoDescendant(parentHeader) + ""; - }) -} - -function addRatingMarkers() { - document.querySelectorAll('.rating').forEach(function(node){ - var parentHeader = findHeading(node.parentElement); - var sectionHeader = node.querySelector('summary'); - sectionHeader.innerHTML = "Rating for " + textNoDescendant(parentHeader) + ""; - - var table = node.querySelector('table'); - table.querySelector("caption").remove(); - var caption = document.createElement("caption"); - caption.innerHTML = "Rating scale for \"" + textNoDescendant(parentHeader) + "\""; - table.insertBefore(caption, table.firstChild); - }) -} - function addSummaryMarkers() { document.querySelectorAll('.summary').forEach(function(node){ var parentHeader = findHeading(node.parentElement); @@ -121,15 +49,6 @@ function addSummaryMarkers() { }) } -function addNoteMarkers() { - document.querySelectorAll(".note").forEach(function(node){ - var el = document.createElement("p"); - el.className = "summaryEnd"; - el.innerHTML = "End of note"; - node.appendChild(el); - }) -} - var statusLabels = { placeholder: 'We will be addressing this topic.', exploratory: 'We are exploring one or more possible directions for this content.', @@ -161,15 +80,9 @@ function addStatusMarkers() { }); } -function termTitles() { - // put definitions into title attributes of term references - document.querySelectorAll('.internalDFN').forEach(function(node){ - var dfn = document.querySelector(node.href.substring(node.href.indexOf('#'))); - if (dfn.parentNode.name == "dt") node.title = dfn.parentNode.nextElementSibling.firstElementChild.textContent.trim().replace(/\s+/g,' '); - else if (dfn.title) node.title=dfn.title; - }); } + function removeDraftMethodLinks() { document.querySelectorAll('.method-link').forEach(function(node){ uri = node.href; @@ -219,18 +132,6 @@ function alternateFloats() { }); } -function edNotePermalinks() { - document.querySelectorAll(".note").forEach(function(node){ - var id = node.id; - var heading = node.querySelector(".marker"); - var permaLink = document.createElement("a"); - permaLink.classList.add("self-link"); - permaLink.setAttribute("aria-label", "§"); - permaLink.setAttribute("href", "#" + id); - heading.appendChild(permaLink); - }); -} - // somewhere along the chain image sizes are being added where I don't want them, doesn't happen locally function removeImgSize() { document.querySelectorAll("img").forEach(function(node){ @@ -324,20 +225,13 @@ function moveStatusFilterToToc() { function preRespec() { adjustDfnData(); linkOutcome(); - addCategoryMarkers(); - addErrorMarkers(); - addRatingMarkers(); addSummaryMarkers(); } // scripts after Respec has run function postRespec() { - addOutcomeMarkers(); adjustNormativity(); - termTitles(); removeDraftMethodLinks(); - edNotePermalinks(); - addNoteMarkers(); addStatusMarkers(); removeImgSize(); outputJson(); From bd632d3bff6e5bf2fbe349b3f4bfadcbf100ce09 Mon Sep 17 00:00:00 2001 From: Kevin White Date: Wed, 20 Nov 2024 12:32:03 +0000 Subject: [PATCH 46/49] Update presentation of decision trees --- guidelines/guidelines.css | 15 +- guidelines/guidelines.js | 19 + guidelines/index.html | 763 +++++++++++++++++++------------------- 3 files changed, 405 insertions(+), 392 deletions(-) diff --git a/guidelines/guidelines.css b/guidelines/guidelines.css index d871bdd..7d93423 100644 --- a/guidelines/guidelines.css +++ b/guidelines/guidelines.css @@ -38,6 +38,9 @@ summary::after { word-wrap: normal !important; } +.decision-tree summary::after { +} + /* removing for readability .howto-link, .outcome-link { font-style: italic; @@ -155,9 +158,8 @@ caption { content: "§"; display: block; } -.status-marker { +.status-marker, .provision-type-marker { font-weight: 700; - color: #091832; font-size: 11px; font-size: .6125rem; line-height: 1.4; @@ -165,10 +167,17 @@ caption { margin-left: 1em; padding: 4px 8px; border-radius: 3px; - background: #d0e1f1; text-transform: uppercase; letter-spacing: 1px; } +.status-marker { + background: #d0e1f1; + color: #091832; +} +.provision-type-marker { + background: #6bc8fe; + color: #111111; +} a[href].status-link { color: var(--text); } diff --git a/guidelines/guidelines.js b/guidelines/guidelines.js index cea80c9..8fdb27f 100644 --- a/guidelines/guidelines.js +++ b/guidelines/guidelines.js @@ -80,6 +80,24 @@ function addStatusMarkers() { }); } +var provisionTypeLabels = { + foundational: 'Used to test the most basic level of accessibility.', + supplemental: 'Used for higher levels of conformance.', + assertion: 'An attributable and documented statement of fact regarding procedures practiced in the development and maintenance of the content or product to improve accessibility.', +} + +function addProvisionTypeMarkers() { + var typeKeys = Object.keys(provisionTypeLabels); + typeKeys.forEach(function (provisionType) { + var headingSelector = '[data-provision-type="' + provisionType + '"] > .header-wrapper'; + var headings = document.querySelectorAll(headingSelector); + headings.forEach(function (heading) { + var provisionTypeMarker = document.createElement("span"); + provisionTypeMarker.classList.add("provision-type-marker"); + provisionTypeMarker.innerHTML = sentenceCase(provisionType); + heading.firstElementChild.insertAdjacentElement('beforeend', provisionTypeMarker); + }); + }); } @@ -232,6 +250,7 @@ function preRespec() { function postRespec() { adjustNormativity(); removeDraftMethodLinks(); + addProvisionTypeMarkers(); addStatusMarkers(); removeImgSize(); outputJson(); diff --git a/guidelines/index.html b/guidelines/index.html index d6de3fb..124278a 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -53,16 +53,16 @@

    Introduction

    The Requirements are grouped into the following sections:

    @@ -131,248 +131,66 @@

    Guidelines

    -
    -

    Animation and movement

    -
    -

    Avoid physical harm

    -

    Users do not experience physical harm from content.

    -
    -
    Audio shifting
    -

    Audio shifting designed to create a perception of motion is avoided; or can be paused or prevented.

    -

    Needs additional research

    -
    -
    -
    Flashing
    -

    Flashing or strobing beyond thresholds defined by safety standards are avoided; or can be paused or prevented.

    -
    -
    -
    Motion
    -

    Visual motion and pseudo-motion that lasts longer than 5 seconds is avoided; or can be paused or prevented.

    -

    Needs additional research

    -
    -
    -
    Motion from interaction
    -

    Visual motion and pseudo-motion triggered by interaction is avoided; or can be prevented, unless the animation is essential to the functionality or the information being conveyed.

    -

    Needs additional research

    -
    -
    -
    - -
    -

    Error handling

    -
    -

    Correct mistakes

    -

    Users know about and can correct mistakes.

    -
    -
    Error association
    -

    Error notifications are programmatically associated with the error source so that users can access the error information while focused on the source of the error.

    -
    -
    -
    Error identification
    -

    Errors are visually identifiable without relying on only text, only color, or only symbols.

    -
    -
    -
    Error notification
    -

    Errors that can be automatically detected are identified and described to the user.

    -
    -
    -
    Persistent errors
    -

    Error notifications persist until the user dismisses them or the error is resolved.

    -
    -
    -
    Visible errors
    -

    Error notifications are visually collocated with the source of the error within the viewport, or provide a link to the source of the error which, when activated, moves the viewport to the error.

    -

    Needs additional research

    -
    -
    -
    - -
    -

    Process and task completion

    -
    -

    Avoid cognitive tasks

    -

    Users can complete tasks without needing to memorize nor complete advanced cognitive tasks.

    -
    -
    Allow automated entry
    -

    Automated input from user agents, 3rd party tools, or copy-and-paste is not prevented.

    -
    -
    -
    No cognitive tests
    -

    Processes, including authentication, can be completed without puzzles, calculations, or other cognitive tests (essential exceptions would apply).

    -
    -
    -
    No memorization
    -

    Processes can be completed without memorizing and recalling information from previous stages of the process.

    -

    Needs additional research

    -
    -
    - -
    -

    Adequate time

    -

    Users have enough time to read and use content.

    -
    -
    Adjust timing at start
    -

    For each process with a time-limit, a mechanism exists to disable or extend the limit before the time-limit starts.

    -
    -
    -
    Adjust timing at timeout
    -

    For each process with a time-limit, a mechanism exists to disable or extend the time-limit at timeout.

    -
    -
    -
    Disable timeout
    -

    For each process with a time-limit, a mechanism exists to disable the limit.

    -
    -
    - -
    -

    Unnecessary steps

    -

    Users can complete tasks without unnecessary steps.

    -
    -

    Optional information

    -

    Processes can be completed without being forced to read or understand unnecessary content.

    -
    -
    -

    Optional input

    -

    Processes can be completed without entering unnecessary information.

    -
    -
    - -
    -

    Avoid deception

    -

    Users do not encounter deception when completing tasks, unless essential to the task.

    -
    -

    Deceptive controls

    -

    Interactive components are not deceptively designed.

    -

    Needs additional research

    -
    -
    -

    Exploitive behaviors

    -

    Process completion does not include exploitive behaviors.

    -

    Needs additional research

    -
    -
    -
    Misinformation
    -

    Processes can be completed without navigating misinformation or redirections.

    -

    Needs additional research

    -
    -
    -
    Preselections
    -

    Preselected options are visible by default during process completion without additional interactions.

    -
    -
    -
    Redirection
    -

    A mechanism is available to prevent fraudulent redirection or alert users they are exiting the site.

    -

    Needs additional research

    -
    -
    - -
    -

    Retain information

    -

    Users do not have to reenter information or redo work.

    -
    -
    Go back in process
    -

    In a multistep process, the interface supports stepping backwards in a process and returning to the current point without data loss.

    -
    -
    -
    Redundant entry
    -

    Information previously entered by or provided to the user that is required to be entered again in the same process is either auto-populated, or available for the user to select.

    -
    -
    -
    Save progress
    -

    Data entry and other task completion processes allow saving and resuming from the current step in the task.

    -
    -
    - -
    -

    Complete tasks

    -

    Users understand how to complete tasks.

    -
    -
    Action required
    -

    In a process, the interface indicates when user input or action is required to proceed to the next step. c

    -
    -
    -
    Inform at start of process
    -

    Information needed to complete a multi-step process is provided at the start of the process, including: -

    • number of steps it might take (if known in advance),
      • -
    • details of any resources needed to perform the task, and
      • -
    • overview of the process and next step.
    -

    -
    -
    -
    Steps and instructions
    -

    The steps and instructions needed to complete a multistep process are available

    -
    -
    -
    -

    Image and media alternatives

    Image alternatives

    Users have equivalent alternatives for images.

    - -
    -
    Foundational Requirements
    + +
    + Which provision applies?

    For each image:

    1. Would removing the image impact how people understand the page? -

    +
    -
    -
    Decorative image
    -

    Decorative image is programmatically hidden.

    -
    -
    -
    Content image
    -

    Equivalent text alternative is available for image that conveys content.

    -
    -
    -
    Detectable image
    -

    Image is programmatically detectable.

    -
    +
    +
    Decorative image
    +

    Decorative image is programmatically hidden.

    - - -
    -
    Supplemental Requirements
    - -
    -
    Image role
    -

    The role and importance of the image is programmatically indicated.

    -
    -
    -
    Image type
    -

    The type of image (photo, icon, etc.) is indicated.

    -
    -
    -
    Editable Alternatives
    -

    Auto generated text descriptions are editable by content creator.

    -

    Needs additional research

    -
    +
    +
    Content image
    +

    Equivalent text alternative is available for image that conveys content.

    +
    +
    +
    Detectable image
    +

    Image is programmatically determinable.

    -
    -
    Assertions
    -
    -
    Style Guide
    -

    Text alternatives follow an organizational style guide.

    -
    +
    +
    Image role
    +

    The role and importance of the image is programmatically indicated.

    +
    +
    +
    Image type
    +

    The type of image (photo, icon, etc.) is indicated.

    +
    +
    +
    Editable Alternatives
    +

    Auto generated text descriptions are editable by content creator.

    +

    Needs additional research

    + +
    +
    Style Guide
    +

    Text alternatives follow an organizational style guide.

    +
    @@ -453,68 +271,201 @@
    Use of spatial audio
    +
    +

    Text and Wording

    +
    +

    Text appearance

    +

    Users can read visually rendered text.

    +
    +
    Maximum text contrast
    +

    The rendered text against its background meets a maximum contrast ratio test for its text appearance.

    +

    Needs additional research

    +
    +
    +
    Minimum text contrast
    +

    The rendered text against its background meets a minimum contrast ratio test for its text appearance.

    +

    Needs additional research

    +
    +
    +
    Text size
    +

    The rendered text meets a minimum font size and weight.

    +

    Needs additional research

    +
    +
    +
    Text style
    +

    The rendered text does not use a decorative or cursive font face.

    +
    +
    + +
    +

    Text-to-speech

    +

    Users can access text content and its meaning with text-to-speech tools.

    +
    +
    Text-to-speech supported
    +

    Text content can be converted into speech.

    +

    Needs additional research

    +
    +
    +
    Human language
    +

    The human language of the view and content within the view is programmatically available.

    +
    +
    +
    Semantic text appearance
    +

    Meaning conveyed by text appearance is programmatically available.

    +

    Needs additional research

    +
    +
    + +
    +

    Clear language

    +

    Users can access clear language content.

    +
    +
    Acronyms and abbreviations
    +

    The expanded form or meaning of abbreviations and acronyms is available.

    +
    +
    +
    Ambiguous numbers
    +

    Alternative formats for ambiguous number formats are available.

    +
    +
    +
    Ambiguous pronunciation
    +

    All letters and diacritics needed to identify (phonetically read) words are available.

    +
    +
    +
    Appropriate tone
    +

    The language and tone used is respectful and appropriate to the topic or subject matter.

    +

    Needs additional research

    +
    +
    +
    Double negatives
    +

    Content does not include double negatives to express a positive unless it is standard usage for that language or dialect.

    +
    +
    +
    Implied Meaning
    +

    Users can access the literal meaning of text.

    + +
    +
    Foundational Requirements
    +

    For each item of non-literal text: +

      +
    1. Is the non-literal text presented in a way that is available to user agents, including assistive technology + (AT)? + + +
      2. + +
    2. Does the available user agent, including assistive technology, sufficiently Explain non-literal text or + provide a literal alternative? +
        +
      • Yes, pass. Stop.
        • +
      • No, continue.
        • +
      +
      3. + +
    3. Does the publisher sufficiently explain the non-literal text or provide a literal alternative? + +
      4. +
    +

    +

    Exceptions

    +
      +
    • If the purpose is to showcase works of art, such as a poetry journal but if the purpose is to educate students + about + pieces of art, then the exception would not apply.
      • +
    +
    +
    +
    +
    Literal text
    +

    Explain non-literal text or provide a literal alternative

    +
    + +
    +
    Sentence voice
    +

    The voice used is easiest to understand in context.

    +

    Needs additional research

    +
    +
    +
    Topic sentence
    +

    For text intended to inform the user, each paragraph of text begins with a topic sentence stating the aim or purpose.

    +
    +
    +
    Uncommon words
    +

    Definitions for uncommon or new words are available.

    +

    Needs additional research

    +
    +
    +
    Unnecessary words or phrases
    +

    Sentences are concise, without unnecessary filler words and phrases.

    +
    +
    +
    Verb tense
    +

    The verb tense used is easiest to understand in context.

    +

    Needs additional research

    +
    +
    +
    +

    Interactive components

    Keyboard Focus Appearance

    Users can see which element has keyboard focus.

    -
    -
    Foundational Requirements
    - +
    + Which provision applies?

    For each focusable item:

    1. Is the user-agent default focus indicator used?
    2. Is the user-agent default focus indicator used, and meets contrast across backgrounds?
    3. Is the focus indicator defined by the author?

    +
    -
    -
    Custom indicator
    -

    A custom focus indicator is used with sufficient size, change of contrast, adjacent contrast, distinct style and adjacency.

    -
    -
    -
    Default indicator
    -

    The platform’s default indicator is used, and where the backgrounds are changed, the indicator contrast is checked.

    -
    -
    -
    User agent default indicator
    -

    Focusable item uses the user agent default indicator.

    -
    +
    +
    Custom indicator
    +

    A custom focus indicator is used with sufficient size, change of contrast, adjacent contrast, distinct style and adjacency.

    +
    +
    +
    Default indicator
    +

    The platform’s default indicator is used, and where the backgrounds are changed, the indicator contrast is checked.

    +
    +
    +
    User agent default indicator
    +

    Focusable item uses the user agent default indicator.

    -
    -
    Supplemental Requirements
    -
    -
    Supplementary indicators
    -

    @@

    -
    +
    +
    Supplementary indicators
    +

    @@

    -
    -
    Assertions
    -
    -
    Style Guide
    -

    Focus indicators follow an organizational style guide.

    -
    +
    +
    Style Guide
    +

    Focus indicators follow an organizational style guide.

    @@ -763,9 +714,65 @@
    Use without device movement
    Interactive component contrast

    Visual information required to identify user interface components and states meet a minimum contrast ratio test, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author.

    Needs additional research

    -
    +
    +
    +
    + +
    +

    Error handling

    +
    +

    Correct mistakes

    +

    Users know about and can correct mistakes.

    +
    +
    Error association
    +

    Error notifications are programmatically associated with the error source so that users can access the error information while focused on the source of the error.

    +
    +
    +
    Error identification
    +

    Errors are visually identifiable without relying on only text, only color, or only symbols.

    +
    +
    +
    Error notification
    +

    Errors that can be automatically detected are identified and described to the user.

    +
    +
    +
    Persistent errors
    +

    Error notifications persist until the user dismisses them or the error is resolved.

    +
    +
    +
    Visible errors
    +

    Error notifications are visually collocated with the source of the error within the viewport, or provide a link to the source of the error which, when activated, moves the viewport to the error.

    +

    Needs additional research

    +
    +
    +
    + +
    +

    Animation and movement

    +
    +

    Avoid physical harm

    +

    Users do not experience physical harm from content.

    +
    +
    Audio shifting
    +

    Audio shifting designed to create a perception of motion is avoided; or can be paused or prevented.

    +

    Needs additional research

    +
    +
    +
    Flashing
    +

    Flashing or strobing beyond thresholds defined by safety standards are avoided; or can be paused or prevented.

    +
    +
    +
    Motion
    +

    Visual motion and pseudo-motion that lasts longer than 5 seconds is avoided; or can be paused or prevented.

    +

    Needs additional research

    +
    +
    +
    Motion from interaction
    +

    Visual motion and pseudo-motion triggered by interaction is avoided; or can be prevented, unless the animation is essential to the functionality or the information being conveyed.

    +

    Needs additional research

    +
    -
    +

    Layout

    @@ -892,205 +899,183 @@
    Persistent navigation
    -

    Policy and Protection

    +

    Process and task completion

    -

    Content source

    -

    Users can determine when content is provided by a Third Party

    +

    Avoid cognitive tasks

    +

    Users can complete tasks without needing to memorize nor complete advanced cognitive tasks.

    -
    Citation
    -

    The author or source of the primary content is visually and programmatically indicated.

    -

    Needs additional research

    +
    Allow automated entry
    +

    Automated input from user agents, 3rd party tools, or copy-and-paste is not prevented.

    -
    Indicate 3rd party content
    -

    Third party content (AI, Advertising, etc.) is visually and programmatically indicated.

    -

    Needs additional research

    +
    No cognitive tests
    +

    Processes, including authentication, can be completed without puzzles, calculations, or other cognitive tests (essential exceptions would apply).

    -
    Obscuring primary content
    -

    Advertising and other third-party content that obscures the primary content can be moved or removed without interacting with the advertising or third-party content.

    +
    No memorization
    +

    Processes can be completed without memorizing and recalling information from previous stages of the process.

    Needs additional research

    -

    Security and Privacy

    -

    Users’ safety, security or privacy are not decreased by accessibility measures.

    +

    Adequate time

    +

    Users have enough time to read and use content.

    -
    Clear agreement
    -

    The interface indicates when a user is entering an agreement or submitting data.

    -

    Needs additional research

    +
    Adjust timing at start
    +

    For each process with a time-limit, a mechanism exists to disable or extend the limit before the time-limit starts.

    -
    Disability information privacy
    -

    Disability information is not disclosed to or used by third parties and algorithms (including AI).

    -

    Needs additional research

    +
    Adjust timing at timeout
    +

    For each process with a time-limit, a mechanism exists to disable or extend the time-limit at timeout.

    -
    Sensitive information
    -

    Prompts to hide and remove sensitive information from observers are available.

    -

    Needs additional research

    -
    -
    -
    Risk statements
    -

    Clear explanations of the risks and consequences of choices, including use, are stated.

    -

    Needs additional research

    +
    Disable timeout
    +

    For each process with a time-limit, a mechanism exists to disable the limit.

    -

    Algorithms

    -

    Users are not disadvantaged by algorithms.

    +

    Unnecessary steps

    +

    Users can complete tasks without unnecessary steps.

    +
    +

    Optional information

    +

    Processes can be completed without being forced to read or understand unnecessary content.

    +
    +
    +

    Optional input

    +

    Processes can be completed without entering unnecessary information.

    +
    +
    + +
    +

    Avoid deception

    +

    Users do not encounter deception when completing tasks, unless essential to the task.

    -
    Algorithm bias
    -

    Algorithms (including AI) used are not biased against people with disabilities.

    +

    Deceptive controls

    +

    Interactive components are not deceptively designed.

    Needs additional research

    -
    Social media algorithm
    -

    A mechanism is available to understand and control social media algorithms.

    +

    Exploitive behaviors

    +

    Process completion does not include exploitive behaviors.

    Needs additional research

    -
    -
    -
    - -
    -

    Text and Wording

    -
    -

    Text appearance

    -

    Users can read visually rendered text.

    +
    -
    Maximum text contrast
    -

    The rendered text against its background meets a maximum contrast ratio test for its text appearance.

    +
    Misinformation
    +

    Processes can be completed without navigating misinformation or redirections.

    Needs additional research

    -
    -
    Minimum text contrast
    -

    The rendered text against its background meets a minimum contrast ratio test for its text appearance.

    -

    Needs additional research

    -
    -
    Text size
    -

    The rendered text meets a minimum font size and weight.

    -

    Needs additional research

    -
    +
    Preselections
    +

    Preselected options are visible by default during process completion without additional interactions.

    +
    -
    Text style
    -

    The rendered text does not use a decorative or cursive font face.

    -
    -
    +
    Redirection
    +

    A mechanism is available to prevent fraudulent redirection or alert users they are exiting the site.

    +

    Needs additional research

    +
    +
    -

    Text-to-speech

    -

    Users can access text content and its meaning with text-to-speech tools.

    +

    Retain information

    +

    Users do not have to reenter information or redo work.

    -
    Text-to-speech supported
    -

    Text content can be converted into speech.

    -

    Needs additional research

    -
    -
    -
    Human language
    -

    The human language of the view and content within the view is programmatically available.

    +
    Go back in process
    +

    In a multistep process, the interface supports stepping backwards in a process and returning to the current point without data loss.

    -
    Semantic text appearance
    -

    Meaning conveyed by text appearance is programmatically available.

    -

    Needs additional research

    +
    Redundant entry
    +

    Information previously entered by or provided to the user that is required to be entered again in the same process is either auto-populated, or available for the user to select.

    +
    +
    +
    Save progress
    +

    Data entry and other task completion processes allow saving and resuming from the current step in the task.

    -

    Clear language

    -

    Users can access clear language content.

    +

    Complete tasks

    +

    Users understand how to complete tasks.

    -
    Acronyms and abbreviations
    -

    The expanded form or meaning of abbreviations and acronyms is available.

    +
    Action required
    +

    In a process, the interface indicates when user input or action is required to proceed to the next step. c

    -
    Ambiguous numbers
    -

    Alternative formats for ambiguous number formats are available.

    +
    Inform at start of process
    +

    Information needed to complete a multi-step process is provided at the start of the process, including: +

    • number of steps it might take (if known in advance),
      • +
    • details of any resources needed to perform the task, and
      • +
    • overview of the process and next step.
    +

    -
    Ambiguous pronunciation
    -

    All letters and diacritics needed to identify (phonetically read) words are available.

    +
    Steps and instructions
    +

    The steps and instructions needed to complete a multistep process are available

    +
    +
    + +
    +

    Policy and Protection

    +
    +

    Content source

    +

    Users can determine when content is provided by a Third Party

    -
    Appropriate tone
    -

    The language and tone used is respectful and appropriate to the topic or subject matter.

    +
    Citation
    +

    The author or source of the primary content is visually and programmatically indicated.

    Needs additional research

    -
    -
    -
    Double negatives
    -

    Content does not include double negatives to express a positive unless it is standard usage for that language or dialect.

    -
    -
    Implied Meaning
    -

    Users can access the literal meaning of text.

    - -
    -
    Foundational Requirements
    -

    For each item of non-literal text: -

      -
    1. Is the non-literal text presented in a way that is available to user agents, including assistive technology - (AT)? - - -
      2. - -
    2. Does the available user agent, including assistive technology, sufficiently Explain non-literal text or - provide a literal alternative? -
        -
      • Yes, pass. Stop.
        • -
      • No, continue.
        • -
      -
      3. - -
    3. Does the publisher sufficiently explain the non-literal text or provide a literal alternative? - -
      4. -
    -

    -

    Exceptions

    -
      -
    • If the purpose is to showcase works of art, such as a poetry journal but if the purpose is to educate students - about - pieces of art, then the exception would not apply.
      • -
    -
    +
    +
    Indicate 3rd party content
    +

    Third party content (AI, Advertising, etc.) is visually and programmatically indicated.

    +

    Needs additional research

    -
    -
    Literal text
    -

    Explain non-literal text or provide a literal alternative

    +
    +
    Obscuring primary content
    +

    Advertising and other third-party content that obscures the primary content can be moved or removed without interacting with the advertising or third-party content.

    +

    Needs additional research

    +
    +
    +

    Security and Privacy

    +

    Users’ safety, security or privacy are not decreased by accessibility measures.

    -
    Sentence voice
    -

    The voice used is easiest to understand in context.

    +
    Clear agreement
    +

    The interface indicates when a user is entering an agreement or submitting data.

    Needs additional research

    -
    Topic sentence
    -

    For text intended to inform the user, each paragraph of text begins with a topic sentence stating the aim or purpose.

    +
    Disability information privacy
    +

    Disability information is not disclosed to or used by third parties and algorithms (including AI).

    +

    Needs additional research

    -
    Uncommon words
    -

    Definitions for uncommon or new words are available.

    +
    Sensitive information
    +

    Prompts to hide and remove sensitive information from observers are available.

    Needs additional research

    -
    -
    -
    Unnecessary words or phrases
    -

    Sentences are concise, without unnecessary filler words and phrases.

    -
    Verb tense
    -

    The verb tense used is easiest to understand in context.

    +
    Risk statements
    +

    Clear explanations of the risks and consequences of choices, including use, are stated.

    +

    Needs additional research

    +
    +
    + +
    +

    Algorithms

    +

    Users are not disadvantaged by algorithms.

    +
    +
    Algorithm bias
    +

    Algorithms (including AI) used are not biased against people with disabilities.

    Needs additional research

    +
    +
    Social media algorithm
    +

    A mechanism is available to understand and control social media algorithms.

    +

    Needs additional research

    +
    From 5f7200041e6bc7ea0550398890b1c2b9cfa712c1 Mon Sep 17 00:00:00 2001 From: Kevin White Date: Wed, 20 Nov 2024 12:32:30 +0000 Subject: [PATCH 47/49] Explore different numbering presentation --- guidelines/guidelines.js | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/guidelines/guidelines.js b/guidelines/guidelines.js index 8fdb27f..9d919d0 100644 --- a/guidelines/guidelines.js +++ b/guidelines/guidelines.js @@ -168,6 +168,13 @@ function removeGLNum() { sectionEl.querySelectorAll("bdi.secno").forEach(function(node){node.remove();}); } +function removeProvisionNum() { + var tocEl = document.querySelector(".tocline > a[href=\"#guidelines\"]").parentNode.querySelector("ol"); + tocEl.querySelectorAll("ol ol ol ol bdi.secno").forEach(function(node){node.remove();}); + + document.querySelectorAll(".provision bdi.secno").forEach(function(node){node.remove();}); +} + function outputJson() { params = new URLSearchParams(window.location.search); if (params.get("json") != null) { @@ -254,5 +261,6 @@ function postRespec() { addStatusMarkers(); removeImgSize(); outputJson(); - removeGLNum(); + // removeGLNum(); + removeProvisionNum(); } From e82379c5f1c6b117ababe6d1a86ed2254cd2f0f4 Mon Sep 17 00:00:00 2001 From: Kevin White Date: Wed, 20 Nov 2024 17:42:09 +0000 Subject: [PATCH 48/49] Remove Implied Meaning decision tree --- guidelines/index.html | 42 +++--------------------------------------- 1 file changed, 3 insertions(+), 39 deletions(-) diff --git a/guidelines/index.html b/guidelines/index.html index 75b69f5..f8560b6 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -16,7 +16,7 @@

    See WCAG 3.0 Introduction for an introduction and links to WCAG technical and educational material.

    -

    This is an update to the W3C Accessibility Guidelines (WCAG) 3.0. It includes a restructuring of the guidelines and first draft decision trees for three Guidelines: Image alternatives, Keyboard Focus Appearance and Implied meaning.

    +

    This is an update to the W3C Accessibility Guidelines (WCAG) 3.0. It includes a restructuring of the guidelines and first draft decision trees for two Guidelines: Image alternatives and Keyboard Focus Appearance.

    To comment, file an issue in the W3C wcag3 GitHub repository. The Working Group requests that public comments be filed as new issues, one issue per discrete comment. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, send email to public-agwg-comments@w3.org (comment archive). In-progress updates to the guidelines can be viewed in the public editors’ draft.

    @@ -70,7 +70,7 @@

    Introduction

    The purpose of this update is to demonstrate a potential structure for guidelines and indicate the current direction of the WCAG 3.0 conformance. Please consider the following questions when reviewing this draft:

    • What requirements are missing from this list to make web content accessible?
    • What research supports or refutes the requirements marked as needing additional research?
      • -
    • Three guidelines (Image alternatives, Keyboard Focus Appearance and Implied Meaning) have moved from exploratory to developing and demonstrate a potential structure. Do the following make the guidelines easier to understand and use: +
    • Two guidelines (Image alternatives and Keyboard Focus Appearance) have moved from exploratory to developing and demonstrate a potential structure. Do the following make the guidelines easier to understand and use:
      • Grouping related requirements and assertions?
      • Using a decision tree for foundational requirements?
        • @@ -343,45 +343,9 @@
        Double negatives
        Implied Meaning

        Users can access the literal meaning of text.

        - -
        -
        Foundational Requirements
        -

        For each item of non-literal text: -

          -
        1. Is the non-literal text presented in a way that is available to user agents, including assistive technology - (AT)? - -
      -
      • - -
    • Does the available user agent, including assistive technology, sufficiently Explain non-literal text or - provide a literal alternative? -
        -
      • Yes, pass. Stop.
        • -
      • No, continue.
        • -
      -
      • - -
    • Does the publisher sufficiently explain the non-literal text or provide a literal alternative? - -
      • - -

      -

      Exceptions

      -
        -
      • If the purpose is to showcase works of art, such as a poetry journal but if the purpose is to educate students - about - pieces of art, then the exception would not apply.
        • -
      -
    -
    Literal text
    +
    Literal text

    Explain non-literal text or provide a literal alternative

    From 00ff0da5499ead3902aa78fef1ddfccb2d4e3d93 Mon Sep 17 00:00:00 2001 From: Kevin White Date: Wed, 20 Nov 2024 19:45:47 +0000 Subject: [PATCH 49/49] Update guidelines/acknowledgements/current-contributors.html Co-authored-by: Patrick H. Lauke --- guidelines/acknowledgements/current-contributors.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guidelines/acknowledgements/current-contributors.html b/guidelines/acknowledgements/current-contributors.html index ff26e0c..1fb581f 100644 --- a/guidelines/acknowledgements/current-contributors.html +++ b/guidelines/acknowledgements/current-contributors.html @@ -52,7 +52,7 @@

    Contributors to the development of this document

  • Mike Beganyi (Invited Expert)
  • Mike Gower (IBM Corporation)
  • Nina Krauß (SAP SE)
    • -
  • Patrick Lauke (TetraLogical Services Ltd)
    • +
  • Patrick H. Lauke (TetraLogical Services Ltd)
  • Poornima Badhan Subramanian (Invited Expert)
  • Rachael Bradley Montgomery (Library of Congress)
  • Rain Breaw Michaels (Google LLC)