Well, the docs might not be clear enough here. It's not really chaining in the sense that both authentication methods are executed all the time. It's more like you described/want: If the first method fails, the second is executed, until one authentication method succeeds. Kind of "first successful authenticator wins"
Regarding using JWT and Basic Auth together, you need to pay attention to the order and the challenge flag. For example, a working scenario would be to have JWT as the first authenticator, and then Basic Auth with challenge set to true. Result would be: If there is no valid JWT token in the request, the Basic Auth dialog will pop up and challenge the user for credentials.
The other way round would not work. If you have Basic Auth with challenge set to true as the first authenticator, then the Basic Auth dialogue would pop up until you entered valid credentials, and the JWT module is never called. So, the actual configuration highly depends on the use case you want to implement.