RE: Proposed Final Design for W3C Technical Reports style in 2016

Hi Paul,

 

Good question, and thanks for beating me to the punch. I will ensure this is taken to the APA (formally PFWG) to ensure that happens.

 

JF

​-- 

John Foliot

Principal Accessibility Strategist

Deque Systems Inc.

 <mailto:john.foliot@deque.com> john.foliot@deque.com

 

Advancing the mission of digital accessibility and inclusion

 

 

 

From: Belfanti, Paul [mailto:paul.belfanti@pearson.com] 
Sent: Tuesday, November 10, 2015 11:18 AM
To: Carlos A Velasco <carlos.velasco@fit.fraunhofer.de>
Cc: Coralie Mercier <coralie@w3.org>; spec-prod@w3.org; chairs@w3.org; w3c-ac-forum <w3c-ac-forum@w3.org>
Subject: Re: Proposed Final Design for W3C Technical Reports style in 2016

 

+1 on the kudos for quality of the redesign and the accompanying documentation.

 

My only question/suggestion: has this undergone an Accessibility review? As much as I like the design some elements strike me as potentially problematic for someone with color blindness or vision impairment. 

 

Best,

 

Paul
-- 
Paul Belfanti
Director, Content Architecture
Core Platforms & Enterprise Architecture
office: +1 201-236-7746
mobile: +1 201-783-4884

 

On Tue, Nov 10, 2015 at 7:32 AM, Carlos A Velasco <carlos.velasco@fit.fraunhofer.de <mailto:carlos.velasco@fit.fraunhofer.de> > wrote:

Dear Coralie, all,

As already expressed in the list, I also welcome the new redesign of the specifications' stylesheets. I have just a couple of suggestions.

The first one would be to put the whole header sections into some kind of accordion tab that you can expand whenever you need that information (and please, do not forget the aria attributes). This will make the whole thing friendlier to mobile devices as well.

The second suggestion would be (for small screen sizes) to collapse under an icon the whole table of contents at the top, like the menus in most of the responsive design CSS frameworks. That will save also a lot of useless scrolling in such devices.

I also think that the "list of substantive improvements" should be somehow extracted in a help document so that "beginners" in editorial tasks can have at hand a list of best practices and their corresponding markups/styles.

On 10/29/2015 07:14 PM, Coralie Mercier wrote:


Dear Editors,
Advisory Committee representative, Chairs,

Back in May [1], we expressed our intention to update the style sheets
used by future W3C Drafts, starting on 1 January 2016. Elika Etemad
kindly agreed [2] to be the Design point person for 2015.

The final proposal from Elika is available:
   http://fantasai.inkedblade.net/style/design/w3c-restyle/2016/

A sample document is also available:
   http://fantasai.inkedblade.net/style/design/w3c-restyle/2016/sample

The list of substantive improvements is available:
   http://fantasai.inkedblade.net/style/design/w3c-restyle/2016/base.css

We welcome your feedback on the proposal by 27 November 2015 at the
latest, in e-mail to <spec-prod@w3.org <mailto:spec-prod@w3.org> > or using Github [3].

Thank you,

For Tim Berners-Lee, Director,
Philippe Le Hegaret, Interaction Domain Lead,
Elika Etemad, Design point person for 2015;
Coralie Mercier, Head of W3C Marketing & Communications

[1] https://lists.w3.org/Archives/Public/spec-prod/2015AprJun/0010.html
[2] https://lists.w3.org/Archives/Public/spec-prod/2015AprJun/0018.html
[3] https://github.com/w3c/tr-design/issues


-- 
Best Regards, Mit freundlichen Grüßen, Saludos,
carlos

Dr Carlos A Velasco
  Web Compliance Center
  Fraunhofer Institute for Applied Information Technology FIT
  Schloss Birlinghoven, D53757 Sankt Augustin (Germany)
  https://imergo.com/ · http://www.fit.fraunhofer.de/
  Tel: +49-2241-142609 <tel:%2B49-2241-142609>  · Fax: +49-2241-1442609 <tel:%2B49-2241-1442609>