Speaking of scripts, I think using a good font is important as well. I have seen too many letters in 굴림체 for translated services! (which, unfortunately, is the default for many systems and is seldom a nice choice for readability perspective...)

This gives me a question - are there cases where internationalization is required for users who use the same language? UK-US comes to mind at first (although it is more due to the language itself rather than culture, I think)

To me, this sounds too much like an ideal case - if an interface is better for everyone, then the previous one was an objectively bad one in the first place! I guess that it is more common to sacrifice something to make the interface better for certain types of users - especially for non-computer-program interfaces. Is my guess valid?

This word refers to joint related disorder/pain.

This image is pretty painful to look at. Can you replace this with a "weaker" one? I can't really focus on the text on the right.

I already answered the questions, but I am still not familiar with a postscript laser printer (and got that one wrong). What is it exactly?

What would be a good example of a locus of attention? This paragraph gives examples of places that are NOT loci of attention.

While I also do not think that this should be very accurate, I have seen too many cases where it is too far off from the actual accuracy because this 'progress' was not based on the estimated time. The experience was quite awkward.

I think it's often very difficult to know if any information would bias the test or not beforehand. From my experience of development and testing, users often do completely unexpected actions, and they get clues from very basic facts I told them that I thought would be irrelevant.

What happens later when I get this right/wrong? This is the first time that feels like I should really answer this question correctly. (There is 총점: 0/1 right above the question!) I actually answered this twice to see what happens when I get the right answer (After getting it wrong the first time)

This is out of curiosity - Do users actually do this? When they are being watched?

I think it would have been so much better if we knew this before our paper prototyping sessions!

This is 매독 in Korean.

So I was unfamiliar with this term and found this:

In engineering and its various subdisciplines, acceptance testing is a test conducted to determine if the requirements of a specification or contract are met.

In software testing the ISTQB defines acceptance as: formal testing with respect to user needs, requirements, and business processes conducted to determine whether a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to determine whether or not to accept the system.

Wikipedia, Acceptance Testing

The term is slightly confusing - this reminds me of storyboards in paper prototypes, and that one was more like a comic strip with a user case. Does this storyboard have something to do with that one?

Which one is the tool used to make the prototype shown below?

I guess speed is an issue as well - is it often the case? Is " It also helps if the wizard’s interface can intentionally dumb down the responses" related to this?

What's the tool used to make this?

I think this worked well because what he wanted to prototype was a DEVICE and its programs, rather than a visual software. Do you think there is an example where a non-paper prototype would work for an ordinary software?