802.3 Ethernet and 802.11 Wireless LAN are two separate L2 standards maintained by the IEEE. Neither one has any direct relation to the other, although there certainly are some similarities. Neither is embedded in the other nor encapsulates the frames of the other, and their frame structure is incompatible without some device to bridge the connection.
The device that allows a wireless client to connect to the wired LAN is called an access point (AP). An AP is simply a L2 translating bridge that allows devices using two different L2 protocols to communicate with each other. As a frame passes through the AP, the AP will translate one L2 protocol to the other.
This in many ways is similar to the way bridges were used to connect Ethernet networks to Token Ring, FDDI or other L2 protocols before Ethernet became predominant.
Digging some Linux kernel sources also doesn't reveal too much - most of the WPA communication is being done by hardware support, as I understood it, the kernel can see only an ethernet interface from it.
From what I understand, on some operating system the driver functions as a L2 bridge and translates the traffic to 802.3 Ethernet before handing it off to an existing network stack (which was written to accept 802.3 traffic). Apparently this was the most expedient way to do things for developers rather than rewriting the network stack to accept a new, somewhat confusing, and rapidly changing L2 protocol.
This is largely based off information I was given by a couple individuals I met when I was looking into this myself (see this question on AskUbuntu where I received no answer if you were wondering why). I don't have any direct knowledge or documentation to back this understanding, so take it for what it is worth.