[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [www.kde.org] [Bug 317553] www.kde.org webpages should not set font-size of unstyled body text and s
From:       Ingo Malchow <imalchow () kde ! org>
Date:       2013-03-30 1:02:39
Message-ID: bug-317553-17878-sfEYI7g6tP () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=317553

Ingo Malchow <imalchow@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |imalchow@kde.org
         Resolution|---                         |WONTFIX

--- Comment #2 from Ingo Malchow <imalchow@kde.org> ---
First, it is a lie that your first link doesn't provide a font-size to its body
or paragraphs. It does set some rem based font size.
Second, notice the difference between the links you provided and what the KDE
websites drive. A single column, no functions, no nothing, plain simple html
page. This is very well done, if you have nothing more than just some texts,
followed hierarchically. 
But it tends to break when you try to do complex layouts in a lot of different
CMS. And that is the situation with KDE, we have a lot of them, and a lot of
functionality that needs to be put somewhere, e.g. sidebars, horizontal bars,
buttons, boxes etc. Now imagine how hard it will get when you just try to
strike out any font declaration. Bad idea, especially considering, users
favourites are something between 6px and 20px... 

Then, the referenced page from www.kde.org does use an old theme, which is no
longer maintained. The newer themes use an em/rem approach, which is far more
flexible regarding dimensions.

Another point, we do use a specific font (on the new themes). We do so because
we believe it is the most readable font, not only aesthetically pleasing. This
of course removes the choice from the user, but for good hopefully.

So, all in all, valid points you raise, the maintenance horror overweighs
though. This is no screenreader blogpage, this is a set of around a dozen
different CMS that need to be themed and work properly. 

Oh, and i know the forum post, we have discussed there before. Rejected there,
rejected here. Any other accessibility request is welcome.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]