May 19, 2015 UXC Meeting Page
USER EXPERIENCE COMMITTEE MEETING NOTES -- approved July 28, 2015
Attendees:
- Mary Hodder
- Ann Racuya-Robbins
- Suzanne Lightman
- Ellen Nadeau
- Paul Knight
- Jamie Clark
- Linda Braun, Global Inventures
Meeting Notes
- Recording Minutes; Recording Policy link (https://www.idecosystem.org/page/recording-policy-conduct-meetings)
̶* Linda to send a copy of the WebEx recording to Mary Hodder and Ann Racuya-Robbins.
- No prior minutes were posted for approval.
- Current Work and Activities Discussion
Mary asked about the results from the election for the UXC Secretary. Linda will send results from SurveyMonkey to Mary.
̶ The UXC continued in its review of FMO’s feedback to the UXC requirements that were sent on May 12. Original submission was in Excel, FMO sent their feedback in Word. FMO will be using Word documents going forward. At that last meeting, the team looked at requirements and raised issues, walked through each 1 by 1. Original number 1 requirement were split into two pieces. ̶ Suzanne summarized comments: Found issue with FMO replacement word for pathways. Discussion on entities. Roles discussed, being driven by TFTM. Testing usability was OK. While testing usability is good, UXC pointed out that it should not be our first priority. Team discussed switching requirement priorities (1 and 2) and agreed to do so.
̶ USABLE – 2 SUPPLEMENTAL INFORMATION (nonnormative): ̶ This requirement requires that entities confirm that they have responded to and remediated material*** defects raised by their usability assessment (other than trivial*** defects), but does not require a specific methodology or measurement approach. ̶ *** rather than define terms (either significant or material) give way to measure (measurements and methodology) by adding graphic from J. Nielsen on Severity Errors and Fixes (Noreen to add).
NEW NUMBER: USABLE-3 OLD NUMBER: UX-2 SHORT NAME: PLAIN LANGUAGE
REQUIREMENT STATEMENT (normative): ̶ Information presented to USERS in digital identity management functions and transactions MUST be in plain language that is clear and easy for a general audience [or the transaction's identified target audience] to understand ̶ Supplementation guidance and requirements: A number of the (shoulds) were changed to (must). Mary went through each line and made the appropriate changes.
NEW NUMBER: USABLE-4 OLD NUMBER: UX-3 SHORT NAME: NAVIGATION
REQUIREMENT STATEMENT (normative): All choices, pathways* and solutions provided to USERS in digital identity management functions and transactions MUST be clearly identifiable by the user.
Pathways was added back to USABLE-4.
And to USABLE-1 added definition of pathways.
REFERENCES AND GUIDANCE (nonnormative): See "Usability Evaluation Methods" (US DHHS 2015): http://www.usability.gov/how-to-and-tools/methods/usability-evaluation/index.html; Jakob Nielsen's Heuristics evaluation methodology, summarized at http://www.nngroup.com/topic/heuristic-evaluation/ and http://en.wikipedia.org/wiki/Heuristic_evaluation. Normative Definitions (could be used in glossary for all requirements):
- Definition of processes or “pathways” to be added: Pathways generally means that users understand where else the information will be use once entered. It also means a series of steps or sequence of choices that leads to intended result.
- Expecting response from FMO re: humans v. non-humans definition in supplemental.
(Should) to (must) changes were made in the Supplemental Information.
Meeting adjourned at 1:06p.m., EDT. Next regular meeting scheduled for May 22, 2015, 10:00 a.m. EDT.