if you have the full version of access 2016, you cannot install the runtime alongside. If you want to see how you app performs under runtime, temporarily change the file extension to .accdr.
It is for your client to install the runtime. The best you can do is package a zipped file containing the runtime version to be installed. I provide my clients with a link since the file becomes rather bloated and may not be emailable, plus it means they get the latest version.
Runtime does not provide ribbon, navigation window or shortcut menus but you can write your own equivalents if required.
Also be aware of the differences between 32bit and 64bit access. (not windows). If your client already has MS Office, but not access, ensure you supply them with the same 'bit' of access. If you have developed in 64bit and are providing a .accde file, it will not run under 32bit access - and visa versa.
I've not tried it, but I believe you can install different versions (e.g. 2010, 2013, 2016) of access alongside each other, but windows will only run one at a time. If you are currently using 2016 and want to run 2013, windows will remove 2016 and install 2013, this creates a time overhead when you switch systems.