Kevin has excellent points here but to add

1) Yes, you need someone who's on the ball with Windows Server Failover Clusters, you also need to understand a great deal about the way an AlwaysOn group is handled (specifically the AO cluster resource) within the failover cluster.

2) it cant be stressed enough, you need to push your mirror traffic down a segregated pipe (network link), this removes the overhead on the Public network and ensures sufficient performance\segregation.

3) this is massive in AO and needs to be fully reaslised

4) to be fair its the same with database mirroring and log shipping, how do the apps handle a role reversal? With AO and a listener its more transparent, but still needs to be considered.

5) your choice of synch and asynch needs to be carefully realised. Remember you can only have 3 synch replicas of which only 2 can be configured for auto failover and those replicas cannot be an FCI.

6) again even with mirroring or log shipping this is an issue

7) again same with mirroring and log shipping

Don't rush into this or you'll likely regret it