Re: SC 1.4.11

> In fact, changes of state MUST be properly communicated (and perceived) to and by all users. That is exactly why we have role, STATE, and property in ARIA (to accommodate non-sighted users),

Agree.

> therefore I will assert, for sighted users the argument could be made (I'm making it) that state is indeed visually separate i.e. we get differing visual values/cues when state changes, just like we get differing aria-state (audio) values/cues when state changes.

As I think you said before, it doesn’t have to be. It could be visually part of it, around it, even somewhat visually separate. Buit it isn’t necessarily one or the other.

I agree there has to be a dfiference that the person can spot, but it doesn’t help us with the language of the exception and how people interpret that.

If you agree that the language around ‘nature’ is essentially role, then the definition of state is that it is “of” the component.

If you then assert that any change by the author means the exception doesn’t apply, then the list of ‘absurd’ outcomes I put before also apply.

-Alastair