E-mail List Archives

Re: Interesting cause: http://contrastrebellion.com

for

From: YOUNGV5@nationwide.com
Date: Jul 29, 2011 5:48AM


Got it. Very interested to find out more. Most every accessibility
evaluation tool cries about in-line styles We all have been taught to use
external style sheets for accessibility reason and have told others to do
so. I'd like to be able to point people to a definitive practical answer
why in-line styles are a problem. As of right now, I find it tough to do
so from an accessibility perspective.

Vincent Young
User Experience, Web Accessibility Specialist
Nationwide Corporate Marketing
Nationwide®
o | 614·677·5094
c | 614·607·3400
e | <EMAIL REMOVED>




From:
"Jukka K. Korpela" < <EMAIL REMOVED> >
To:
<EMAIL REMOVED>
Date:
07/29/2011 02:58 AM
Subject:
Re: [WebAIM] Interesting cause: http://contrastrebellion.com
Sent by:
<EMAIL REMOVED>



29.07.2011 02:06, <EMAIL REMOVED> wrote:

> @YUCCA - I'd like a little more explanation from you on the following
> comment:
>
> Inline styles have their problems, but how would it make a difference to
> set, say, some properties for a single paragraph using <p style="...">
> versus using <p id="foo"> and setting the styles for #foo in a style
> element or in an external stylesheet?
>
> Did you mean what difference would it make from an accessibility
> perspective?

Exactly. The differences from other perspectives have at most a
potential indirect influence on accessibility. If code is easier to
maintain, authors may have more time to devote to accessibility
considerations. But an author who wants to style an individual element a
bit, for some special reason, may well find it easier and more
maintainable to just slap in a style='...' attribute, instead of
inventing a class or id attribute and finding a place in a style sheet
to enter a CSS rule.

--
Yucca, http://www.cs.tut.fi/~jkorpela/