Does location transparency imply access transparency?
There is certainly a strong dependency between these two properties and many examples will point to this conclusion. Think about an API that needs to use the same operations to access both local and remote files. If you already have a list of files, you are unaware of their physical location (e.g., some URL) since you retrieved these files or how they were retrieved (e.g., ftp?). It should imply that you used the same means to retrieve that list of files. But this is not entirely true. Let's simplify Wikipedia's definition:

Access transparency - enables resources to be accessed using identical operations.

Location transparency - enables resources to be accessed without knowledge of their physical or network location.

This 2 forms of transparency are necessary since they refer to 2 different architectural layers. The access transparency refers to the application layer, whereas location transparency refers to the physical layer. 
Returning to the initial example, you access the list of files using the API, but you are not entirely sure how that list was retrieved or where those files were located before they were retrieved.