Well, you need to find out if the host has a WiFi port. If it does, see if it is available. Bind it to a socket and you can treat it like any other one.
That you get so few reactions is simply, that in almost all cases the OS and driver do this for you. It's just a socket that connects you to the network. You might have different "routes" for the network traffic to follow, like an Ethernet cable or a WiFi connection, but that is transparent to the software and can change.
Often, the only way to distinguish them is if they both connect to a different network with a different IP address range.
So, essentially, you're asking either:
1. Can I write a driver for a WiFi interface in FPC?
2. Can I capture and take over the communication to and from some WiFi hardware with a program written in FPC?
The answer to both questions is "yes". But for the second, you have to study specific adapters and their drivers and see how you can worm your way in, which has nothing to do with the programming language used. It has more to do with knowing how to disassemble code and how to use a debugger. And knowing the strengths and weaknesses of the various methods used.