Agile teams have to address usability to properly catch their users experience. But like in traditional software development, this task is not easy to achieve; there exists an interesting debate in the agile and usability communities about how to deal with this integration. In this paper we try to contribute to this debate by discussing the incorporation of particular usability recommendations into one of the most popular artifacts for communicating agile requirements, user stories. We discuss about the changes the incorporation of particular usability issues may introduce in a user story, and describe a tool that helps the agile team to deal with such usability issues during the specification of user stories. Some encouraging results about preliminary validation are also presented in the paper.