You haven't given an example, so I'm not sure which acronyms and abbreviations you've seen that could cause problems. As Fabby pointed out, many tech-related things are better known by their acronyms than their full names, and typing out the whole thing would be both cumbersome and obfuscatory.
On the other hand, when editing posts (though I wouldn't always edit a post only for that purpose) I expand abbreviations which I think may not be as easily understood as the whole word, or which may hinder machine translation or text-to-speech. For example, I'll change cmnd to command, win10 to Windows 10, ex to "for example" and so on.
I do think it could be helpful for the Help Center guidance to say something about using clear language so that people can decipher what you actually want to know, but it would be better to avoid overly prescriptive advice, I think.
This site is a community based around a shared interest, and many terms that would be obscure to passers-by will be widely understood here, as Kulfy hinted. My own view is that acronyms are very useful (because who likes typing?) and by using them here, we teach them to others who might find them helpful too. Rather than avoiding acronyms, in a context where you think they might not be understood and their meaning is important, you can hyperlink them to some explanatory resource, like so:
UEFI has largely replaced BIOS...
