If your personal projects are:
- Paid freelancing gigs
- Volunteer stuff for non-profits
- Contributions to a well-known open source project
- At least reasonably popular releases on an app store like Google Play, for example
- Side projects for any of your last jobs that used these technologies in a production environment
Then they're fair-game resume-fodder not only for your list of skills, but also for your experience/projects section.
If they're not, then it will be harder to display that you're actually competent in the technologies you list, but still doable. Even if you don't have it open sourced, making your code available to review by your prospective employers will go a long way to them considering you, despite your lack of formal experience. You can provide the code easily through sites like GitHub (it may also be worth annotating with something like DocBlock or Docco, and explaining why you did certain things the way you did).
When it comes to software development, what you know and have used -- and your ability to demonstrate your knowledge -- is more important than how you learned it. To developers, it's generally a given that you taught yourself the vast majority of languages and technologies that you use (it's part of the personality that's expected of good developers - the ability to learn and find resources without a formal structure or a teacher).