[New Tip] Use of the terms "user story"

[dboudreau]

After having given it some thought, I am uncomfortable with using the terms "user stories" in our quick tips to link to the content from the "How people use the Web" resource. I would be in favor of changing "User story" to "Persona", which I think is much closer to what we're conveying, here. While these are stories about users, that particular term has been deviated from its original meaning in Agile to mean the description of a requirement, based on the expectation of a person using the site/app/software/etc.

In most designers' and developers' minds nowadays, the expectation of a user story is likely to be related to a very high-level definition of a requirement or a feature, in the form of "as a [x], I want/need [y], so that I can [z]". This is not what we're providing here. I think it's misleading, and I think we'D be better of avoiding that confusion if we can.

So this a global proposal to replace "User story" by "Persona", on every tip that links to one:

Designing

• https://www.w3.org/WAI/gettingstarted/tips/designing.html#provide-sufficient-contrast-between-foreground-and-background
• https://www.w3.org/WAI/gettingstarted/tips/designing.html#dont-use-color-alone-to-convey-information
• https://www.w3.org/WAI/gettingstarted/tips/designing.html#ensure-that-interactive-elements-are-easy-to-identify
• https://www.w3.org/WAI/gettingstarted/tips/designing.html#provide-clear-and-consistent-navigation-options
• https://www.w3.org/WAI/gettingstarted/tips/designing.html#ensure-that-form-elements-include-clearly-associated-labels
• https://www.w3.org/WAI/gettingstarted/tips/designing.html#provide-easily-identifiable-feedback
• https://www.w3.org/WAI/gettingstarted/tips/designing.html#use-headings-and-spacing-to-group-related-content
• https://www.w3.org/WAI/gettingstarted/tips/designing.html#create-designs-for-different-viewport-sizes
• https://www.w3.org/WAI/gettingstarted/tips/designing.html#include-image-and-media-alternatives-in-your-design

Developing

• https://www.w3.org/WAI/gettingstarted/tips/developing.html#include-alternative-text-for-images
• https://www.w3.org/WAI/gettingstarted/tips/developing.html#use-mark-up-to-convey-meaning-and-structure
• https://www.w3.org/WAI/gettingstarted/tips/developing.html#help-users-avoid-and-correct-mistakes
• https://www.w3.org/WAI/gettingstarted/tips/developing.html#write-code-that-adapts-to-the-users-technology
• https://www.w3.org/WAI/gettingstarted/tips/developing.html#ensure-that-all-interactive-elements-are-keyboard-accessible

Writing

• https://www.w3.org/WAI/gettingstarted/tips/writing.html#use-headings-to-convey-meaning-and-structure
• https://www.w3.org/WAI/gettingstarted/tips/writing.html#write-meaningful-text-alternatives-for-images
• https://www.w3.org/WAI/gettingstarted/tips/writing.html#create-transcripts-and-captions-for-multimedia
• https://www.w3.org/WAI/gettingstarted/tips/writing.html#provide-clear-instructions
• https://www.w3.org/WAI/gettingstarted/tips/writing.html#keep-content-clear-and-concise