Design process interaction design basicsPreeti Mishra
This document provides an introduction to interaction design basics and terms. It discusses that interaction design involves creating technology-based interventions to achieve goals within constraints. The design process has several stages and is iterative. Interaction design starts with understanding users through methods like talking to and observing them. Scenarios are rich stories used throughout design to illustrate user interactions. Basic terms in interaction design include goals, constraints, trade-offs, and the design process. Usability and user-centered design are also discussed.
The document provides an introduction to human-computer interaction. It discusses key concepts like interaction design, the design process, understanding users, scenarios, navigation, iteration, prototypes, usability, and common interaction styles. The design process involves understanding constraints, the human and computer, and is iterative without a clear end. Interaction starts by learning about users and their context. Scenarios and navigation help address user needs. Prototyping and iteration are used to evaluate designs. Usability focuses on effectiveness, efficiency and satisfaction. Common interaction styles include command lines, menus, forms, and the WIMP model using windows, icons, menus and pointers.
This document discusses user experience considerations for multi-platform applications. It covers industry standards and best practices for different platforms including desktop, web, mobile and tablets. It provides examples of typical users for each platform and discusses differences in screen size, input methods, mobility and tasks. The document also outlines the user experience design process, including understanding user and business needs, concept development, prototyping and user testing. Common myths about multi-platform design are debunked.
The document provides an overview of design process and factors that affect user experience in interface design. It discusses various principles and heuristics to support usability, including learnability, flexibility, and robustness. The document outlines principles that affect these factors, such as predictability, consistency and dialog initiative. It also discusses guidelines for improving usability through user testing and iterative design. The document emphasizes the importance of usability and provides several heuristics and guidelines to measure and improve usability in interface design.
Before spending your budget on Evaluating Interfaces with Users, it's essential to do a evaluation at your end.
At SwitchMe, I took a session with my team of developers to explain importance and method of Evaluating Interfaces at our end first.
This document discusses human-computer interaction and user interface design. It covers interaction design principles like understanding users and iteration. It also describes common interaction styles like command line interfaces, menus, forms, and the WIMP (windows, icons, menus, pointer) style. User-centered design techniques are outlined, including data collection, analysis, modeling, prototyping and evaluation to create effective, efficient and satisfying user experiences.
Design process interaction design basicsPreeti Mishra
This document provides an introduction to interaction design basics and terms. It discusses that interaction design involves creating technology-based interventions to achieve goals within constraints. The design process has several stages and is iterative. Interaction design starts with understanding users through methods like talking to and observing them. Scenarios are rich stories used throughout design to illustrate user interactions. Basic terms in interaction design include goals, constraints, trade-offs, and the design process. Usability and user-centered design are also discussed.
The document provides an introduction to human-computer interaction. It discusses key concepts like interaction design, the design process, understanding users, scenarios, navigation, iteration, prototypes, usability, and common interaction styles. The design process involves understanding constraints, the human and computer, and is iterative without a clear end. Interaction starts by learning about users and their context. Scenarios and navigation help address user needs. Prototyping and iteration are used to evaluate designs. Usability focuses on effectiveness, efficiency and satisfaction. Common interaction styles include command lines, menus, forms, and the WIMP model using windows, icons, menus and pointers.
This document discusses user experience considerations for multi-platform applications. It covers industry standards and best practices for different platforms including desktop, web, mobile and tablets. It provides examples of typical users for each platform and discusses differences in screen size, input methods, mobility and tasks. The document also outlines the user experience design process, including understanding user and business needs, concept development, prototyping and user testing. Common myths about multi-platform design are debunked.
The document provides an overview of design process and factors that affect user experience in interface design. It discusses various principles and heuristics to support usability, including learnability, flexibility, and robustness. The document outlines principles that affect these factors, such as predictability, consistency and dialog initiative. It also discusses guidelines for improving usability through user testing and iterative design. The document emphasizes the importance of usability and provides several heuristics and guidelines to measure and improve usability in interface design.
Before spending your budget on Evaluating Interfaces with Users, it's essential to do a evaluation at your end.
At SwitchMe, I took a session with my team of developers to explain importance and method of Evaluating Interfaces at our end first.
This document discusses human-computer interaction and user interface design. It covers interaction design principles like understanding users and iteration. It also describes common interaction styles like command line interfaces, menus, forms, and the WIMP (windows, icons, menus, pointer) style. User-centered design techniques are outlined, including data collection, analysis, modeling, prototyping and evaluation to create effective, efficient and satisfying user experiences.
Requirements Engineering for the HumanitiesShawn Day
This workshop explores how requirements engineering can be employed by digital and non-digital humanities scholars (and others) to conceptualise and communicate a research project.
requirementsEngineeringAs the field of digital humanities has evolved, one of the biggest challenges has been getting the marrying technical expertise with humanities scholarly practice to successfully deliver sustainable and sound digital projects. At its core this is a communications exercise. However, to communicate effectively demands an ability to effectively translate, define and find clarity in your own mind.
Julie Grundy gives an overview of user experience Design, why it's important, guiding principles, UX research overview, and tactics used by UX professionals. November 2015.
The document discusses key principles of user interface and user experience design. It covers several important topics:
1) It defines usability and explains why it is important, noting that users will leave a website or app if it is difficult to use, understand, navigate, or find answers.
2) It outlines various usability principles for designing interfaces, such as learnability, efficiency, memorability, reducing errors, and satisfaction.
3) It discusses important concepts like understanding users, designing for the user's mental model, following conventions like the "7+/-2 rule", reducing unnecessary tasks, and applying principles like visibility and feedback.
4) It describes different types of navigation, improving navigation, and common
The document discusses user experience (UX) design and how it relates to the software development process. It describes UX tools that can be used during each development phase, including mind maps, site maps, personas, user flows, wireframes, heatmaps and analytics. The goal is to involve UX design principles at every step to develop software that meets users' needs and provides a positive experience.
Usability Workshop at Lillebaelt AcademyDániel Góré
The document summarizes key points about usability workshops and testing. It defines usability and discusses its importance. Usability is defined as how easy user interfaces are to use based on factors like learnability, efficiency and satisfaction. The document outlines usability testing methods like card sorting, prototyping and A/B testing. It emphasizes the need to test assumptions and iteratively improve products based on user research.
The document discusses usability, which refers to the quality of a user's experience when interacting with a product or system. Usability is measured by factors like ease of learning, efficiency, memorability, errors, and satisfaction. Low usability can result in frustrated users, reduced visits and productivity. Usability testing evaluates interfaces with real users and can identify problems like poor layout, unexpected events, lack of feedback, and unclear help documents. Ensuring high usability requires understanding users and their needs and tasks.
BIG2016- Lessons Learned from building real-life user-focused Big Data systemsXavier Amatriain
1) More data is not always better than better models. Sometimes, better modeling techniques are needed rather than just collecting more data.
2) Ensembles of different models generally perform better than any single model and are commonly used in practice. Feature engineering to create new inputs for ensembles can improve their effectiveness.
3) Implicit signals from user behavior usually provide more useful information than explicit feedback, but both should be used to best represent users' long-term goals.
This document discusses characteristics of ICT users and how they interact with systems. It outlines 5 main user characteristics: physical, experience, task, age, and environment. It then examines different types of interfaces like command line, menus, graphical and natural language. The document also discusses how help and training can be provided to users. Finally, it briefly outlines some common ICT jobs and skills needed to work in the field, as well as what makes an effective ICT team.
The document discusses agile product development and user experience design, describing agile methodology as an iterative approach performed by cross-functional teams to deliver high-quality, cost-effective software. It also outlines different user types, techniques for simplifying complex interfaces, principles of behavior-driven development, and how to use analytics and A/B testing to continuously improve products based on validated user feedback.
The document discusses various aspects of usability design for software applications, including usable security, dialog boxes, and mobile usability. It provides guidance on how to balance usability and security, including focusing on simplicity, engaging users, and testing the balance. It discusses different types of dialog boxes like modal and modeless dialog boxes and when each is appropriate. It also covers some common mobile usability issues.
This document provides an overview of the user experience design process. It discusses key concepts like human factors engineering, usability, user-centered design, and user experience design. The user experience design process involves gathering user research through contextual inquiry, creating personas and task analyses, designing wireframes and prototypes, testing designs through usability evaluations, and iterating based on user feedback to meet design goals. The overall goal is to understand users and design products that provide a positive experience.
This document discusses the importance of thoughtful copywriting for user experience (UX). It begins by noting that both designers and copywriters are tasked with making experiences intuitive and compelling for users. The document then outlines how copy, like design, should consider the user, context, flow, business goals, and brand. It provides examples of where copy is needed and recommends that copy be researched, concise, put the audience first, and reduce ambiguity. The document also discusses how copy is typically created using spreadsheets and comments in design tools, and the importance of brand guides, content guides, and product marketing in aligning copy with UX and business goals.
Key Tactics for a Successful Product Launch by Kespry Senior PMProduct School
Main takeaways:
- Learn how to create a solid foundation for the successful release of a product by applying structured frameworks and user
- Center design processes from discovery to roadmap definition phases of the product lifecycle
- Learn how to methodically translate empathy for the customer to data for driving prioritization, decision -making, and clear communication for your teams
- This will be an interactive session for the audience based on a real-life example from the speaker's work
User Experience 101 - A Practical GuideAdrian Bunge
This document provides an overview of user experience (UX) design. It discusses different approaches to UX design such as relying on empathy, looking at competitors, following design patterns, and collecting user data. The document also outlines one designer's process which includes understanding business requirements, user needs, constraints, designing prototypes, and testing. Key UX principles like hierarchy of information, reducing friction, and designing for contrast, repetition, alignment and proximity are covered. The goal is to help product teams build great products that users love.
Usability engineering is a field that is concerned generally with human-computer interaction and specifically with devising human-computer interfaces that have high usability or user friendliness. It provides structured methods for achieving efficiency and elegance in interface design.
By Thoughtworks | Accessible by default: Shift accessibility left with Katie ...IngridBuenaventura
Accessible by default: Shift accessibility left
Requirements around accessibility and inclusivity are often overlooked all together or until just before, if not just after, the release of software. Not only are accessible experiences a legal requirement, they also improve the usability of applications for everybody, so why is it still an afterthought? This talk will explore how accessible practices can be embedded into the development lifecycle and become the default way of working.
Speaker: Katie Peterson, Senior Software Developer, Thoughtworks
Katie is a senior software developer and community lead for the internal Thoughtworks Asia Pacific frontend community. Katie joined Thoughtworks as a graduate developer after undergoing a career change. She loves how coding allows her to build creative solutions that solve real-world problems and how technology is constantly evolving. She's passionate about the future of frontend technologies and making products that are inclusive. Katie's also passionate about how teams can use their time more efficiently to deliver practical results and improve ways of working without trading off against future sustainability.
The document provides an introduction to user experience (UX) design. It defines UX as how users feel when interacting with a product or service, as opposed to the user interface (UI) which refers to what people use to interact. The importance of UX is discussed, noting that good UX can increase sales, loyalty and reduce support costs. UX design is the process of creating meaningful experiences for users. Usability testing involves observing representative users performing tasks to identify difficulties. Evaluation tools discussed include heuristics, which involve experts examining a design against recognized usability principles. The 10 usability heuristics cover visibility of system status, matching system design to the real world, user control and error prevention.
Requirements Engineering for the HumanitiesShawn Day
This workshop explores how requirements engineering can be employed by digital and non-digital humanities scholars (and others) to conceptualise and communicate a research project.
requirementsEngineeringAs the field of digital humanities has evolved, one of the biggest challenges has been getting the marrying technical expertise with humanities scholarly practice to successfully deliver sustainable and sound digital projects. At its core this is a communications exercise. However, to communicate effectively demands an ability to effectively translate, define and find clarity in your own mind.
Julie Grundy gives an overview of user experience Design, why it's important, guiding principles, UX research overview, and tactics used by UX professionals. November 2015.
The document discusses key principles of user interface and user experience design. It covers several important topics:
1) It defines usability and explains why it is important, noting that users will leave a website or app if it is difficult to use, understand, navigate, or find answers.
2) It outlines various usability principles for designing interfaces, such as learnability, efficiency, memorability, reducing errors, and satisfaction.
3) It discusses important concepts like understanding users, designing for the user's mental model, following conventions like the "7+/-2 rule", reducing unnecessary tasks, and applying principles like visibility and feedback.
4) It describes different types of navigation, improving navigation, and common
The document discusses user experience (UX) design and how it relates to the software development process. It describes UX tools that can be used during each development phase, including mind maps, site maps, personas, user flows, wireframes, heatmaps and analytics. The goal is to involve UX design principles at every step to develop software that meets users' needs and provides a positive experience.
Usability Workshop at Lillebaelt AcademyDániel Góré
The document summarizes key points about usability workshops and testing. It defines usability and discusses its importance. Usability is defined as how easy user interfaces are to use based on factors like learnability, efficiency and satisfaction. The document outlines usability testing methods like card sorting, prototyping and A/B testing. It emphasizes the need to test assumptions and iteratively improve products based on user research.
The document discusses usability, which refers to the quality of a user's experience when interacting with a product or system. Usability is measured by factors like ease of learning, efficiency, memorability, errors, and satisfaction. Low usability can result in frustrated users, reduced visits and productivity. Usability testing evaluates interfaces with real users and can identify problems like poor layout, unexpected events, lack of feedback, and unclear help documents. Ensuring high usability requires understanding users and their needs and tasks.
BIG2016- Lessons Learned from building real-life user-focused Big Data systemsXavier Amatriain
1) More data is not always better than better models. Sometimes, better modeling techniques are needed rather than just collecting more data.
2) Ensembles of different models generally perform better than any single model and are commonly used in practice. Feature engineering to create new inputs for ensembles can improve their effectiveness.
3) Implicit signals from user behavior usually provide more useful information than explicit feedback, but both should be used to best represent users' long-term goals.
This document discusses characteristics of ICT users and how they interact with systems. It outlines 5 main user characteristics: physical, experience, task, age, and environment. It then examines different types of interfaces like command line, menus, graphical and natural language. The document also discusses how help and training can be provided to users. Finally, it briefly outlines some common ICT jobs and skills needed to work in the field, as well as what makes an effective ICT team.
The document discusses agile product development and user experience design, describing agile methodology as an iterative approach performed by cross-functional teams to deliver high-quality, cost-effective software. It also outlines different user types, techniques for simplifying complex interfaces, principles of behavior-driven development, and how to use analytics and A/B testing to continuously improve products based on validated user feedback.
The document discusses various aspects of usability design for software applications, including usable security, dialog boxes, and mobile usability. It provides guidance on how to balance usability and security, including focusing on simplicity, engaging users, and testing the balance. It discusses different types of dialog boxes like modal and modeless dialog boxes and when each is appropriate. It also covers some common mobile usability issues.
This document provides an overview of the user experience design process. It discusses key concepts like human factors engineering, usability, user-centered design, and user experience design. The user experience design process involves gathering user research through contextual inquiry, creating personas and task analyses, designing wireframes and prototypes, testing designs through usability evaluations, and iterating based on user feedback to meet design goals. The overall goal is to understand users and design products that provide a positive experience.
This document discusses the importance of thoughtful copywriting for user experience (UX). It begins by noting that both designers and copywriters are tasked with making experiences intuitive and compelling for users. The document then outlines how copy, like design, should consider the user, context, flow, business goals, and brand. It provides examples of where copy is needed and recommends that copy be researched, concise, put the audience first, and reduce ambiguity. The document also discusses how copy is typically created using spreadsheets and comments in design tools, and the importance of brand guides, content guides, and product marketing in aligning copy with UX and business goals.
Key Tactics for a Successful Product Launch by Kespry Senior PMProduct School
Main takeaways:
- Learn how to create a solid foundation for the successful release of a product by applying structured frameworks and user
- Center design processes from discovery to roadmap definition phases of the product lifecycle
- Learn how to methodically translate empathy for the customer to data for driving prioritization, decision -making, and clear communication for your teams
- This will be an interactive session for the audience based on a real-life example from the speaker's work
User Experience 101 - A Practical GuideAdrian Bunge
This document provides an overview of user experience (UX) design. It discusses different approaches to UX design such as relying on empathy, looking at competitors, following design patterns, and collecting user data. The document also outlines one designer's process which includes understanding business requirements, user needs, constraints, designing prototypes, and testing. Key UX principles like hierarchy of information, reducing friction, and designing for contrast, repetition, alignment and proximity are covered. The goal is to help product teams build great products that users love.
Usability engineering is a field that is concerned generally with human-computer interaction and specifically with devising human-computer interfaces that have high usability or user friendliness. It provides structured methods for achieving efficiency and elegance in interface design.
By Thoughtworks | Accessible by default: Shift accessibility left with Katie ...IngridBuenaventura
Accessible by default: Shift accessibility left
Requirements around accessibility and inclusivity are often overlooked all together or until just before, if not just after, the release of software. Not only are accessible experiences a legal requirement, they also improve the usability of applications for everybody, so why is it still an afterthought? This talk will explore how accessible practices can be embedded into the development lifecycle and become the default way of working.
Speaker: Katie Peterson, Senior Software Developer, Thoughtworks
Katie is a senior software developer and community lead for the internal Thoughtworks Asia Pacific frontend community. Katie joined Thoughtworks as a graduate developer after undergoing a career change. She loves how coding allows her to build creative solutions that solve real-world problems and how technology is constantly evolving. She's passionate about the future of frontend technologies and making products that are inclusive. Katie's also passionate about how teams can use their time more efficiently to deliver practical results and improve ways of working without trading off against future sustainability.
The document provides an introduction to user experience (UX) design. It defines UX as how users feel when interacting with a product or service, as opposed to the user interface (UI) which refers to what people use to interact. The importance of UX is discussed, noting that good UX can increase sales, loyalty and reduce support costs. UX design is the process of creating meaningful experiences for users. Usability testing involves observing representative users performing tasks to identify difficulties. Evaluation tools discussed include heuristics, which involve experts examining a design against recognized usability principles. The 10 usability heuristics cover visibility of system status, matching system design to the real world, user control and error prevention.
Similaire à Design For Accessibility: Getting it right from the start (20)
Batteries -Introduction – Types of Batteries – discharging and charging of battery - characteristics of battery –battery rating- various tests on battery- – Primary battery: silver button cell- Secondary battery :Ni-Cd battery-modern battery: lithium ion battery-maintenance of batteries-choices of batteries for electric vehicle applications.
Fuel Cells: Introduction- importance and classification of fuel cells - description, principle, components, applications of fuel cells: H2-O2 fuel cell, alkaline fuel cell, molten carbonate fuel cell and direct methanol fuel cells.
Optimizing Gradle Builds - Gradle DPE Tour Berlin 2024Sinan KOZAK
Sinan from the Delivery Hero mobile infrastructure engineering team shares a deep dive into performance acceleration with Gradle build cache optimizations. Sinan shares their journey into solving complex build-cache problems that affect Gradle builds. By understanding the challenges and solutions found in our journey, we aim to demonstrate the possibilities for faster builds. The case study reveals how overlapping outputs and cache misconfigurations led to significant increases in build times, especially as the project scaled up with numerous modules using Paparazzi tests. The journey from diagnosing to defeating cache issues offers invaluable lessons on maintaining cache integrity without sacrificing functionality.
Redefining brain tumor segmentation: a cutting-edge convolutional neural netw...IJECEIAES
Medical image analysis has witnessed significant advancements with deep learning techniques. In the domain of brain tumor segmentation, the ability to
precisely delineate tumor boundaries from magnetic resonance imaging (MRI)
scans holds profound implications for diagnosis. This study presents an ensemble convolutional neural network (CNN) with transfer learning, integrating
the state-of-the-art Deeplabv3+ architecture with the ResNet18 backbone. The
model is rigorously trained and evaluated, exhibiting remarkable performance
metrics, including an impressive global accuracy of 99.286%, a high-class accuracy of 82.191%, a mean intersection over union (IoU) of 79.900%, a weighted
IoU of 98.620%, and a Boundary F1 (BF) score of 83.303%. Notably, a detailed comparative analysis with existing methods showcases the superiority of
our proposed model. These findings underscore the model’s competence in precise brain tumor localization, underscoring its potential to revolutionize medical
image analysis and enhance healthcare outcomes. This research paves the way
for future exploration and optimization of advanced CNN models in medical
imaging, emphasizing addressing false positives and resource efficiency.
Software Engineering and Project Management - Introduction, Modeling Concepts...Prakhyath Rai
Introduction, Modeling Concepts and Class Modeling: What is Object orientation? What is OO development? OO Themes; Evidence for usefulness of OO development; OO modeling history. Modeling
as Design technique: Modeling, abstraction, The Three models. Class Modeling: Object and Class Concept, Link and associations concepts, Generalization and Inheritance, A sample class model, Navigation of class models, and UML diagrams
Building the Analysis Models: Requirement Analysis, Analysis Model Approaches, Data modeling Concepts, Object Oriented Analysis, Scenario-Based Modeling, Flow-Oriented Modeling, class Based Modeling, Creating a Behavioral Model.
Null Bangalore | Pentesters Approach to AWS IAMDivyanshu
#Abstract:
- Learn more about the real-world methods for auditing AWS IAM (Identity and Access Management) as a pentester. So let us proceed with a brief discussion of IAM as well as some typical misconfigurations and their potential exploits in order to reinforce the understanding of IAM security best practices.
- Gain actionable insights into AWS IAM policies and roles, using hands on approach.
#Prerequisites:
- Basic understanding of AWS services and architecture
- Familiarity with cloud security concepts
- Experience using the AWS Management Console or AWS CLI.
- For hands on lab create account on [killercoda.com](https://killercoda.com/cloudsecurity-scenario/)
# Scenario Covered:
- Basics of IAM in AWS
- Implementing IAM Policies with Least Privilege to Manage S3 Bucket
- Objective: Create an S3 bucket with least privilege IAM policy and validate access.
- Steps:
- Create S3 bucket.
- Attach least privilege policy to IAM user.
- Validate access.
- Exploiting IAM PassRole Misconfiguration
-Allows a user to pass a specific IAM role to an AWS service (ec2), typically used for service access delegation. Then exploit PassRole Misconfiguration granting unauthorized access to sensitive resources.
- Objective: Demonstrate how a PassRole misconfiguration can grant unauthorized access.
- Steps:
- Allow user to pass IAM role to EC2.
- Exploit misconfiguration for unauthorized access.
- Access sensitive resources.
- Exploiting IAM AssumeRole Misconfiguration with Overly Permissive Role
- An overly permissive IAM role configuration can lead to privilege escalation by creating a role with administrative privileges and allow a user to assume this role.
- Objective: Show how overly permissive IAM roles can lead to privilege escalation.
- Steps:
- Create role with administrative privileges.
- Allow user to assume the role.
- Perform administrative actions.
- Differentiation between PassRole vs AssumeRole
Try at [killercoda.com](https://killercoda.com/cloudsecurity-scenario/)
Advanced control scheme of doubly fed induction generator for wind turbine us...IJECEIAES
This paper describes a speed control device for generating electrical energy on an electricity network based on the doubly fed induction generator (DFIG) used for wind power conversion systems. At first, a double-fed induction generator model was constructed. A control law is formulated to govern the flow of energy between the stator of a DFIG and the energy network using three types of controllers: proportional integral (PI), sliding mode controller (SMC) and second order sliding mode controller (SOSMC). Their different results in terms of power reference tracking, reaction to unexpected speed fluctuations, sensitivity to perturbations, and resilience against machine parameter alterations are compared. MATLAB/Simulink was used to conduct the simulations for the preceding study. Multiple simulations have shown very satisfying results, and the investigations demonstrate the efficacy and power-enhancing capabilities of the suggested control system.
International Conference on NLP, Artificial Intelligence, Machine Learning an...gerogepatton
International Conference on NLP, Artificial Intelligence, Machine Learning and Applications (NLAIM 2024) offers a premier global platform for exchanging insights and findings in the theory, methodology, and applications of NLP, Artificial Intelligence, Machine Learning, and their applications. The conference seeks substantial contributions across all key domains of NLP, Artificial Intelligence, Machine Learning, and their practical applications, aiming to foster both theoretical advancements and real-world implementations. With a focus on facilitating collaboration between researchers and practitioners from academia and industry, the conference serves as a nexus for sharing the latest developments in the field.
8. Measure twice, cut once
Time
Source: Deque
1x
3x
12x
95x
Requirements Design Development Testing Production
Cost
Before commit
Automated testing
Manual testing
9. Measure twice, cut once
Time
Source: Deque
3
9.5
15.5
37.5
Requirements Design Development Testing Production
Cost
(Hours)
Majority of
accessibility
issues (67%)
10. Refinement is an opportunity
Source: Ehrlich and Rohn, 1994
Requirements Production
Development
Increasing cost of changes
Decreasing design alternatives
11. Framing decisions
User Want
Hear what users say
User Need
See what users do
Hunch
Sense what users like
Product
Idea
Idea
Product
Idea
Product
User
Source: Bryan Zmijewski
13. Universal design principles
1. Equitable Use: The design is useful and marketable to people with diverse abilities.
2. Flexibility in Use: The design accommodates a wide range of individual preferences
and abilities.
3. Simple and Intuitive Use: Use of the design is easy to understand, regardless of the
user's experience, knowledge, language skills, or current concentration level.
4. Perceptible Information: The design communicates necessary information effectively to
the user, regardless of ambient conditions or the user's sensory abilities.
5. Fault Tolerant: The design minimizes hazards and the adverse consequences of
accidental or unintended actions.
6. Low Physical Effort: The design can be used efficiently and comfortably and with a
minimum of fatigue.
7. Size and Space for Approach and Use: Appropriate size and space is provided for
approach, reach, manipulation, and use regardless of user's body size, posture, or
mobility.
16. The four principles of digital accessibility
Operable Understandable Robust
Perceivable
17. … and some kind of prioritisation*
Issues that could cause harm, distress, or
otherwise make something unusable
Where something may be difficult to use, but
a workaround can be found
Additional features specifically targeted at
making the experience pleasurable
* my recommendations are purely advisory, you need to evaluate the situation for yourself in context
18. Text Make sure there is text associated with everything
● Alternative text / content description
● Captions
Except when:
● The image is decorative
● The same information is provided within an immediate context (same
screen, same area)
Perceivable
19. Colour
Percevable
● Color should not be the only mechanism by which something is
identified.
● Elements to consider:
○ Links
○ Graphs
○ Tabs
○ Elements that have an internal state
● Contrast is not a requirement on disabled controls
21. Keyboard
accessible
Operable
Keyboards are the most versatile input types
Make sure users can
● Reach everything via tab presses
○ Build focus order into the structure rather than manipulating it with code!
● Interact by pressing space or enter
● Have access to the same features provided by all gestures
● The focus highlight is clearly visible
22. Font size
Perceivable
● Allow for font scaling
● Be careful how containers are sized
● Scale up to 200%without the loss of
○ Content: Give users the ability to expand when content is contracted
○ Functionality: Make sure views are scrollable
26. Enough time
Operable
Ensure users have enough time to complete an action
● Allow users to inform the system if they need additional time
● Android has a “time to take action” setting built in
27. Target size
Operable
Make sure components are large enough to be interacted with
● iOS: 44 x 44
● Android: 48 x 48dp
● Web: 44 x 44 CSS pixels
28. Actions
Operable
In a list of elements where each element has several different
interactable components, use actions:
● Allow streamlined iteration over the list
● Avoid repetitive unwanted focus
31. Role, name,
value
Robust
Role:
● The type of element, e.g. button, label, check box
Name:
● A unique name of the element on the screen, e.g. submit, play, etc.
Value:
● The current state of the element, e.g. disabled, checked, selected, 25%
● A description of what will happen when activated
32. Headings
Pause, stop, hide
Enough time
Keyboard accessible
Error identification
Input labels or instructions Role, name, value
Operable
Understandable Robust
Perceivable
Putting it all together
Text descriptions
Colour supported
Font scale
Orientation
Target size
Actions
33. Communication skills
- Assume good intent*
- There are three kinds of money:
- Smart: work on known potential issues (i.e. accessibility) before development
- Good: make it work for everyone
- Bad: deal with regressions, complaints and lawsuits
- Accessibility is about human beings, not about numbers
- It’s a discipline akin to security, performance and safety
- Disabled people are impacted the most, however a lot of features we should support help more than just
disabled people
- Just because you need a feature doesn’t make you disabled
- Exact numbers are impossible to obtain, and would be even harder to maintain
■ If we start by giving numbers, we create an unmaintainable precedent
- You do not need to ask for permission to do a good job
35. How do you eat an elephant?
… one bite at a time
36. Conclusion
- A lot of issues can be resolved before development takes place
- Benefits of catching issues early:
- Saves the business money
- Less time dedicated to
- Doing the wrong thing
- Doing the thing wrong
- Fixing regressions (firefighting)
- Effort per user ratio is minimized
- We know what the potential issues are in advance
- For ~ 70 criteria reducing to principles can be helpful
- Identify silos and increase communication
Notes de l'éditeur
This story highlights the importance of taking ownership, not leaving what can be done to another person, and ensuring that important things are followed up on.