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)
...
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?
Accessible & Universal
Q: Is the app “approachable”?
Q: Does the app feel cluttered?
Q: Does the app follow WCAG requirements? At what level?
Engaging & Unambiguous
Q: Does the app actively engage users?
Unassuming
Q: Does the app use simple language, explain all accronyms?
Q: Are used icons universally recognized for desired function?
2. Efficient
Modular while functioning as a whole
Q: Does the app take advantage of DRY principles and is logically separated?
Minimal (in design & latency)
Q: Does the UI display more than is needed?
Intuitive
Q: Is it easy to understand and follow with minimal to no training needed?
Q: Is it easy for users to avoid and correct errors?
Predictable, uncomplicated and precise.
Q: Ex. Does the app use consistent breadcrumbs & buttons placement? Consistent color and icons usage?
3. Unified
Follow standards, guidelines, conventions and best practices.
Q: Does the app use popular open-source libraries/packages?
Q: If core developers left the app, could its maintenance continue?
Consistent behavior patterns and functionality
Q: Does the app feel very different on any screens?
Clearly documented (for designers and users)
Q: Where would a user find the app’s documentation?
Q: Where would a developer find the. app’s documentation?
...
Flexibility balanced with Friction
Prioritise Sustainability over Trends
Q: Is the app built upon technologies less than 2 years old?
Maintenance demands should match organizational commitment to a resource.
Q: Are bug issues outweighing new feature issues?
Design (visual, technical, etc.) should be forward-looking, taking into account likely future scenarios, and avoid short-term trends.
Q: Are any trends in design you are considering encorporating reliant on Proprietary systems?
5. Ethical
Transparent
Q: Is the app Open Source (for ease of Adoption & Integration)
Q: Is the app Community driven/managed
Around User Data Collection and Analysis
Mindful of trends and unintended favouritism thru integration choices (ie. FB, Google+ integrations)
Q: Does the app rely heavily on 3rd party modules (FB/Google/etc)?
Prioritise security in code
Ease of Adoption for all communities
Prioritise Design choices that favour all communities.
...
Drafting notes below
Human-Centered
Points:
Inclusive
Accessible, Accommodating
Be approachable, uncluttered and give people room to maneuver.
Make sure that your website is unobtrusive and can be accessed by different devices of all shapes and sizes.maintain device independence
Universal
Equitable
Be welcoming, don’t discriminate.
Engage with people.
Aesthetics matter.
Be welcoming, don’t discriminate, and engage with people. Create different user experiences and make certain they have equally valuable outcomes.
Flexible:
Provide options.
Modular Application development
Think who, how, why, what, where & when people will be using your website.
Make sure there is choice for diverse users and .
Straightforward:
Be obvious and not ambiguous.
Make sure your website’s features add value, not complexity.
Good design is as little design as possible.
Title: Efficient
Points:
Minimal latency
Easy to understand and follow
Make it easy for users to avoid and correct errors
Good Documentation
Development happens with efficiency of entire application in mind, not individual needs
Perceptible:
Don’t assume anything.
Make sure the application’s purpose is clear, and its content, structure and sequence are meaningful.
Informative:
Be timely, predictable, uncomplicated and precise. (breadcrumbs & buttons placement, etc. Best practice wireframes)
Make sure people know where they are in your application/component. navigation
Provide different ways for them to find what they’re looking for.
Modular
...
Security of using Open Source
Consistent:
Follow standards, guidelines, conventions and best practices.
Provide a familiar environment with memorable functionality.
Title: Unified
Points:
Be consistent, not uniform
Follow standards, guidelines, conventions, and best practices
Consistent behavior patterns and functionality
Source: https://principles.design/examples/the-ten-principles-of-inclusive-design
...