Export to flash "508 compliance" error?

If i export to flash i get the rather cryptic eroor: the
following elements in your project have not been converted. They
are not supported by this importer 508 compliance
(flash 8)

Hi there
You probably have Section 508 enabled along with possibly
some of the areas where information has been entered. I'm not sure
this is really an error. More likely, it's simply an advisory that
the 508 stuff doesn't survive the trip to Flash editing land.
Cheers... Rick

Similar Messages

Export from Flash Builder with Error Message

I was attempting to reduce my file size by removing the embedding. Got an error message when I tried to open it in Catalyst. "Flash Catalyst cannot open this project because it was created by an incompatible version of Flash Catalyst" Please help. Urgent.

Hey Blink,
Just to clarify, you completed the following steps:
1) opened your Catalyst project in Flash Builder
2) removed the 'embed' statements
3) exported as an FXP
4) Tried to re-open in Catalyst?
We currently do not support a roundtrip workflow between Flash Catalyst and Flash Builder.
Meaning once you open a Catalyst created project in Flash Builder, you can't bring it back to Catalyst for editing.
We know this is really, really important to our users and it is on our list.
Blink, let me know if this answers your question. If the steps I listed are incorrect, and you did not in fact open your project in Builder, let me know.
Are you using beta 1 or beta 2? Flash Catalyst 1.0, available today, contains a feature which allows you to toggle your images between 'embedded' and 'non-embedded'. You can right click an image in the library panel to 'convert it to a linked image'.
Thanks for posting!
Tara

Export error when exporting to Flash

Hi there,
I'm trying to export a 14 slide Keynote presentation to Flash. Every time I try it allows me to choose a place to save it, but then comes back with the message:
Export Error
The file format is invalid
Nothing gets exported.
Any ideas gratefully recieved.
Thanks,
Mark

Hi medicineball and welcome to our community
You said:
Really what good is this product if you can't export to
Flash?
Believe it or not, this product can actually be used quite
satisfactorily without ever needing to export to Flash. I'm
guessing you are of the camp that views Captivate as simply a
"Flash add on" that is used only as a mechanism to move something
into Flash for subsequent tweaking. While this is certainly
possible, it was never the primary intent. Had that been the case,
you would see much tighter integration between the products.
Now before I instigate a long tirade about how this is Adobe
and they are huge and should make all their products work
seamlessly together, I'd like to point out that they are dealing
with a product that has had at least four different owners. So the
tight integration isn't there yet, but they are making strides.
Sincerely... Rick

Error in export to Flash MX 2004

Hi,
While exporting to Flash MX 2004 it shows an dialogue box "
To export a Captivate movie to flash, you should have Macromedia
Flash MX 2004 installed."
Even though I've Flash MX 2004 already installed on my
machine, this error shows. How can I get an FLA output from
Captivate ?
FYI: I am making a screen capture movie like elearning
course.

Hi Guys!
Greg said ...
quote:
I wonder if Captivate 2.0 will import a Captivate 1.0 and then
export to Flash with the tweens intact? Any idea yet?]
Hey
Rick, you only made one mistake (but for you even that is
rare). Greg said
"with the tweens intact" ... and you read
"... when tweens interact.".
I'm sure you'll agree that with the clarification, it's not
confusing except the extent to which Greg expects or desires that
movement of objects - including "transitions"? - in the original
Captivate project be preserved after bringing it into Flash 8. As
far as CP1 - to - CP2 - to Flash 8 is concerned, CP1 projects seem
to me to be converted very well. And moving the (now CP2) project
conversion into Flash 8, there is little that won't come along
nicely.
Yes, Greg, including the tweens, which are preserved for the
objects I looked at specifically ... but the right person to answer
that question might be Mark (Fletcher) instead of myself. I
imported CP movies to Flash 8 only to see if it was being done
without the previous loss of non-supported elements (etc.) but I
have no intention of actually working with my Captivate projects
inside the Flash environment - during beta, now, or ever. I just
feel that the power of Captivate is sufficient for my purposes, and
importing it to Flash 8 would accomplish little except to put the
horse in hen-house. (That makes perfect sense to me, and is greatly
humorous as well; but if you don't "get it", I don't think I can
explain it.
.

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

Error when trying to export as Flash

I'm attempting to export my very small test project as Flash, but two errors occur:
1. Adobe Encore has encountered an error. [..\..\src\AMEEncoder.cpp-2359]
There is only a "Continue" button to click, so I click it and the Build Progress bar finishes and states "Completed". I then click "OK" and get this second error:
2. "An input contract violation has occurred!"
There is only an "OK" button to click, so I click it and that's it.
I try to play the swf or index.html that was created and though the Flash build opens to my main menu, complete with correct navigation and highlights states, their respective videos do not playback when selected from the menu. Only a blank black screen appears. If I click Pause or Play respectively, nothing changes, but I can select the "Next" button and it initiates my set end action for that clip and correctly returns me to the main menu. So, some of the settings stick, but video playback does not.
Some other info about this Encore project:
From Premiere Pro CS3, I used the "Export to Encore" export option. I selected "Author With Menus", and changed my Encoding Settings to a custom setting of:
NTSC, 720x480, 29.97 drop frame [fps], Progressive, Quality 5.0
192 [kbps], 48kHz, 16 bit, Stereo, MPEG
CBR, 9.00 [Mbps]
It successfully encoded without error and opened Encore and such.
Hope I have provided enough info...

Hey Neil,
Thanks for replying. When I author DVD's, I use the basic encoding standards you listed above.
In this case, since the output is not written media, I was encoding in a way that would give me the best possible results (in theory at least) when planning on flv being the final encoded output, where lowest possible file size with best possible quality is the goal (since it's home will be on the web, not a DVD).
As for my issue with the errors generated from the Export to Flash option, I have learned some things, and was able to successfully Export to Flash.
One thing is that apparently the Flash encoder that EncoreDVD CS3 uses is not the same as the Adobe Flash CS3 Video Encoder or whatever Flash encoding engine Premiere uses. Encore's Flash output settings are limited, and so are the results.
What I had to do was export my PP CS3 projects to Flash using Adobe Media Encoder and update the XML that Encore spits out accordingly to point to my newly encoded flv's, replacing the flv's that Encore created... not a big deal, but one extra step and little more waiting time.
Now, the results are stunning! And since I'm not comfortable in Flash CS3 or coding ActionScript, having Encore create the menu interface, with all the navigation and interactivity and such, for me was a big BIG plus!

Float4() causes "error saving Pixel Bender Byte Code file" error when exporting for flash player

Simple test
<languageVersion : 1.0;>
kernel untitled
<   namespace : "Your Namespace";
    vendor : "Your Vendor";
    version : 1;
>
    input image4 src;
    output pixel4 dst;
    void
    evaluatePixel()
        dst = float4(sampleNearest(src, outCoord()));
The above code will produce a "error saving Pixel Bender Byte Code file" error when exporting for flash player in Pixel Bender Toolkit 2.5.449694.
"dst = (sampleNearest(src, outCoord()));" works fine. And anything like "float4 a= float4(b);" will give same error.

Thank you for the error report. I'll put it into our bug database. We're bottling things up for the current version. Gven the workaround, it is unlikely we'll be addressing this bug soon. Please accept my apologies for the annoyance this will cause.
In your second example, float4 a = float4(b), does it return an error if b is only a float4 or regardless of what b is? If b is a scalar float, for example, is the conversion performed correctly? If so, this could be an error that only crops up when using constructor/conversion syntax when the thing being converted is already the correct type.
Thanks,
Chuck.

Captivate 4 export to Flash CS4

Hi,
I am encountering a few problems with Adobe Captivate 4:
- In the previously version it was possible to export a project into different smaller swf files. Is this also possible in Captivate 4?
- I am trying to export my project to Flash CS4 but I get the following error:
The following elements in your project have not been converted. They are not supported by this importer.
508 Compilance
After that I won't be able to see the mousemovents and hint boxes.
- I am not able to play the swf file in internet explorer on windows XP machines. In the previous version it was possible to safe the skin as bitmap, that worked in windows XP. Is this also possible in Captivate 4?
Can somebody help me with one of these problems?

Hello, I'm not able to answer all of your question, but will give it a try:
What do you mean by 'exporting to several small swf's'? I do not know this functionality, have been using CP since version 1. Perhaps you are talking about the splitting up when having FMR recordings: every FMR would end up in a different SWF in CP3. This has been removed in CP4, but if you want really to have the files separated, you can activate 'Externalize resources, part FMR SWF' in the Project, Preferences, Publish settings. You can also externalise skin, widgets and animations.
508 Compliance has something with accessibility options. Here I'm not sure at all, why there are problems with exporting to Flash CS4.
Problem with playing CP-movies can be due to Flash Security Settings or to the Flash Player installed compared with the Publish settings (for which Player?).
I believe that BMP has been abandoned for playbars because of lower quality. You have to use a playbar, could use the TOC (instead or in combination with the playbar) or have your buttons on the slides (some of the widgets perhaps).
Perhaps someone else could complete this answer,
Lilybiri

ADA 508 Compliance Workflow Overview (tab key for navigation / WebAim Toolbar)

Hi,
I've been assigned to update interactive training for a State agency..... with of course, an emphasis on ADA / 508 compliance.
So, before I pinpoint my two questions/scenarios, here is a basic, initial attempt at providing an overview of ADA compliance workflow in Captivate and beyond.
PS - useful Captivate forum urls are at the end of this post. I'm using Captivate v.6
ADA Compliance Workflow Overview:
1. All assets need an alt tag and conceivably a description > highlight the asset, like a pic, and click the Accessibility button under Properties.
2. Create slide notes for each slide > load slide, highlight no assets and click the Accessibility tab under Properties. Copy and paste your notes > for screen readers.
3. Need closed captioning for video/audio content > I use Camtasia for CC and will use the JW player for screen reader of video content.
4. Interactivity needs to be accessible via the tab and enter keys.
What else am I missing?
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 gettining 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.
Question 2 (Scenario 2)
I have downloaded the WebAim Toolbar feature designed for FireFox, used to check ADA compliance issues.
I am getting this error message:
A frame does not have a title attribute or value. Okay... I bet I can fix this via the .html file or via the standard.js file??
and these warnings:
Alert: Javascript in head - A javascript element is present in the page head section.
Alert: Flash - A Flash object is present.
Does anyone know if these alerts are worth fixing?
Obviously Captivate is going to pump out, or rather publish... javascript elements, but is this bad in the page head section?
And..... of course a Flash object is present...Captivate produces Flash / Shockwave files.
I'll obviously ask the programmers at WebAim for guidance as well. As always any help would be appreciated and Tanks in advance.
http://forums.adobe.com/message/117985#117985
http://gneil.blogspot.com/2008/09/target-6-million-settlement-is-your.html
http://kb2.adobe.com/cps/403/kb403160.html
http://forums.adobe.com/message/3515968#3515968
Screen grabs are attached.
Thanks, Calif Dreamin'

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

Exporting to Flash Question.

My client created individual Captivate demos. I would like to
import them into flash and place them on a custom background with
logo as well as build a flash menu to jump from Captivate section
to section.
I'm wondering if when exporting a file to flash then opening
up in the Flash environment how will Flash build/ display the
content on the timeline, how much can I edit it and will it publish
out of Flash and display fine? Is there anything from Captivate
that will get lost in this process such as audio or playback
quality, etc.... I would try this myself but I'm on a Mac, our PC
has the Captivate demo with no flash (I believe you need both
programs in order to have the export option available) and I don't
want to purchase flash for this computer if it won't do what I need
it to.
Hope someone can help,
Thanks,
Jason

Hello Jason,
Please find below the current Captivate 2 Export limitations:
508 compliance: At this time none of
the 508 compliance extensions export to Flash. If this is a
critical aspect of your project, you may want to consider other
options to address all of your accessibility requirements in Adobe
Captivate.
Interface skin: Skins are not
exported through the Flash export function. This means that if your
project uses the new Adobe Captivate 2 menu feature of skins, you
must manually recreate that functionality in the Flash
environment.
Navigation bar: Adobe Captivate
currently does not export the navigation bar used in the interface
skin. If you use this asset in your project, you must manually
create or add it to your Flash project.
Advanced compression: Advanced
compression occurs specifically as part of the Adobe Captivate
publish process.
Slide transitions: Transitions added
to slides are not exported to the Flash environment. If you prefer
to use transitions, you must rebuild the slide-level transitions in
the Flash development environment.
Real-time synchronization: Adobe
Captivate does not export items recorded using the "real-time"
option to the Flash environment. Although the objects exist, the
export process does not retain the timings.
You can learn more about exporting to Flash by reading the
excellent article by Scott Young -
Exporting
your Captivate project to Flash
Regards,
Mark

Exporting to Flash Issues

Okay, I have done EVERYTHING I can think of to get the export
to Flash to work with Captivate. However, I am at a loss now. I
keep getting this really weird error message: "Windows cannot find
'#$^&\Flash.exe.' Make sure you typed the name correctly, and
then try again." Does ANYONE know what I am doing wrong???
I already followed the directions provided in an adobe
article. Just FYI.
Thanks,
Liz

If I can just step in here for a moment... You must have
Flash installed on your computer; not just any Flash but
1) the full program for creating and editing Flash objects,
and
2) the right version for compatibility with the version of
Captivate you are running. With that in mind, the Flash Player
isn't what it is looking for (with all respect to you, Andrew).
If you have Captivate 1, it is looking for the executable
file for Flash 2004MX, and for Captivate 2 or 3, it is looking for
Flash 8 (or CS3 will do also).
If you do not have the proper version of Flash, Liz, that is
the problem. If you do have the right version installed, you might
have to re-install. It may be looking in the default folder and you
have it installed elsewhere, or when you installed Captivate 3, it
might have missed that install, so it couldn't provide the link it
needs to open Flash when you export from Captivate.
Try this before pulling out your hair:
1) Check to make sure you have the right version of Flash
(see above)
2) If you do, open it, then open a "New Flash Document", then
go to "File > Import > to Stage" (and be sure you have the
*.CP file-type selected in the Import navigator).
Have a good one!

Adobe Presenter 8 and 508 Compliance

So I am in the middle of work for the US government. The output needs to be 508 compliant to meet Federal regulations. I have been building projects in Presenter 7 and using workarounds to achieve 508 compliance (e.g. printed script/handout in PDF). I have been informed that from here on out, no workarounds will be accepted -the presentation MUST be 508 compliant in the manner that they test. With that in mind, has Presenter 8 improved the accessibility of its output files compared to Presenter 7? JAWS compatibiilty, in particular, is what I need to know. The folks doing my 508 testing use JAWS and it always raises flags with Presenter output.
Before I drop the money to get the latest version of Presenter, I am wondering if things have improved or if I should be looking at another solution?

Hi Mukul,
Thanks for the prompt reply!
My compliancy checker sent me the following notes (unfortunately, not as specific as I would like):
html version:
Videos need running timer bar.
Slides just stop; no indication that you need to select "next slide" in the menu.
Not all slides are read by JAWS; rather, it reads around the slide like it isn't there – check coding.
All charts and graphics need alt-tags.
and for the PDF version:
508 Compliancy &JAWS:
JAWS needs to be able to see a flash file, whether it is in a webpage , within a .pdf, or self contained. The flash movie needs to be “described” Within Adobe Flash Professional there is an option and the ability to access the “Accessibility Panel.” But this Digging Deeper Demo.PDF was developed within Adobe Presenter, and I have yet to create a project with this tool, so I am unsure there is the same “Accessibility Panel.” If there is not, I would imagine there is something similar to ensure the flash portion of the .PDF is seen by JAWS or any screen reader.

AS3 and 508 Compliance?

Hi,
When setting up Flash content to be 508 compliant, has anyone encountered any issues in tabbing through the buttons? It seems that the buttons' descriptions aren't being picked up by the screen reader.
Thanks,
Dan

I've done (partial) 508 compliance with AS3 on a couple projects this year and last year. In the end, we decided to make the Flash version of the project "half-way" 508 compliant (which isn't really 508 compliant then, is it?) - we only focussed on tab navigation, not the screen reader. We then provided an HTML, text-only version for those who prefer the nice and simple HTML screen reader experience. I got lucky here and wasn't forced to figure out a way of dealing with full Flash + screen reader technology (but it would have been a great learning experience).
Like you, Dan, I also expereinced lots of inconsitency with what a screen reader reads when I was trying & testing things in AS3. For example, there are two ways to set up the accessible name & description for a button - via the Accessibility panel, or via AS3 code. Either way you choose, it's done - easy to do...at least as far as preping your Flash file. However, regardless of a developer doing things perfect there, we have two other levels of inconsistency: the screen reader being used, and the browser being used. I can't remember the combinations of things, but sometimes I'd get a screen reader to read the name of a tabbed-to button, other times nothing would get read. Frustrating, indeed. It's not that I programmed Flash incorrectly...it's that the technology isn't standard or consistent enough. But, then again, my experience was somewhat limited.
I don't have any answers for you, sadly, and can only to say "test, test, test", and search the heck out of it online. Luckily for us developers, the two top PC-based screen readers are avilalbe as free demos (though they only run for a limited time before you must restart your computer, which you may already be familiar with): Windows Eyes, and JAWS. A company in the UK also has one called Thunder that is totally free, but also behaves differently.When testing with a screen reader, it's also really important to learn each one's various keyboard shortcuts.
Also, if possible, working with a user who DEPENDS on screen readers for their daily lifestyle gets you the most feedback. I never got to do this, but felt that learning how a person uses a screen reader, like JAWS, and how they use the shortcuts, would provide a lot of insight.
In a nuthsell, I was only able to get complete control over a somewhat complex interface via tabbing. But I wasn't able to "conquer" the screen reader experience with AS3.
Things really get hairy when you want to update just one portion of a screeen, and have that new content - and only that - read via the screen reader. Any asynchronously updated screen type of experience has these problems, though - Flash isn't totally alone. AJAX and other HTML/JavaScript experiences can also be limited, or be challenging for developers.

508 compliance and rollovers

The client wants full 508 compliance but also a couple of slides to have rollover interactions. Most of the 508 compliance issues are easy to solve in 7. However, I'm not finding a good solution for the issue of what to do about the rollovers, since complete 508 compliance means the user who can not operate a mouse must be accommodated. The only thing I'm coming up with is to branch off with the rollovers on one branch and an option that doesn't require them on the other. Has anybody figured out a more elegant solution?
To further complicate matters some on the team that will be hosting don't want Flash. I can see substituting drag and drop for the rollovers, but there's still the problem of needing a mouse.
thank you.

Jumping in while Rod sleeps on the other side of the world.
Don't use a click box if you're trying to be 508 compliant - the click box will fail every test - no screen readers pick it up.
Don't set "Enter" as a shortcut key - it's already assigned by Captivate (and every major screen reader) as a default key and this will foul up your accessibility
If you are using the playbar -
Rod is correct - if you've got the playbar showing in the lesson, the "tab/enter" sequence will only advance the slide when the "forward" button on the playbar is selected. While you can change the behaviors and tab orders of buttons and other interactives you create within the project, you can't reset the tabbing sequence for the playbar (unless you build your own custom bar, but let's not go there).
As far as the tab staying within the flash and not going out to the browser - that's a seamless tabbing issue that seems to have risen from the dead after the last couple of Cp7 updates. You need to turn seamless tabbing off - which is supposed to be accomplished by making sure the box on the publish window is NOT checked:
If this works, it resets the parameter in your .js file to turn seamless tabbing off. The problem is, it seems to work occasionally - see http://forums.adobe.com/message/6113307#6113307; http://forums.adobe.com/message/6121301#6121301; and http://forums.adobe.com/message/6097324#6097324
These seem to be the most current work-arounds to disable the function when the setting fails.

Has anyone had any luck exporting to Flash from FC Server?

We haven't been able to get it to work with any of the third party encoders (Telestream, On2, Adobe) for Flash. If anyone has it working we would love to know how you did it!

I've also had no luck exporting to Flash, very frustratingly. In the logs I get an error message:
*ERROR: EMISSINGPARAM*
*Wrapper format missing from destination media format*
I'm not using Episode, just have Flash installed on the server and created a Compressor QuickTime Export Components preset.

Export to flash "508 compliance" error?

Similar Messages

Maybe you are looking for