[css-cascade-4] transition effects, accessibility and the cascade…

Cross-posted to PF and www-style (I am not a member of the latter, and  
unless the CSS group thinks this needs internal discussion I think  
follow-up should go to PF only).

Hi,

this spec is in last call:  
<http://www.w3.org/TR/2015/WD-css-cascade-4-20150908/>

I had a look, and it mostly seems good. The new cascade order means that  
users can turn off animations, individually or en masse.

The one edge case concern I can imagine is where a transition is  
specified, which has some harmful effect (flash, movement, etc).  
Transitions are given the highest priority in the Cascade.

I *think* that in such a rare case, a user's !important transition would  
still override one supplied by an author, but I don't see that clearly  
 from the spec since it lumps all transitions together.

If that is true, a user can fix such a problem with a site-specific  
userCSS patch. If so, and given that people would have to work very hard  
to construct such a case (although I am pretty sure it can be done), I  
don't think that's a real problem.

It might be worth an informative note around the cascade, although there  
is already one elsewhere in the spec so that might just be cluttering the  
information.

cheers

Chaals

-- 
Charles McCathie Nevile - web standards - CTO Office, Yandex
  chaals@yandex-team.ru - - - Find more at http://yandex.com

Received on Wednesday, 9 September 2015 22:39:45 UTC