This document provides an overview of accessibility considerations for various users and how to test for their needs. It introduces several personas with different accessibility needs such as reduced vision, color blindness, cognitive disabilities, outdated technology, and more. For each persona, it describes their situation and technology use, then suggests how to test to ensure their needs are met. It emphasizes the importance of user research, considering accessibility from the start of a project, and having all team members focus on it in their work. The document concludes by listing additional resources on various aspects of accessibility.
Introduction to Accessibility Testing - CSUN14Patrick Dunphy
Intended for people new to accessibility testing, this session details freely available testing tools and how they relate to identifying different user issues.
Beat the Tsunami with a WAVE. Web Accessibility Testing 101 #PSUWebPatrick Dunphy
Presented at Penn State's 2014 Web Conference: The Future Friendly Web
An introduction to web accessibility. Discusses what it is, & who is affected as well as tools and techniques for addressing accessibility issues
Accessibility testing with an overview of the various disabilities and how to approach each along with a round up on most popular tools used for Accessibility evaluation
Introduction to Accessibility Testing - CSUN14Patrick Dunphy
Intended for people new to accessibility testing, this session details freely available testing tools and how they relate to identifying different user issues.
Beat the Tsunami with a WAVE. Web Accessibility Testing 101 #PSUWebPatrick Dunphy
Presented at Penn State's 2014 Web Conference: The Future Friendly Web
An introduction to web accessibility. Discusses what it is, & who is affected as well as tools and techniques for addressing accessibility issues
Accessibility testing with an overview of the various disabilities and how to approach each along with a round up on most popular tools used for Accessibility evaluation
Enabling your disabled market through UXMark Flint
The government estimates that in the UK alone the disabled consumer market (Purple Pound) is worth £249 billion per year. Why would an organisation miss out on a market this big? How do we enable the vast variety of disabled users to use our products? And how do we involve them in the UX process? There is no average disability to design for so how can our disabled participants help us make our systems as flexible as possible?
Accessibility is ease of use, being inclusive with most of the audience who are able to perform the task in a different way than normal users.
Here is the collated research on visual design best practices from accessibility perspective.
Did you know that over 20% of the world’s population has trouble using the web due to accessibility challenges? Have you thought about how accessible your website is to impaired users? Do you and your team know how to test for accessibility?
This lunch 'n learn style webinar will walk you through how to test your online assets for accessibility.
During this webinar Linn Vizard and Heather Moore from the Usability Matters team, will share with you some of the needs this audience has, design considerations geared toward making your website accessible, and how to how to conduct an accessibility focused user test.
We all get the WHO or we wouldn’t be here, same with the WHY. This presentation looks at WHAT, WHERE and HOW.
Accessibility is often a lot closer than you realise. Organisations rely on and invest heavily in technology, one of the options being considered in the mix may open up a whole new pool of resourcing options.
This presentation explores how an organisation can quickly and easily include accessibility in their organisational planning. Government departments started with accessible websites, now this is flowing onto NGOs while government departments focus on the next levels of digital accessibility.
When you know the right questions to ask, it isn’t that hard and there are some quick wins organisations can and should be implementing right now. Areas covered in this presentation include:
Technology – it is probably already on the hardware you are using!
Accessible documents – what are they and how can you produce them?
Outsourcing digital – what do you put in your brief?
Websites – internet and intranet – we all know content is king – who owns accessibility
Alternative media – video, social, webinars
Organisational accessibility – it’s not a box to tick, it’s a way of doing business - how do you embed this into an organisation?
Incorporating accessibility into your software.
What does accessibility mean?
Why should we do this?
How we should do this?
What impacts does this have?
"Alexa, when does the keynote start?" - building VUIs for eventsNelli Hergenröther
Designing and building VUIs (Voice User Interfaces) has its challenges - especially when they are built for events. I created the concepts for the Amazon Alexa skills for the conferences re:publica and Tech Open Air and give an overview over the pros and cons of VUIs in general, the concept process of the event skills and decisions on the feature set.
Web accessibility refers to the inclusive practice of removing barriers that prevent interaction with, or access to, websites by people with disabilities. When your website is inaccessible, research shows you could be excluding up to 20 percent of your visitors from interacting with your content and functionality. If your university website is inaccessible, you could be preventing access to education, student services, and more.
When your website is accessible, everyone can consume your information freely. Visually-impaired users can visit your website using a screen reader. Those who can’t use a mouse can navigate your site using a keyboard or other input device.
While creating accessible websites involves every step, including design and content, the foundation for good accessibility starts with good markup. Join my workshop to learn more about accessibility and how to program a high-quality user experience that is inclusive and beneficial to all.
Session Description
Whether you are developing a new course, selecting a new LMS or thinking about developing a mobile app you'll need to understand what's involved in designing and delivering content on mobile devices from smartphones to tablets to hybrids, this webinar will provide a overview of what you need to define, how to sketch out concepts, prototyping and testing your ideas and then how to deliver. You'll learn about apps vs web apps and understand which works best.
The webinar topics cover:
Understanding Mobile technology and how to take advantage of it
Analyzing your audience and how they are accessing your content
3 Major types of Apps, how you can use them in learning and looking beyond them
Prototyping tips and techniques from paper to functional prototypes
Several App and Course examples under the microscope
About Nick Floro
Nick has over 20 years of experience developing e-Learning solutions, applications and web platforms. He has worked with numerous Fortune 500 companies to help them understand the technology and develop innovative solutions to help their teams and customer base. Nick has won numerous awards from Apple and interactive organizations for productions and services. Nick is passionate about how technology can enhance learning and loves to share his knowledge and experience to inspire, teach and motivate.
Accessibility: Are UX-perienced? Understanding User Needs for an Accessible U...Angela M. Hooker
Some of your users have disabilities, and some don't, but if you consider their needs, then they all can have an accessible and delightful user experience.
Presentation given to students on the Bachelor in Web Development degree at the Business Academy Southwest (https://www.easv.dk/en) in Esbjerg, Denmark on the 17th November 2017.
Enabling your disabled market through UXMark Flint
The government estimates that in the UK alone the disabled consumer market (Purple Pound) is worth £249 billion per year. Why would an organisation miss out on a market this big? How do we enable the vast variety of disabled users to use our products? And how do we involve them in the UX process? There is no average disability to design for so how can our disabled participants help us make our systems as flexible as possible?
Accessibility is ease of use, being inclusive with most of the audience who are able to perform the task in a different way than normal users.
Here is the collated research on visual design best practices from accessibility perspective.
Did you know that over 20% of the world’s population has trouble using the web due to accessibility challenges? Have you thought about how accessible your website is to impaired users? Do you and your team know how to test for accessibility?
This lunch 'n learn style webinar will walk you through how to test your online assets for accessibility.
During this webinar Linn Vizard and Heather Moore from the Usability Matters team, will share with you some of the needs this audience has, design considerations geared toward making your website accessible, and how to how to conduct an accessibility focused user test.
We all get the WHO or we wouldn’t be here, same with the WHY. This presentation looks at WHAT, WHERE and HOW.
Accessibility is often a lot closer than you realise. Organisations rely on and invest heavily in technology, one of the options being considered in the mix may open up a whole new pool of resourcing options.
This presentation explores how an organisation can quickly and easily include accessibility in their organisational planning. Government departments started with accessible websites, now this is flowing onto NGOs while government departments focus on the next levels of digital accessibility.
When you know the right questions to ask, it isn’t that hard and there are some quick wins organisations can and should be implementing right now. Areas covered in this presentation include:
Technology – it is probably already on the hardware you are using!
Accessible documents – what are they and how can you produce them?
Outsourcing digital – what do you put in your brief?
Websites – internet and intranet – we all know content is king – who owns accessibility
Alternative media – video, social, webinars
Organisational accessibility – it’s not a box to tick, it’s a way of doing business - how do you embed this into an organisation?
Incorporating accessibility into your software.
What does accessibility mean?
Why should we do this?
How we should do this?
What impacts does this have?
"Alexa, when does the keynote start?" - building VUIs for eventsNelli Hergenröther
Designing and building VUIs (Voice User Interfaces) has its challenges - especially when they are built for events. I created the concepts for the Amazon Alexa skills for the conferences re:publica and Tech Open Air and give an overview over the pros and cons of VUIs in general, the concept process of the event skills and decisions on the feature set.
Web accessibility refers to the inclusive practice of removing barriers that prevent interaction with, or access to, websites by people with disabilities. When your website is inaccessible, research shows you could be excluding up to 20 percent of your visitors from interacting with your content and functionality. If your university website is inaccessible, you could be preventing access to education, student services, and more.
When your website is accessible, everyone can consume your information freely. Visually-impaired users can visit your website using a screen reader. Those who can’t use a mouse can navigate your site using a keyboard or other input device.
While creating accessible websites involves every step, including design and content, the foundation for good accessibility starts with good markup. Join my workshop to learn more about accessibility and how to program a high-quality user experience that is inclusive and beneficial to all.
Session Description
Whether you are developing a new course, selecting a new LMS or thinking about developing a mobile app you'll need to understand what's involved in designing and delivering content on mobile devices from smartphones to tablets to hybrids, this webinar will provide a overview of what you need to define, how to sketch out concepts, prototyping and testing your ideas and then how to deliver. You'll learn about apps vs web apps and understand which works best.
The webinar topics cover:
Understanding Mobile technology and how to take advantage of it
Analyzing your audience and how they are accessing your content
3 Major types of Apps, how you can use them in learning and looking beyond them
Prototyping tips and techniques from paper to functional prototypes
Several App and Course examples under the microscope
About Nick Floro
Nick has over 20 years of experience developing e-Learning solutions, applications and web platforms. He has worked with numerous Fortune 500 companies to help them understand the technology and develop innovative solutions to help their teams and customer base. Nick has won numerous awards from Apple and interactive organizations for productions and services. Nick is passionate about how technology can enhance learning and loves to share his knowledge and experience to inspire, teach and motivate.
Accessibility: Are UX-perienced? Understanding User Needs for an Accessible U...Angela M. Hooker
Some of your users have disabilities, and some don't, but if you consider their needs, then they all can have an accessible and delightful user experience.
Presentation given to students on the Bachelor in Web Development degree at the Business Academy Southwest (https://www.easv.dk/en) in Esbjerg, Denmark on the 17th November 2017.
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 idea of digitizing your high-value training materials may seem like a daunting task. But in fact, there is a road of best practices that you can follow to make it seamless. The key is to start small – perhaps with PDFs and securely delivering them – and work up to interactive material with analytics so that there is a continuous improvement of content. Just do this one step at a time.
This webinar will provide easy-to-understand insights on:
The steps to take to go from print and PDFs to more interactive content with analytics
Best practices for securely distributing your training content
How to engage your learners with your high-value training content
APM Webinar hosted by the Thames Valley Branch on 14 March 2024.
Speaker: Jade Matos Carew, Head of Digital, Accessibility and Usability, The Open University
What is digital accessibility? (Spoiler: it’s making sure we design and develop websites, systems, and digital content and experiences which are accessible by everyone – including disabled users.) This webinar was held on 14 March 2024.
We took a look at the principles behind it and why it’s vital (and often overlooked) in today’s organisations. We thought about how it can benefit staff, clients and customers, and how ensuring best practice in digital accessibility can act as a strong foundation to help to foster an inclusive and diverse organisational culture. We also considered the practical challenges which are faced when embedding best practice in digital accessibility into ways of working, and how applying change management principles can provide an effective toolkit for approaching and assisting with this.
The Equality Act (2010) broadly protects certain characteristics, including the rights of disabled people so that everyone can have equal access to participate in society. This includes online and digital spaces, and it’s therefore vital to make sure that our organisations, services, digital content, and ways of working are set up in the right way to accommodate the needs of a diverse audience so that everyone can feel included and engaged. This includes considering best practice in a wide range of contexts – from the documents you make and use, the websites you build, the development cycles you follow, to the IT solutions you procure, and the online meetings you host. Good digital accessibility is more than just meeting our legal obligations, it’s the right thing to do. Without an inclusive approach, you could be at risk of excluding people, whether that’s team members, or potential customers.
There are principles, standards, and best practice which we need to follow, and these can often take a certain amount of time, effort, and expertise to interpret, but you don’t have to be an expert to get to grips with the basics. The journey to becoming more accessible is exactly, that – a journey rather than a quick fix. There are ways in which you can embed good digital accessibility into ways of working sustainably and effectively by following small steps to ensure the change management process is as smooth as possible.
https://www.apm.org.uk/news/demystifying-digital-accessibility-webinar/
Enhancing Mobile Apps Quality-Manual Testing RevisitedMindfire Solutions
Amidst the increasing emphasis on mobile app test automation, this presentation aims to take a fresh look at the manual testing of those tiny little apps which are fast becoming a part of our day to day lives. Primarily focused towards QAs with beginner level experience in mobile app testing, it will also cover ideas and case studies of a few real world app use case scenarios which the veteran mobile testers might also find useful.
Prototyping Accessibility - WordCamp Europe 2018Adrian Roselli
Learn some fundamentals of accessibility and how it can benefit you (whether future you from aging or you after something else limits your abilities). We’ll review differing abilities, generate (minimal) user stories and personas, discuss best practices for design and development, prototype some ideas (on paper), and discuss where to get help. This isn’t intended to be a deep dive into technologies, but more of an overall primer for those who aren’t sure where to start with accessibility nor how it helps them.
Product development teams have people who focus on user experience, with responsibility for creating designs, content, and interaction that meet user expectations and provide enjoyable experiences. User experience practitioners know that making people successful is the best way to achieve product success. Some product development teams also have accessibility specialists who focus on making sure people with disabilities have access to designs, content, and interaction, but accessibility is typically a separate activity, in the engineering or QA phase. What if we joined these activities, such that UX included responsibility for the user experience for people with disabilities? And what if, as user experience designers, we welcome accessibility as a creative challenge?
In this workshop we cover universal design principles and design thinking activities to identify problems and explore creative and innovative solutions that benefit all users. We cover:
• Principles of Universal Design
• Design Thinking methodologies as applied to accessibility
• Accessible user experience principles and guidelines for creating good experiences for people with disabilities
• How to integrate responsibility for accessibility into product teams
• How to integrate practices to support accessibility into the product development lifecycle
Presented at WebVisions Barcelona on July 2, 2015: http://www.webvisionsevent.com
Exploring basic skills and talents for digital opportunities David Nzoputa Ofili
A presentation as guest speaker at the Rotary Youth Leadership Awards, hosted by RI District 9141, on August 31, 2019, at St. Patrick's College, Asaba, Delta State, Nigeria.
Since the fall of 2012, Oregon State University Extension has been delivering bi-monthly webinars focused on encouraging and educating Extension personnel on the use and application of mobile devices..meaning tablets and smart phones of all sizes, shapes and colors. This has become the flagship activity in our Extension Mobile Device Users Group initiative (EMDUG.) In this session, Click & Clack (Victor and Jeff) give some of the tips and tricks on how to create a well-received, light-hearted but informative webinar series that doesn’t put your audience to sleep! We discuss platforms, equipment, planning, and share our Top Ten List on Ways To Improve Your Webinars.
5 Keys for Implementing Accessibility in Your TeamAngela M. Hooker
You've been chosen to wrangle your colleagues into a thriving accessibility team. How will you do that? Stay calm and get 5 keys to help you form an effective plan for working with your team, changing your institutional approach, and producing accessible projects.
You've been working with your "chummies" for years on accessibility, and they still don't quite "get it." You give them rules, an accessibility audit reports, deadlines, and standards--but they're unsure of how to use these resources. Learn how to educate them for success so they can create accessible, usable digital media.
I Was Wrong! Learn from My Accessibility Program MstakesAngela M. Hooker
Whether you're new to the field, when you manage an accessibility program, you may fall into common traps--but there's no need to! Learn from my observations and old mistakes! Get tips for running a successful program and avoiding poor management choices, poor policy, poor planning, and more that can hinder your program.
Yes, Virginia, PMs Are Responsible for AccessibilityAngela M. Hooker
Ho-ho-ho, Virginia! For too long, we've relied on developers to be the accessibility champion for tech projects. But if you put the sole responsibility on them, you're setting your project up for problems--big, costly problems that can cause delays. I'd like to show how you--as the PM--can make sure your digital media projects are accessible, because it really does start with you. You'll learn the why, what, and how to do it. You've got this, Virginia! Love, Santa's Helper
Make It Plain: Accessbility and Usability Through Plain LanguageAngela M. Hooker
We know that “content is king” on the web, and content clarity determines whether a user can complete a task, such as registering for a course, finding a job, or shopping. We can provide accessible, usable content–and make those tasks easier to complete–by writing content in plain language.
Plain language is a major building block of an effective website. Unclear content frustrates users and causes them to abandon sites quickly. However, by focusing on top tasks, eliminating unnecessary words, using common terms, and writing well-structured content, we ensure that our sites are usable and accessible, and almost everyone can understand the messages we wish to communicate and use our sites successfully.
Get Your Train On: Building Your UX Team Through Practical Usability TestingAngela M. Hooker
Learn how to start a usability program at your organization, through a process that multiplies your current resources and can cost you little or nothing.
2.Cellular Networks_The final stage of connectivity is achieved by segmenting...JeyaPerumal1
A cellular network, frequently referred to as a mobile network, is a type of communication system that enables wireless communication between mobile devices. The final stage of connectivity is achieved by segmenting the comprehensive service area into several compact zones, each called a cell.
Gen Z and the marketplaces - let's translate their needsLaura Szabó
The product workshop focused on exploring the requirements of Generation Z in relation to marketplace dynamics. We delved into their specific needs, examined the specifics in their shopping preferences, and analyzed their preferred methods for accessing information and making purchases within a marketplace. Through the study of real-life cases , we tried to gain valuable insights into enhancing the marketplace experience for Generation Z.
The workshop was held on the DMA Conference in Vienna June 2024.
Understanding User Behavior with Google Analytics.pdfSEO Article Boost
Unlocking the full potential of Google Analytics is crucial for understanding and optimizing your website’s performance. This guide dives deep into the essential aspects of Google Analytics, from analyzing traffic sources to understanding user demographics and tracking user engagement.
Traffic Sources Analysis:
Discover where your website traffic originates. By examining the Acquisition section, you can identify whether visitors come from organic search, paid campaigns, direct visits, social media, or referral links. This knowledge helps in refining marketing strategies and optimizing resource allocation.
User Demographics Insights:
Gain a comprehensive view of your audience by exploring demographic data in the Audience section. Understand age, gender, and interests to tailor your marketing strategies effectively. Leverage this information to create personalized content and improve user engagement and conversion rates.
Tracking User Engagement:
Learn how to measure user interaction with your site through key metrics like bounce rate, average session duration, and pages per session. Enhance user experience by analyzing engagement metrics and implementing strategies to keep visitors engaged.
Conversion Rate Optimization:
Understand the importance of conversion rates and how to track them using Google Analytics. Set up Goals, analyze conversion funnels, segment your audience, and employ A/B testing to optimize your website for higher conversions. Utilize ecommerce tracking and multi-channel funnels for a detailed view of your sales performance and marketing channel contributions.
Custom Reports and Dashboards:
Create custom reports and dashboards to visualize and interpret data relevant to your business goals. Use advanced filters, segments, and visualization options to gain deeper insights. Incorporate custom dimensions and metrics for tailored data analysis. Integrate external data sources to enrich your analytics and make well-informed decisions.
This guide is designed to help you harness the power of Google Analytics for making data-driven decisions that enhance website performance and achieve your digital marketing objectives. Whether you are looking to improve SEO, refine your social media strategy, or boost conversion rates, understanding and utilizing Google Analytics is essential for your success.
Italy Agriculture Equipment Market Outlook to 2027harveenkaur52
Agriculture and Animal Care
Ken Research has an expertise in Agriculture and Animal Care sector and offer vast collection of information related to all major aspects such as Agriculture equipment, Crop Protection, Seed, Agriculture Chemical, Fertilizers, Protected Cultivators, Palm Oil, Hybrid Seed, Animal Feed additives and many more.
Our continuous study and findings in agriculture sector provide better insights to companies dealing with related product and services, government and agriculture associations, researchers and students to well understand the present and expected scenario.
Our Animal care category provides solutions on Animal Healthcare and related products and services, including, animal feed additives, vaccination
Instagram has become one of the most popular social media platforms, allowing people to share photos, videos, and stories with their followers. Sometimes, though, you might want to view someone's story without them knowing.
4. What we’re going to talk about
We'll briefly review the basics of
accessible user experiences.
We’ll discuss how disabilities or
conditions relate to what people need
for an accessible, usable experience,
and our responsibility to our users.
Enjoy some boss ‘60s culture.
7. Poll: If you use a screen reader, like JAWS or
NVDA, to test for accessibility, will that tell
you if your digital project is accessible to
all users?
8. There’s no silver bullet…
“No tool exists that you can run against
your web site (or web page for that
matter) in order to assert that it is
accessible and/or complies with the
Section 508 provisions or the
Web Content Accessibility
Guidelines [WCAG], however much
you are willing to pay … (continued)
9. And furthermore…
“When a web site claims Section 508
Conformance or WCAG Conformance from
some tool or other (and many do it), the
most it can mean is that the site (or page)
passed all of the automatic Section 508 or
WCAG tests.”
– Jim Thatcher, Web Accessibility Testing
10. “Oh, one of us tested it with a
screen reader…”
But what have you done to
ensure your project is
accessible?
15. Craft a wonderful, engaging,
accessible user experience:
Design for accessibility.
Include people
with
disabilities in
user research.
Write content in
plain language.
Use good
development
practices.
Choose accessible
platforms, frameworks,
and technologies.
Consider accessibility at the
beginning of your
project.
16. You'll do this by considering the
conditions and needs of your current and
prospective audience…and thinking of how will
this inform each team member’s work.
17. Ona, age 65
“Everyone says technology is easy
to use, but I find it frustrating.”
About her:
• Retired baker
• Not very tech savvy
• Uses e-mail and Skype to
talk with her grandkids
• New Facebook user
• Her daughter, Amelia (a
web developer), set up her
browser.
Accessibility consideration:
Tunnel vision (loss of peripheral
vision) due to glaucoma
Technology use:
Galaxy S5
AsusVivoBook
Accommodations or
assistive technologies used:
Using Stylish, a Firefox and
Chrome add-on, Amelia
created custom style sheets
to override font sizes that are
too large on websites (also
see UserStyles.org).
Needs for a good experience:
• Very small text (while neither intentional nor
a best practice, some sites almost meet her
needs because they use small text)
• Ability to resize text based on her personal
style sheets, or through her browser or
devices
18. How to test for Ona’s considerations
Tools and/or how to test:
• Ensure text is set in percentages (preferable) or ems.
• Use ems for container divs; set up some custom styles and see if they work
with your project; if they don't, you'll need to adjust your code to fix the
conflicts.
• Turn off styles and see if the content makes sense—make sure there's no
hidden content, that becomes visible with styles overriden or disabled,
and doesn't make sense when it's visible.
Applicable WCAG 2.0 standards and verification techniques:
• Distinguishable Content: Guideline 1.4
• Resize text: Success Criterion 1.4.4
• Contrast (Enhanced): Success Criterion 1.4.6
• Visual Presentation: Success Criterion 1.4.8
• Images ofText: Success Criterion 1.4.9
19. Myrna, age 51
“Can you hook me up to an
internet IV?”
About her:
• Teacher
• Mega sports fan and avid
video gamer
• Computer savvy: ran her
middle school's computer
lab
• Enjoys watching sports
videos on her laptop or on
her phone
Accessibility consideration:
She’s had photosensitive
epilepsy since age 5. Flashing
content can trigger seizures
(see London 2012 Olympics
Site Withdraws Film). She has
aging eyes, and needs larger
fonts.
Technology use:
Acer Chromebook 13; Dell
Inspiron 11; iPhone 5S
Accommodations or
assistive technologies used:
• None
Needs for a good experience:
• She can't use content that causes the screen
to flash more than three times within one
second.
• This includes videos, animations, and
Escher-style graphics that are optical
illusions or have strobe-like effects.
• She must be able to resize text.
20. How to test for Myrna’s considerations
Tools and/or how to test:
• UseTrace Center's PEAT (Photosensitive Epilepsy AnalysisTool).
• This is one area that is a bit beyond “access”—most people with epilepsy
will be able to access your content, and they won't necessarily know if
your content can induce a seizure; flashing content is potentially
dangerous.This does not test static graphics that can be dangerous.
• If you must post content that could cause a seizure, post it with a warning
and do not auto-play it or show it automatically.
• See OK.gov's information about graphics that can cause seizures and
WebAIM's guidance on seizures and neurological conditions.
• Ensure font sizes are in percentages (preferable) or ems so users can zoom
in browsers.
Applicable WCAG 2.0 standards and verification techniques:
• Seizures: Guideline 2.3
• ResizeText: Success Criterion 1.4.4
• Contrast (Minimum): Success Criterion 1.4.3
21. Glen, age 25
“I’ve got to take a pic of that …
and tweet it, Instagram it, and …”
About him:
• Thinks texting is an art
• Blogs about food
• Takes lots of pictures
• PowerYelp user
• Impulsive and will go
almost anywhere on the
spur of the moment
Accessibility consideration:
Has deuteranopia (color blind
with green deficiencies)
Technology use:
iPhone 6 Plus phone; HP
Slate 10Tablet
Accommodations or
assistive technologies used:
• The HueVue app helps Glen
to identify colors when he
needs them. It's not always
convenient to use.
Needs for a good experience:
• Content that doesn't rely on color to provide
meaning or content
• Buttons and controls that have clearly
indicated states (active or inactive)
• Uses maps a lot and finds them difficult to
understand when they're color coded
without further explanation of color
meanings
22. How to test for Glen’s considerations
Tools and/or how to test:
• Wickline Colorfilter
• Vischeck (the online page testing function is down, but you can run
images or download it)
Applicable WCAG 2.0 standards and verification techniques:
• Contrast (Enhanced): Success Criterion 1.4.6
23. Betty, age 16
“I love looking at vintage maps
and stamps.”
About her:
• Average kid, loves games,
hates homework
• Was in an accident at age
7; injuries resulted in brain
damage
• Wants to be a veterinarian
• Collects maps and stamps
Accessibility consideration:
Has a mild cognitive
(intellectual) disability; short-
term memory loss
Technology use:
Galaxy Note 4 phone
(Android), MacBook Pro
Accommodations or
assistive technologies used:
• Occasionally uses a screen
reader, particularly when
she's researching online for
homework assignments or
when she has a hard time
understanding things
(narration is easier to
understand than reading)
Needs for a good experience:
• Simple, clear layout; consistent navigation
• Headings and bullets
• Content written in plain language without
slang, irony, and sentence fragments
• Inline definitions for abbreviations,
acronyms, and jargon
• Iconography, drawings, animations
• Captions and transcripts for videos
24. How to test for Betty’s considerations
Tools and/or how to test:
• Check the fonts you’ve used to ensure that lower and uppercase letters
(especially “i” and “L”) are clearly distinguishable from other letters.
• Test your content with users.
• Do a hallway test: Set up in a coffee shop close to a high school and ask
people what your content means; ask them to complete a task (or how
they'd complete a task) based on instructions you provide.
• Review the wireframes and initial design against WebAIM's Accessibility
for Designers reference.
Applicable WCAG 2.0 standards and verification techniques:
• Adaptable: Guideline 1.3
• Visual Presentation: Success Criterion 1.4.8
• Reading Level: Success Criterion 3.1.5
25. George, age 37 “I need to find a job—fast!”
About him:
• Unemployed—was a
general contractor and
house flipper in Florida;
was hit hard in the
housing market crash
• Lives with his parents until
his situation improves
• Works odd jobs to pay
back his outstanding loans
Accessibility consideration:
Uses outdated technology
because he can't afford to
replace his devices
Technology use:
iPhone 3GS; Dell Latitude
D630. He gets frustrated
using both devices because
content loads slowly
(content weight is heavy).
Accommodations or
assistive technologies used:
• None
Needs for a good experience:
• High contrast since his phone doesn't adjust
for lighting conditions
• Well-formed code that isn't bloated or too
heavy from multiple processes, that will load
as quickly as possible
26. How to test for George’s considerations
Tools and/or how to test:
• Check contrast of all foreground and background color combinations: In
this mobile first age, make sure color contrast is at least 7:1; if mobile is a
priority, make it happen; it's not difficult.
• Use Paciello Group's Color Contrast Analyser orWebAIM's Color Contrast
Checker.
Applicable WCAG 2.0 standards and verification techniques:
• Distinguishable: Guideline 1.4
• Contrast (Enhanced): Success Criterion 1.4.6
• Parsing: Success Criterion 4.1.1
27. What didn't I mention?
• People who are blind
• People who are deaf or
hard-of-hearing
• People who have autism or
Asperger Syndrome, or who
are on the autism spectrum
• People who have cerebral
palsy
• People who have chronic
pain
• People who have low-
language proficiency
• People who have migraines
• People who have dyslexia
• People who are DeafBlind
• What about multiple
disabilities?
• More mobile situations
• So much more …
28. Now: How will you and each of your team
members apply these concepts to
your work?
29. Have you done user research with
people with disabilities?
30. Only you can prevent barriers to
content.
Photograph of “Smokey Bear” character holding a sign that says, “Remember – Only you can prevent forest fires!”
31. We are problem solvers
+ + + =
hard work!
design development content
project
management
32. What's your role?
Use the Accessibility ResponsibilityTool to break
down theWCAG 2.0 guidelines by team roles
and responsibilities (see the resources
section).
33. Wrap-up/recap
• Provide a good user
experience—that’s when
everyone can access our
information.
• Use the six points for
creating an accessible,
engaging user experience.
• Prevent any barriers to
access—it’s in your hands.
• Accessibility isn't a feature.
• Don't get into a rut with
Agile—minimum viable
product must work for your
entire audience.
• People are watching digital
media hard and they’re fed
up with inaccessibility!
• User research is the key to
good experiences—know
your audience’s needs and
involve them in your testing.
34. Remember …
“For people without disabilities, technology
makes things easier. For people with
disabilities, technology makes things
possible.”
– IBM training manual, 1991
36. Jason Becker, age 45
(real life example)
What would he do without
accessible technology?
About him:
• Jason Becker is a highly
respected guitarist who
played with David Lee
Roth’s band when he was
diagnosed with ALS.
• He still writes music and
has released several
albums after he lost the
use of his hands and arms.
Accessibility consideration:
He's paralyzed, except for his
eyes, facial muscles, and lips.
He uses a custom eye chart to
communicate, and he only uses
his head and eyes to control his
computer system.
Technology use:
Speculatively, a MacBook
Accommodations or
assistive technologies used:
• Custom eye chart
• Eye tracking software
• Writes music using his head
and eyes
Needs for a good experience:
• Support for non-mouse/alternate keyboard
devices
• Well-designed pages, without many links
• While using his eyes as a keyboard, he can
tire easily from exertion before he gets to
any info he needs and the task he needs to
complete.
37. How to test for Jason’s considerations
Tools and/or how to test:
• Ensure keyboard/device independence—unplug your mouse and test with
a keyboard!
• SeeW3C's keyboard navigation schemes for widgets.
• Keep abreast ofW3C's Indie UI Events spec to see what effect it will have
eventually.
• Use device independent event handlers in scripts.
Applicable WCAG 2.0 standards and verification techniques:
• Keyboard Accessible: Guideline 2.1
39. WCAG 2.0 and general *a11y
• Constructing a POURWebsite,WebAIM
• BBC’s Future Media Standards and Guidelines
• A11y Buzz
• Accessibility ResponsibilityTool, WETToolkit
* accessibility
40. Mobile
• MobileAccessibilityGuidelines, BBC
• MobileAccessibilityTests, Henny Swan
• iOS Accessibility – A Useful Guide ForTesting, Rosie
Sherry
• Setting Up iOS and Android for AccessibilityTesting,
KathyWahlbin
• Why MobileAccessibility Matters: Best Practices to
MakeYour Mobile SiteAccessible, mobiForge
41. Project management
• Integrating Accessibility in the Organization’sWeb
Development Life Cycle, Denis Boudreau
• Accessibility for Project Managers, Henny Swan
• Managing AccessibilityCompliance in the Enterprise,
Karl Groves
• Plan for Accessibility, Option Keys
• PlanningAccessibility,Government of Canada
• Just Ask: Integrating AccessibilityThroughout Design,
Shawn Lawton Henry
42. Design
• Web Accessibility for Designers,WebAIM
• Just Ask: Integrating AccessibilityThroughout Design,
Shawn Lawton Henry
• Design Considerations,WebAIM
• Color Contrast Checker,WebAIM
• AccessibilityColor Wheel
• Trace Photosensitive Epilepsy AnalysisTool (PEAT)
43. Development resources 1
• Web Accessibility for Developers (videos), BBC
• Build a code library or find one on Github!
• Use code generators (seeAccessify’s tools).
• Web DeveloperToolbar, Chris Pederick
• Firebug, Mozilla
• WCAG 2.0 Checklist,WebAIM
• Web AccessibilityGoneWild,WebAIM
44. Development resources 2
• W3C MobileWeb Best Practices
• Juicy Studio AccessibilityToolbar —for ARIA, data
tables, color contrast
• aChecker, Inclusive Design Institute at OCAD University
• WAVEToolbar,WebAIM
• Favelets for CheckingWeb Accessibility, JimThatcher
45. Writing content
• Accessibility forWebWriters, by 4 Syllables
• Content and Usability:WebWriting,Web Credible
• Make it Plain:Accessibility and UsabilityThrough Plain
Language,Angela Hooker (hey!)
• Plain Language:Accessibility for Information,Whitney
Quesenbery
• Plain LanguageChecklist, PlainLanguage.gov
47. Quality assurance 2
• Firebug, Mozilla
• Favelets for CheckingWeb Accessibility, JimThatcher
• Trace Photosensitive Epilepsy AnalysisTool (PEAT) –
tests flashing content
• WAVE,WebAIM
• Web Accessibility Initiative (WAI), EvaluatingWebsites
for Accessibility
48. Quality assurance 3
• Central Office of Information (COI), Delivering Inclusive
Websites
• Establishing a Screen ReaderTest Plan, Henny Swan
• How to Use NVDA and Firefox toTest for Accessibility,
Marco Zehe
• Web AccessibilityGoneWild,WebAIM
49. Usability
• UsabilityTesting and Conducting UsabilityTesting, Just
Ask: Integrating AccessibilityThroughout Design, Shawn
Lawton-Henry
• UsabilityTesting for People with Disabilities, Kathy
Wahlbin and Mary Hunter Utt
• Steve Krug, Rocket Surgery Made Easy
50. Thanks, guys and dolls!
Angela M. Hooker
@AccessForAll
SlideShare
LinkedIn
ange@angelahooker.com
51. Photo credits 1
• “Youth Culture – Mods and Rockers…” PaulTownsend
https://www.flickr.com/photos/brizzlebornandbred/5130733677/
• Veterans of the FSM
https://www.flickr.com/photos/quinnanya/15230011727
• “1964 Ad,Advance Spectacle Co.,” Classic Film
https://www.flickr.com/photos/29069717@N02/14208321625/
• “Silver bullet,” Ed Schipul
https://www.flickr.com/photos/eschipul/4160817135
• “DECVT05Terminal,” Matthew Ratzloff
https://www.flickr.com/photos/mratzloff/9171586772/
• “Starry Night into the Light,” Bo Insogna,TheLightningMan.com
https://www.flickr.com/photos/thelightningman/12056816983
• “JHS Cheerleaders…” Beth Scupham
https://www.flickr.com/photos/bethscupham/5919260366/
52. Photo credits 2
• Don Sniegowski,They're Off
https://www.flickr.com/photos/sniegowski/8671556299
• "Mission: Impossible…“ MidCentArc
https://www.flickr.com/photos/midcentarc/8189306568/
• ZombiesAhead, BC Ministry ofTransportation and Infrastructure
https://www.flickr.com/photos/tranbc/10578481755
• “Street Painter,” Pedro Ribeiro Simoes
https://www.flickr.com/photos/pedrosimoes7/190673196/
• Daftastic Data atWoodstock, Suzi Duke
https://www.flickr.com/photos/suzijan
• “TV ShowsWe Used toWatch,” PaulTownsend
https://www.flickr.com/photos/brizzlebornandbred/4933754453/
53. Photo credits 3
• “Engineering Department Employees, 1962,” Seattle Municipal
Archives
https://www.flickr.com/photos/seattlemunicipalarchives/4818952324
• “Smokey Bear” http://cbldf.org/wp-content/uploads/2012/11/gov-
comics024-1024x928.jpg
• “Family Heirloom,” Ken
https://www.flickr.com/photos/skistz/398429879
• “Duluoz Cats,” Groovy
https://www.flickr.com/photos/duluoz_cats/249672451/
• “Huh…?!?” Cheryl
https://www.flickr.com/photos/eraphernalia_vintage/2691558545
• “Martin Luther King, Jr. I Have a Dream Speech,” David Erickson
https://www.flickr.com/photos/e-strategycom/1054179588/
54. Photo credits 4
• Register toVote, Kheel Center
https://www.flickr.com/photos/kheelcenter/5278846477
• "New Shoes," Suedehead
https://www.flickr.com/photos/suedehead/6306822304
• "Royal PortableTypewriter,"Alexkerhead
https://www.flickr.com/photos/alexkerhead/3495304775
• “American Adulthood,” A. Davey
https://www.flickr.com/photos/adavey/15215010126/
• "BrotherTed andT'Chaka..."Virgo200745
https://www.flickr.com/photos/brodeuse/2242880390
• "1964 Human Interest Piece …" Classic Film
https://www.flickr.com/photos/29069717@N02/16762991150/
• Happy NewYear 2015! http://itsmyfun.net/happy-new-year-2015/
55. Photo credits 5
• “SteveWatson,” Graham Lees
https://www.flickr.com/photos/tram_painter/4181430550/
• "ConstructionWorker 3,” Johnny Mitchell
https://www.flickr.com/photos/johnny_mitchell/15961202/
• "Meaghan," Hillary Boles
https://www.flickr.com/photos/hillaryraindeer/6209841403
• "The Mummy,"Tom
https://www.flickr.com/photos/tom1231/5069205181
• "Louis Stulberg looks on as Hubert H. Humphrey gives a speech
during his November 15, 1968 presidential campaign," Kheel
Center https://www.flickr.com/photos/kheelcenter/5278459275
• “1960s ComputerTerminal,” John Drake
https://www.flickr.com/photos/johndrake45/8999339647/
Editor's Notes
Look at your team! Aren’t they spiffy?
Surprise! It's 2015, and we're still struggling to make our web and digital media projects accessible—despite our laws and requirements, and organizations receiving negative press and lawsuits stemming from inaccessibility.
Why?
Let’s go back in time—to the ‘60s, and in black and white—for a bit of help…
Does anyone here wear glasses? Yes, they’re an assistive device!
Why am I asking you about assistive technologies?
Empathy for your users; relate to them; see yourself in their shoes
When I ask people if they've considered accessibility, usually the first thing they say is, "Oh, we tested it with a screen reader!" I ask what else they've done to ensure their project is accessible, and I all I hear is <crickets>.
As a person who is visually impaired and an occasional screen reader user, I want to scream some days because people think that testing with a single tool ensures accessibility for all people who have disabilities. Our needs are different.
Sometimes people are shocked when they hear that assistive technologies aren't the starting point for ensuring accessibility, or sometimes people don't understand how to make digital media accessible in other situations when people don't use assistive technologies.
Good UX is the goal: Your goal is to give a good experience to all your users—that includes people with disabilities. Get into the habit of thinking of accessibility as part of the UX process. Sometimes accessibility principles will address situations where different abilities aren't the issue.
Think about it like this—what do drivers need on the road?
Signs with text large enough to be read quickly and without straining
Good contrast (green/white; yellow/black; white/black; etc.)
Lights that direct our path
Rules that govern driving, for a safe experience
A place to pull over during emergencies
Help for when you run into problems (call box)
Six major points to craft an accessible user experience.
So, you see that it's not only people who serve in a UX role that are responsible for crafting a good user experience.
Sometimes we get into a rut and put accessibility in a box when we think about how to solve accessibility problems.
Let's look at who your audience members could be and what they need to have an accessible experience—persona style. We’re anticipating their needs.
These personas cover user needs, accessibility considerations, how to test, and WCAG 2.0 requirements (main points—not necessarily all requirements).
So, as you can see, we really can't lump people into one box when it comes to understanding disabilities, how people cope with them, and the assistive technologies and adaptive tools they may use.
For example:
If you know your audience includes people who have low-language proficiency, how will you write your content?
If your audience has people who use a head wand to navigate, how will you design the layout with them in mind?
What about information architecture for people who have cognitive impairments?
Etc.
You should test with assistive technologies (AT); however, unless you’re very experienced at it, you’re probably not using AT the way your users do.
You won't know if your users will encounter a bug. You can file a bug with the AT maker.
Have a solution for the problematic component ahead of time, so you won't have to scramble at the last minute to help your users. Always be prepared.
Know that you should have users test before you launch; if you're new to accessibility, testing with AT isn't necessarily easy.
You probably won't use AT the way real users do. Though there are resources out there that will lessen the learning curve, it's not quite the same.
Build in slots in your usability testing phase for people with disabilities and know that people with different abilities may use AT differently than you think.
If users encounter barriers that prevent them from accessing our content, then we've created them by not considering our users needs.
You can't say, "This is an excellent design!" if it doesn't work for all or most of your users. In that case, it's just unfinished work, and you're introducing barriers, which is always unnecessary.
Developers: "It works!" No, it doesn't, because there's a group of people who can't use it.
If you’re an agile shop, I don’t want to hear that accessibility is a feature that can be added later; your minimum viable product isn’t viable if your users can’t use it. Build accessibility into your user stories.
I believe in role-based accessibility—it helps us incorporate accessibility in our work so we’re not left at the end of a project wondering how we’re going to make it accessible.
Also remember, if you plan to get older, you’re probably going to need accessibility one day.