class: centre, middle, inverse name: UX from 30,000ft specific: COMP33511 topic: Principles of Effective Experience # {{name}}: {{topic}} ### Lecture 08 (50 minutes) ### [@sharpic](http://twitter.com/sharpic) .controls[[SAQ](saqs.html) [D](discuss.html) [OH](oh.html) [C](coffee.html) [P](coffee.html#2) [SLIDES](http://sharpic.github.io/COMP33511/#slides) [↩](#)] --- layout: true class: left, middle name: UX from 30,000ft noteid: Ch 05 - Effective Experience (part 2) specific: COMP33511 website: http://sharpic.github.io/COMP33511 author: [@sharpic](http://twitter.com/sharpic) --- class: middle topic: Potted Principles .noteids[{{noteid}}] .credits[ {{author}} | UX from 30,000ft | {{specific}} | {{topic}}] .controls[[SAQ](saqs.html) [D](discuss.html) [OH](oh.html) [C](coffee.html) [P](coffee.html#2) [SLIDES](http://sharpic.github.io/COMP33511/#slides) [↩](#)] ## {{topic}} - **'Perceivable'** Can you 'see' it? - **'Operable'** Can you use it? - **'Understandable'** Can you understand it? and - **'Robust'** Is it fault tolerant. -- ### ...again I don't hold with these four only. --- class: middle topic: --Foot Stool .noteids[{{noteid}}] .credits[ {{author}} | UX from 30,000ft | {{specific}} | {{topic}}] .controls[[SAQ](saqs.html) [D](discuss.html) [OH](oh.html) [C](coffee.html) [P](coffee.html#2) [SLIDES](http://sharpic.github.io/COMP33511/#slides) [↩](#)] ## {{topic}} - **'Perceivable'** Can you 'see' it? - **'Operable'** Can you use it? - **'Open'** Is it open to programatic extension? - **'Understandable'** Can you understand it? and - **'Flexible'** Is it flexible? --- class: middle topic: -- POOUF .noteids[{{noteid}}] .credits[ {{author}} | UX from 30,000ft | {{specific}} | {{topic}}] .controls[[SAQ](saqs.html) [D](discuss.html) [OH](oh.html) [C](coffee.html) [P](coffee.html#2) [SLIDES](http://sharpic.github.io/COMP33511/#slides) [↩](#)] ## {{topic}} - '**P**erceivable' Can you 'see' it? - '**O**perable' Can you use it? - '**O**pen' Is it open to programatic extension? - '**U**nderstandable' Can you understand it? and - '**F**lexible' Is it flexible? --- class: middle topic: Facilitate Perceivability .noteids[{{noteid}}] .credits[ {{author}} | UX from 30,000ft | {{specific}} | {{topic}}] .controls[[SAQ](saqs.html) [D](discuss.html) [OH](oh.html) [C](coffee.html) [P](coffee.html#2) [SLIDES](http://sharpic.github.io/COMP33511/#slides) [↩](#)] ## {{topic}} ### Questions to think about as you design your prototype: -- 1. Does your system convey information by colour alone but without an alternate textual description? 1. Is there a succinct meaningful name and label for each interface component -- including alternatives for icons, etc.? 1. Can the user personalise the interface settings, including different styles and sizes of typography, fore and background colours, and default interface look and feel? 1. How easy is it to find and interact interface controls and the shortcuts too them? 1. Have you provided keyboard focus and text cursors, and will your system restore it's previous state when regaining focus? --- class: middle topic: Facilitate Openness .noteids[{{noteid}}] .credits[ {{author}} | UX from 30,000ft | {{specific}} | {{topic}}] .controls[[SAQ](saqs.html) [D](discuss.html) [OH](oh.html) [C](coffee.html) [P](coffee.html#2) [SLIDES](http://sharpic.github.io/COMP33511/#slides) [↩](#)] ## {{topic}} ### Questions to think about as you design your prototype: -- 1. If you have provided succinct meaningful name and label for each interface component -- including alternatives for icons, and the like -- are these names displayed and available to third-party technology? 1. Is you software open such that its information is available to third part systems including conventional assistive technologies? 1. Does your software allow input and manipulation by these third party systems? 1. If your systems is closed then does it allow all input and output to pass through to third-party software? --- class: middle topic: Facilitate Operability .noteids[{{noteid}}] .credits[ {{author}} | UX from 30,000ft | {{specific}} | {{topic}}] .controls[[SAQ](saqs.html) [D](discuss.html) [OH](oh.html) [C](coffee.html) [P](coffee.html#2) [SLIDES](http://sharpic.github.io/COMP33511/#slides) [↩](#)] ## {{topic}} ### Questions to think about as you design your prototype: -- 1. Can the user control all aspects of an audio - visual presentation (such as a video)? 1. Can the user personalise the interaction settings, and change the length of any timed events? 1. Are all functions/interface components/interactions able to be controlled via the keyboard? 1. Are all functions/interface components/interactions able to be controlled via a mouse like pointer controller? 1. Are all multiple chorded key presses available in a sticky-key sequential form? 1. Have you provided keyboard focus and text cursors, and will your system restore it's previous state when regaining focus? --- class: middle topic: Facilitate Understandability .noteids[{{noteid}}] .credits[ {{author}} | UX from 30,000ft | {{specific}} | {{topic}}] .controls[[SAQ](saqs.html) [D](discuss.html) [OH](oh.html) [C](coffee.html) [P](coffee.html#2) [SLIDES](http://sharpic.github.io/COMP33511/#slides) [↩](#)] ## {{topic}} ### Questions to think about as you design your prototype: -- 1. Is there a succinct meaningful name and label for each interface component -- including alternatives for icons, and the like? 1. Are all interface control and interaction features well documented? 1. Do all error or alert messages give consistent information, appear in a consistent place, and facilitate movement to the site of those errors? 1. Do you follow the OS keyboard conventions and best practice and style guides? 1. Have you tied into the system wide spell checker? --- class: middle topic: Facilitate Flexibility .noteids[{{noteid}}] .credits[ {{author}} | UX from 30,000ft | {{specific}} | {{topic}}] .controls[[SAQ](saqs.html) [D](discuss.html) [OH](oh.html) [C](coffee.html) [P](coffee.html#2) [SLIDES](http://sharpic.github.io/COMP33511/#slides) [↩](#)] ## {{topic}} ### Questions to think about as you design your prototype: -- 1. Does you system allow users to conform the colour encoding to their preferences? 1. Can the user personalise the interaction settings, and change the length of any timed events? 1. Can the user personalise the interface settings, including different styles and sizes of typography, fore and background colours, and default interface look and feel? 1. Can the keyboard be remapped? 1. Do you allow keyboard shortcuts and accelerator keys to be personalised to the user preferences?