Keep focused

[iheni]

Keep focused

Strapline

Provide context-specific information and functionality in a clear and timely fashion.

Description

A site or application may provide lots of information and functionality. Each page within the site or app should have a single or primary purpose. People should be able to focus on one thing at a time. For complex interactions, features should be revealed progressively so as to not overwhelm.

Examples

• Keep task focused, progressively reveal features and content when needed not all in one go (now, next, always) e.g. CC button on/off always on player toolbar (now), CC customisation tools available via an 'advanced' button and panel (next), CC button always on via settings (always)
• Considered disabled users in context i.e. first time user, repeat user, super user, average user
• Consider the functional geography – primary content and text first, positioning and layout (now, next, always)
• Minimal viable interaction "Create the minimum viable interaction by providing the most valuable info as early as possible. @feather #a11y #aeasf” Jeffry Zeldman
• Keep it simple
• Be transparent, make sure the action or key content is clearly perceivable and understandable

[Heydon]

@iheni As we discussed, I think it would be better not to single out disabled users — at least not in the description. If we do so, then we risk making inclusion 'for some' which would be inaccurate and put off developers who already think of accessibility as a bolt-on thing.

However, I think referring to specific disabilities / scenarios in the examples would be ace.

What do you think?

[iheni]

Yes - I like that, making the description universal put giving specific scenarios in the examples makes sense. The examples are important as people can lose focus on the fact this is about people with disabilities. Will update the Description.

BTW - the description needs work anyway I think. Not entirely convinced by it.

[IanPouncey]

I've added #11 which is slightly different but has overlap with this.

[Heydon]

"Give people only the information they need when they need it"?

[Heydon]

"Surface context-specific information and functionality in a timely fashion."?

[iheni]

@LJWatson, @Heydon, @IanPouncey, @iheni Review the principle name, strap line, and write a description by Friday 2nd Dec.

Consider context

Strap line

Provide context-specific information and functionality in a clear and timely fashion.

Description

xyz..

[Heydon]

Keep focused

Strap line

Provide context-specific information and functionality in a clear and timely fashion.

Description

Interfaces may provide lots of information and functionality simultaneously. However, people using interfaces should be able to focus on one thing at a time. It is while a user is focused on a particular task that information which may assist them in completing that task should be provided. This information should be clearly associated with the functionality at hand, and the remainder of the interface should be set back (or hidden completely) relative to that which is in focus.

[Heydon]

Description

Interfaces may provide lots of information and functionality simultaneously. However, people using interfaces should be able to focus on one thing at a time. It is while a user is focused on a particular task that information which may assist them in completing that task should be provided. This information should be clearly associated with the functionality at hand.

[Heydon]

Example:

• A form in steps: Your have a form which requires the entry of highly complex information. As a single page with multiple fields, it is daunting and difficult to traverse. By dividing the form into steps, with one field per page, the problem is broken down and you have more room on each page to provide assistive information.

[Heydon]

Description

A site or application may provide lots of information and functionality. Each page within the site or app should have a single or primary purpose. People should be able to focus on one thing at a time. For complex interactions, features should be revealed progressively so as to not overwhelm.

[IanPouncey]

Example:

• A media player might have a large number of controls, but only those needed for the current purpose should be shown. Further controls can be progressively revealed as needed, e.g. caption customisation options shown only when captions are enabled.

[IanPouncey]

• A news story page should focus primarily on the story, with secondary page content such as related stories displayed unobtrusively. Consider the functional geography – primary content and text first, positioning and layout (now, next, always).

[IanPouncey]

• Complex forms can be split into more focused steps.

[Heydon]

Keep focused

Strapline

Provide context-specific information and functionality in a clear and timely fashion.

Description

A site or application may provide lots of information and functionality. Each page within the site or app should have a single or primary purpose. People should be able to focus on one thing at a time. For complex interactions, features should be revealed progressively so as to not overwhelm.

[iheni]

Like the strapline, description and examples. If everyone else is shall we bump them up to the top?

[iheni]

Marking as invalid as merging with Prioritise tasks #11