交互设计基础：AB注释参考文献

需积分: 10 163 浏览量更新于2024-07-18 收藏 932KB PDF 举报

"报告样本（AB Starter Text for Info-Tech & Design）" 这篇资源涉及的是一个关于Web可用性原则的文章——“AB Starter Text for Info-Tech & Design”。文章要求读者阅读一篇提供的文章，并撰写一篇200字的注释性书目（Annotated Bibliography, AB），其中应包含三个部分：按照APA第6版规范编写的文后参考文献，对文章内容的总结，以及一个反思性段落，解释这篇文章中的观点如何帮助回答研究问题。由于期刊文章可能难以阅读，作者建议重点阅读那些有助于回答研究问题和完成AB写作的部分，忽略内文引用，因为它们可能会分散注意力。参考文献的示例是Bruce Tognazzini在2014年发表的“First Principles of Interaction Design (Revised & Expanded)”，可以在http://asktog.com/atc/principles-of-interaction-design/#AnnotatedBibliographyStarterText找到。这篇文章探讨了交互设计的基本原理，对于理解和优化网页用户体验至关重要。 Web报告的标签提示我们，这篇资源与网络报告的编写有关，可能是为了教导用户如何撰写有关Web可用性或交互设计的研究报告。在文章的某些部分，作者可能会讨论以下关键概念： 1. Web可用性原则：这些原则指导设计师创建直观、易于使用的网站，确保所有用户都能高效地导航和交互。 2. 交互设计基础：包括反馈机制、用户控制、一致性、防止错误和灵活性等元素，这些都是构建良好用户体验的基础。 3. 文献综述：撰写注释性书目时，需要对所引用的文献进行批判性思考，理解作者的观点，评估其对研究问题的贡献。 4. APA引用格式：学习如何按照APA第6版的规则正确引用资源，这是学术写作的基本技能，有助于确保作品的学术诚信。 5. 反思性写作：这部分要求作者反思文章中的观点如何与自己的研究问题相联系，展示理论如何应用于实践。通过这个任务，读者不仅可以深入了解Web设计的理论，还能提升批判性阅读和学术写作的能力。同时，这也有助于培养对网络报告格式和内容组织的理解，使读者能够更有效地传达他们的研究成果。

The following list is ordered from those interface elements demanding the least faithful consistency effort to those demanding the most.

(Many people assume that the order of items one through six should be exactly the reverse. This can lead to real confusion as users

confront pages that look familiar, but act completely different.)

1. Top level consistency

• Platform consistency: Be generally consistent with de jure (As dictated by guidelines and standards) & de facto (The unwritten

rules to which the community adheres) standards

• In-house consistency: Maintain a general look & feel across your products/services

Communicates brand and makes adoption of your other products and services easier and faster

2. Consistency across a suite of products, e. g., Microsoft Office

General look & feel communicates family

3. The overall look & feel of a single app, application or service–splash screens, design elements, etc.

A visual designer should establish a purposeful & well thought-through visual language, shaped by usability testing. User behaviors

should be fully transferable throughout the product.

4. Small visible structures, such as icons, symbols, buttons, scroll bars, etc.

The appearance of such objects needs to be strictly controlled if people are not to spend half their time trying to figure out how to scroll

or print. Their location is only just slightly less important than their appearance. Where it makes sense to standardize their location, do

so.

5. Invisible structures

Invisible structures refers to such invisible objects as Microsoft Word‟s clever little left border that has all kinds of magical properties, if

you ever discover it is there. It may or may not appear in your version of Word. And if it doesn‟t, you‟ll never know for sure that it isn‟t

really there, on account of it‟s invisible. That is exactly what is wrong with invisible objects and why, if you insist on using them, rigid

consistency becomes so important.

Apple apparently thought this was a good idea and started copying Microsoft by adding invisible controls from scroll bars to buttons

everywhere. The situation on the Mac got so bad that, by the early 2010s, the only way a user could discover how to use many of the

most fundamental features of the computer was to use Google to search for help. (For more, see:Discoverability)

Some objects while, strictly speaking, visible, do not appear to be controls, so users, left to their own devices, might never discover

their ability to be manipulated. If you absolutely insist on disguising a control, the secret rule should be crisp and clean, for example,

“you can click and drag the edges of current Macintosh windows to resize them,” not, “You can click and drag various things

sometimes, but not other things other times, so just try a lot of stuff and see what happens.”

Objects that convey information, rather than being used to generate information, should rarely, if ever, be made invisible. Apple has

violated this in making the scroll bars on the Macintosh invisible until a user passes over them.

6. Interpretation of user behavior

Changing your interpretation of a user‟s habitual action is one of the the worst things you can do to a user. Shortcut keys must maintain

their meanings. A learned gesture must be interpreted in the standard way. If the button that carries the user to the next page or screen

has been located at the bottom right for the last 30 years, don‟t move it to the top right. Changes that require a user to unlearn a

subconscious action and learn a new one are extremely frustrating to users. Users may not even realize what has happened and

assume that something has failed in their hardware or software.

If you want to attract existing users of someone else‟s product to your product, you should try to interpret your new user‟s commands in

the same way by, for example, allowing them to reuse the same shortcut keys they‟ve grown used to.

Case Study: Apple ―Command‖ Modifier Key

It was years before Apple finally gave Windows users a simple way to continue to use the Control key, rather than the Command key,

for their keyboard shortcuts. Windows users new to Mac faced great difficulty in unlearning/relearning such an ingrained habit. Users

having to switch between the two operating system as they moved between office and home had to unlearn/relearn twice a day and

would end up constantly making errors as well as having to set aside their task to consciously consider what modifier key to press each

and every time they wanted to make use of “shortcut” keys that were shortcuts no more. A large percentage of the difficulty in switching

or using dual operating systems was due to this one missing capability, and it was a completely unnecessary hindrance from the start.

剩余20页未读，继续阅读

18501611109

粉丝: 0
资源: 1

交互设计基础：AB注释参考文献

Report-Sample-Injector-crx插件

rvsystemmoveto_rvsystem_

Report design tools for Eclipse-开源

blue-annual-report-leaflet-design_templatehtml_BLUE_

邓白氏资信报告全-Sample-Report_Business-Information-Report_CH.pdf

EPP-PowerBI-Report-Starter-Kit

ReportMachine5.5(For D7-D2010)

ReportBuilder Enterprise 18.01 for D7-D10.2 Tokyo

sbt-scoverage-multiproject-sample:sbt-coverage-multiproject-sample

sample-vue-pwa-cryptocurrency-watcher

最新资源