@LeeJensen That doesn't impact the question or this answer at all. If there is a requirement to support some accessibility standard or assistive device that requires the website to behave in a certain way with JavaScript disabled, this answer holds. The testing is valid, the requirements are not satisfied, and it's a bug. If there is no such requirement, then the testing is not valid and there is no bug.

@Y-BCause I have seen specifications that say that a web application must provide certain functionality with JavaScript disabled. A lack of statement either way could be seen as ambiguous. However, a reasonable default could be the expectation that JavaScript is enabled. Clarity would be needed from someone in a position to make a decision on the requirements.

I'm not sure this question can be answered until after you've contacted the vendors. In my experience, most vendors offer developer licenses to people integrating with their product, so it becomes a problem of credential management. If they don't, it becomes a problem of risk and cost management.

Have you reached out to the vendors yet? You've said that it's something you've considered. If you have, what did the vendors say? I'm also curious if you are paying for these integrations or if this is an integration where your customer would be paying for both services.

This is an XY problem. It may be true that product management decisions are outside your responsibility, but you are responsible for process improvements related to quality assurance and communicating the state of quality of the product or service. I can expand on this in an answer.

But that doesn't answer my question. Where are those OKRs and actionable units of work tracked? What tool is used to capture them? OKRs likely have actionable units of work for more than the next Sprint. Where do those go?

If Jira only contains the work for the next Sprint, how is work associated with future efforts tracked and managed? How do product managers keep track of ideas and concepts that need to be refined before they are ready for selection at Sprint Planning? I don't see much of a difference between a defect deferred for a longer time and these longer-term product concepts. The only difference is the level of specificity - a defect report is usually specific and well-defined, while the concepts need to be refined and decomposed into actionable units of work.