W3C home > Mailing lists > Public > www-archive@w3.org > February 2016

Re: [css-transitions] Accessibility Considerations section

From: Janina Sajka <janina@rednote.net>
Date: Wed, 3 Feb 2016 10:41:11 -0500
To: "L. David Baron" <dbaron@dbaron.org>
Cc: www-archive@w3.org
Message-ID: <20160203154111.GA2259@opera.rednote.net>
Thanks, David. I appreciate your start on this, and I will follow up
with you. First step for me will be to raise your draft statement during
the APA call later today.

I'm really happy you thought to do this, I've been thinking there are a
number of W3C specs that probably should have a11y impact sections!

More soon.

Janina

L. David Baron writes:
> Janina -
> 
> I'm contacting you about this since you're chair of APA WG, and I'm
> not sure what the best point of contact for this is otherwise.
> 
> Given that current practice is to add sections on security and
> privacy considerations, I just added such sections to
> css-transitions.  While I was doing this, it seemed like an
> accessibility considerations section was also appropriate, so I
> added one as well:
> 
> https://drafts.csswg.org/css-transitions/#accessibility
> 
> Beware that I just wrote this and it hasn't had any review from the
> CSS WG.  It's also relatively short (5 paragraphs across 2
> sub-sections).  However, it seems like something that would benefit
> from review by one or two accessibility experts sooner rather than
> later.  (I'm particularly interested in whether I've characterized
> the issues in a reasonable way, and whether there are things that
> are useful to link to from such a section.)  So I'm hoping that
> you're able to forward this to an appropriate location or person so
> that that might happen.
> 
> Feedback is perhaps best sent to
> https://lists.w3.org/Archives/Public/www-style/ with cc: to me so
> that I don't miss it, although reply to this thread also works.
> 
> As far as specification status goes:  the CSS WG is hoping to take
> this specification to new-process CR relatively soon; the main
> blocker for that is that the editor (me) is behind on responding to
> comments.  I believe there have been some past discussions about
> this specification between PFWG and CSS, but I couldn't find the
> minutes.  I think I attempted to cover the issues that came up in
> those discussions.
> 
> Thanks.
> 
> -David
> 
> -- 
> 𝄞   L. David Baron                         http://dbaron.org/   𝄂
> 𝄢   Mozilla                          https://www.mozilla.org/   𝄂
>              Before I built a wall I'd ask to know
>              What I was walling in or walling out,
>              And to whom I was like to give offense.
>                - Robert Frost, Mending Wall (1914)



-- 

Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina@asterisk.rednote.net
		Email:	janina@rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
Received on Wednesday, 3 February 2016 15:41:46 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 3 February 2016 15:41:46 UTC