It's not a good look to have the first line in the "alerts" be that the OrganizationAccountAccessRole exists in a member account, and twice as bad that there are 2 _different_ alerts, one Critical and one High for the exact same OAAR situation
Maybe there's some nuance that the role just happens to be named that and there's in fact no AWS Organizations relationship, but for demo purposes, best to either include some disambiguation that would show a user that such introspection exists or pick a less wtf scenario for "3rd party access"