Article View: adobe.framemaker
Article #1373Accessiblity Tagging
From: Scott_Turner
Date: Mon, 15 Dec 2008 16:54
Date: Mon, 15 Dec 2008 16:54
5 lines
1348 bytes
1348 bytes
I am beset with a particularly clueless implementation of Accessibility requirements. The company I work for is required to support Section 508, yet the instructions they have produced are basically waving their hands over the subject without concrete guidelines. So I'm having to define these as I go. My question is: When tagging the paragraph tags for Accessibility, what kind of hierarchy detail is necessary? For instance, do I set a descending hierarchy from the heading tags down to the body text, and lump all of the body text, tables, bullets etc. under the same tag level? Or do I follow the structure of the document strictly, separating the body text from levels of bullets, steps, tables, etc?
Technical Details
Message-ID:
<59b74613.-1@webcrossing.la2eafNXanI>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news1.google.com!postnews.google.com!news1.google.com!news.glorb.com!feeder.erje.net!feeder1.news.weretis.net!newsfeeder.dynfx.net!weretis.net!news4us.nl!webcrossingShow Full Headers
Complete Article Headers
X-Google-Thread: fd315,99bde4aaaf73d4e3,start X-Google-Attributes: gidfd315,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit From: Scott_Turner@adobeforums.com Newsgroups: adobe.framemaker Subject: Accessiblity Tagging Message-ID: <59b74613.-1@webcrossing.la2eafNXanI> Date: Mon, 15 Dec 2008 08:54:51 -0800 Lines: 14 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Path: arc1-ca.pugleaf.net!g2news2.google.com!news1.google.com!postnews.google.com!news1.google.com!news.glorb.com!feeder.erje.net!feeder1.news.weretis.net!newsfeeder.dynfx.net!weretis.net!news4us.nl!webcrossing