508 compliance Rendering

Hi ,
Could you please let me know how to dynamically change the 508 compliance to normal view and from normal view to 508 compliance.
I was able to change the accessibility mode in triandad.xml file to screen reader to change the normal UI to 508 compliance mode, But I am doing it manually . Could you please let mek know how can we achieve with a button click in UI .
I mean to say by clicking a button in UI page the screen should change to 508 compliance dynamically .
Thank you,
sashank P

Hi Jay
I'm going to say no. This is because it is currently
impossible to publish a Captivate output in .FLV format. At least,
not from Captivate as it ships.
Cheers... Rick

Similar Messages

508 compliance woes

I'm using Robohelp X3 on the pc platform.
508 compliance has become a priority issue for my employer. I
have a large (1500 page) WebHelp file and have spent the past few
weeks adding alt tags, language tags, table summaries, etc.
Yesterday I compiled the Webhelp and selected the 508
compliant option. Ran the compiled help through our compliance tool
and what a disaster.
The problem I am having is with the files Robohelp generates
to run the Help - the frame sets, the icons it adds in the table of
contents, and the scripts Robohelp inserts. Framesets are not
titled, frames are not named, alt tags are non-existent, noscript
tags and language tags are not used - these are all Level One
violations. I have scoured the help files to discover how to repair
these files, but there appears to be no method other than opening
up each of the "w" files and doing the fixes manually - the fact
that the tasks have to be repeated with every compile is a strong
indicator (hah) that RH is NOT rendering 508 compliant help.
Has anyone else run into a similar situation? Would switching
to the X5 version solve this little problem? Is there someplace in
RH where I can go to configure these "w" pages ONCE instead of
manually repairing each file after every compile? RH Help tells me
to doubleclick on the frameset to open the frameset dialog or call
it from the file menu -- it's not on the file menu and the pages I
need to open aren't accessible inside RH.
Thanks
Russ

Hello Russ -
No, I haven't had time to do more 508 testing with RH7.
Can you tell us more about the concerns your customer has? Is
there something very specific that they need such as text readers
for hearing impaired, mobile device displays, etc.? I ask because
Section 508 is still fairly "open" and "allows" programmers some
latitude.
Is your customer aware that full compliance will limit the
appearance and functionality of their product? If your customer
wants "strict" 508 programming, I'm afraid you may have to do it
all from scratch as I haven't found any HAT that is 100% compliant.
Regards,
GEWB

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

Flex 3 And Section 508 Compliance

Hey guys,
We are developing a new RIA that has pretty complex screens,
navigation system, modal modules loading on top of others, detailed
interaction with grids, trees, etc. and a requirement for making it
508 compliant has come across my desk.
I've done a bit of research on what Adobe has to offer on
their compliance. The components look to be compliant, but from
what I can tell the compliance works best on simple forms and
screens that don't require a great deal of complexity. I'm also
having trouble finding real world examples of people who have
developed complex RIAs in Flex made for 508 compliance.
Silverlight is also being evaluated, and I'm not sure if they
are any better when it comes to the complexity of a deep RIA.
Does anyone here have any experience developing for 508 in
Flex, and if so can you shed some light on what challenges a
developer might face, or any short comings of Flex that would
prevent it from conforming to 508?
I'd also appreciate any RIAs anyone can point me to that are
508 compliant, they seem to be few and far, even the ones listed at
Adobe, most are broken links or no longer available.
Thanks.

That is a concern for state governments as well. We (alaska)
are required to make our (outward facing) sites compliant. Flex
will not allow that unless you stick to the basics ... however, if
you do that, then you might as well script in html as the results
would be basically the same.

Viewing language property on PDF document (508 compliance)

I'm currently working on a content management system that produces some PDF files to be published to external web sites. These PDF files have to be 508 compliant and one of the requirements listed by the user group is to have a Language set on the document. Using iText I'm setting the language property to the corresponding locale and I can see the value set on an editable dropdown on my Adobe Acrobat 9 Pro, so far so good. Problem is, I cannot see the language code value when viewing properties on any given document on Adobe Reader.
I checked the Adobe Reader 508 compliance overview document and there is no mention of document properties such as language so I'm guessing language does not get displayed on Adobe Reader? It isn't obvious to me why showing the language code value on the document properties would be an accessibility requirement but I just need to double check.
Any help is greatly appreciated.

I am having the same problem-I have several papers due by Friday and so
far this is my only hang up!
Any help would be greatly appreciated.

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.

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.

Accessibility-mode set to inaccessible and 508 compliance

Hi,
I'm using JDEV 10.1.3.3.0.
I've set accessibility-mode to inaccessible in adf-faces-config.xml in order to set the InitialFocusID on some of my pages. Does this setting mean that my application is not/cannot be 508 compliant?
Is there a way to use the InitialFocusID (or other way to position the cursor) and use ADF Faces automatic 508 compliance code?
TIA,
Dave

Hi,
ensure you use the correct version of JAWS. In the past I've seen things like this caused by the JAWS reader. If the problem still shows and you have a support contract, provide a test case and file a bug
My problem is when i use tab key from keyboard to navigate on the page the component highlights(dotted line around the component ) but it does not open the required popup.
This is because there is no setting in your page code that says that the popup should show when the component is in focus.
+<af:showPopupBehaviour popupId="alertPopup" triggerType="mouseOver" align="startbefore"/>+
+<af:showPopupBehaviour popupId="alertPopup" triggerType="contextMenu" align="startbefore"/>+
Frank

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.

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

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

508 compliance

Is there some standardized guide as to how to make an APEX application section 508-compliant? The most obvious obstacle is the "liberal" use of JavaScript within any generated application. Are any new releases of APEX geared toward 508 compliancy?

As per my knowledge Dashboards is partially 508 compliant.

Screen Reader/508 Compliance - Robohelp

Hello Fellow Robohelpers!
I wanted to see if any of you great minds could assist me
with a pending issue.
I need to verify with my client that RH truly is "508"
compliant. They would like to know how to:
- ensure that the text size changes in RH when you change the
font size for your browser (smallest to largest) - currently, RH
text does not change in size
- how do you tab away from 'drop lists' or 'pop-ups' in RH
without using a mouse
Apparently, there are other 508 complianec requirements as
well too. I did review the documentation Adobe provides, but it
does not provide specific keystrokes to verify their
allegations/proof.
Hope you can help or direct me where I can find such useful
information!
Thanks!

In HTML at least, changing font sizes in the browser has more
to do with the styles than with RH's 508 compliance. Current
standards are to style text using percentages rather than fixed
point or pixel values for sizes. So this is up to the help author
rather than being something RH will manage automatically.
Apparently, browsers contain settings that allow the viewer to
override text and color settings (see
this W3C page). But
its nice to not force them to do that.
When it comes to resizing text on skins or in the HTML Help
interface, someone else would have to comment on that, as well as
the rest of your question.
--Ben

Accessibile PDF generated by SSRS - 508 compliance

Does anyone know if there is any possible release or a version of SSRS that will be able to generate PDF that is accessible/508 compliant (such as alt tag for images in PDF...)?

Hi Caudu,
Based on my research, there are some VPAT documents describing how the accessibility features of Microsoft products help federal agencies address the requirements of Section 508 Standards. Here is the link:
http://www.microsoft.com/government/en-us/products/section508/Pages/default.aspx
Reference:
508 Compliance using ReportViewer and .rdlc
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

508 compliance Rendering

Similar Messages

Maybe you are looking for