[css-transforms-1] Add accessibility section

[IanPouncey]

The CSS Accessibility task force would like an accessibility guidance section added to this module.

The guidance would relate to WCAG 2.0/1 Success Criterion 2.2.2 Pause, Stop, Hide, indicating that in some circumstances a mechanism for pausing, stopping, or hiding moving content must be provided.

I think it will be possible to write standard guidance that can be applied to any module that enables movement or animation and the task force would be happy to help draft this.

[birtles]

I wonder, would it not be better to add this to CSS Transitions, CSS Animations, and Web Animations instead? CSS Transforms by itself does not produce moving content.

[tabatkins]

Yes, that's my thought. Nothing in Transforms "enables" motion any more than 'margin' does; transforms are just a (static) layout tool unless you apply an animation.

[IanPouncey]

The reason for including it here (as well as everywhere else you mention) is that the module does include examples of animation using transforms with SVG. I agree that it's not necessary to include this note in every module that includes a property that can be animated, but there is a specific case covered in css-transforms-1.

[tabatkins]

Ah, yeah, that's reasonable. I'd forgotten that section was even in there.

[dirkschulze]

I think we should remove this section entirely. There is no UA that implements animation of the transform attribute/property via <animate> or <set> nor did I hear any interest from UAs to do the implementation.

To animate transforms with SMIL, users may choose <animateTransform> which gets covered by a different specification SVG Animations.

Edit: Simple example https://codepen.io/krit/pen/qBWMZJZ

[css-meeting-bot]

The CSS Working Group just discussed ???, and agreed to the following:

• RESOLVED: Remove section on animation and wontfix issue about paragraph about accessibility because no longer relevant

The full IRC log of that discussion

<fantasai> Topic: ???
<astearns> github: https://github.com//issues/3870
<fantasai> krit: To summarize issue here, we ahve a spec where animations are appleid to transforms in the transforms spec with combination of SMIL
<fantasai> krit: but I think this entire section shoudl be removed
<astearns> s/???/accessibility section in transforms
<fantasai> krit: section introduces transform to the animate and set elements, both SMIL elements that refer to svg aniamtions
<fantasai> krit: in addition to what is in SVG already
<fantasai> krit: but there is no ? and no interest to implement
<fantasai> krit: so request to either defer or remove entirely
<fantasai> krit: if section gets removed, then there's nothing about motion in the spec anymore
<fantasai> AmeliaBR: issue is just asking you to add an accessibiltiy section?
<fantasai> krit: issue was about adding section about accessibility
<fantasai> krit: but we removed the section reference to motion, so no need for adding an accessibility section
<fantasai> AmeliaBR: one paragraph of animating transforms can be bad ?
<fantasai> fantasai: anything can be animated, width, margins, etc. do we add to every layout feature of CSS?
<fantasai> fantasai: I think better to keep in the animation section
<fantasai> AmeliaBR: so requesting to clsoe this issue as wontfix and follow up with getting it addressed in CSS Animations
<fantasai> krit: yes, but request woudl be to defer the entire feature
<fantasai> krit: if we want to do that, would suggest to try with SVGWG or SVGCG first
<fantasai> AmeliaBR: so other feature request is adding way to pause CSS Animations, which we don't currently have
<fantasai> krit: right
<IanPouncey> q+
<fantasai> AmeliaBR: Dont' see why this should be deferred to SVG, CSS Animations has ...
<fantasai> fantasai: do we need to discuss all this with A11y?
<fantasai> krit: need to close issue no change beause moving teh section
<fantasai> IanPouncey: comment about documenting a11y concerns
<fantasai> IanPouncey: while I don't have a particular problem in this case
<fantasai> IanPouncey: just want to say the wya ppl use these documents is to find example they need and copy it directly
<tantek> I'm wondering if the request for the ability to "pause animation" also includes the ability to slow down the animation
<fantasai> IanPouncey: not going to look at different document
<fantasai> IanPouncey: in some cases we might want to have notes in multiple locations therefore
<fantasai> krit: would maybe put in boilerplate to add to every single module
<heycam> fantasai: if you put it in the boilerplate, it'll be at the top of the spec, and someone linking into the middle of the spec won't see it. maybe in the animation type definition?
<fantasai> fantasai: which is linked from propdef table
<fantasai> IanPouncey: happy to draft that note
<fantasai> AmeliaBR: I like fantasai's point, we do have a link from every CSS property definition "Animation Type", can put the note there
<fantasai> AmeliaBR: each spec item in the spec would be connected to the warning
<xfq> ack Ian
<fantasai> AmeliaBR: Proposal is wontfix on request to add a11y consideration section to css-transforms
<fantasai> AmeliaBR: for the remainder of the issue, request for pausing/stopping
<fantasai> AmeliaBR: that will be opened as new issue on Animations or Transitoins
<fantasai> krit: can only wontfix if remove the animation section
<fantasai> krit: so request is to remove animation section
<fantasai> krit: since feature that is added on top of SMIL and no interest form impelmenters and from community
<fantasai> astearns: so proposed to remove the section and wontfix the issue
<fantasai> AmeliaBR: can be moved to SVG Animations Level 2 which may or may not ever go anywhere
<fantasai> AmeliaBR: but that's where the text is lived
<fantasai> astearns: open a separate issue on that
<fantasai> astearns: for this particular issue, remove section and wontfix
<fantasai> RESOLVED: Remove section on animation and wontfix issue about paragraph about accessibility because no longer relevant
<fantasai> astearns: out of time

[dirkschulze]

As discussed during the CSS WG meeting: We did agree that there should be text in the CSS Transitions spec (which already has a section) and CSS Animations spec with a description of the issue and a reference to the accessibility guidance. If possible, the text should be easily accessible from all motion affected properties (for instance when following the link for "Animation type" that is already set on all CSS properties in updated specifications).

We also acknowledge that UAs should provide an option to mute/pause/slow down motions and will work on it as part of the mentioned specification.

With the removal of the SVG Animations sections from CSS Transforms we agreed that there is nothing to do for CSS Transforms right now.