Organizations are looking for mobile accessibility standards but is mobile different than desktop? Learn about is new in WCAG 2.1, Europe and around the world.
Accessibility is not a rare edge case, it is something that concerns all of us. This is an introduction to Web Accessibility for Web Developers, in context of the German BITV and the international WAI Guidelines (mostly WCAG 2.0). It should raise general awareness of accessibility for Web Development, and shows that accessibility is not an extreme hard to implement requirement, but a matter of care and common sense.
With increased complaints and legal action for organisations of inaccessible websites (Coles, Peapod) and apps (Westpac), now is the time for all web and app Project Managers, Developers, UX/Designers, Content Producers, Business Analysts and Testers to be ‘baking in’ accessibility into processes and work practices.
This presentation will show that accessibility is everyone’s responsibility and it is not difficult to get started or find resources that will help you and your team produce a website, app or digital presence that works for everyone!
An introduction to the concept of Web Accessibility describing the What, Why and How of making your website accessible i.e. available to users with disabilities such as color blindness, low vision, deafness and/or motor control disability.
Understanding and Supporting Web AccessibilityRachel Cherry
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 accessible, all users can access your content and functionality no matter their abilities. 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. Most accessibility features will also improve your SEO.
When your site is inaccessible, research shows you could be excluding up to 20 percent of your users.
This talk will cover the basics of accessibility, why it’s important, and how you can support accessibility in your projects.
Learn about the basics of web accessibility: what it is, who it affects, why it matters, and some of the fundamental things you ought to be doing in your pages to make them more accessible.
Learn about the new A and AA criteria in WCAG 2.1 from Jason Ament and Jen Smith. This presentation was given on 3/20/19 to a group of Seattle area accessibility folks as part of the A11ySEA MeetUp group.
The views, thoughts, and opinions expressed in this presentation belong to the speakers (Jen and Jason) and do not represent the views, policies, or positions of our employers or the a11y SEA community
Accessibility is not a rare edge case, it is something that concerns all of us. This is an introduction to Web Accessibility for Web Developers, in context of the German BITV and the international WAI Guidelines (mostly WCAG 2.0). It should raise general awareness of accessibility for Web Development, and shows that accessibility is not an extreme hard to implement requirement, but a matter of care and common sense.
With increased complaints and legal action for organisations of inaccessible websites (Coles, Peapod) and apps (Westpac), now is the time for all web and app Project Managers, Developers, UX/Designers, Content Producers, Business Analysts and Testers to be ‘baking in’ accessibility into processes and work practices.
This presentation will show that accessibility is everyone’s responsibility and it is not difficult to get started or find resources that will help you and your team produce a website, app or digital presence that works for everyone!
An introduction to the concept of Web Accessibility describing the What, Why and How of making your website accessible i.e. available to users with disabilities such as color blindness, low vision, deafness and/or motor control disability.
Understanding and Supporting Web AccessibilityRachel Cherry
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 accessible, all users can access your content and functionality no matter their abilities. 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. Most accessibility features will also improve your SEO.
When your site is inaccessible, research shows you could be excluding up to 20 percent of your users.
This talk will cover the basics of accessibility, why it’s important, and how you can support accessibility in your projects.
Learn about the basics of web accessibility: what it is, who it affects, why it matters, and some of the fundamental things you ought to be doing in your pages to make them more accessible.
Learn about the new A and AA criteria in WCAG 2.1 from Jason Ament and Jen Smith. This presentation was given on 3/20/19 to a group of Seattle area accessibility folks as part of the A11ySEA MeetUp group.
The views, thoughts, and opinions expressed in this presentation belong to the speakers (Jen and Jason) and do not represent the views, policies, or positions of our employers or the a11y SEA community
This primer on mobile accessibility will give you a solid grounding on standards, guidelines and principles of making websites accessible on mobile devices, and demonstrate some of the accessibility features available on iOS and Android.
This presentation was delivered at Digpen 7:
http://lanyrd.com/2014/digpen7/sdfcth/
Web Accessibility: A Shared ResponsibilityJoseph Dolson
This a presentation prepared for a Montana Web Developer's Meetup in December, 2011. The focus is on collaborating with content providers and employers to share the responsibility for web accessibility.
This presentation will help you understand:
- The legal requirements behind Web Accessibility
- How do people with disabilities use the web and what assistive technologies they use
- How good usability makes up for better accessibility and improves site’ SEO
- Financial benefits of having an accessible website
If a website or mobile app is not accessible to all potential visitors, is it truly a quality product? Services, products, information, and entertainment on the web and mobile devices can be made available to millions of consumers with vision, hearing, or motor control difficulties by complying with accessibility standards. Assistive technologies enable access by converting the text and images of mobile screens and web pages into computerized voice. But these technologies cannot interpret pages that are not built and tested for compliance to accessibility standards and programming guidelines. Join Nancy Kastl to learn about Section 508 and WCAG standards, Mobile Web Best Practices, and Apple and Android Developer Accessibility Guidelines. Learn how to test for accessibility on mobile devices and desktop using screen readers and open source tools. Become an advocate of accessible mobile apps and websites throughout the project lifecycle and add accessibility testing to your testing capabilities.
A Web for Everyone: Accessibility as a design challengeWhitney Quesenbery
Let's get past the idea that checklists and compliance all there is to accessibility. Designing for accessibility is a user experience design problem, starting with understanding how people with disabilities use your products. If we aim to design for all senses we can focus on easy interaction, helpful wayfinding, clean presentation, plain language and media instead of "rules." Doing so, we can create a web for everyone and a delightful user experience where accessibility and usability work together.
Updated January 21
Replay of the O'Reilly webcast: http://www.oreillynet.com/pub/e/2992
Transcript of the O'Reilly webcast: http://www.wqusability.com/handouts/AWFE-Challenge-OReilly-Transcript.pdf
Incorporating accessibility into your software.
What does accessibility mean?
Why should we do this?
How we should do this?
What impacts does this have?
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?
Practical tools for Web Accessibility testingToufic Sbeiti
There is no single tool that does a full accessibility assessment of a web page. Developers use a variety of tools to help them evaluate websites. This is a practical talk with lots of demos. I will share my favorites, free and easy to use, tools to measure the level of accessibility of web page.
This PPT throws light on some of the essential elements of Accessibility testing which have become crucial to ensure quality in this day and age. To know more on accessibility testing, accessibility mandates, WCAG 2.0, paired testing approach, accessibility guidelines and standards go through this presentation as well as the ones coming soon.
Early introduction of WCAG 2.2 for understanding the likely changes in preparation for future adoption.
Presented at Accessibility Twin Cities (A11yTC) Meetup July 26, 2021
Automating Accessibility Tests: Web is for Everyone (by Manoj Kumar)Applitools
Accessibility testing is an all too often forgotten part of test automation, typically left for the manual test team. Well now we can go back to our managers with some really great initiatives on how to save them time/money by automating these tests as well.
Focusing on it will not only help those with disabilities who use the application you're testing, but optimizing for accessibility will also make automated testing so much easier to accomplish and maintain for your app.
Test Automation and Selenium expert Manoj Kumar takes this in-depth look at accessibility testing, covering the essentials, including:
• What is Accessibility testing
• The Accessibility standards
• Different tools available to automate Accessibility testing
• How to automate Accessibility testing, and what resources are needed
• How to implement an effective Accessibility strategy within your organization
Web accessibility 101: The why, who, what, and how of "a11y"ecentricarts
Our in-house ecentricarts Accessibility Team (known as EAT) has compiled a ton of resources to help you understand the ins and outs of web accessibility. This includes: why it matters, who it impacts, common misconceptions, a beginner's guide to WCAG 2.0 and accessibility legislation, and how you can test, design, develop, and create more accessible websites.
This presentation also includes examples of before/after screenreader demos, and our 2017 company video made with described audio.
Even though WCAG 2.0 was written before smartphones put mobile accessibility in the public eye, WCAG 2.0 was written to be forward-thinking and has proved to be so. During this session, you’ll learn about available mobile accessibility resources from the W3C Web Accessibility Initiative. You’ll also learn about the new work going on in the Mobile Accessibility Task Force to create and update techniques for WCAG in mobile websites and native apps.
This primer on mobile accessibility will give you a solid grounding on standards, guidelines and principles of making websites accessible on mobile devices, and demonstrate some of the accessibility features available on iOS and Android.
This presentation was delivered at Digpen 7:
http://lanyrd.com/2014/digpen7/sdfcth/
Web Accessibility: A Shared ResponsibilityJoseph Dolson
This a presentation prepared for a Montana Web Developer's Meetup in December, 2011. The focus is on collaborating with content providers and employers to share the responsibility for web accessibility.
This presentation will help you understand:
- The legal requirements behind Web Accessibility
- How do people with disabilities use the web and what assistive technologies they use
- How good usability makes up for better accessibility and improves site’ SEO
- Financial benefits of having an accessible website
If a website or mobile app is not accessible to all potential visitors, is it truly a quality product? Services, products, information, and entertainment on the web and mobile devices can be made available to millions of consumers with vision, hearing, or motor control difficulties by complying with accessibility standards. Assistive technologies enable access by converting the text and images of mobile screens and web pages into computerized voice. But these technologies cannot interpret pages that are not built and tested for compliance to accessibility standards and programming guidelines. Join Nancy Kastl to learn about Section 508 and WCAG standards, Mobile Web Best Practices, and Apple and Android Developer Accessibility Guidelines. Learn how to test for accessibility on mobile devices and desktop using screen readers and open source tools. Become an advocate of accessible mobile apps and websites throughout the project lifecycle and add accessibility testing to your testing capabilities.
A Web for Everyone: Accessibility as a design challengeWhitney Quesenbery
Let's get past the idea that checklists and compliance all there is to accessibility. Designing for accessibility is a user experience design problem, starting with understanding how people with disabilities use your products. If we aim to design for all senses we can focus on easy interaction, helpful wayfinding, clean presentation, plain language and media instead of "rules." Doing so, we can create a web for everyone and a delightful user experience where accessibility and usability work together.
Updated January 21
Replay of the O'Reilly webcast: http://www.oreillynet.com/pub/e/2992
Transcript of the O'Reilly webcast: http://www.wqusability.com/handouts/AWFE-Challenge-OReilly-Transcript.pdf
Incorporating accessibility into your software.
What does accessibility mean?
Why should we do this?
How we should do this?
What impacts does this have?
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?
Practical tools for Web Accessibility testingToufic Sbeiti
There is no single tool that does a full accessibility assessment of a web page. Developers use a variety of tools to help them evaluate websites. This is a practical talk with lots of demos. I will share my favorites, free and easy to use, tools to measure the level of accessibility of web page.
This PPT throws light on some of the essential elements of Accessibility testing which have become crucial to ensure quality in this day and age. To know more on accessibility testing, accessibility mandates, WCAG 2.0, paired testing approach, accessibility guidelines and standards go through this presentation as well as the ones coming soon.
Early introduction of WCAG 2.2 for understanding the likely changes in preparation for future adoption.
Presented at Accessibility Twin Cities (A11yTC) Meetup July 26, 2021
Automating Accessibility Tests: Web is for Everyone (by Manoj Kumar)Applitools
Accessibility testing is an all too often forgotten part of test automation, typically left for the manual test team. Well now we can go back to our managers with some really great initiatives on how to save them time/money by automating these tests as well.
Focusing on it will not only help those with disabilities who use the application you're testing, but optimizing for accessibility will also make automated testing so much easier to accomplish and maintain for your app.
Test Automation and Selenium expert Manoj Kumar takes this in-depth look at accessibility testing, covering the essentials, including:
• What is Accessibility testing
• The Accessibility standards
• Different tools available to automate Accessibility testing
• How to automate Accessibility testing, and what resources are needed
• How to implement an effective Accessibility strategy within your organization
Web accessibility 101: The why, who, what, and how of "a11y"ecentricarts
Our in-house ecentricarts Accessibility Team (known as EAT) has compiled a ton of resources to help you understand the ins and outs of web accessibility. This includes: why it matters, who it impacts, common misconceptions, a beginner's guide to WCAG 2.0 and accessibility legislation, and how you can test, design, develop, and create more accessible websites.
This presentation also includes examples of before/after screenreader demos, and our 2017 company video made with described audio.
Even though WCAG 2.0 was written before smartphones put mobile accessibility in the public eye, WCAG 2.0 was written to be forward-thinking and has proved to be so. During this session, you’ll learn about available mobile accessibility resources from the W3C Web Accessibility Initiative. You’ll also learn about the new work going on in the Mobile Accessibility Task Force to create and update techniques for WCAG in mobile websites and native apps.
I don't always feel like a wizard. Like many of you, I've been doing operations for a couple of years, and I still have a TON TO LEARN about how to do this "SRE" job.
But along the way, I have learned a few ways to debug tricky problems, get the information I need from my colleagues, and get my job done. We're going to talk about
* how asking dumb questions is actually a superpower
* how you can read the source code to the Linux kernel when all else fails
* debugging tools that make you FEEL like a wizard
* and how understanding what your _organization_ needs can make you amazing
At the end, we'll have a better understanding of how you can get a lot of awesome stuff done even when you're not the highest level wizard on your team.
Accessibility metrics Accessibility Data Metrics and Reporting – Industry Bes...Ted Drake
Accessible version: http://www.last-child.com/a11y-data-metrics/
Learn how top companies are tracking and graphing product accessibility progress and incorporating data from automated, manual, and user testing to create management dashboards.
Determining which assistive technology to test with and what the accessibility test matrix should be is a challenge that many organizations are facing. The W3C provides information about what it means to be accessibility supported (http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html), but otherwise there is little guidance from the W3C or other guidelines. This session explores the question of whether it is sufficient to test with screen readers and what the test matrix should look like.
Focus Management and Accessibility on iOS, Android, and HTML5Ted Drake
The iPhone revolutionized the world for people with disabilities. Nobody (outside Apple) imagined this touch-only phone with no physical buttons would become the defacto device for people with disabilities. In fact, today's smart phones have not only replaced computers, but also expensive dedicated assistive technology equipment.
Make your application accessible
To be accessible, your app's content must be discoverable, actionable, and understandable. All of these depend on management of content focus. Fortunately, the platforms have made this fairly easy. The first step is being aware, that is the first part of this presentation. You will learn how to navigate with a phone's screen reader.
This presentation is available in an accessible version: http://www.last-child.com/focus-mobile-accessibility/
How to Become a Thought Leader in Your NicheLeslie Samuel
Are bloggers thought leaders? Here are some tips on how you can become one. Provide great value, put awesome content out there on a regular basis, and help others.
Does responsive design make a website more or less accessible? In this session you will learn best practices and techniques for accessible responsive design.
Responsive web design (RWD) can be very good for accessibility but is also poses some new challenges and design considerations to provide an optimal experience for people with disabilities. When done properly, RWD can address many accessibility issues related to low vision and certain mobility impairments. While responsive web design was not created specifically to address accessibility, its aim is to craft sites to provide an optimal viewing experience and easy navigation for all users and thereby address some accessibility issues. RWD enables the website to adapt its layout to the format of the viewing environment through the use of fluid, proportion-based grids, flexible images and CSS3 media queries. Responsive sites adjust to the screen and presents in the most readable and usable way for that particular screen size and format. This can ensure that font size remains readable and at a high resolution for people with low vision. It also keeps interactive elements large and easier to operate for people with mobility impairments. In this session we will review what a responsive website is and talk about the challenges and opportunities for accessibility in regards to responsive web design.
PDF, audio, and voiceover are now available on designintechreport.wordpress.com
Today’s most beloved technology products and services balance design and engineering in a way that perfectly blends form and function. Businesses started by designers have created billions of dollars of value, are raising billions in capital, and VC firms increasingly see the importance of design. The third annual Design in Tech Report examines how design trends are revolutionizing the entrepreneurial and corporate ecosystems in tech. This report covers related M&A activity, new patterns in creativity × business, and the rise of computational design.
Evaluating a product for accessibility can be challenging. How do you know a product is really accessible? What can you do to verify the information in a VPAT?
VPAT stands for Voluntary Product Accessibility Template. Organizations request VPATs for products to determine if it is accessible but how do you know if that information is correct and if the product is really accessible. In this session you will learn what a VPAT is and what you can do to evaluate a product to see if it meets the Section 508 standards and WCAG 2.0 guidelines.
SEO Campixx 2017 SEO Präsentation von Christian TembrinkChristian Tembrink
Begegne deinen zukünftigen Kunden im SEO Sales-Funnel möglichst früh mit hilfreichen Inhalten. Denn Google und SEO sind ein wichtiger Kunden-Kontaktpunkt zwischen einem Auslöser und dem späteren Kauf. Die Präsentation von Christian Tembrink zeigt, wie du abseits der hart umkämpften KeyWords einfach Nischen findest bei denen deine Inhalte einfach und schnell bei Google Ranken und aus Interessenten Kunden machen. Mehr Details findest du auch unter: https://www.netspirits.de/seo-beratung/
A presentation I made at the House of Lords on the future of digital heathcare looking at future technologies and those more immediate that can change patients outcomes
Optimize your social media channels in order to find a job!
Have a look at PART 2 of this infographic: http://www.slideshare.net/europelanguagejobs2015/job-search-facts-part-2
Mystery Meat 2.0 – Making hidden mobile interactions accessibleTed Drake
Mystery Meat was the unsavory term for hiding menus behind a parent link. Learn about today’s mobile version and how to make it accessible.
Accessible version: http://www.last-child.com/mystery-meat-2-accessible/
2017 CSUN The Art of Language in AccessibilityCrystal Baker
Presentation covers 9 key areas related to language and accessibility:
1. Person-First Language
2. Plain Language
3. Flesch-Kincaid Readability
4. Captioning
5. Transcription
6. Audio Description
7. Alternative Text
8. Long Description
9. Language Attribute
Community App for Promoting Cross-Cultural InteractionMike Taylor
Community app for promoting cross-cultural interaction with facebook, Gtalk and multiple social networking sites integration. It includes blogging and photo sharing
Community App for Promoting Cross-Cultural InteractionMike Taylor
Community app for promoting cross-cultural interaction with facebook, Gtalk and multiple social networking sites integration. It includes blogging and photo sharing
Hitting a moving target: achieving mobile inclusionJon Gibbins
Mobile interaction and use is narrowing the digital divide, providing new opportunities for digital inclusion around the world. Mobile platforms such as iOS, Android, and Windows are rapidly evolving with richer and more robust accessibility features and support, giving developers more ways to create accessible mobile web applications.
This presentation was delivered at e-access '13:
http://www.headstar.com/eaccess13/agenda.html
Online presentation:
http://www.w3.org/People/shadi/Talks/2013/1031/Mobile/
Or:
https://dl.dropboxusercontent.com/u/64311/training/2013-eaccess-553d7c/index.html
Mobile Accessibility Breakfast Briefing - Oct 2020User Vision
Contents:
Why mobile accessibility is important for everyone
How has legislation effected accessibility on mobile
WCAG 2.1
Built-in accessibility features on mobile
Mobile accessibility downfalls:
-Navigation
-Layout
-Providing use of context
Examples of common accessibility issues
SMARCOS Abstract Paper submitted to ICCHP 2012Smarcos Eu
This study is part of the European project "Smarcos" (http://www.smarcos-project.eu/) that includes among its goals the development of services which are specifically designed and accessible for blind users.
In this paper we present the prototype application designed to make the main phone features available in a way which is accessible for a blind user. The prototype has been developed to firstly evaluate the interaction modalities based on gestures, audio and vibro-tactile feedback.
This is my dissertation paper in which I present an approach towards developing interactive applications and propose a way this can be accomplished in a clean and maintainable way.
WorldKit: Rapid and Easy Creation of Ad-hoc Interactive
Applications on Everyday Surfaces.
Instant access to computing, when and where we need it,
has long been one of the aims of research areas such as
ubiquitous computing. In this paper, we describe the
WorldKit system, which makes use of a paired depth camera
and projector to make ordinary surfaces instantly interactive.
Using this system, touch-based interactivity can,
without prior calibration, be placed on nearly any unmodified
surface literally with a wave of the hand, as can other
new forms of sensed interaction. From a user perspective,
such interfaces are easy enough to instantiate that they
could, if desired, be recreated or modified “each time we sat
down” by “painting” them next to us. From the programmer’s
perspective, our system encapsulates these capabilities
in a simple set of abstractions that make the creation of
interfaces quick and easy. Further, it is extensible to new,
custom interactors in a way that closely mimics conventional
2D graphical user interfaces, hiding much of the
complexity of working in this new domain. We detail the
hardware and software implementation of our system, and
several example applications built using the library.
Log into android mobile to fetch the device oriented information using remote...eSAT Journals
Abstract This paper presents a platform for sharing device oriented mobile information via a local private cloud. The android application helps the user to fetch the device oriented information like missed call history, messages, battery status and GPS. Our system contains a website which helps the user to track all the required information through his personal account. Thus our system helps in making it easier to support new cloud services as output, and our android application helps in setting various triggers to push the device oriented information into the cloud. Keywords: List Android, Device oriented information, Cloud.
Log into android mobile to fetch the device oriented information using remote...eSAT Publishing House
IJRET : International Journal of Research in Engineering and Technology is an international peer reviewed, online journal published by eSAT Publishing House for the enhancement of research in various disciplines of Engineering and Technology. The aim and scope of the journal is to provide an academic medium and an important reference for the advancement and dissemination of research results that support high-level learning, teaching and research in the fields of Engineering and Technology. We bring together Scientists, Academician, Field Engineers, Scholars and Students of related fields of Engineering and Technology
AGE BASED USER INTERFACE IN MOBILE OPERATING SYSTEMIJCSEA Journal
The mobile phones are becoming now an irreplaceable utility of every household. It serves as wall clock, alarm clock, calculator, calendar, timer and many more, but have this multi-functionality overloaded the interface of the new generation of the mobile phones. The youth have adapted well to these multiple functionalities graphical user interface, but the interface has now haunting effects for usage by the two age groups i.e. elderly and kids. The interface may end up leading the new generation mobiles in the market useless or of very little use to the elderly and kids. This leads towards the need of age based user interface in the mobile operating system which will consist of interface selection home screen which further directs to age oriented interfaces.
AGE BASED USER INTERFACE IN MOBILE OPERATING SYSTEMIJCSEA Journal
The mobile phones are becoming now an irreplaceable utility of every household. It serves as wall clock, alarm clock, calculator, calendar, timer and many more, but have this multi-functionality overloaded the interface of the new generation of the mobile phones. The youth have adapted well to these multiple functionalities graphical user interface, but the interface has now haunting effects for usage by the two age groups i.e. elderly and kids. The interface may end up leading the new generation mobiles in the market useless or of very little use to the elderly and kids. This leads towards the need of age based user interface in the mobile operating system which will consist of interface selection home screen which further directs to age oriented interfaces.
This presentation will explore the user experience mobile design principles noting how it can help and in some cases make it more challenging for people with disabilities, using practical examples to illustrate both good and challenging designs for mobile. Participants will learn what challenges people with disabilities face using mobile devices and how to balance the design needs for all users.
Explore how WCAG 2.1 helps you design accessible desktop and mobile websites and applications for a variety of devices, including smart phones and beyond.
Many organizations today are struggling with knowing the best way to support accessibility and how to maintain accessibility compliance over time. Complying with WCAG 2.0 is a corporate-wide effort and goes well beyond technical accessibility. This webinar will discuss how to integrate accessibility across your organization and how to assess where you are on the accessibility maturity scale using the Capability Maturity Model.
Personal computers arrived on campuses around 25 years ago. The Web followed on most college campuses about 10 to 12 years later. Now both technologies are ubiquitous throughout campuses (and everywhere else). The Internet, in tandem with the computer, is used in the classroom, for grading, for faculty-student communication and for myriad other academic and administrative activities. Campus’ today learning environment that is dramatically different from that seen just over two decades ago or even ten years ago. This session discusses the challenges and promises of eBooks.
Web applications today are a challenge to make accessible because native HTML does not have the language to support the types of widgets added to Web pages. WAI-ARIA provides a way to add roles, states and properties to make RIA accessible to assistive technology such as screen readers.
3. What is Mobile Accessibility?
Primary question asked by the taskforce
Started by looking at the challenges faced by
users with disabilities using mobile devices
Looked at current WCAG 2.0 and evaluated the
applicability to mobile
3/2/2017 3
4. Question Also Asked by Policy Makers
US Section 508: WCAG 2.0
Europe: EN 301 549 + additional requirements
to be defined (WCAG 2.1?)
Other local developments with risk of standards
fragmentation
3/2/2017 4
5. Mobile
Landscape
Changed the way people are
consuming information
5
All ages are using mobile
Using one handed
Using touch screens
Situations where we have
busy eyes and hands
Out in bright light
In noisy, public spaces
3/2/2017
6. What is Mobile?
Technology that
• Has touch screens, but increasingly supports
other input methods
• Usually smaller than laptops and desktops
• More portable
• Used in many more situations
3/2/2017 6
7. Mobile Accessibility Isn’t Just Mobile
Touch screens are on devices other than mobile
including traditional desktop, home
automation, car interfaces etc.
Devices come in all different sizes – small
screens are not limited to only mobile
Technology is used in many different situations
3/2/2017 7
8. Mobile Accessibility Task Force
Task force of WCAG working group
Determine what is important for mobile space
Drafted WCAG Success Criteria that may be
included in WCAG 2.1
WCAG 2.0 does apply and we are adding language
to the understanding documents and techniques
3/2/2017 8
9. 2015: How WCAG 2.0 and Other
W3C/WAI Guidelines Apply to Mobile
First Public Working Draft
◦ http://www.w3.org/TR/mobile
-accessibility-mapping/
It doesn't set requirements
It doesn't replace WCAG 2.0
or WCAG 2.1
93/2/2017
10. Key Areas for Mobile Accessibility
1. Touch screens
2. Keyboard use on mobile
3. Device sensors and the impact on how users interact
(e.g. 3-D touch, device orientation etc.)
4. Small Screen Size
5. Impact of using device in many locations (e.g. glare)
6. Capabilities of devices including accessibility
features and assistive technology
3/2/2017 10
11. Gabi uses a screen reader with touch, and uses
dictation and Siri to more quickly enter content
and perform functions
She prefers to access content on her iPhone
Gets frustrated when the touch and gestures do
not work with screen reader
Understands where things are positioned on the
screen through the touch interface
Faces challenges with inaccessible content similar
to the desktop
Screen Reader: Meet Gabi
11
12. Joe has hand tremors from Parkinsons
Touching small areas of the screen is difficult
He often accidentally activates a control when
controls are close together
12
Touch: Meet Joe
13. Rebecca uses an external keyboard with her
Android tablet and prefers to use the onscreen
keyboard on her Android phone
She will often use touch, speech and keyboard to
access the content
She prefers the standard onscreen keyboard to
update based on the type of data that needs to be
entered
Keyboard: Meet Rebecca
13
14. Mark has light sensitivity and 20/200 vision
His device is set to large fonts, increased
contrast and he uses the zoom function
He has a hard time seeing the screen –
especially outside where there is a lot glare
To see the screen, Mark holds the device close
to his face and also relies the on text-to-speech
14
Reading Content: Meet Mark
15. Shawn uses a wheelchair and a head wand
His iPad is bolted onto the side of his wheelchair in
landscape orientation
He sets his device to remain in landscape
orientation because it would not be possible to
turn the device if the orientation were to change
Orientation: Meet Shawn
15
16. Joyce has repetitive strain injuries in her hands
that limit her keyboard, mouse and
touchscreen use.
She uses the speech button on her smart
phone to dictate texts and email
She uses her smart phone’s intelligent agent to
launch apps and search the web (e.g. “Launch
Editorial”, “Search the web for green apples”)
16
Speech: Meet Joyce
17. So, based on this research
we concluded…
3/2/2017 17
18. WCAG 2.0 Still Applicable
WCAG2ICT provides interpretations for “non-
web documents and software”
WCAG 2.1 to provide improvements
UAAG 2.0 relevant in some situations
“AG 3.0” may address broader context
3/2/2017 18
19. WCAG 2.1
First Public Working Draft published February 28, 2017
◦ https://www.w3.org/TR/WCAG21/
New success criteria submitted from low vision task force, cognitive
task force and mobile task force
◦ Everything is applicable to mobile
◦ Task force did not propose success criteria that would be addressed by Low
Vision or Cognitive task forces
◦ 10 new proposed success criteria specifically from mobile taskforce
◦ See proposed success criteria that did not make this first editors draft at
https://github.com/w3c/wcag21/issues
3/2/2017 19
20. 2.1.4 Speech Input
Level A
All functionality of the content does not
obstruct a user’s ability to access the
commands through speech input.
3/2/2017 20
21. 2.4.11 Single-key Shortcuts
Single-character shortcuts are not the only way
activate a control, unless a mechanism is
available to turn them off or remap them to
shortcuts with two or more characters.
3/2/2017 21
22. 2.5.1 Target Size
Level A
The size of the target in relation to the visible display at the default viewport
size is at least:
◦ 44 px by 44 px for pointer inputs with coarse pointing accuracy (such as a
touchscreen)
◦ 22 px by 22 px for pointer inputs with fine pointing accuracy (such as a mouse,
trackpad or stylus)
where px is a CSS pixel when the page is using the device ideal viewport.
Except when a link or control:
◦ is not part of the primary purpose or function of the page OR
◦ has an alternative link/control whose target does meet the minimum size
requirements
3/2/2017 22
23. 2.5.2 Pointer inputs with additional sensors
Level A
All pointer functionality can be operated using
screen coordinate information, without
requiring additional pointer sensor information.
3/2/2017 23
24. 2.5.3 Touch with Assistive Technology
All functions available by touch are still available
by touch after platform assistive technology
that remaps touch gestures is turned on.
3/2/2017 24
25. 2.5.4 Pointer Gestures
Level A
Functionality requiring complex or timed
pointer gestures or multi-pointer gestures can
also be operated with simple pointer gestures.
3/2/2017 25
26. 2.6.1 Device Sensors
Level A
All functionality of the content can be operated
without requiring specific device sensor
information unless the device sensor is essential
for the function and not using it would
invalidate the activity.
3/2/2017 26
27. 2.6.2 Orientation
Level AA
Content is not locked to a specific orientation,
and functionality of the content is operable in
all orientations, except where orientation is
essential for use of the content.
3/2/2017 27
28. 3.2.6 Accidental Activation
Level A
For single-pointer activation, at least one of the following is
true:
◦ Activation is on the up event, either explicitly or implicitly as a
platform's generic activation/click event;
◦ A mechanism is available that allows the user to choose the up-
event as an option;
◦ Confirmation is provided, which can dismiss activation;
◦ Activation is reversible;
◦ Timing of activation is essential and waiting for the up-event would
invalidate the activity.
3/2/2017 28
29. 3.2.8 Change of Content
Level AA
Programmatic notification is provided for each change of
content that indicates an action was taken or that conveys
information, unless one or more of the following is true:
◦ There is an accessibility supported relationship between the new
content and the control that triggers it.
◦ The user has been advised of the behavior before using the
component.
◦ There are more than 5 notifications per minute.
◦ The change of content is not a result of a user action AND not
related to the primary purpose of the page.
3/2/2017 29
30. How to Comment
File an issue in the W3C WCAG 2.1 Github
repository
◦File as new issues
◦One issue per discrete comment
Send email to public-agwg-comments@w3.org
Deadline: 31 March 2017
3/2/2017 30
Sometimes the standard keyboard can be customized in device settings
Sometimes additional custom keyboards can be installed
Sometimes different virtual keyboards are available depending on data entry type
Sometimes the standard keyboard can be customized in device settings
Sometimes additional custom keyboards can be installed
Sometimes different virtual keyboards are available depending on data entry type
Sets practical limits on how much information people can view at once
When magnification is needed there are best practices for helping users make the most of small screens
Excessive paging and scrolling can inhibit users who have mobility issues
Sometimes the standard keyboard can be customized in device settings
Sometimes additional custom keyboards can be installed
Sometimes different virtual keyboards are available depending on data entry type
Sets practical limits on how much information people can view at once
When magnification is needed there are best practices for helping users make the most of small screens
Excessive paging and scrolling can inhibit users who have mobility issues
Color contrast for icons and user interface controls, linearization
Success criteria proposed for attention
Do the new and proposed Success Criteria address current user needs for web content accessibility?
Does conformance to the new and proposed Success Criteria seem achievable and testable?
How well do the new and proposed Success Criteria fit with the existing Success Criteria from WCAG 2.0?
How completely does the set of new and proposed Success Criteria address current user needs, particularly for users of touch- and small-screen mobile devices, users with low vision, or users with cognitive or learning disabilities?
Is the impact of WCAG 2.1 on policies that reference WCAG 2.0 understandable and not disruptive?