October 24, 2017 UXC Meeting Page

From IDESG Wiki
Revision as of 04:02, 28 June 2018 by Omaerz (talk | contribs) (6 revisions imported: Initial Upload of old pages from IDESG Wiki)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

TODO

USER EXPERIENCE COMMITTEE MEETING NOTES

October 24, 2017
Attendees:

  • Mary Hodder
  • Tom Jones
  • Jim Kragh
  • Linda Braun, Global Inventures


Meeting Minutes

  • As Mary Hodder is stepping down as Chair of the User Experience Committee, the committee will hold an election for a new Chair. Jim Kragh has been nominated. Linda Braun will schedule a vote via Survey Monkey.


  • The team reviewed the Useable-7 requirement in the Registry Interviews – Analysis document that Noreen Whysel authored.
  • Useable-7 Requirement: Wherever public open STANDARDS or legal requirements exist for collecting user requests, entities conducting digital identity management functions MUST offer structured opportunities for USERS to document and express these requests, early in their interactions with those functions. Entities MUST provide a response to those user requests on a reasonably timely basis.
  • Since this was written there have been a lot of discussions among WC3, do not track folks, and IAW; they refer to this as user terms. In your browser, you have a do not track request on your phone or desktop. Some cell phone manufacturer takes the Android code base, modify it and make the decision if location based services should be added. In Apple you have three choices, do you agree to share your location: never, all the time, or only when the application is running. This is about open standards, we thought do not track would be approved when we wrote this requirement, but it is not yet completed. There is an IEE forum taking on do not track work.
  • The team recommends that they update the Usable-7 requirement and supplemental guidance to better address the problem.
  • Proposed Draft Usable-7 Requirement update: Wherever public open STANDARDS or legal requirements exist for collecting user requirements, entities conducting digital identity management functions MUST offer structured opportunities for USERS to document and express their interface and accessibility requirements, early in their interactions with those functions. Entities MUST provide a response to those user requirement communications on a reasonably timely basis.
  • Proposed Draft Usable-1: Usable Req 1
    • USABLE-1. USABILITY PRACTICES Entities conducting digital identity management functions MUST apply user-centric design, and industry-accepted appropriate usability guidelines and practices, to the communications, interfaces, policies, data transactions, and end-to-end processes they offer, and remediate significant defects identified by their usability assessment.
  • SUPPLEMENTAL GUIDANCE
    • The term "user-centric" design is a key tenet and requirement of the IDESG founding document: the National Strategy for Trusted Identities in Cyberspace (NSTIC) dated April 15, 2011. This term is further described in Appendix A and is a common term in the User Experience domain.
    • Proposed new text 
    • The term “user-centric” permeates the NSTIC Strategy and the IDESG principles. Besides those items related to security, privacy and interoperability, these UX items are included:

• Transparency, the user understands the data collected and how it will be used • Reduced Cognitive Load on the User, minimize the number of authentication factors, like passwords. • Easy to Use by automating the user’s ability to know and change data held about them. • Improve confidence by showing users that web sites are part of a trusted framework. • Choice to present alternative identifiers or authentication servers to authorize access.


  • Adjourn
    • 1:01 p.m. EDT


  • Next UXC meeting is scheduled for October 31, 2017
[[Category: User Experience]
Retrieved from "https://wiki.idesg.org/index.php?title=October_24,_2017_UXC_Meeting_Page&oldid=5087"