I prefer to not use VLAN1 for any user traffic, and keep it reserved for cisco management functions.
For DHCP to work on an AP "out of the box" (before it has gotten any configurations from a zonedirector or elsewhere) it has to receive untagged packets.
There are 2 ways to do this:
1) configure the switch port as an access port in whatever VLAN you want the AP to have it's management IP/subnet.
This is usually *not* the way you want to do it.
2) configure the switch port as a trunk port w/ a native VLAN set to the VLAN you want to use for AP management addresses.
Packets from the native VLAN arrive at the AP untagged, so DHCP will work, and a plain vanilla (unconfigured) AP will be "happy" out-of-the-box. If there's a zonedirector on the same subnet, it will be able to join.
By default, the native VLAN is 1, so this agrees w/ Jeff's comment, except that I don't think your WIFI should be forced to use VLAN1. (who knows what it might be used for already in your environment)