ThePacielloGroup / inclusive-design-principles

A set of principles for designing inclusive web interfaces.
http://inclusivedesignprinciples.org/
12 stars 6 forks source link

Be consistent #6

Closed iheni closed 7 years ago

iheni commented 7 years ago

Be Consistent

Strapline

Be consistent with conventions and with their application throughout your interface.

Description

Familiar interfaces borrow from well-established patterns. These should be used consistently within the interface to reinforce their meaning and purpose. This should be applied to functionality, behavior, editorial, and presentation. You should say the same things in the same way and users should be able to do the same things in the same way.

Examples

Examples not included

Heydon commented 7 years ago

@iheni I believe consistency and conventionality should be different principles. One can be consistent without being conventional and vice versa.

So "Use standard rather than custom components where possible" and "Do not apply non standard gestures or keyboard behavior to standard components" should be moved to Respect conventions or perhaps Embrace conventions.

?

iheni commented 7 years ago

Consistency and convention are two that overlap so it would be good to try and define these more. My only concern is that designers might bristle at the word 'convention'.

Add Respect/Embrace convention (undecided as to which) for now with a break down of examples and when we go through them all we can work out the final definitions.

Heydon commented 7 years ago

@iheni Great. For me, consistency is about doing the same things in the same ways. So, I could employ an unconventional design pattern, but then use it consistently within the app (whenever whatever it does is called for, it is provided in the same way).

iheni commented 7 years ago

I updated the examples.

Heydon commented 7 years ago

Be Consistent

Strapline

Offer the same information, functionality, and behavior in the same way throughout your interface.

Description

Form should follow function. Where form diverges between separate instances of the same functionality, an unnecessary burden on cognition is introduced. Maintain a pattern library where each reusable design pattern solves a discrete problem.

iheni commented 7 years ago

One thing to keep in mind is that while we want consistency throughout your interface you also want consistency across platforms. For example if you have we website, native iOS and Android apps you should aim for consistent editorial for buttons, or consistent content order for player controls on a media player. So for the strapline maybe:

Offer the same information, functionality, and behavior in the same way throughout your product.

I know I am being picky but in the back of my head I am always trying to simplify the sentences. To that end could we maybe use 'differs' rather than diverges in the description?

IanPouncey commented 7 years ago

Examples

Change:

Ensure consistency with existing design patterns across the web and platform design patterns.

to:

Heydon commented 7 years ago

You should never present the same information and functionality in different ways.

iheni commented 7 years ago

Where the same information and functionality is inconsistently implemented within an interface it can introduce confusion.

Heydon commented 7 years ago

When users identify functionality by a particular layout, aesthetic or behavior, divergence risks users coming to believe the functionality itself is different.

iheni commented 7 years ago

Where the same information and functionality is inconsistently implemented within an interface it can introduce confusion. Users may think the component is broken, different, or lose confidence in what they are doing.

Heydon commented 7 years ago
iheni commented 7 years ago

If the same content is used in multiple places always use the same design pattern so the experience is consistent.

iheni commented 7 years ago

Be Consistent

Strapline

Be consistent with conventions and with their application throughout your interface.

Description

Familiar interfaces borrow from well-established patterns. These should be used consistently within the interface to reinforce their meaning and purpose. This should be applied to functionality, behavior, editorial, and presentation. You should say the same things in the same way and users should be able to do the same things in the same way.

Examples

Heydon commented 7 years ago

Familiar interfaces borrow from well-established patterns. These should be used consistently within the interface to reinforce their meaning and purpose. This should be applied to functionality, behavior, editorial, and presentation. You should say the same things in the same way and users should be able to do the same things in the same way.

Heydon commented 7 years ago

Harmonized examples

iheni commented 7 years ago

Closing the original principle.