Samvera community packages range from Ruby gems, generators, Rails and Elixir applications, Node modules, to JavaScript UI components. 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)
...
Flexibility balanced with Friction
Prioritise Sustainability over Trends
Maintenance demands should match organizational commitment to a resource.
Design (visual, technical, etc.) should be forward-looking, taking into account likely future scenarios, and avoid short-term trends.
5. Ethical
Transparent
Open Source
(for ease of Adoption & Integration)
Community driven/managed
Around User Data Collection and Analysis
Mindful of trends and unintended favouritism thru integration choices (ie. FB, Google+ integrations)
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
...