Accessibility Issues in Rise

Hello! We use buttons consistently in our Articulate Rise courses to indicate optional resources (external web sites) for our learners. Keeping in mind that Rise limits the number of characters on buttons (which makes sense), we have been searching for the accessible method to label buttons in our courses with common/consistent language that will fit on the button.

After reading the WCAG 2.1 Report and "3.2.4 Consistent Identification (Level AA) Rise 360 consistently identifies built-in components. When you use an object or interaction more than once, be sure to identify it the same way each time. For example, if you use button blocks to jump to other locations, label them consistently throughout your course." I was thinking that if we made all buttons labeled as "VIEW WEBSITE" and describe the title and purpose of the website in the button description that is available for learners to read that would make our buttons accessible (consistent, described, etc.). I wasn't quite sure if "VIEW WEBSITE" was an accessible label, so I started searching this site and the web for advice. 

I found this thread and read this point of the author of this thread "It is best practice (and expected behavior) that LINKS navigate users to a place on the page or to another page. BUTTONS should be used to perform an action. Screen reader users would not expect to come to a “button” that would navigate them to a section of a page."

Excellent point! However, Articulate Rise provides the choice for the destination of buttons to be links to web pages. With the information from the author contradicting what the tool offers, a) what is the recommended use of buttons in Rise? b) if it is accessible to link out to external web sites/pages, what is the recommended label that should be associated? c) if buttons should only be used to perform an action, how are we defining action?

Thank you!