I know the "Tab Order" will allow the screen reader to read out lout the content and the default/buit-in "Next" and "Prev" buttons can work as they were meant to be. I just want to double check that if a chevron shape on the screen functions as the "Next" button (with "to the next slide" trigger), will this shape still work as "Next" button and lead to the next page?
If the object is accessible to the screen reader and has the triggers designed as such, you shouldn't have any issues using that shape as a next button.
If you run into any issues, definitely let us know! We'll want to take a look at your .story file in that case.
2 Replies
Hi Phoebe,
If the object is accessible to the screen reader and has the triggers designed as such, you shouldn't have any issues using that shape as a next button.
If you run into any issues, definitely let us know! We'll want to take a look at your .story file in that case.
Thank you Ashley for your confirmation. This was also my assumption. :-)
Sure, will let you staff know if I still run into any issues regarding this.
This discussion is closed. You can start a new discussion or contact Articulate Support.