How do you handle a user story when it depends on horizontal integrations in an application?

An example would be a user story such as, "I would like to have audio help on the start screen." Let's say that audio help depends on us creating an audio player in our application which would handle audio across multiple screens and may even be a component of another user story such as "I would like to have audio help on the settings screen". I guess what I'm getting at is how to handle architecture in user stories? 

What I have considered so far:

1. have common repeated task in each story
2. break out architectural and
horizontal pieces into their own stories
3. just plain don't write  

stories for these issues and instead track them independently