diff --git a/techniques/css/C43.html b/techniques/css/C43.html index 0295e33221..ee3d14329f 100644 --- a/techniques/css/C43.html +++ b/techniques/css/C43.html @@ -167,12 +167,14 @@
For each user interface component that can receive keyboard focus:
Individuals who are unable to detect changes of context or may not realize that the - context has changed are less likely to become disoriented while navigating a site. +
Individuals who are unable to detect changes of context or who may not realize that the context has changed are less likely to become disoriented if they initiate the change themselves. For example:
diff --git a/understanding/20/name-role-value.html b/understanding/20/name-role-value.html index e0db538bbb..8629273f72 100644 --- a/understanding/20/name-role-value.html +++ b/understanding/20/name-role-value.html @@ -1,50 +1,41 @@ - +The intent of this Success Criterion is to ensure that Assistive Technologies (AT) can gather appropriate information about, activate (or set) and keep up to date on the status of user interface controls in the content.
-When standard controls from accessible technologies are used, this process is straightforward. If the user interface elements are used according to specification the conditions of this provision will be met. (See examples of Success Criterion 4.1.2 below)
-If custom controls are created, however, or interface elements are programmed (in code or script) to have a different role and/or function than usual, then additional measures need to be taken to ensure that the controls provide important and appropriate information to assistive technologies and allow themselves to be controlled by assistive technologies.
-What roles and states are appropriate to convey to assistive technology will depend on what the control represents. Specifics about such information are defined by other specifications, such as WAI-ARIA, or the relevant platform standards. Another factor to consider is whether there is sufficient accessibility support with assistive technologies to convey the information as specified.
-A particularly important state of a user interface control is whether or not it has focus. The focus state of a control can be programmatically determined, and notifications about change of focus are sent to user agents and assistive technology. Other examples @@ -52,48 +43,32 @@
Success Criterion 4.1.2 requires a programmatically determinable name for all user interface components. Names may be visible or invisible. Occasionally, the name needs to be visible, in which case it is identified as a label. Refer to the definition of name and label in the glossary for more information.
-- - Using markup features to expose the name and role, allow user-settable properties - to be directly set, and provide notification of changes - using technology-specific techniques below: +
+ using technology-specific techniques below:
-- - Using the accessibility API features of a technology to expose the names and roles, - allow user-settable properties to be directly set, and provide notification of changes - using technology-specific techniques below: - + using technology-specific techniques below:
- -- - Creating components using a technology that supports the accessibility API features - of the platforms on which the user agents will be run to expose the names and roles, - allow user-settable properties to be directly set, and provide notification of changes - using technology-specific techniques below: - + using technology-specific techniques below:
- -In Figure 2 the last portion of text is cut off in 3 side-by-side headings. The 1st heading should read "A cog in the wheel." But it reads "A cog in the whe". Only half of the second "e" is visible and the letter "l" is completely missing. The 2nd heading should read "A penny for your thoughts". But it reads "A penny for your". The 3rd should read "Back to the drawing board." But it reads "Back to the drawi".
+In Figure 2 the last portion of text is cut off in three side-by-side headings. The first heading should read "A cog in the wheel", but it reads "A cog in the whe". Only half of the second "e" is visible and the letter "l" is completely missing. The second heading should read "A penny for your thoughts". But it reads "A penny for your". The third should read "Back to the drawing board." But it reads "Back to the drawi".