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

Re: Review Request for CSS Text Level 3 [css-text-3]

From: Michael Cooper <cooper@w3.org>
Date: Wed, 7 Oct 2020 12:34:25 -0400
To: fantasai <fantasai.lists@inkedblade.net>, public-apa@w3.org
Cc: "www-style@w3.org" <www-style@w3.org>
Message-ID: <50dd22ff-af99-c299-369d-98e7fb205ba4@w3.org>
Thank you for your horizontal review request. The APA WG has reviewed 
this in the past and is comfortable with the document, so you can mark 
accessibility horizontal review as complete. We do appreciate that you 
took the effort to complete the FAST checklist even though it wasn't 
really relevant. :)

Michael

On 07/10/2020 1:44 a.m., fantasai wrote:
> Hi APA Working Group,
>
> CSS WG requests Accessibility review of CSS Text Module Level 3
>   https://drafts.csswg.org/css-text-3/
>
> This CSS module defines properties for text manipulation and specifies 
> their processing model. It covers line breaking, justification and 
> alignment, white space handling, and text transformation. By improving 
> internationalization and controls for typography, CSS Text Level 3 
> reduces the incentive for design-conscious authors to serve text as 
> images.
>
> 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.
>
> Please raise any issues in the csswg GitHub repo:
>    https://github.com/w3c/csswg-drafts/issues
> and let us know when you have completed your review.
>
> = FAST Checklist =
>
> Because the spec defines how text is rendered, but doesn't itself 
> provide any text, I wasn't able to check off boxes in the FAST 
> checklist the way it expects them. Here's responses per section in 
> sentence form:
>
> If technology allows visual rendering of content:
> * Non-visual rendering, resizing of content, pointers, cursors and 
> color are all out of scope for this module.
> * Text presentation attributes defined here can be used by authors or 
> users; these interact via the cascade 
> https://www.w3.org/TR/css-cascade/#cascading
> * Text wrapping and its controls enable changing content, resizing, 
> and other presentational shifts without losing readability. (Whether 
> the result is actually readable, however, depends on author decisions 
> and higher-level layout.)
> * Does not enable blinking or flashing.
> * No facilities for reordering content.
>
> 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:
> This module is not about whether to present text, but how to present 
> text when you do, so non-text alternatives are out of scope.
>
> 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:
> No graphics.
>
> If technology provides internationalization support:
> Afaict, no limitations here.
>
> 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 Wednesday, 7 October 2020 16:34:27 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 7 October 2020 16:34:28 UTC