W3C home > Mailing lists > Public > www-archive@w3.org > June 2015

[wbs] response to 'TR Design Survey'

From: Michael Cooper via WBS Mailer <sysbot+wbs@w3.org>
Date: Tue, 09 Jun 2015 20:42:01 +0000
To: www-archive@w3.org
Message-Id: <wbs-5c02504a1a811dfab8fc269a21f1d509@w3.org>
The following answers have been successfully submitted to 'TR Design Survey'
(public) for Michael Cooper.

> 
> ---------------------------------
> Group
> ----
> 
> On behalf of which W3C Working Group are you answering this survey?
> 
> 
> 
 
Protocols and Formats

> 
> 
> ---------------------------------
> Sample(s)
> ----
> Paste in URLs to a representative sample (1-3 links) of your specs. If
> styling differs substantially between /TR and your editor's drafts,
> please link to both versions. 
> 
> 
 
http://www.w3.org/TR/core-aam-1.1/ particularly mapping tables, in two
incarnations flipped by script
http://www.w3.org/TR/wai-aria-1.1/


> 
> 
> ---------------------------------
> Specification Processor(s)
> ----
> What spec pre-processor(s) does your WG use?
> 
> 
 
Respec

> 
> 
> ---------------------------------
> Group style sheet(s)
> ----
> Paste in URLs to any WG-specific style sheets you use.
> 
> 
 
https://raw.githubusercontent.com/w3c/aria/master/common/css/common.css
https://raw.githubusercontent.com/w3c/aria/master/common/css/mapping-tables.css
https://raw.githubusercontent.com/w3c/aria/master/core-aam/css/core-aam.css
https://raw.githubusercontent.com/w3c/aria/master/html-aam/css/html-aam.css
https://raw.githubusercontent.com/w3c/aria/master/practices/css/aria-apg.css


> 
> 
> ---------------------------------
> Like
> ----
> What do you like about your current styles?
> 
> 
 
Support readability by making inline elements with special meaning more
visually distinct (e.g., role, state, and property references).

Support readability by increasing spacing in certain situations,
particularly padding.

Calling out important features like notes and editorial notes (two distinct
concepts btw).

> 
> 
> ---------------------------------
> Dislike
> ----
> What do you dislike about your current styles?
> 
> 
 
Difficult to tell heading level from style.

> 
> 
> ---------------------------------
> Complex style
> ----
> Paste in URLs to any parts of your spec that are stylistically complex or
> tricky, and we should therefore be careful not to screw up.
> 
> 
 
http://www.w3.org/TR/core-aam-1.1/#h-mapping_role_table has a table that
can be presented in two ways, both of which we want to preserve.
http://www.w3.org/TR/wai-aria-1.1/#alert tables have both row and column
headers that are meaningful.

> 
> 
> ---------------------------------
> Table style
> ----
> The new styles will include rules for rendering data tables. These will
> be opt-in by class name, and rely heavily on good markup (use of THEAD,
> TBODY, COLGROUP, scope attributes, etc.). See Simple Example, Less Simple
> Example, and Extra-Complex Example. Paste in URLs to a sampling of any
> data tables you are using so that we can try to accommodate those in the
> styling, if practical. 
> 
> 
 
Same as above:

http://www.w3.org/TR/core-aam-1.1/#h-mapping_role_table has a table that
can be presented in two ways, both of which we want to preserve.
http://www.w3.org/TR/wai-aria-1.1/#alert tables have both row and column
headers that are meaningful.

The styles suggested look ok but the above specs probably wouldn't be able
to opt into them for the most part. As long as they're opt-in that's ok.

> 
> 
> ---------------------------------
> CSS WG Style
> ----
> The CSSWG has made a number of minor improvements to the existing spec
> styles, which we might just adopt wholesale. Please comment on what you
> like/dislike about these styles, as demonstrated in the CSS3 Text
> specification.
> 
> 
 
Do not like the narrow centered column of text. While I appreciate that
wide lines are hard to read, it's jarring to have my browser set a certain
size and yet have the rendering just have a bunch of unused whitespace.
I've set my browser to the width that is most useful for me and the styles
should presume that.

Permalinks to the left of the heading are distracting. They should be to
the right of the heading, after the heading itself in the reading order.

There are various colored sections that is not apparent what the different
colors mean. The styles themselves are ok but without a "key" they raise
questions that interrupt reading.

Multiline figure captions that are centered are hard to read.

I did not check the WCAG luminosity contrast of all color combinations. On
quick sample they look good overall, but the final proposed TR stylesheet
will need a careful check on this front to be sure.

> 
> 
> ---------------------------------
> Anything else?
> ----
> 
>     Is there anything else we should consider?
> 
> 
> 
 
Consistency with W3C recognized TR style will be important, so documents
are still recognized as W3C TR documents.

Not over-developing styles, that make it harder for WGs to provide custom
features when needed.

On the other hand, providing styles for common usages like notes and
examples is very helpful so, lacking a reason to do otherwise, WGs can
choose to use a recognized W3C-wide approach.

Documenting the available styles and / or a sample page showing them all
for editors will be important. Also need to indicate which must not be
overridden or ignored (e.g., heading styles), and which may be (e.g., note
styles).

> 
> These answers were last modified on 9 June 2015 at 20:41:25 U.T.C.
> by Michael Cooper
> 
Answers to this questionnaire can be set and changed at
https://www.w3.org/2002/09/wbs/1/tr-design-survey-2015/ until 2015-07-07.

 Regards,

 The Automatic WBS Mailer
Received on Tuesday, 9 June 2015 20:42:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:35:20 UTC