pretty mailman listinfo pages?

Mon Apr 21 09:15:13 UTC 2014

Le 2014-04-20 19:04, Ahmed Fathy Hussein a écrit :
> On Fri, Apr 18, 2014 at 3:55 AM, Lydia Pintscher <lydia at kde.org> wrote:
> 
>> *poke*?
>> I am very unhappy that comments on this list have again killed this
>> project.

Lydia,

In general, comments by themselves should not and do not kill an 
individual's motivation to get involved. A comment can be constructive, 
relevant and valuable too even if some could consider those using a few 
"rough" words and ventilating irritation, legitimate irritation.

For whatever it's worth, I have in the past offered to help, to improve 
the style sheets (eg bootstrap.css) affecting KDE-www webpages. In more 
than 1 way. Not just its accessibility condition.
https://bugs.kde.org/show_bug.cgi?id=317553

>> Overall a completely unnecessary fail for KDE. This will not
>> happen again!

There is a need to update the style sheets affecting KDE-www webpages so 
that they honor and respect fundamentals of accessibility, notably and 
namely readability and legibility fundamentals. There is now a very 
large consensus, if not unanimity, arond fundamental principles of 
"readable-accessible" webpages.

"
There are many things that can contribute to the readability of a page 
such as font choice, line length, white space, paragraph markers, line 
spacing, kerning, contrast, and placement of images.
(...)
Research has shown that different letter spacing, stroke sizes, and 
x-height can have a positive effect on the readability of different 
sizes of text.
(...)
for example uses Sitka Small, which is designed with thicker strokes, 
larger x-height, and looser letter spacing, (...)
research has shown that reading speed increases at larger sizes (up to a 
plateau at very, very large sizes).
(...)
padding (white space) between columns, around images, and between 
paragraphs. The goal was for the page to feel clean and free of 
distractions, and this padding helps your eyes and brain quickly 
identify and distinguish the different elements of the article from each 
other, as well as provide cues for orienting your path through the text.
"
http://blogs.msdn.com/b/ie/archive/2014/03/04/introducing-reading-view-in-ie-11.aspx

I have said it before and I'm going to say it again in this mailing 
list: the most important factor of readability of a webpage is font size 
of its text and the most (and surest, most reliable) accessible way to 
choose a font size for each and all of its readers/viewers/visitors is 
to set it to 100% for unstyled body text. All browsers (IE9+, Firefox, 
Chrome, Safari, Opera, Blink) use now the same user agent style sheet 
rules for headings (h1 to h6) as far as font-size is involved:

Chrome 26.0.1410.63
*******************

h1 {font-size: 2em;}

h2 {font-size: 1.5em;}

h3 {font-size: 1.17em;}

h4 no font-size declaration

h5 {font-size: 0.83em;}

h6 {font-size: 0.67em; Appendix D gives font-size: .75em;}

body no font-size declaration

p no font-size declaration

pre no font-size declaration // monospace

input, textarea, keygen, select, button, isindex {font: 
-webkit-small-control;}

big {font-size: larger;} // Appendix D gives big {font-size: 1.17em}

small, sub, sup {font-size: smaller;} // Appendix D gives small, sub, 
sup {font-size: .83em}

Firefox 20 (see resource://gre-resources/html.css)
**********

h1 {font-size: 2em;}

h2 {font-size: 1.5em;}

h3 {font-size: 1.17em;}

h4 {font-size: 1.00em;}

h5 {font-size: 0.83em;}

h6 {font-size: .67em; Appendix D gives font-size: .75em;}

body no font-size declaration

p no font-size declaration

pre no font-size declaration // monospace though: font-family: 
-moz-fixed

form no font-size declaration

input {font: -moz-field;}

textarea {font: medium -moz-fixed;}

select {font: -moz-list;}

optgroup {font: -moz-list; font-size: inherit;}

input[type="image"] {font-size: small;}

input[type="file"] > input[type="text"], input[type="file"] > 
input[type="button"] {font-size: inherit;}

big {font-size: larger;} // Appendix D gives big {font-size: 1.17em}

small, sub, sup {font-size: smaller;} // Appendix D gives small, sub, 
sup {font-size: .83em}

Adapatability is Accessibility by John Allsop

http://web.archive.org/web/20010124093700/http://www.alistapart.com/stories/dao/dao_3.html

http://alistapart.com/article/dao#section6

"
Make pages which are accessible, regardless of the browser, platform or 
screen that your reader chooses or must use to access your pages. This 
means pages which are legible regardless of screen resolution or size, 
or number of colors (and remember too that pages may be printed, or read 
aloud by reading software, or read using braille browsers). This means 
pages which adapt to the needs of a reader, whose eyesight is less than 
perfect, and who wishes to read pages with a very large font size.
"

Absolute font-size like body {font-size: 14px} is widely known to be 2 
mistakes: not relative font size (it is not text-resizable in all 
versions of IE) and not honoring the users' preferred font size for 
unstyled body text.

Gérard
-- 
Konqueror Implementation Report of CSS 2.1 test suite (RC6): 9418 
testcases
http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/Konq-IR-CSS21TestSuite.html
54 Bugs in Konqueror 4.13.0
http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/
Contributions to the CSS 2.1 test suite
http://www.gtalbot.org/BrowserBugsSection/css21testsuite/
CSS 2.1 Test suite RC6, March 23rd 2011
http://test.csswg.org/suites/css2.1/20110323/html4/toc.html