5. Changing Content and 4.1.2

[kengdoj]

4.1.2 is applicable to all user interface components (including but not limited to: form elements, links and components generated by scripts).

Baseline 5. Changing Content test for 4.1.2 must be edited to limit testing to user interface components. Understanding 4.1.2 version 2.1:

user interface component - a part of the content that is perceived by users as a single control for a distinct function
NOTE: Multiple user interface components may be implemented as a single programmatic element. "Components" here is not tied to programming techniques, but rather to what the user perceives as separate controls.
NOTE: User interface components include form elements and links as well as components generated by scripts.
NOTE: What is meant by "component" or "user interface component" here is also sometimes called "user interface element".
An applet has a "control" that can be used to move through content by line or page or random access. Since each of these would need to have a name and be settable independently, they would each be a "user interface component."

[kengdoj]

Understanding 4.1.2 version 2.0 definition:

user interface component - a part of the content that is perceived by users as a single control for a distinct function
Note 1: Multiple user interface components may be implemented as a single programmatic element. Components here is not tied to programming techniques, but rather to what the user perceives as separate controls.
Note 2: User interface components include form elements and links as well as components generated by scripts.
Example: An applet has a "control" that can be used to move through content by line or page or random access. Since each of these would need to have a name and be settable independently, they would each be a "user interface component."

This note is new in 2.1 version of definition:

NOTE: What is meant by "component" or "user interface component" here is also sometimes called "user interface element".

[kengdoj]

Failure 20: Failure of Success Criterion 1.1.1 and 4.1.2 due to not updating text alternatives when changes to non-text content occur.

This fails 4.1.2, but the non-text content is not a control, i.e., not a user interface component.

Seeking comment from @bruce-usab, please.

[bruce-usab]

This is another good example of TT/Baseline close review of WAI materials spotting less-than-great prose in Understanding et al.

None of those examples are UIC, so those three examples all fail 1.1.1 and none of them fail 4.1.2. The page is not wrong, but it is misleading not to include a 4.1.2 failure. From the lack of exposition, there is an implication is that the examples fail both 1.1.1 and 4.1.2 — but that is not true.

An F20 4.1.2 example would be a button, perhaps a slider, which changes from visually presenting as on to off with Accessible Name having a static/wrong value.

But with HTML5 and WAI-ARIA — is this sort of button example anything but quaint? I do not think it would be alt doing the work nowadays.

Please be encouraged to files an issue, and maybe a PR. Or ask me to do so.

Even the title has problems -- since it implies a hard logical AND not a soft grammatical "and also maybe".

[kengdoj]

Or ask me to do so.

Asking @bruce-usab to open the issue/PR for Failure 20.

[bruce-usab]

I will use my best judgement, changing as little as possible.

An F20 4.1.2 example would be a button, perhaps a slider, which changes from visually presenting as on to off with Accessible Name having a static/wrong value.

Can anyone code pen this or what?

[drewnielson]

I think we have an example already:

• Test Case
• Sample Code

[bruce-usab]

Thank you @drewnielson — that is exactly the sort of (bad) model example I was hoping for!

[kengdoj]

closed by #377