I am creating a course with 508 compliance , i just noticed that custom buttons are not working through tab+enter(keyboard functions), what is the best solution i can give for this? please let me know if any one find any solution for this.
If you need an item to be accessible with the Tab key, you'll want to make sure you've enabled as such within the Size and Position window as described here. The typical behavior is that tab gets you to the object or button and then the user can use the Enter key or Spacebar to actually "click" on the button.
Thanks for your reply , i got it how to add the tab features and its working fine also, i can navigate using tab+enter but its not working in custom buttons, i can able to select the buttons using tab but function is not working. i request you to please check the file i have attached and provide the solution.
This is a known issue where if you've added a shape to a state, of an object or a custom button, that button is no longer accessible to keyboard triggers such as the "enter" or "spacebar" key. I'll add this thread here to the report that was filed with our Quality Assurance team so that they're aware it's impacted another user and so I can update you if additional information becomes available, but at this point I don't have a time frame or information to share.
3 Replies
Hi Sinchu,
If you need an item to be accessible with the Tab key, you'll want to make sure you've enabled as such within the Size and Position window as described here. The typical behavior is that tab gets you to the object or button and then the user can use the Enter key or Spacebar to actually "click" on the button.
HI Ashley,
Thanks for your reply , i got it how to add the tab features and its working fine also, i can navigate using tab+enter but its not working in custom buttons, i can able to select the buttons using tab but function is not working. i request you to please check the file i have attached and provide the solution.
Hi Sinchu,
This is a known issue where if you've added a shape to a state, of an object or a custom button, that button is no longer accessible to keyboard triggers such as the "enter" or "spacebar" key. I'll add this thread here to the report that was filed with our Quality Assurance team so that they're aware it's impacted another user and so I can update you if additional information becomes available, but at this point I don't have a time frame or information to share.
This discussion is closed. You can start a new discussion or contact Articulate Support.