Accessibility and Validation

Question

QUESTION ONE: How does one test for proper accessibility?
(See Background)
QUESTION TWO: Why I am obtaining an error code for my
<p> tag when I go to validate for HTML? (See Error Message)
BACKGROUND
I have been playing around with floated images, div tags,
wrappers, and the like in an effort to obtain a better
understanding of how CSS styling works. One of the issues of image
placement that I have run into, though, is accessibility. Although
I can readily see the alt and longdesc attributes in my <img>
tag, I can think of no way to test how these might appear to those
for whom accessibility might be an issue.
ERROR MESSAGE
"The Validator found an end tag for the above element, but
that element is not currently open. This is often caused by a
leftover end tag from an element that was removed during editing,
or by an implicitly closed element (if you have an error related to
an element being used where it is not allowed, this is almost
certainly the case). In the latter case this error will disappear
as soon as you fix the original problem."
SOURCE:
http://homepage.mac.com/moogoonghwa/practice/CSS/floatedImageInParagraph.html
Roddy

Answer 1

> Do you always do it that way? I.e. if you think that a
style is only
> used once on a page you use an ID? What if you change
your mind later or
> a change of the markup requires a second element with
that style?
Usually, yes. Of course, I never change my mind. I always
'Stay the
course'....
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"Michael Fesser" <[email protected]> wrote in message
news:[email protected]...
> .oO(Murray *ACE*)
>
>>> Are you forgetting that there is a caption with
the image?
>>
>>Yes. I think it's fine in that case. I would have
used an ID for the
>>selector UNLESS it's your intention to reuse the
"image" class on the
>>page.
>
> Do you always do it that way? I.e. if you think that a
style is only
> used once on a page you use an ID? What if you change
your mind later or
> a change of the markup requires a second element with
that style?
>
> I more and more tend to prefer classes over IDs, mainly
because of
> specificity issues. I only use IDs for the big
structural elements on a
> page (header, nav, content, footer etc.), form elements
or if I need an
> anchor for a link. The rest is done with classes, even
if a particular
> class is only used once on a page.
>
>>By the way, fully justified text can be harder to
read, and can look funny
>>at time with the inter-word spacing....
>
> Indeed. The result might
> look really ugly because
> of the gaps, especially
> if there are
> some_really_long_words
> which can't be broken.
>
> For wider paragraphs it works quite well, but with a
short width it can
> get really ugly because no browser does automatic
hyphenation yet.
>
> There are ways to do that, though, and the result can be
quite
> impressive. Here's an example based on JavaScript which
performs
> hyphenation like in LaTeX:
>
>
http://www.mnn.ch/hyph/silbentrennung1.html
>
http://code.google.com/p/hyphenator/
>
> Micha