Comments (4)
Thank you for putting this together, @jfhector
One quick question: under 1.1, there is this outcome:
As many users as possible find the interface easy to use.
Does "the interface" refer to the interface the web developer is building, or the interface for the data that we are providing?
from aria-at.
Thanks @mfairchild365 for spotting this ambiguity.
I've just fixed the phrasing under 1.1 and 1.2 to say:
As many users as possible find the interface I'm developing easy to use.
Spelling out our users' / stakeholders' situations of struggles and desired outcomes is a way to better understand their needs.
So the 'Outcomes they're hoping for' are their desired outcomes as they experience the situation of struggle – rather than ours.
from aria-at.
Here's a diagram with an example of how understanding someone's 'situation of struggle' and 'desired outcomes' helps us understand their needs. (I've put it together for a design conference last week).
The diagram represents someone who's experiencing a situation of struggle. It's the morning and they are leaving home for the day. They're in a rush. They don’t know what clothes, jacket or other rain equipment they might need during the day. This is a situation of struggle.
The outcomes they're hoping for is that they enjoy their day and stay dry, and that they're out of the door immediately so as not to be late.
Experiencing this situation of struggle is a bit like being stuck on one side of a river, not knowing how to get to the other side. The other side of the river represents the outcomes that the person is hoping for.
In this example, that person thinks of different ways to go from their situation of struggle to their desired outcomes. They could look at a weather app, they might just look at the sky, or they might just take a chance and just guess what sort of clothes or rain equipment they'll need. Different solutions have different pros and cons.
Starting from our users' situations of struggle and desired outcomes (rather than feature ideas) is a useful way to make sure that we design things that are actually helpful to them. It helps us compare our design ideas with other solutions our users already have available to our users, and avoid waste.
from aria-at.
Closed because this document is complete.
from aria-at.
Related Issues (20)
- Should one tester be able to assign verdicts to AT responses collected by another? HOT 3
- Should it be possible for multiple testers to assign verdicts to a single set of AT responses? HOT 2
- Should verdict assignment depend on response verification? HOT 2
- Presenting results in a more intuitive and useful manner HOT 1
- Rethinking the wording for assertion verdicts HOT 3
- Disambiguating 'Test Plan Run' in the Working Mode
- Feedback: "Open a nested modal dialog using a link in reading mode" (Modal Dialog Example, Test 27) HOT 1
- Feedback: "Read information about a slider in interaction mode" (Color Viewer Slider, Test 8) HOT 2
- Explore including test cases outside APG HOT 3
- Establish explicit test plan life cycle in working mode HOT 1
- Feedback: "Increment a slider by one step in interaction mode" (Color Viewer Slider, Test 10)
- Feedback: "Navigate forwards to a slider" (Color Viewer Slider, Test 5) HOT 1
- System reporting conflicts where there are none apparent: "Open a menu in reading mode" (Navigation Menu Button, Test 10) HOT 1
- Feedback: "Open a menu in reading mode" (Navigation Menu Button, Test 10) HOT 1
- Inconsistent announcement of W3C Quick Links Menu "Open a menu in interaction mode" (Navigation Menu Button, Test 11) HOT 1
- Feedback: "Open a menu in interaction mode" (Navigation Menu Button, Test 11) HOT 1
- Plan changing assertion verdicts to PASS/FAIL from GOOD/NO/INCORRECT output
- Feedback: "Navigate forwards to an expanded disclosure button in reading mode" (Disclosure Navigation Menu Example, Test 7)
- Feedback: "Navigate forwards to an expanded disclosure button in reading mode" (Disclosure Navigation Menu Example, Test 7)
- Initial Mode Switching Exploration HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from aria-at.