So, from what i understand, the generally accepted and designed way to do ADA best available is as follows and best put by Alan Levine. I arrived at the same conclusion in concept, but i'm yet to get it to successfully deliver the expected results.
"I just wanted to chime in and state that we have essentially implemented our ADA Ticketing using the methods Chuck describes below and it has worked incredibly well. The ability to use a specific hold code made all the difference. We are using it for wheelchair/companion seating, as well as sign-interpreted seating. We use Seat Types to designate actual wheelchair seats, but then we set all of the wheelchair seats and companion seats to the hold code. It allows us to seat those requiring wheelchair seats properly and get the best companion seats near them. We do allow patrons to select companion seats from unheld available inventory if there are not enough held companion seats nearby. We were also able to make it work not only on Best Seating but also in Select-Your-Own-Seat. Chuck and his team really came through in enabling us to meet the ADA requirements when they added the ability to specify a hold code and use held seats in Best Seating. We’re also able to handle situations where we have a special offer on seats in a particularl price zone, but have no wheelchair seats in that price zone. We can recognize that and allow the patron to purchase accessible seats in a different price zone, but at the price of the special offer. We’d be happy to review the details of all of this if anyone is interested."
As Alan explains, i'm using 1 Wheelchair SeatType in an Companion Hold in concunction with 3 regular SeatTypes in Companion Holds, all in 1 zone.
I should be able to exec ReserveTicketsEx with the following params:
WheelchairSeats=1andContiguousSeats=4andHoldCode=444andLeaveSingleSeats=Y
~~~
James--
This was actually broken in the initial v11 release, but fixed in the "Post v11.0.3 Hot Fixes" patch. Are you on the latest/greatest release?
Thanks,
Patrick