On the "Switch ports configuration" page, click on the blue text Swx 0/2 for port 2. This will open a new page with a tab for "Allowed VLAN list".
Make sure that both 1 and 33 are there. You could set it to "All" but it's a good habit for larger networks to limit the VLANS to those that are required. If the port is going directly to the access point, then also enable "Edge port mode" which will allow the port to come up immediately without waiting fot spanning tree negotiation. If there is an intermediate switch, then it too must be set as a trunk with the vlans allowed on both the port to the 3120 and the port to the AP, and you do NOT want Edge port mode enabled because an accidental loop can take down your network.
Of course, the access point itself must be capable of and configured for multiple VLANs mapped to the different SSIDs. From your description it sounds as if this may not be the case and the AP is using only the untagged native VLAN. You'll need to verify that the AP indeed supports 802.1q trunking for multiple VLANs and is configured so that the tagged VLANs line up with the desired SSIDs.
Note that by default VLAN 1 is considered "native" and neither sends nor receives tags. If the AP is expecting that both VLANs are tagged, then you can either create a dummy VLAN other than 1 and 33 and make it "native" or use a different VLAN than 1 for your Windows-DHCP traffic.
If it's an Adtran access point, then you can check the AWCP box and follow the wireless configuration menu to configure it automatically.
Thanks jayh, you rock! As you suggested, the problem was resolved by defining the VLAN numbers in the switch port's 'allowed VLAN list.' The default setting was all VLANS. By deleting that and explicitly adding the VLAN numbers the Adtran router is behaving.
Extra credit for getting out of command line mode and showing me the GUI solution.