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!

Similar Messages

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

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.

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.

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

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.

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

Limit to Custom Screen Reader Text for 508 Compliance

I am converting forms for a government Agency. The forms must be Section 508 compliant. Some pages of the forms are full pages of instructional text. I am using a single field to contain all of the accessibility text so that I can control the flow of information through the tab order with limited additional tabbing from the original version. I am adding all of the text in a Jaws friendly format into the Custom Screen Reader Text field under the Accessibility tab in the Object window. When I test the form, Jaws stops reading the Accessibility text about 980 characters in. The only way to get it to read the text in its entirety is to use the down arrow key, which forces the Jaws reader to read it line by line. This is not desirable. Has anyone else experienced this? Why is there a seemingly arbitrary limit to how much Accessibility text that can be passed to Jaws?
I am using Livecycle 7.1 and testing in Acrobat Professional 7 and Adobe Reader 8 with Dynamic PDF 7.0.5.

An associate in the field told me this is not a problem with Adobe's product. Rather it is a problem with Jaws. Apparently he has the same problem with Jaws and IBM Workplace Forms.

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?

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

[OLAP DML] display on screen the output while the program is running

Hi,
I'm running a script in AWM that is quite long, and I've placed some few 'show' so that I know what the program is doing, but it won't show on the screen the outputs until the program ends. I guess it writes all the outputs in a kind of buffer and release the content of the buffer at the end of the program.
How could I have it to release this buffer continuously?
Thanks

i think the relational analogy would be an anonymous pl/sql block executing a list of commands while outputting a list of useful dbms_output.put_line log statements:
Just as with SHOW and olap worksheet cmd line, you cant see the running dbms_output log while the pl/sql program is running... you need to wait for it to complete before you can see the log.
You can write to a file and close/exit the file each time or you can write to log table and commit each time but i guess, some such heavy lifting is needed if you want to track the long running process mid-way.
NOTE: For regular operations like dbms_cube.build load/forecast/allocate process/steps, you can always run queries against CUBE_BUILD_LOG etc mid-way. But if it's pure olap dml actions being performed then no neat pre-built handle to check things mid-way exists.

Tell me about at selection-screen on output

hi,
could u explain at selection-screen on output
any body give the wchich purpose it was used?
i will be waiting for reply.
regards
eswar.

PBO of the Selection Screen
In the PBO of the selection screen, the
AT SELECTION-SCREEN OUTPUT
event is triggered. This event block allows you to modify the selection screen and its fields directly before it is displayed.
Initializations of selections screen fields at this moment always take effect, whereas at the execution of an executable program, initializations at moment INITIALIZATION only take effect at the first program start, and are otherwise overwritten by the previous user inputs at the beginning of AT SELECTION-SCREEN OUTPUT.
REPORT demo_at_selection_screen_pbo.
PARAMETERS: test1(10) TYPE c MODIF ID sc1,
            test2(10) TYPE c MODIF ID sc2,
            test3(10) TYPE c MODIF ID sc1,
            test4(10) TYPE c MODIF ID sc2.
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
    IF screen-group1 = 'SC1'.
      screen-intensified = '1'.
      MODIFY SCREEN.
      CONTINUE.
    ENDIF.
    IF screen-group1 = 'SC2'.
      screen-intensified = '0'.
      MODIFY SCREEN.
    ENDIF.
ENDLOOP.
The parameters test1 and test3 are assigned to the modification group sc1, while test2 and test4 are assigned to group sc2. During the AT SELECTION-SCREEN OUTPUT event, the INTENSIFIED field of internal table screen is set to 1 or 0, depending on the contents of the group1 field. On the standard selection screen, the lines for test1 and test3 are highlighted while those for test2 and test4 are not, as shown below:
reward if useful
anju

Selection Screen and Output

Hi,
I am developing one report. My customer is requested me he needs Selection-screen and Output of the report both need in the same screen i.e upper part is selection screen below is the Output..
Is it possible?
If YES could you please help me..........?
Thank you advance.......

Hi Kishore,
It is possible create the upper block using selection-screen this will be screen 1.Then create the another block and use INCLUDE to include the upper block.Hope your query resolves.
An example to create selection-screen.
SELECTION-SCREEN BEGIN OF BLOCK SEL1 WITH FRAME TITLE TIT1.
PARAMETERS: CITYFR LIKE SPFLI-CITYFROM,
CITYTO LIKE SPFLI-CITYTO.
SELECTION-SCREEN END OF BLOCK SEL1.
SELECTION-SCREEN BEGIN OF SCREEN 500 AS WINDOW.
SELECTION-SCREEN INCLUDE BLOCKS SEL1.
SELECTION-SCREEN BEGIN OF BLOCK SEL2
WITH FRAME TITLE TIT2.
PARAMETERS: AIRPFR LIKE SPFLI-AIRPFROM,
AIRPTO LIKE SPFLI-AIRPTO.
SELECTION-SCREEN END OF BLOCK SEL2.
SELECTION-SCREEN END OF SCREEN 500.
We can use loop at screen to make it active or inactive at user command.That is enter or F8 whatever user chooses.
Have a best day ahead.

Screen readable output (section 508)

Similar Messages

Maybe you are looking for