W3C home > Mailing lists > Public > public-apa@w3.org > October 2020

Re: Accessibility Review Request for CSS Sizing Level 3 [css-sizing-3]

From: Carney, Amy L (EED) <amy.carney@alaska.gov>
Date: Fri, 23 Oct 2020 22:29:53 +0000
To: "public-apa@w3.org" <public-apa@w3.org>
Message-ID: <SJ0PR09MB61102B2DBA2FF1B952B8E6E5E61A0@SJ0PR09MB6110.namprd09.prod.outlook.com>
I'm on it.

-Amy Carney
________________________________
From: fantasai <fantasai.lists@inkedblade.net>
Sent: Friday, October 23, 2020 11:56 AM
To: public-apa@w3.org <public-apa@w3.org>
Cc: www-style@w3.org <www-style@w3.org>
Subject: Accessibility Review Request for CSS Sizing Level 3 [css-sizing-3]

Hi APA Working Group,

CSS WG requests Accessibility review of CSS Sizing Module Level 3
   https://urldefense.com/v3/__https://www.w3.org/TR/css-sizing-3/__;!!J2_8gdp6gZQ!8kEgmys22Bt2SouyrA5wqPnpr3ZYPlbwQjUmu-12FUhxWRzep6BNnrZnfClxhSAEzFyq$

This CSS module defines the various sizing properties and concepts used
throughout CSS. New features since CSS2 are summarized in
   https://urldefense.com/v3/__https://www.w3.org/TR/css-sizing-3/*changes-3__;Iw!!J2_8gdp6gZQ!8kEgmys22Bt2SouyrA5wqPnpr3ZYPlbwQjUmu-12FUhxWRzep6BNnrZnfClxheS-4wV_$

This specification is in the “almost CR” stage of development, so we expect it
to transition, in more or less its current form, after completing horizontal
review.

I don't expect accessibility to have much to say on any of this spec, except
that as enabling better control over content-based sizing as we're doing here
is good because it makes pages more robust to differing font choices. But in
any case:

Please raise any issues in the csswg GitHub repo:
    https://urldefense.com/v3/__https://github.com/w3c/csswg-drafts/issues__;!!J2_8gdp6gZQ!8kEgmys22Bt2SouyrA5wqPnpr3ZYPlbwQjUmu-12FUhxWRzep6BNnrZnfClxhRNkhrUK$
and let us know when you have completed your review.

Thanks!

= FAST Checklist =

If technology allows visual rendering of content:
* New keywords allow design of pages to more precisely use content-based
sizing algorithms, which improves ability to create resizeable pages.
* No other concerns apply.

If technology provides author control over color:
No control over color.

If technology provides features to accept user input:
No features to accept user input.

If technology provides user interaction features:
No user interaction features.

If technology defines document semantics:
Does not define document structure or semantics.

If technology provides time-based visual media:
No time-based visual media.

If technology provides audio:
Does not provide audio.

If technology allows time limits:
No time limits.

If technology allows text content:
Does not provide or define text layout.

If technology creates objects that don't have an inherent text representation:
Doesn't create objects that aren't text.

If technology provides content fallback mechanisms, whether text or other formats:
No fallback mechanisms.

If technology provides visual graphics:
Does not provide graphics.

If technology provides internationalization support:
N/A

If technology defines accessible alternative features:
N/A

If technology provides content directly for end-users:
I don't think this section applies...

If technology defines an API:
No APIs defined.

If technology defines a transmission protocol:
No transmission protocols defined.

~fantasai
Received on Friday, 23 October 2020 22:30:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 23 October 2020 22:30:12 UTC