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

Similar Messages

Removing numerals/garbage characters from search in Section 508 build WebHelp

I need to remove (prevent inclusion of) numerals and garbage characters from search results in WebHelp when compiled with Section 508 Output enabled. I need to have Section 508 enabled. Can that be done?
Thanks for your time!

Thanks, Jeff. I tried including the characteres in the Stop list and recompiling. (I even closed the project and reopened.) The characters still appear. The characters I'm trying to remove are: !, #, ', (, ), -, /, :, ;, and ,. I am also trying to exclude some numbers (100.00usd, 1999.99, 2999.99, 3999.99, 4999.99, and 6pm).
The Stop list consists of those characters and the default text. Forgot to mention is the first post ... I'm using RH9.
The Section 508 flag does create 508-compliant HTML output and that is one of the requirements for this help system. This is the first time I am enabling this flag.

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
>
>
>

Is there a forum for Captivate that specifically addresses Section 508 compliance issues?

I currently use Captivate 5.5 and would like to get ahead of the 508 issues that may arise and be able to go to a forum or site that may have similar questions, and hopefully answers.

No such forum. Shoot your queries here, you might get the required help. There are couple of Section 508 specialists here.
Sreekanth

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 Search ability

I'm brand new to RoboHelp (v6), so forgive the elementary
question. The "Search" function for Section 508 compliance appears
to be limited, to put it nicely. The results appear to be similar
to an Index, only much less helpful, returning words like "above"
and pages upon pages of other unhelpful words we used in our topics
like "system". I understand the need to create a Stop List for
these terms for the Index. However, before getting in too deep with
RoboHelp I was hoping someone could validate that entering terms in
the Stop List for the Smart Index will remove the terms from being
picked up in the Search function? For some reason the documentation
doesn't make that clear and I'm unable to test it because of a
separate issue posted to the forum. Also, because Section 508 is
the requirement and a non-508 webhelp is not desired for any other
reason than to implement a search using a text field (for non-508
users, of course), is it less of a maintenance hassle in the long
run to implement a third-party tool like ZoomSearch, or is a
non-508 webhelp option better?

Hi again
No, I'm pretty sure you aren't the first to ask. But what we
have is what we have. So it's either use that or develop your own
custom implementation.
You (and others) are strongly encouraged to voice your
concerns or desires to the RoboHelp development team. How? Why I'm
so happy you ask! You
Click
here and complete the form you should find there.
Cheers... Rick

ADA & Section 508 Compliance Functional Group - ILLINOIS

Hello,
I have been doing extensive research on iTunes U and how ADA is implemented along with Section 508.
I have seen many other Universities implementing iTunes U but given that they are located in different states, I was thinking we should have functional groups (or special threads) for each state.
I believe this would help invigorate the iTunes U discussion and help create a knowledge base that is applicable to each state.
Thank you.

Hi,
Attached is my zipped project file. I did create my own buttons in Flash - this might be the problem. I have only been problem solving with navigation on the first four slides.
To clarify, hitting the Enter key does engage navigation, however I’m having difficulty controlling the navigation so that it goes to the correct location.
I’m using Captivate v.6 / publishing SCORM 1.2 / Using IE to deliver via the SyberWorks LMS.
Here is question 1:
Question 1
My question targets how to get the enter key to initiate after a successful tab. To be clearer.... I hit tab and I can navigate through all the buttons in the correct order, but hitting enter provides no action. I am getting the yellow highlights around buttons when I tab through. Everything works very well when using the mouse, but blind users don't use mice.
I did create my own animation buttons in Flash and imported them in as animations. I then placed a Click Box behind the button animation to engage the rollover action. Could this be causing problems? The prebuilt (and clunky looking) buttons on the quizzes do work (ie) tabbing to them and hitting enter provides effective navigation.
I'm opting not to use the playback control skin, only my Flash nav bar.
Thanks for reaching out!!
Thanks,
Bill Farrell (aka Calif Dreamin’)

Screen readable output (section 508)

Hi Everyone,
I've been tasked with finding a way of generating screen
readable output rom RH which is section 508 compliant.
By this I mean not having to use the mouse and use keystrokes
only. A customer has suggested that a tagged PDF was one of the
most accessible forms in which to deliver a help system. I'm not
convinced from previous experience and aalso at present PDF output
fails to complile anyway.
Any one tangled with this one? I am using RH6.

Thanks Colum and Peter for your prompt replies. I have
generated a web help output that is section 508 ticked but I still
seem to need to use the mouse. Mind you that's probably my lack of
experience! Any more thought greatly appreciated!

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.

Adobe Section 508 compliance check question

I've run the Adobe Section 508 compliance check on a document. The only errors I receive now are 5 tables without designated table headers. I click on the link to these tables, but nothing happens. It doesn't point me to the tables with the errors. Any help would be greatly appreciated. I'm using Adobe Pro v9.2.0.

I work at a college and have to create complex Section 508-compliant PDFs throughout the year. Though you've probably upgraded to CS6 or higher, I thought I'd share info on an ID plug-in that is very helpful with determining and setting the reading order from within ID. It is called "FrameMaker," by Rorohiko, and it puts a tiny label on each frame of a page. For example, if I select a frame, the reading order "number" will show on the top right of the frame. So I'll know immediately that I need to fix the order before creating a pdf.
Very inexpensive. Definitely worth the money.
http://www.rorohiko.com/wordpress/2013/09/17/easily-edit-stacking-order-of-page-items/
BTW: If you have to create text files from large ID files, their TextExporter is fabulous.

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.

OBIEE - Section 508 Compatibility

Hi,
I am trying to create a OBIEE dashboard using charts which is Section 508 compliant. Has anybody done this before? If so, do you have any guidelines that might be helpful?
Thanks

Check the certification matrix
http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/bi-11gr1certmatrix-166168.html

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

Is the OBPM Workspace application section 508 Compliant

Our customers need the application to be section 508 compliant. Is the out of the box ...OBPM workspace application compliant or would we have to build our own user interface and use papi to interact with BPM?

Meyers,
You will need to chat with either Oracle Support or PWC should have a Oracle Sales channel or something that can get you this information. I remember reading that they where heading in that direction... other than that it was not an issue for me.
Christopher Whiteley
[email protected]
P.S. How do you like PWC?

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 - Help

Similar Messages

Maybe you are looking for