Adds a defintion for essential text change

[tbostic32]

In Text content that changes automatically can be paused, stopped or hidden it was determined that we need to have essential in the expectation. However, essential is an ambiguous term, so we need to create a new definition that handles the various cases where text changing is an essential function of a page.

Need for Call for Review:
This will require a 1 week Call for Review

How to Review And Approve

• Go to the “Files changed” tab
• Here you will have the option to leave comments on different lines.
• Once the review is completed, find the “Review changes” button in the top right, select “Approve” (if you are really confident in the rule) or "Request changes" and click “Submit review”.
• Make sure to also review the proposed Call for Review period. In case of disagreement, the longer period wins.

[tbostic32]

This feels very awkward, namely specifying that the information must be important in order for this to qualify. I felt the need to do this since I wouldn't qualify the examples given in Understand 2.2.2 like weather or stock ticker information as important enough to be exempt from having controls. However, there could be information such as safety alerts/updates that I would consider to be exempt.

[WilcoFiers]

Yeah, this one's difficult. Who decides what should and what should not be ignored? I think we should maybe just try to give a list of the types of things that shouldn't be ignored? Maybe, financial data, information on the status of a user session, that kind of thing.

[tbostic32]

I find this to be awkward, but I also couldn't figure out a good way to say it without doing something like:

An essential text change occurs when the changing of text on a page is essential.

[WilcoFiers]

Yeah, this one's difficult. Who decides what should and what should not be ignored? I think we should maybe just try to give a list of the types of things that shouldn't be ignored? Maybe, financial data, information on the status of a user session, that kind of thing.

[tbostic32]

@carlosapaduarte From our review we found that the applicability is somewhat hard to understand, so I would like to propose the change below:

1. Remove the no-child-changed and not-alone applicability conditions
2. Modify the change condition to only consider the text content of child text nodes (only direct children, not all descendants)

At least my understanding was that the no-child-changed condition was meant to prevent an parent element from being applicable when a the text content of a child was changed. If we only consider the text content of child text nodes then the an ancestor node will never be applicable when one of its descendants text changes.

[WilcoFiers]

Would something like a clock or a count-down be considered essential. For example on a new years calendar, an auctioning site counting down when the auction closes, or a ticket site counting down to when tickets go on sale?

[tbostic32]

I think if it is a core functionality of the website then it would be considered essential. E.g., in a web page that is only a large clock counting down to new year then the text change of the clock would be essential.

some changes done

[WilcoFiers]

This still feels fairly open-ended. Who decides that something is important, and that the user shouldn't ignore it? I think I'd like to see a list here of scenarios what we think are essential.

[tbostic32]

I would agree, though the fact that it isn't objective helps with that some. I could add a few more examples so our total list would be the examples below. Would that be sufficient?

Important information:

1. Browsing session status (from definition)
2. Safety information (from definition)
3. Changing text which represents a core functionality of the web page, such as the time readings at https://www.time.gov/ or a countdown timer for an auction site (I'm not sure if this one works, as pausing it you should still be able to get something from the site)
4. A change in text when using collaborative systems, such as a chat messenger, forum, or other collaboration software.
5. A text change triggered by user input, such as selecting an option in a text-based adventure game.

Non-Important Information:

1. Stock ticker information (from definition)
2. Advertisements (from definition)
3. Live sports scores
4. "Rolling" updates such as job postings, or news article titles and links
5. Countdown timer to an event that does lose opportunity for the user, such as a countdown to the start of a sports game.

[WilcoFiers]

I like that, yeah that sounds good to me.

Changes were done

[WilcoFiers]

This is still open ended. What I was really hoping for here is a semi-definitive list of things that are essential. Anything that isn't on the list isn't essential. I tried to do something like that with the definition of essential text presentation.

[carlosapaduarte]

Agree that It is open-ended, but this is not an objective definition. Does it really have to be close-ended?

[carlosapaduarte]

Agree that It is open-ended, but this is not an objective definition. Does it really have to be close-ended?

[WilcoFiers]

We should have some examples for essential text changes passing the rule.

[tbostic32]

Coming back to this after way too long, I think this rule will actually be subject to the changes we are suggesting in the subjective applicability discussion. I think this would fall into the third category of "[Thing] is/has [subjective attribute]". In this case, filling in the blanks, it would be 'Text change is not non-essential'.

With this, we could move this into the applicability and not have to worry about having that test in the expectation which should really be there, and we wont need to include an example in the test cases.

[WilcoFiers]

Waiting for subjective applicability / state discussions to resolve before picking this back up.