Versions Compared

Old Version 19

changes.mady.by.user Carla Arton

Saved on

compared with

New Version 20

changes.mady.by.user Carla Arton

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Samvera community packages run the gamut from Ruby gems, to generators, to Rails and Elixir applications, Node modules, JavaScript UI components and more. Thinking about a meaningful purpose the UX Interest Group could serve the community in 2021, the following questions have surfaced.

...

  • Backend Developers (current & future)

  • Front End Developers (current & future)

  • Administrative Users

  • End Users / Patrons (students, faculty, research, general public, etc.)

***We want to put in questions with each principle we settle on to help people think thru how they are/arent' reaching those principles. **

Samvera Design Principles (working draft)

...

Design Principle

Sub-Theme

Qs for All

Additional Qs for Developers

Human-Centered

Inclusive & Equitable

  • Q: Does the app feel welcoming?

  • Q: Does the app (unintentionally) leave any users out (culturally, language, eye-sight conditions, etc)?

  • Q: Is it obvious where to request help? Report a problem?

Human-Centered

Accessible & Universal

  • Q: Is the app “approachable”?

  • Q: Does the app feel cluttered?

  • Q: Is the app responsive across viewport sizes?

  • Q: Easy to find and manipulate any accessibility features?

  • Q: Does the app follow WCAG requirements? At what level?

Human-Centered

Engaging & Unambiguous

  • Q: How does the app actively engage/empower users?

Human-Centered

Unassuming

  • Q: How does the app use simple language (Ie. Explains all accronyms)?

  • Q: Are used icons universally recognized for desired function?

  • Q: How does the design translate well to multiple communities and account for cultural/institutional differences?

  • Q: How is the user experience changed when used on different devices?

  • Q: Does the app assume a certain level of technical proficiency to navigate?

  • Q: How does the app adapt to various devices?

Efficient

Modular while functioning as a whole

  • Q: Does the app take advantage of DRY principles and is logically separated?

Efficient

Minimal (in design & latency)

  • Q: Does the UI display more than is needed?

Efficient

Intuitive

  • Q: How easy is it to understand and follow with minimal to no training needed?

  • Q: How easy is it for users to avoid and correct errors?

Efficient

Predictable, uncomplicated and precise

  • Q: How does the app use consistent breadcrumbs & buttons placement?

  • Q: How does the app use consistent color and icons?

Efficient

Managed Flexibility

  • Q: Does the application create endless flexibility to the detriment of the workflow?

    • Ie. Endless top folder creation instead of applying information architecture/minimum rules for information organization/categorization.

    • Ie. Endless choice typically doesn’t lead to efficiency

...