We have four multi-state buttons on a page that the learner must select one to hear a story. I named each button in the accessibility option for the initial state and the visited. After all four buttons have been clicked and all four stories heard, the learner then can click next to advance to the next section of the project. To give an example the first multi-state button is described: Liang Incomplete in the Accessibility tab. Then in the visited state, it is described as Liang Complete. Liang Incomplete is read by the screen reader (Chrome Vox) and then when the user returns to that page and the button has turned to its visited state color, if clicked it still is read as Liang Incomplete. We need this to work,
please advise on how to resolve this. 
Is it possible to upload this course?
You get to see only the published output: click the blue arrow.
Hi, going to an older version not an option, but thank you. Adobe hasn’t responded. I’ll need to contact them for sure.
I didn’t tell you to go to an older version, but to use the older workflow. Did you misunderstand?
Did my answer offer any help with your problems? Did you contact Adobe (I am just a user)?
I do not have a solution for the visited state, only the engineers could answer that.
Maybe you have to revert to the ‘old’ workflow which was needed before multistate objects appeared with CP9? It will be less automatic of course, because the Visited state is appearing after the button has been clicked. This workflow will not be possible for fluid boxes because you cannot stack objects. Create a second button, hidden at the start with the look of your present Visited state. Hide the first button and replace it by the second button when the first is clicked. This can be done with a shared action used for all the buttons. Bit cumbersome, hope it will be a temporary solution.
You must be logged in to post a comment.
