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.
What does such a wide variety of Samvera code have in common, besides serving the digital repository needs of the Library/cultural heritage community?
What does it mean to be a “Samvera application”?
What if there were general criteria which Samverians (developers, product owners, managers, designers), could reference when designing and developing an app or module?
Mission
The UX Interest Group proposes crafting a set of Design Principles, which reflect the values and goals of the Samvera Community. In addition, perhaps these Design Principles could:
Serve as a guide for application design before development begins.
For example, when creating wire-frames for a new feature, does the wire-framed content meet Design Principles standards?
Act as a reference point for applications in active development.
Be a tool to evaluate existing Samvera applications, such as:
Identify areas which might fall short of meeting Samvera Design Principles, thus becoming opportunities for improvement.
Samvera Design Principles (working draft)
Equitable:
Be welcoming, don’t discriminate.
Engage with people.
Aesthetics matter.
Flexible:
Provide options.
Think who, how, why, what, where & when people will be using your website.
Make sure there is choice for diverse users and maintain device independence.
Straightforward:
Be obvious and not ambiguous.
Make sure your website’s features add value, not complexity.
Good design is as little design as possible.
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.
Make sure people know where they are in your application/component.
Provide different ways for them to find what they’re looking for.
Preventative:
Provide easy to follow instructions and gently guide users in interacting with your application.
Help users minimize errors when submitting data, through well considered form design.
Tolerant:
Handle errors respectfully and indicate precisely what the error is, where it is and how to fix it.
Remember to let people know the outcome.
Effortless:
Don’t make demands or place restrictions on your users.
People should not have to work or think hard to find what they want in your application.
Ensure the app can be used efficiently and effectively.
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.
Consistent:
Follow standards, guidelines, conventions and best practices.
Provide a familiar environment with memorable functionality.
Source: https://principles.design/examples/the-ten-principles-of-inclusive-design