Creating a 508-compatible site is not the easiest thing to do. As of late, however, it IS a task with which my company has been saddled more frequently. Some customers demand an AS 2.0 solution, while others want something more up-to-date, and demand AS 3.0.

Now, in AS 2.0, 508 was a little easier. You could force a screenreader to read what you wished by changing the focus to your intended destination. Once the focus was changed, JAWS or Window-Eyes (or your preferred reader) would automatically read the _accProps for the newly focused-upon object.

However, in AS 3.0, this does not seem to be the case. Updating an object's accessibilityProperties is not difficult. However, forcing the screenreader to reread programmatically, without actually touching the keyboard or mouse, seems to be far more difficult than previously.

I'm sure there's a way to force this reading, but I have not yet found a programmatic way in which to accomplish it. Has anyone else?