Section 508 Accessibility

We have a government client that requires our fillable PDF forms be Section 508 compliant. I have run the accessibility report on my end, using Acrobat 8 Pro, and the doc passes. On their end, it has one item that fails. I do not know what version they are using. They say they can fix this, but I have to unlock one section. However, as far as I can see, all sections of the PDF are unlocked.
Here is a link to the doc in question: http://asiflex.com/test2/fsadcap%20claim%20form.pdf
I've spent a lot of time messing around and googling for answers, but can't find anything. Any thoughts on how to remedy this would be greatly appreciated.

Quick clarifying question: When you ask about a potential third party tool to tag documents, are you looking for something that will automatically generate tags or allow you to manually set them? I would assume that you would want to manually set them as automatic tagging isn't the best for creating Section 508 compliant reports.
Acrobat Pro has tagging capabilities on PDFs that were created using other applications. You can read about it in the following document. This was based on Acrobat Pro 6; however, the same principles should apply.
[http://www.adobe.com/enterprise/accessibility/pdfs/acro6_pg_ue.pdf|http://www.adobe.com/enterprise/accessibility/pdfs/acro6_pg_ue.pdf]
I am continuing to research your options and will get back to this thread shortly.
Coy

Similar Messages

[JS][CS5] Enhancing Section 508 accessibility of pdfs from InDesign script

I was using a script to automate mapping styles to tags and tagging graphics as artifacts or as figures with Alt attributes for section 508 accessibility reasons, but in order to encourage use by designers, I wanted to add code to unlock all locked items in the document and then relock those items before the end of the script. Otherwise, the script would hang up when it encountered a locked item. I have an approach that seems to work, but is there a more elegant way of handling the locking and unlocking, especially for anchored and inline graphics?
Also, if anyone finds this code useful, I'd appreciate any feedback based on your use of it.
Preps an InDesign document for pdf output that is closer to section 508 compliancy.
This script acts on the active InDesign document. It removes any unused tags from the tags palette.
It unlocks everything that is locked.
It creates all necessary tags in the tags palette if they do not already exist.
It tags all untagged, placed graphics as either Artifacts or as Figures as follows:
Any graphic on a master page is tagged as an artifact.
Any graphic with a file name that contains either of two 4-character sequences, “art_” or “_art” (case insensitive) is also tagged as an artifact.
All other untagged graphics are tagged as figures and assigned an Alt attribute.
Graphics appearing on publication pages (not master pages) that were tagged prior to running the script will have an Alt attribute added to the pre-existing tag if it does not already have one.
The script relocks everything that the script previously unlocked.
It removes any existing styles-to-tags mappings.
It creates new styles-to-tags mappings for all paragraph styles based on the following paragraph style naming convention:
Every paragraph style is mapped to the P tag, unless the style name contains a prefix, suffix, or infix matching the format H2_ or _H1 (underscore character optional)
where the numeric digit indicates the level in the document hierarchy for the headings to which the style is applied.
Paragraph styles with names containing H1, H2, H3, H4, H5, or H6 are mapped to tags with those names.
The script then maps paragraph styles to tags based on the newly created mappings.
THIS SCRIPT IS MADE AVAILABLE ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED.
#target "InDesign-7.0" //for InDesign CS5
var markup_tag_names = new Array( "H1","H2","H3","H4","H5","H6","Figure","P","Story","Article","Table","Cell","Artifact");
var re_artifact = new RegExp("(ART_)|(_ART)", "i" );
var re_heading = new RegExp("(H[1-6]_?)|(_?H[1-6])", "i" );
var arraysAnchoredInlineGraphicsLockStatuses = new Array();
var d = app.documents[0];
d.deleteUnusedTags();
var arrLayersLockStatuses = d.layers.everyItem().locked;
var arrPageItemsLockStatuses = d.pageItems.everyItem().locked;
for (var k = 0; k < d.stories.count(); k++ ) {
 arraysAnchoredInlineGraphicsLockStatuses.push( d.stories[k].pageItems.everyItem().locked );
d.layers.everyItem().locked = false;
d.pageItems.everyItem().locked = false;
d.stories.everyItem().pageItems.everyItem().locked = false;
for ( var i = 0; i < markup_tag_names.length; i++ ) {
 zTag = d.xmlTags.itemByName( markup_tag_names[i] );
 if ( zTag.isValid ) continue;
 else d.xmlTags.add( markup_tag_names[i] );
var p_tag = d.xmlTags.itemByName('P');
var figure_tag = d.xmlTags.itemByName( 'Figure' );
var artifact_tag = d.xmlTags.itemByName( 'Artifact' );
var root = d.xmlElements[0];
for ( var i = 0; i < d.allGraphics.length; i++ ) {
 g = d.allGraphics[i];
 pg = g.parentPage;
 if ( pg == null ) continue;
 isOnMaster = pg.parent.constructor.name == 'MasterSpread';
 if ( g.itemLink.isValid != true ) continue;
 fname = g.itemLink.filePath;
 fname = fname.substring( fname.lastIndexOf(':') + 1 ); //Mac-specific folder separator ':'
 if ( g.associatedXMLElement == null ) {
 if ( isOnMaster ) {
 root.xmlElements.add( artifact_tag, g );
 else if ( re_artifact.exec( fname ) != null ) {
 root.xmlElements.add( artifact_tag, g );
 else {
 xmle = root.xmlElements.add( figure_tag, g );
 xmle.xmlAttributes.add('Alt', '' );
 else if ( ! ( g.associatedXMLElement.xmlAttributes.itemByName('Alt').isValid ) && !(isOnMaster ) ) g.associatedXMLElement.xmlAttributes.add('Alt', '' );
for (var k = 0; k < d.stories.count(); k++ ) {
 if ( d.stories[k].pageItems.count() > 0 ) {
 for ( var z = 0; z < d.stories[k].pageItems.count(); z++ ) {
 d.stories[k].pageItems[z].locked = arraysAnchoredInlineGraphicsLockStatuses[k][z];
for ( var i = 0; i < d.pageItems.count(); i++ ) {
 d.pageItems[i].locked = arrPageItemsLockStatuses[i];
for ( var i = 0; i < d.layers.count(); i++ ) {
 d.layers[i].locked = arrLayersLockStatuses[i];
d.xmlExportMaps.everyItem().remove();
for ( var i = 0; i < d.allParagraphStyles.length; i++ ) {
 var psty = d.allParagraphStyles[i];
 var rslt = re_heading.exec( psty.name);
 if ( rslt != null ) {
 rslt = rslt[0].replace("_", "");
 rslt = rslt.toUpperCase();
 d.xmlExportMaps.add( psty, d.xmlTags.itemByName(rslt) );
 else { d.xmlExportMaps.add( psty, p_tag ); }
d.mapStylesToXMLTags();

Are you running this in a persistent engine?
Have you tried wrapping the myDisplayDialog() call in a try/catch block to see if it is throwing an error?
I can provide all the relevant scripts if necessary, but they're pretty convoluted. The most important one is the user input function. Here it is:
It's quite common that the convolutions are related to the problem. A good exercise is narrowing it down to a small reproducible test case without the convolutions, and often as not you may find the problem in the process. If not, well, at least you'll provide something to test with.

Cp 5.5, Section 508 Accessibility - Is it possible to create a skip tag in the Accessibility dialog?

Hi,
We're working with a US Federal client so our Captivates need to fully Section 508 compliant. We've been able to work out strategies for all the elements of our course except one:
In order to auto-play each slide, then have it pause until the user chooses to move forward using the playbar, we've added a click box to each slide. We would like for JAWS to skip reading the click bos, since it is not used as anything other than an automatic pause. If we could use the Accessibility dialog to create a skip tag for the click boxes, that would be ideal.
Here's our experience so far:
If we leave the Accessibility dialog in default (Auto Label checked), JAWS read "click box" - acceptable but not ideal
If we uncheck Auto Label and leave Name and Description empty, JAWS reads "unlabeled button" - unacceptable
If we uncheck Auto Label and populate Name and Description with empty quotation marks, JAWS reads "quote quote" - unacceptable
Appreciate any techniques you've come up with -
Thanks,
KN

System board for use in models with 1 GB of discrete graphics memory 616244-001
System board for use in models with 512 MB of discrete graphics memory 608203-001
System board for use in models with UMA graphics 608204-001
http://h10032.www1.hp.com/ctg/Manual/c02437489.pdf
Graphics is built into the motherboard.
Can only upgrade with new motherboard.
Only a few laptops have graphics cards that can be up graded. "Like Alienware"
Good luck.
HP Expert Tester "Now testing HP Pavilion 15t i3-4030U Win8.1, 6GB RAM and 750GB HDD"
Loaner Program”HP Split 13 x2 13r010dx i3-4012Y Win8.1, 4GB RAM and 500GB Hybrid HDD”
Microsoft Registered Refurbisher
Registered Microsoft Partner
Apple Certified Macintosh Technician Certification in progress.

RH and Section 508

Hi -
I'm investigating Help creation tools for a customer and one
of the criteria is that the the HTML files that RH creates be
compatible for Section 508 accessibility standards for the web. I
suppose that includes that they could be read by a screen reader.
Thanks,
JL

Hi JL. If you are generating webhelp as your SSL you can
select the "Section 508 Compliant Output" option in the SSL
properties. You'd have to test that the output can be read by a
screen reader as I have no experience of this.

Can Adobe Forms Central produce Section 508 compliant web forms?

Hello! I've been investigating using Adobe Forms to create a survey for a product I'm creating. While I love the functionality available to me, when I tested the preview of the form I created, WAVE Accessibility Checker noted the form a lot of errors associated with it.
I'm curious if there is a method by which one can make the survey 508 Compliant, or if plans were in the works to add this functionality?

This page documents our level of 508 compliance:
http://www.adobe.com/accessibility/products/compliance/formscentral-section-508-vpat.html
Randy

Need Guidance on Section 508 Compliance (This is a "When" question - not a "How")

Hi, I've been doing a lot of research on Section 508 compliance and I am totally clear on how it is handled in Captivate. I am just not sure when it needs to be implemented.
I have a software demo I am working on that is basically, self-running. The user sits, watches, and listens. There are a few times when there is some user interaction (They have to click on something to go to another section or something), and I totally get implementing the accessibility features for those elements. What I don't get is, am I supposed to add accessibility to all of the other objects that appear on the stage during the self-running part of the demo? For example, if a visually impaired person were listening to my demo (the entire demo is narrated) would they really want their screen reader reading off elements on the screen at the same time?
Anyone who could shed some light on the types of accessibility features that should be enabled during narrated, self-running demos would be greatly appreciated! (Closed Captioning aside)
Thanks!
Vicky

Basically, the only need yo're addressing is for visually impaired users here, correct? Most visually disabled learners are going to turn off the audio on a presentation because it interferes with the screen reader.
The simplest way to test if the demo is accessible is to listen to the narration or read it without the visual cues. If you find there are elements that are not expressed in the narration that are necessary to the demo, you may want to create an accessible text equivalent that describes what is happening on the screen in addition to the narration, insert it in the slide notes for your project and create directions that highlight this option for those learners.

Section 508 Compliance - Spry Menu

I work for the government and am wondering if you could help
me figure out how I can (or if it's even possible) make the spry
menu features in Dreamweaver Section 508 Compliant, so that people
who have screen readers or Java Script turned off would still be
able to access the spry menu items. When we run the pages that have
spry menus through Dreamweaver's accessibility report it just
relays to us the fact that we are using Java script and we need to
provide a "noscript" tag. Do you have any ideas on how we could
accommodate this in our new web site design?
Thanks! Eleanor

See if this article helps you:
http://www.projectseven.com/tutorials/accessibility/pop_integrated/index.htm
Al Sparber - PVII
http://www.projectseven.com
Fully Automated Menu Systems | Galleries | Widgets
http://www.projectseven.com/go/Elevators
"luchenburg" <[email protected]> wrote in
message
news:g684j9$7jr$[email protected]..
>I work for the government and am wondering if you could
help me figure out
>how
> I can (or if it's even possible) make the spry menu
features in
> Dreamweaver
> Section 508 Compliant, so that people who have screen
readers or Java
> Script
> turned off would still be able to access the spry menu
items. When we run
> the
> pages that have spry menus through Dreamweaver's
accessibility report it
> just
> relays to us the fact that we are using Java script and
we need to provide
> a
> "noscript" tag. Do you have any ideas on how we could
accommodate this in
> our
> new web site design?
>
> Thanks! Eleanor
>
>
>

FrameMaker 8 - need new Section 508 guidelines

Dear Adobe,
My company may be interested in purchasing Adobe FrameMaker 8.
I need supporting information for Adobe FrameMaker 8 and Section 508 compliance.
The following link lists ONLY Adobe FrameMaker 7 anad Section 508:
http://www.adobe.com/resources/accessibility/tools/vpat/index.html
Could you please provide Adobe FrameMaker 8 and Section 508 compliance documentation?
Please also update your Web site with this information.
Sincerely,
Patricia
[email protected]

Patricia,
You posted your message into a FrameMaker user-to-user forum, not any kind of official Adobe area. Also, it isn't clear from your message whether you're asking if FrameMaker itself is 508 compliant, or if you can use it to produce 508 compliant documentation.
So you may want to go back to the Adobe site and find http://www.adobe.com/accessibility/ and call the 800 number on that page.
Cheers,
Art

Why can't I choose Section 508...

Hi,
I am trying to run a Section 508 Compliance Check using Adobe Acrobat Pro XI and do not have the option to change the name in the accessibility checker.
I can only choose categgories, not specific names.
Thanks for whatever help you can give!

Run the full check, but with the understanding that the Acrobat XI checker, while a big improvement over the X version, is still not very thorough. Selecting a subset of test criteria would merely render the checker even more inadequate.
For a much better PDF accessibility checker download the excellent, free PAC 1.3 from the Swiss foundation Access for All. You can find it here http://www.access-for-all.ch/en/pdf-lab/pdf-accessibility-checker-pac/dl132.html. PAC 1.3 tests for WCAG 2.0 compliance, but the 508 checklist maps to WCAG 2.0. You may notice that a newer version, PAC 2.0, is available but is still in beta and tests for more-difficult -to-meet ISO 14289 compliance. If you are interested, you can find the 508 PDF accessibility checklist here http://www.hhs.gov/web/508/accessiblefiles/checklistpdf.html.
Finally, even the best automated checker can get you no more than about half way to an accessible PDF. Automated tests can verify that a PDF is tagged using correct syntax, but cannot determine if the tags are otherwise correct, ensure correct reading order, or verify that alt text is meaningful – to site just a few examples. Careful, knowledgeable manual inspection of the tag structure is essential. The PAC 1.3 screenreader preview is a big help in the necessary manual inspection – it lets you see what an assistive technology user would hear.
Hope this helps.
a 'C' student

Section 508 Compliance using Flash

I am working on a website requiring Section 508 compliance
and will have some Flash content. I was wondering how it may be
possible to have text within the Flash file read to the user, much
like text HTML is read to the user using JAWS or a similar type
tool. Thanks so much.

It can be done, but it's a bit of a thorny issue. Here are
some places to
start reading...
http://www.adobe.com/accessibility/
http://livedocs.macromedia.com/flash/mx2004/main_7_2/wwhelp/wwhimpl/common/html/wwhelp.htm ?context=Flash_MX_2004&file=00000556.html
http://livedocs.macromedia.com/flash/mx2004/main_7_2/wwhelp/wwhimpl/common/html/wwhelp.htm ?context=Flash_MX_2004&file=00000565.html
http://www.rnib.org.uk/xpedio/groups/public/documents/PublicWebsite/public_macromediaflash .hcsp
Remove '_spamkiller_' to mail

ApEx and Section 508 compliance

1. Is ApEx section 508 compliant? 
2. Any documentation available on this topic? 
(Section 508: employees with disabilities need to have access to information and data in a manner comparable to the access and use by employees who are not individuals with disabilities) Vasan

Hello,
1. Is ApEx section 508 compliant? APEX can build 100% 508/DDA compliant applications. What Apex does not do is enforce 508/DDA compliance nor does it automatically insert accessibility features. Tab index's shortcuts to skip navigation , proper headings etc. This is left up to the developer to do so that you can properly address your application and or organizations accessibility requirements.
One thing that is sometimes a sticking point is APEX's use of javascript. While you can create an APEX application that does not use javascript it has quite limited functionality. APEX does follow Oracle's stance on accessibility and javascript.
http://www.oracle.com/accessibility/standards.html
JAWS testing has also taken place with APEX and with properly built applications and the applications work great.
2. Any documentation available on this topic? Building an accessible application in APEX is exactly like building an accessible application in any HTML environment. Set your tabindex's correctly, make sure data tables have proper headings , make sure that labels are properly linked to form items and such. There used to be a APEX and accisislbuity blog posting but I don't think it's available anymore. Searching this forum will also return you some results.
Most accessibility issues come from improperly constructed templates, and making sure that page report and label templates have accessible features usually takes care of most issues.
Our VPAT can be found here http://www.oracle.com/accessibility/templates/t780.htm and is currently being updated to cover all versions up to 3.1 , there have only been minor changes.
APEX is also going to start taking advantage of ARIA features http://www.w3.org/WAI/intro/aria so that developers can more easily create rich interactive applications that still can use AJAX and other DHTML features. But there is no reason you can't start including ARIA features in your applications today.
Regards,
Carl
blog : http://carlback.blogspot.com/
apex examples : http://apex.oracle.com/pls/otn/f?p=11933:5

Section 508 - Help

We are just beginning to work with Captivate and trying to
test the 508 compliancy issues. Does anyone know of a website that
used Captivate that is 508 compliant that we can run some tests
on?

Hello linwood,
Whilst I don't have any web sites I can point you to. Here is
information on what Adobe Captivate does to be Section 508
compliant.
What does Adobe Captivate do to be Section 508 compliant?
Selecting the 508 compliance option makes certain elements in
Adobe Captivate projects accessible or open to accessibility
technology. For example, if you select the 508 option and you have
filled in the project name and project description text boxes in
the Project Properties dialog box, a screen reader will read the
name and description when the Adobe Captivate SWF file is played.
The following Adobe Captivate elements are accessible when
the 508 compliance option is selected:
• Project name (derived from Project Properties)
• Project description (derived from Project Properties)
• Slide accessibility text
• Slide label (derived from Slide Properties)
• Buttons
Creating accessible projects 65
• Playback controls (function of each button is read by
screen readers)
• Password protection (if an Adobe Captivate SWF file
is password protected, the prompt for a
password is read by screen readers)
• Question slides (title, question, answers, button
text, and scoring report are read by screen
readers)
Note: Output generated with the Section 508 option will be
displayed with all supported browsers.
However, your output may not be Section 508 compliant unless
it is viewed with Internet Explorer.
Internet Explorer is the only browser with support for MSAA
(Microsoft Active Accessibility).
Note: To access Flash content using a screen reader, users
need to have Flash Player 6 or later installed.
I hope this is of some use to you.
Regards,
Mark

Section 508 compliance web sites info ??

Does anybody know the websites designed in APEX, which is Section 508 Compliant ??
Thnx

Hi,
Yes, I see what you mean now.
Unfortunately there is no easy way of rectifying this in 4.0.2. You will find that the situation is greatly improved from 4.1 forwards. Meaningful ALT's or empty ALT's have been added to appropriate images rendered by the engine for IRR's. For example those particular images make up the contents of a link, where the link text is already visible and available to assistive technologies, so the images are treated as decorative (alt=""), and thus ignored by assistive technologies. Also, I should say, considerable time and effort has gone into fixing accessibility related issues since 4.0.2 (and obviously a huge number of other improvements and fixes), so I would strongly recommend you try and upgrade, if it's at all possible. (Although, I know it's often not that simple.)
Regarding fac586's comments, yes definitely and thank you for pointing out those feature requests. Work in the last couple of releases has certainly been moving toward allowing for greater CSS customisation (although mainly with our native themes admittedly). And we've often talked about and wanting to update IRR's to use cleaner, more semantic HTML, using more modern JavaScript and CSS techniques and allowing greater customisation. (We have to be a bit careful with controls or icons that use CSS-served images, where the meaning is solely conveyed by the image, because of how Windows High Contrast treats them (it ignores them). But that's an aside.)
Sorry again I can't offer you more for 4.0.2, but I would definitely look at trying to upgrade if you can to be sure you're getting the most accessible output.
Also, please feel free to contact me directly if you ever want to ask anything accessibility related and I'd be happy to help.
Regards,
Anthony.

Does weblogic portal have section 508 mode

I've seen multiple posts regarding Plumtree's section 508 mode. Is there a similar mechanism in Weblogic Portal to make websites built with Portal to be section 508 compliant?

Regarding accessibility Portal is really far from compliant.
It insert tag in uppercase and this cerate pages that are not XHTML.
It does not write summary in tebles and this takes it out any chances of passing any validator from WAI.
The situation is not so good.
Hope that a patch comes soon since this problem is not so big really (expecially the uppercase of the tags)
Luca

SQL Developer Section 508 VPAT?

Is there a Section 508 VPAT available for SQL Developer?
Making this a "standard" in our organization would be easier if a VPAT is available...

If I understand correctly those are accessibility standards... 2 poorly implemented features in sqldev... so probably not.
Regards,
K.

Section 508 Accessibility

Similar Messages

Maybe you are looking for