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

Similar Messages

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

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.

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

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.

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

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

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.

HTML Scraper (section 508 compliancy issue)

Due to Section508 accessibility requirements, I'm attempting to create a "text only" page.
I've got a scraper written in Perl that uses a socket to connect to a url, then scrape all html content.
Unfortunately, when I call a portal (3.0.9) page through the socket/scraper, no HTML content from the portal is returned to the socket.
Is there a way to capture the HTML generated by the portal either through a PL/SQL object, or through some other HTTP protocol?
null

Due to Section508 accessibility requirements, I'm attempting to create a "text only" page.
I've got a scraper written in Perl that uses a socket to connect to a url, then scrape all html content.
Unfortunately, when I call a portal (3.0.9) page through the socket/scraper, no HTML content from the portal is returned to the socket.
Is there a way to capture the HTML generated by the portal either through a PL/SQL object, or through some other HTTP protocol?
null

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

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

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

Section 508 Compliance - Spry Menu

Similar Messages

Maybe you are looking for