WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: use of <pre> tag

for

From: Hoffman, Allen
Date: Nov 5, 2010 12:48PM

The logic chain here doesn't mean current Section 508 standards require
HTML mark up for inline textual information, however, As my previous
email indicated, such content can meet existing standards, it is not
likely to keep meeting accessibility standards for very long. Even if
you had top and bottom of page navigation with skip-navigation links to
start of pre tags it would be 508 compliant in principle, but in
practice its bad.

At the Department of Homeland Security we do not fail such content for
section 508 compliance. It is, again, not good practice however.







-----Original Message-----
From: Julie Dodd [mailto: <EMAIL REMOVED> ]
Sent: Friday, November 05, 2010 11:26 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] use of <pre> tag

Thank you again, Andrew!

Your reply is very much appreciated.

Julie

On Nov 5, 2010, at 8:20 AM, Simius Puer wrote:

> Hello again
>
> I looked a little further and found what I was looking for:
>
> *Section 508*
>
> (k) *A text-only page*, with equivalent information or
> functionality, *shall
> be provided* to make a web site comply with the provisions of this
> part, *when
> compliance* *cannot be accomplished in any other way*. The content
> of the
> text-only page shall be updated whenever the primary page changes.
>
> *Pass*
>
> A text-only version is created only when there is no other way to
> make the
> content accessible or when it offers significant advantages over the
> main
> version for certain disability types.
>
> *Fail*
>
> A text-only version is provided when the main version is not
> accessible, but
> could be made fully accessible.
>
>
> ....put all the bits together and it does require semantic mark-up.
>
> Hope that helps clarify the case regarding Section 508 and makes
> your case
> that bit stronger.
>
>
>