508 compliance--Playback control shortcuts and screen readers

Reference to 508 compliance. If you publish the SWF file to
include the playback control bar what keyboard shortcuts work
and/or can you program them? What will screen readers programs do
with the playback control buttons?

Hmmm, so if I'm understanding the situation correctly, the
ideal response would work like this?
User types some text and is SUPPOSED to press Enter to
evaluate the text. Instead, they press Tab. Immediately upon
pressing Tab, they might see a message of some sort advising the
action is incorrect and further advising that Enter is the correct
action.
I could see this possibly happening a couple of different
ways.
1. You could insert a click box configured with a Success
caption containing the advisory information. Then set the shortcut
keystroke for the click box object to be Tab. End result should be
that the user presses Tab, sees the success caption (which looks
like a failure caption, since they didn't do what was expected) and
the action of the click box would result in re-displaying the slide
with the Text Entry box. (You do this by pointing at a .1 second
slide immediately preceding the slide with the Text Entry box.)
2. You could possibly configure the Text Entry box so that
either Enter or Tab will serve as the shortcut. You do this by
modifying the Text Entry box properties so it includes a Button as
the trigger. The trick is to assign the Enter key to the Text Entry
box itself and the Tab key to the button. (or vice-versa) Then you
configure the button so it's invisible.
Hopefully one of these helps... Rick

Similar Messages

  • JRE and Screen Readers on Longhorn

    Hi everybody,
    I am a new user, so I hope that I am asking this question on the right site.
    I started doing accessibility testing last year, so I am still relatively new to this. We got an early release of Longhorn, so I decided to try some of our existing applications with JAWS 8.0 and Narrator. The screen readers worked ok for some of our stuff (which is .Net-based).
    However, when I ran one of our Java applications, neither Narrator nor JAWS could see any of the controls (all I got was the window title). These same Java applications worked fine in Windows Server 2003.
    I then downloaded a Java application from the web, and it showed the same behavior. We have thus narrowed this down to Java applications on Longhorn.
    Has anyone else seen this problem? Is there something that I need to set/do? Or, does Sun recommend a different screen reader altogether on Longhorn? I went to Sun's web site, but didn't see anything.
    Thanks in advance for your responses.
    Best regards,
    Tania

    I am not sure if there's official support for longhorn yet. Check out bugs.sun.com
    to see if this is known issue. If not, file a bug!

  • IDEs and Screen readers

    Wel, that is the first question. I was wondering if anyone out there knows of any IDEs for Java that are accessible to screen readers. to be more exact, JAWS for Windows by Freedom Scientific. I can do things through the command line, but it is more (way more) difficult. And that leads me to the second question.
    The other thing is that I am trying to edit my system environment's variables through control panel>System Tols>Advanced Environment Variables so i don't hav to be in the Java\jdk1.6.0\bin folder to compile and test items. I can't seem to get the line right in the variables. here is what the help said: type C:\program files\java\jdk1.6.0_<version>\bin
    what is the damn version I am supposed to enter after the "_"???
    thanks for all the help in advance.

    Okay, let me be more specific. When I am in the folder that I am saving my files in, and using the command line, I type in javac <filename>. when I do that, I get <javac is not recognized as an internal or external command, operable command, or batch file>. To permanently set the path variable, it says go to (on Windows XP) Control panel>System>advanced>Environment Variables and edit the system variable. Here is the direct quote from the help page on what to enter: C:> "\Program Files\Java\jdk1.6.0_<version>\bin\
    On my system, that would be: C:\program files\java\jdk1.6.0_<version>\bin
    I don't know what the version is, and there is nothing more in the folder name than what I have put above.
    I have used the direct cut and paste method, I have put the downloaded filename in the <version> spot, and tried other things.I am just loking for an easy way to not have to clutter up my bin folder with files other than what is supposed to be in there. If there were an IDE that people could inform me about that would work with the screen reader, that would be the easiest method, but I havn't found one yet.
    Message was edited by:
    MattMurdock

  • 508 Compliance, Quiz Radio Button and JAWS Reader

    Hello All, I'm using Captivate 5.5. The 508 compliance issue I'm having is that the Captivate-generated quiz radio buttons are not being properly read by JAWS.  The 508 finding states, "When the user selects a radio button anywhere in the course, the state of the radio buttons are not made correctly for JAWS to read.  Selected radio buttons are read as "unchecked radio button".  Has anyone experienced and overcome this issue?  How did you overcome?

    You've encountered the major accessibility show stopper in using the pre-made question slides. Captivate does not allow you to set the name, role, or state for the buttons on the quiz slides, and unlabeled buttons are a deal killer for any 508 compliance test I have ever worked on. See if your testing group will allow you to include a text equivalent test that a visually impaired user can access and take either proctored on do an alternative submission. If the quiz needs to be scored for completion, there's no way to currently pass a 508 accessibility test with the standard question slides otherwise. If its just a knowledge check that will not be scored, you may be able to create a description of the question and answers and put it in the slide notes area of your slide, JAWS will read that first. you would also need to have a way for the user to get past the slide without navigating it. Details follow:
    JAWS 14 reads a four answer multiple choice question slide as follows (using either tabbing or arrow keys):
    1. Slide Title
    2. Question Title
    3. Question Text
    4. radio button (unchecked) - fails 508 testing
    5. text for answer A
    6. radio button (unchecked) - fails 508 testing
    7. text for answer B
    8. radio button (unchecked) - fails 508 testing
    9. text for answer C
    10. radio button (unchecked) - fails 508 testing
    11. text for answer D
    12. radio button (unchecked) - fails 508 testing
    13. Submit button
    14. Question # of #
    This means that a visually impaired user has to:
    1. figure out that the button before each answer is related to the following answer
    2. navigate through the entire slide to the submit button to be sure they have hear any and all choices
    3. navigate back to through the question and answers
    4. select the button that matches up with the answer; then navigate back to the submit button
    5. select the submit button and (at least in Captivate 7.01.237) listen to the feedback box that opens after activating the submit button
    6. navigate to the next button or playbar
    In short - if you are working off an LMS that has an accessible testing area built in, build your tests there and provide a link from the last frame of your Captivate lesson. Score the test seperately from completion of your Captivate lesson.
    Justenuf

  • Video playback controls in full-screen mode???

    I just downloaded a TV show and want to watch it full screen. Unfortunately, in full-screen mode I can't seem to figure out how to control the playback (e.g. Rewind a few seconds to hear something I missed).
    I tried all sorts of keyboard shortcuts to no avail. Am I missing something?

    Ba,
    It may be of interest to know that streaming video codecs are designed for computers of a specific age (CPU and GPU speeds).
    DVD quality streams MPEG-2 compression at about 10 Mbits/sec, and the older MPEG-1 compression, designed for NTSC television, streams at about 2 Mbits/sec. At 10 Mbits/sec, the processor must work faster to decompress & display the image. The latest compressions are based on MPEG-4. Even a G3 iBook could display MPEG-4 full screen; so I don't think you need a faster GPU.
    Microsoft codecs & containers, the last time I checked, were ancient: based upon MPEG-2. So, check your speed:
    DSL Reports speed tests
    http://www.dslreports.com/stest
    If you use Wi-Fi, IEEE 802.11n is fastest.
    Increase the cache size for your codec, if you can. It needs to be contiguous, so I dare to recommend iDefrag 2 (US$30) to clean your remaining disk space and obtain about 20 GB of contiguous space. Video display uses many operating system files, which are likely not fragmented; but you can also de-fragment the Windows codec if it lies in over 100 fragments. (The Spotlight database usually has over 1000 fragments; but pauses in it don't affect one's pleasure in using it.)
    My low-resolution DVD is interpolated by my graphics card, and look beautiful at maximal resolution. Streaming graphics apparently isn't programmed to interpolate low resolution: it demands high resolution and high bandwidth.
    If you can't increase the cache in WMP, you can lower the resolution of your monitor. That may be why this System Preference was designed to sit on the desktop's top bar.
    Bruce

  • Adobe Reader/Acrobat and Screen Readers, 50 page default?

    The company I work for creates large print PDF for our customers.  A lot of these documents are larger than 50 pages.  Is there a reason that the default setting for reading PDF's is set to 50 pages?  Is there a way that adobe can change this setting to a higher value?  Plus the read out loud option will not read an entire document that is larger then fifty pages. And when using a third party screen reader it will not read the entire document.  

    Hi MT.Freelance
    The way that "Welcome Pages" are done in Acrobat X has changed from Acrobat 9, what you are seeing looks like a bug related to these changes.
    If you would like to log a bug on this issue the form for bug reports can be found here  https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&promoid=E WQQL
    Thanks,
    Josh

  • 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

  • I button on Playback Controls

    Does anyone know how to get rid of the "Info" Button on the
    playback controls or to replace the "Movie Created by Macromedia
    Captivate" that is shown if the user clicks this button???
    THANKS!

    Hi KristyH and welcome to the community
    The buttons are simply bitmap images that follow a specific
    naming convention. For the Info button, you should find two images.
    The prefix of the image file name will be what the control name is
    called. For example, for the Black Mini 1 control, the Info button
    files are named:
    Black mini1-infotransbuttondown.bmp
    Black mini1-infotransbuttonup.bmp
    So if you are using this playback control style and simply
    rename these two image files, the Info bit is removed and doesn't
    display.
    Hopefully this helps... Rick

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

  • MISSION CONTROL, LAUNCHPAD, and FULL SCREEN APPS (one month later)

    I'm pretty good embracing a new thing when it comes along.  I downloaded LION the day it come out, which was over a month ago at this point. On that day, I immediately found MISSION CONTROL and LAUNCHPAD both uninituitve and pointless.  Unhandy iCandy.   And of FULL SCREEN APPS?  Not necessary on an iMac anyway.
    So I quickly sought out quick solutions to 'fix' these new features.  Launchpad and full screen apps have the advantage that they can be simply ignored.  This is a good thing.  Mission Control, on the other hand, got in the way of a beloved feature for me:  what was once SPACES and EXPOSE.  That is, I couldn't simply ignore MC because I still needed the previous helpful features in Snow Leopard.
    My solution was kind of surprising and eye-opening.  It's complicated to explain but I thought I'd share.  This conclusion is likely best suited for someone not using a small screened Mac.  It turns out that most users (with big enough screens) don't really need Mission Control, Launchpad, Spaces, or Full Screen apps. 
    At all.
    Let's go through that conclusion, one by one:
    FULL SCREEN APPS
    If you have a relatively big screen (20 iMac for instance), why do you need Safari full screen?  Unless you intend to sit across the room from the computer, no reason.  And there's lots of bright empty space when you do this.  Do you need the Mail app full screen?  If you need reading glasses, maybe, but otherwise, nope.  I find it's easier just to stretch out an app pretty big and leave it at that.
    Full screen apps DO offer a nice feature which is making your desktop, menubar, and dock go BYE BYE.  I can see where sometimes this is a useful feature, but typically -- NOPE.  Typically I want access to my dock (to switch between open apps without the added step of cancelling full screen first), and typically I want access to my menubar so that I can glance up and see what time it is or find an app menu quickly.
    The only feature I find worthy of praise with full screen apps is that they hide the clutter on your desktop.  But there's an app in the Mac App Store which makes your desktop icons vanish with the touch of a button (CAMOUFLAGE).  I mean, what's the point of a wallpaper if you bury it with desktop clutter or eliminate it with full screen apps?  If it's a busy and distracting wallpaper, umm... you picked bad wallpaper.
    LAUNCH PAD
    LAUNCH PAD offers an iOS experience inside OS X.  At first I thought it was completely silly.  After a month now, I kinda get why it's there.  Kinda.
    You see, before LP, to duplicate it's functionality, you'd have to organize folders yourself.  Put folders of various apps together.  Place them somewhere in the finder heirarchy.  Then drag those folders into the part of the dock with the trashcan.  Then you could click them open and have access to similarly themed folders of apps.  The problem here, of course, is that unless you're a power user, you'll never do this.
    So Apple thought, AH-HA, we'll just drag into OS X a paradigm that users already get from iOS.  Clumping apps together any way you like them.  The misfire, if you ask me, is not allowing users to drag the new iOS folders straight into the dock when finished.  That is to say:  copies of said organized folders.  It's as if Apple's software people have complete contempt for the dock -- and are desperate to have users abandon it.
    My problem is that I like having folders in my dock of stuff I need.  It just works, as Steve says.  Going to the same EXACT place every time I need anything is more intuitive and graceful than ADDING an app called Launchpad that launches you into a different finder altogether.  Makes zero sense and THIS is why I say, like FULL SCREEN APPS, LP can basically be abandoned.
    By the way:  need proof that Apple has complete contempt for the Dock?
    MISSION CONTROL/SPACES
    A month has passed since MC was introduced and SPACES was eliminated.  I dare anyone to tell me why either is needed at all.  Before you get iMiffed, humor me for a moment and hear me out.
    The notion of SPACES was that it's a neat way to keep like minded open apps together.  I totally bought into this, back in the day.  So much so that I was iMiffed when it was gone in Lion.  But let's look at this closer.
    The REASON why we needed SPACES was that we could have WAY too many windows open at once on a Mac.  Right?  A big mess of windows covering each other up.  Suppose you're surfing in Safari but need iTunes?  But iTunes is hidden.  So what did you do?  You went to Spaces as step one, moused over to your iTunes space as move two, and then clicked it as move three.  Seems like a great solution until the day you discover that you could simply click on iTunes in the dock as move one and arrive at iTunes.  As one step.  Period.  Really simple, right? 
    Why have Spaces and apps dance around when you can just click the app you want and be done with it?  That's the critical observation to make in order to follow my entire line of reasoning.  Sure, it may look really cool and make Windows machines look like junk, but at the end of the day, why add two steps to something you might do 100 times a day -- switching between apps.
    So why OH why did Apple add Spaces?  Simple:  because too many apps were visible at once in one 'desktop' window.  So if you can build many new desktops, there might only be one or two in each.  Great solution.  Right?
    Wrong, as it turns out.  Because we still have the two extra steps.  It's a weak solution.  And it's in complete contempt of the Dock, which as it turns out, offers the strongest solution.
    The strong solution would be that only one app is visible in your Mac's window at all times.  Say you're in Safari.  Despite having 12 other apps open, you only see Safari.  Your dock tells you that you have other apps open, but nothing else sits in your window BUT the app you're using.  So you want to go to iTunes?  So click on it in the dock and Safari vanishes and iTunes emerges by itself.  No other windows.  What could be simpler?  (This app is freeware known as ISOLATOR.)
    If you download and try ISOLATOR, you'll say, umm, okay, but wait:  sometimes I do want more than one window in view.  Okay, fine, turn it off then.  From the handy menu bar menu.  I find that 98% of the time I need ISOLATOR on.  Mileage may vary.
    So let's recap.  One third party software removes distracting desktop clutter, the other removes distracting app windows.  Both can be toggled on and off from the menu bar.  One is free, one costs $2.  These two solutions remove the only real feature of FULL SCREEN APPS and make SPACES and it's newfangled cousin MISSION CONTROL pointless.
    Need that last one explained?  Well, what's Mission Control but a variant of spaces?  To invoke MC and switch to the needed window are those same two annoying steps Spaces added into the mix.  Nothing was fixed.  Plus, like spaces, you must invest time and energy organizing such spaces.
    Why bother?  And so I ask again:  can somebody who's read and tried the above carefully explain to me why Mission Control, Launchpad, and Full Screen Apps are really needed at all?  (Outside of small screened Macs.)  Doesn't the dock and these two sharewares together solve most problems?
    Am I missing something?

    I agree with everything you said about full screen apps, mission control and launchpad. For apps that made sense to run full screen, they already could under SL. Launchpad is totally unnecessary and Mission Control is a mere shadow of Expose and Spaces.
    However, I feel you have not given due credit to Spaces. The point of Spaces is to let one organise logical desktops for different tasks, not just a way to reduce the number of windows on display. For example, I have a Space for software development where I run Xcode and the iPhone simulator, a Firefox window showing perhaps documentation or some other websites pertaining to software development, a Finder window that is opened in the folder with my design docs. I have another Space where I have the remote login sessions, yet another Space with another Firefox window where I do general surfing and emailing. I can switch between these spaces using a keyboard shortcut, which is much quicker than having to lift my hand off the keyboard, move it over to the mouse, move the mouse pointer over the Dock, find the app and click on it, only to find that it has switched to the wrong window of the app.
    Without Spaces, organisation of my desktop is disrupted each time I want to switch task, whereas Spaces allows me to drop everything I am doing, go and do something completely different for a while and go back to my exact previous environment. I have a 27" iMac so am not short of screen space but I use Spaces extensively. BTW, switching Spaces using a keyboard shortcut is a lot faster on SL than the equivalent on Lion, thanks to the gratuitous screen animation of the latter.

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

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

  • 508 Compliance and HTML DB

    Where can I find a document or more information illustrating the various features included in HTML DB for meeting 508 compliance?

    I'm the visually impaired programmer Dan Cash was talking about. I ran into 3 basic problems:
    1) Images did not have ALT text. You can give an text alternative to an image that the screen reader will speak. For example, <IMG. ALT="search". ...> will cause the screen reader to say "search" when the focus moves to the image in a browser.
    2) The forms were laid out so that the text label for a data entry field didn't correspond to the field itself. Actually, I had a heck of a time registering for this forum because of this problem on your web site. As the focus moves to a data entry field, the screen reader will read the text just before the field, either to the left or above. But on the page to register with Oracle.com, there's an asterisk after every label (to indicate that the field is required). So all I hear is "star" for every field. In the HTML DB pages, some of the fields worked and some didn't. There must have been an empty table cell between the label and the input field some of the time. Or something like that.
    3) Javascript crashed my screen reader. To a degree, this is a problem with the screen reader itself. But I use the most popular screen reader in the world, JAWS and I believe it's the only screen reader that works with a browser that javascript at all. In other words, if you're not using JAWS, you wouldn't be able to use HTML DB at all. With JAWS, you can sort of use it. You just have to keep restarting JAWS.
    This may sound pretty bad but most apps are worse. I'm aware that I may have given you guys some serious headaches. Good luck with #3 above. #1 shouldn't be too bad though. It's easy to add text alternatives for images although, it may be a little time consuming to go through and add it.

  • 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

Maybe you are looking for