Hello,
We’re looking to use basic triggers and action buttons to unhide articles and navigate to them in a page. In doing so, does the content of the page remain accessible? I know the components themselves are all accessible but I’m wondering about screen readers being successfully redirected to the content in a way that remains accessible.
Thanks in advance!
Jo
Hi Jo,
When we’ve done this in the past, accessibility hasn’t been a problem, as long as the trigger you set up navigates to the component, not the article or block.
I believe whatever you set that navigation trigger to is where the “focus” goes, so if you set the trigger to navigate to a block or article, screen readers may not work properly
Amazing - thanks for the tip!
Adding a slight delay between the ‘Show Hidden Articles’ action and the ‘Navigate to Component’ action is typically necessary when the article being revealed is on the same page as the Action Button. Doesn’t need to be much, 250ms should be fine.