2019 update of Role-Based Analysis for WCAG 2.1 as part of presentation made to the UX design team at 3M HQ. Unlike previous version that either cover just WCAG 2.0 or just the new 2.1 success criteria this version's results (pie charts) covers all level A and AA criteria from both.
A11yTC MeetUp: Role-based Analysis of WCAG 2.2Bill Tyler
Role-based analysis of the eight new WCAG 2.2 proposed success criteria confirm the increasing need for – and the ability of – accessibility to “shift left.” Learn how the new requirements mean content authors, user experience and visual designers must learn more to conform to the new standard now and the future. This presentation also include review of all 10 new WCAG 2.2 success criteria including Level AAA with role-based analysis of each. Also included, a brief look beyond 2.2 to WCAG 3.0
Presented at A11y Twin Cities MeetUp, Monday, July 25, 2022
Accessibility In Mobile Dev LifeCycle.pptxMarkSteadman7
Mobile apps are developed and deployed at a very fast pace, so how can accessibility become a part of that? With automation, quick testing, and definition of done for accessibility we can make it apart of the dev process!
This virtual event focused on how inclusive UX is being put into practice in real life from the lens of both academia and industry.
[Slide 21]
- Mismatch by Kat Holmes (Book): https://mitpress.mit.edu/books/mismatch
- Giving a Damn about Accessibility (PDF): https://accessibility.uxdesign.cc/
- Microsoft Inclusion Toolkit: https://www.microsoft.com/design/inclusive/
- There is no average person; designing with intersectionality in mind: https://www.youtube.com/watch?v=RY9FHkETD5c
[Slide 26]
- The Business Case for Digital Accessibility (Article): https://www.w3.org/WAI/business-case/
- Design for Cognitive Bias (Book): https://abookapart.com/products/design-for-cognitive-bias
- Pocket Biases (Web application): https://pocket-biases.glideapp.io/
- Cards for Humanity (Web-based card game): https://cardsforhumanity.idean.com/
- User Mapping Canvas (Article + template): https://medium.com/@pratistha.sharma/how-to-use-the-user-mapping-canvas-bce146e1788b
[Slide 32]
- Disability Visibility (Book): https://disabilityvisibilityproject.com/book/
- Practical Ways to Include People with Disabilities (Recorded presentation): https://www.youtube.com/watch?v=hueXHhOYFaI&list=PLIyMotGrARQ00zzKgK_xhamLP4pnvjpQQ&index=15
- Just Ask: Integrating Accessibility throughout Design (Online book): www.uiaccess.com/accessucd/ut.html
[Slide 38]
- WCAG 2.1: https://www.w3.org/TR/WCAG21/
- ADA vs. 508 Compliance vs. WCAG: https://www.webfx.com/web-design/ada-vs-508-compliance.html
- Accessibility Checklist: https://www.a11yproject.com/checklist/
- UXCel's "Designing for Accessibility" (Online course): https://app.uxcel.com/
- Inclusive Design Principles: https://inclusivedesignprinciples.org/
- Access Guide: https://www.accessguide.io/
- Stark (Plug in): https://www.getstark.co/
- Sim Daltonism (macOS App): https://apps.apple.com/us/app/sim-daltonism/id693112260?mt=12
[Slide 43]
- Blair Koeneman: https://www.linkedin.com/in/blairkoeneman/
[Slide 130]
- Learn more: www.xcenter.info & www.uegroup.com
- Get in touch: hello@xcenter.info
- Follow us on LinkedIn: Experience Innovation Center: www.linkedin.com/company/experience-innovation-center
- Event recording: https://www.youtube.com/watch?v=oV3SteeMy1U
User experience is complex and multifaceted. One of those facets is making services usable to people in different situations. The needs of people with disabilities, both apparent and not, must be considered on our mobile and web platforms if we are to provide good service and abide by federal and state regulations. Cervone looks at some of the common accessibility issues people may have with mobile sites and websites and how to address those issues while still creating a visually stimulating and interactive environment for all.
A11yTC MeetUp: Role-based Analysis of WCAG 2.2Bill Tyler
Role-based analysis of the eight new WCAG 2.2 proposed success criteria confirm the increasing need for – and the ability of – accessibility to “shift left.” Learn how the new requirements mean content authors, user experience and visual designers must learn more to conform to the new standard now and the future. This presentation also include review of all 10 new WCAG 2.2 success criteria including Level AAA with role-based analysis of each. Also included, a brief look beyond 2.2 to WCAG 3.0
Presented at A11y Twin Cities MeetUp, Monday, July 25, 2022
Accessibility In Mobile Dev LifeCycle.pptxMarkSteadman7
Mobile apps are developed and deployed at a very fast pace, so how can accessibility become a part of that? With automation, quick testing, and definition of done for accessibility we can make it apart of the dev process!
This virtual event focused on how inclusive UX is being put into practice in real life from the lens of both academia and industry.
[Slide 21]
- Mismatch by Kat Holmes (Book): https://mitpress.mit.edu/books/mismatch
- Giving a Damn about Accessibility (PDF): https://accessibility.uxdesign.cc/
- Microsoft Inclusion Toolkit: https://www.microsoft.com/design/inclusive/
- There is no average person; designing with intersectionality in mind: https://www.youtube.com/watch?v=RY9FHkETD5c
[Slide 26]
- The Business Case for Digital Accessibility (Article): https://www.w3.org/WAI/business-case/
- Design for Cognitive Bias (Book): https://abookapart.com/products/design-for-cognitive-bias
- Pocket Biases (Web application): https://pocket-biases.glideapp.io/
- Cards for Humanity (Web-based card game): https://cardsforhumanity.idean.com/
- User Mapping Canvas (Article + template): https://medium.com/@pratistha.sharma/how-to-use-the-user-mapping-canvas-bce146e1788b
[Slide 32]
- Disability Visibility (Book): https://disabilityvisibilityproject.com/book/
- Practical Ways to Include People with Disabilities (Recorded presentation): https://www.youtube.com/watch?v=hueXHhOYFaI&list=PLIyMotGrARQ00zzKgK_xhamLP4pnvjpQQ&index=15
- Just Ask: Integrating Accessibility throughout Design (Online book): www.uiaccess.com/accessucd/ut.html
[Slide 38]
- WCAG 2.1: https://www.w3.org/TR/WCAG21/
- ADA vs. 508 Compliance vs. WCAG: https://www.webfx.com/web-design/ada-vs-508-compliance.html
- Accessibility Checklist: https://www.a11yproject.com/checklist/
- UXCel's "Designing for Accessibility" (Online course): https://app.uxcel.com/
- Inclusive Design Principles: https://inclusivedesignprinciples.org/
- Access Guide: https://www.accessguide.io/
- Stark (Plug in): https://www.getstark.co/
- Sim Daltonism (macOS App): https://apps.apple.com/us/app/sim-daltonism/id693112260?mt=12
[Slide 43]
- Blair Koeneman: https://www.linkedin.com/in/blairkoeneman/
[Slide 130]
- Learn more: www.xcenter.info & www.uegroup.com
- Get in touch: hello@xcenter.info
- Follow us on LinkedIn: Experience Innovation Center: www.linkedin.com/company/experience-innovation-center
- Event recording: https://www.youtube.com/watch?v=oV3SteeMy1U
User experience is complex and multifaceted. One of those facets is making services usable to people in different situations. The needs of people with disabilities, both apparent and not, must be considered on our mobile and web platforms if we are to provide good service and abide by federal and state regulations. Cervone looks at some of the common accessibility issues people may have with mobile sites and websites and how to address those issues while still creating a visually stimulating and interactive environment for all.
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.
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.
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
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.
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!
Slides from AccessU presentation presented by Sarah Pulis and Claire Webber.
Annotating designs with accessibility information is a powerful way to focus on accessibility early in the design phase, as well as communicate your accessibility requirements to developers and testers. Sarah and Claire will cover how to add accessibility annotations in components, patterns and complete wireframes using popular design tools such as Figma.
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.
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.
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
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
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.
Managing Accessibility Compliance in the EnterpriseKarl Groves
From my CSUN 2011 presentation
A lecture style session discussing ways to approach management of accessibility compliance at the enterprise level including project/ program management and procurement.
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
A11y by Design 2018 Rethinking Accessibility 2018-05-08Bill Tyler
Slide Deck from Bill Tyler's presentation on Role-Based Analysis of WCAG 2.0 at the Accessible by Design Conference held at Indiana University on May 8, 2018
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.
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.
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
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.
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!
Slides from AccessU presentation presented by Sarah Pulis and Claire Webber.
Annotating designs with accessibility information is a powerful way to focus on accessibility early in the design phase, as well as communicate your accessibility requirements to developers and testers. Sarah and Claire will cover how to add accessibility annotations in components, patterns and complete wireframes using popular design tools such as Figma.
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.
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.
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
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
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.
Managing Accessibility Compliance in the EnterpriseKarl Groves
From my CSUN 2011 presentation
A lecture style session discussing ways to approach management of accessibility compliance at the enterprise level including project/ program management and procurement.
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
A11y by Design 2018 Rethinking Accessibility 2018-05-08Bill Tyler
Slide Deck from Bill Tyler's presentation on Role-Based Analysis of WCAG 2.0 at the Accessible by Design Conference held at Indiana University on May 8, 2018
Role-based analysis of the eight new WCAG 2.2 proposed success criteria confirm the increasing need for – and the ability of – accessibility to “shift left.” Learn how the new requirements mean content authors, user experience and visual designers must learn more to conform to the new standard now and the future.
Presented at CSUN ATC 2022, Friday, March 18, 2022
Why Usability Testing should be part of your accessibility testing strategypmcnallyux
Usability testing is an accepted process from the domain of user experience (UX) to gauge how easy to learn or use a product is. Users are asked to work on typical scenarios or tasks on the product with the goal of trying to identify challenges in the design of the user interface, interaction or content. In this paper I will discuss the benefits of usability testing in conjunction with accessibility testing and how they can work together. In particular, I will review some recent usability testing projects where we had people with disabilities participate and demonstrate how these findings can augment and support accessibility testing efforts.
Pete McNally, Senior Consultant at User Experience Center receives the Best Paper award at the recent ICT 2017 ICT Accessibility Testing Symposium in Washington, DC.
Is Lean UX Agile’s Brain? How Lean UX Fixes Common Agile ChallengesFITC
Agile development methods are sweeping the software industry, but reconciling UX, Agile and stakeholder demands for certainty are a struggle for many companies.
Expanding on a (in)famous “Agile doesn’t have brain” quote, Nick Van Weerdenburg, founder of Rangleio, shares his insights from 60+ modern front-end JavaScript projects on how Lean UX can drive the conversations that drive the creation of the right solution for the right audience.
Objective
Show the audience how Lean UX practices can drive the conversations that drive the effective adoption of Agile in companies small and large.
Target Audience
Managers, designers, developers and anyone who has a vested interest in build the right software for the right audience in the most effective manner.
Assumed Audience Knowledge
A basic knowledge User experience and Agile development.
Five Things Audience Members Will Learn
How to connect the user to the Agile development process
How to use Lean UX to drive Agile prioritization
How Lean UX creates the right conversations and eliminates the wrong ones
How to avoid UX design become a defacto waterfall process
How to use Lean UX to help drive effective enterprise transformation to Agile practices
This is take two of the presentation, some things added, some removed, but still the regurgitation is best..
The purpose is to raise your awareness of software architecture in light of modern day agile development. Disciplines to incorporate and reconsider
Presented 5/11/17 @LOCO_UX by @jkooda of @liminaUX
This talk covers the anatomy of a UX Eval, how to use it as a business development tool, and how to ensure you have a logical and most importantly beneficial return on your client's investment.
Early Signal Testing: Designing Atlassian’s New LookAtlassian
You probably have noticed the new look of Atlassian's Cloud products. Our new Design Guidelines took many months to create, and our team had many tough decisions to make. Luckily, we incorporated customer research along the way to guide us.
One of our most valuable research tools is called “early signal testing”, and we think it can help you too. Early signal testing can help you gain confidence in a direction, rather than being paralyzed by a choice. It can help assess your design's usability, clarity, comprehension, and more. This talk explains how your team can gather measurable user feedback in as little as a week, for even the very biggest of problems.
Wordcamp 2014 - How to Perform an Accessibility AuditJanis Yee
As Accessibility becomes of increasing importance on the web - also a legal requirement in Ontario, Canada - so too is the rising need to be aware of how to look at sites with a critical eye. This presentation is about the process of How to Perform an Accessibility Audit. I developed this process in early 2014 while working at Metroland Digital.
This marks my very first deck on Slideshare!
On May 15th, the day before Global Accessibility Awareness Day, we hosted SIGNA11Y - our very first accessibility and inclusive design event - at the CodeClan premises in Edinburgh.
Here are the presentations from our expert group of speakers -including our very own Software Engineer Claire Smith, Allan Hutcheon (COO of Neatebox), Iris Winter (Frontend Developer at Modulr Finance) and Chris Wait (Director of Engineering at Passio).
Storytelling results of heuristic evaluationUX Firm, LLC
Presents the traditional way of reporting results from a heuristic evaluation and then a better way that uses storytelling to tell the user's experience.
Applying Usability to Improve Value and Reduce RiskBonitasoft
This technical session was presented by Nathalie Cotte at the online IDEAS conference hosted by the Center for Information Development-Management - to explain how we care more and more about customers, but that we also need to remind everyone that developers also have needs to be considered!
Requirements meet solutions: How to successfully transfer stakeholder needs i...AALForum
Presentation by Markus Garschall, Katja Neureiter, Mona Marill, Christiane Moser and Lex van Velsen during the session 'Requirements meet solutions: How to successfully transfer stakeholder needs in AAL projects' (Markus Garschall) - AAL Forum 2015
Similar to Rethinking Accessibility: Role-based Accessibility of WCAG 2.1 (20)
Shift Left - Require Right WRT A11yTC 2023-07-31.pptxBill Tyler
Choosing to shift accessibility left saves time and money in design. But how can that be done consistently and effectively in your organization?
Starting with initial request for proposals, all product design life cycle documentation can be tested and reviewed for potential accessibility issues. Not only that, those documents can be expanded and enhanced to define additional requirements to further ensure and enhance accessibility. Part of that process is creating an extensive, reusable annotation system created to support content authors, UX and visual designers as well as front-end developers. The methods and analysis presented should help advance your shift left efforts even if you cannot apply them all.
Presented July 31, 2023, A11y Twin Cities Meetup
De-mystifying and Taming the Complexities of WCAG 2.1Bill Tyler
Testing 200 websites in one year at Optum Technology was a major challenge. A lot of lessons and techniques for using and testing WCAG 2.1 were learned. Whether you’re new or experienced in accessibility there is likely something that can be applied to any site.
Introducing ARRM: A Framework To Fight Accessibility ApathyBill Tyler
The Accessibility Roles and Responsibility Mapping (ARRM) is a framework developed by the W3C’s EOWG to help teams break down Web accessibility requirements by roles.
Introducing ARRM: A Framework to Fight Accessibility ApathyBill Tyler
The Accessibility Roles and Responsibility Mapping (ARRM) is a framework developed by the W3C’s EOWG to help teams break down Web accessibility requirements by roles.
CSUN 2018 Analyzing and Extending WCAG Beyond 3 DigitsBill Tyler
Slide deck from Bill Tyler's presentation of the Benefits of Analyzing & Extending WCAG 2.0 Beyond Three Digits from CSUN 2018 Conference (Friday, March 23, 2017)
1.Wireless Communication System_Wireless communication is a broad term that i...JeyaPerumal1
Wireless communication involves the transmission of information over a distance without the help of wires, cables or any other forms of electrical conductors.
Wireless communication is a broad term that incorporates all procedures and forms of connecting and communicating between two or more devices using a wireless signal through wireless communication technologies and devices.
Features of Wireless Communication
The evolution of wireless technology has brought many advancements with its effective features.
The transmitted distance can be anywhere between a few meters (for example, a television's remote control) and thousands of kilometers (for example, radio communication).
Wireless communication can be used for cellular telephony, wireless access to the internet, wireless home networking, and so on.
APNIC Foundation, presented by Ellisha Heppner at the PNG DNS Forum 2024APNIC
Ellisha Heppner, Grant Management Lead, presented an update on APNIC Foundation to the PNG DNS Forum held from 6 to 10 May, 2024 in Port Moresby, Papua New Guinea.
This 7-second Brain Wave Ritual Attracts Money To You.!nirahealhty
Discover the power of a simple 7-second brain wave ritual that can attract wealth and abundance into your life. By tapping into specific brain frequencies, this technique helps you manifest financial success effortlessly. Ready to transform your financial future? Try this powerful ritual and start attracting money today!
Multi-cluster Kubernetes Networking- Patterns, Projects and GuidelinesSanjeev Rampal
Talk presented at Kubernetes Community Day, New York, May 2024.
Technical summary of Multi-Cluster Kubernetes Networking architectures with focus on 4 key topics.
1) Key patterns for Multi-cluster architectures
2) Architectural comparison of several OSS/ CNCF projects to address these patterns
3) Evolution trends for the APIs of these projects
4) Some design recommendations & guidelines for adopting/ deploying these solutions.
Bridging the Digital Gap Brad Spiegel Macon, GA Initiative.pptxBrad Spiegel Macon GA
Brad Spiegel Macon GA’s journey exemplifies the profound impact that one individual can have on their community. Through his unwavering dedication to digital inclusion, he’s not only bridging the gap in Macon but also setting an example for others to follow.
# Internet Security: Safeguarding Your Digital World
In the contemporary digital age, the internet is a cornerstone of our daily lives. It connects us to vast amounts of information, provides platforms for communication, enables commerce, and offers endless entertainment. However, with these conveniences come significant security challenges. Internet security is essential to protect our digital identities, sensitive data, and overall online experience. This comprehensive guide explores the multifaceted world of internet security, providing insights into its importance, common threats, and effective strategies to safeguard your digital world.
## Understanding Internet Security
Internet security encompasses the measures and protocols used to protect information, devices, and networks from unauthorized access, attacks, and damage. It involves a wide range of practices designed to safeguard data confidentiality, integrity, and availability. Effective internet security is crucial for individuals, businesses, and governments alike, as cyber threats continue to evolve in complexity and scale.
### Key Components of Internet Security
1. **Confidentiality**: Ensuring that information is accessible only to those authorized to access it.
2. **Integrity**: Protecting information from being altered or tampered with by unauthorized parties.
3. **Availability**: Ensuring that authorized users have reliable access to information and resources when needed.
## Common Internet Security Threats
Cyber threats are numerous and constantly evolving. Understanding these threats is the first step in protecting against them. Some of the most common internet security threats include:
### Malware
Malware, or malicious software, is designed to harm, exploit, or otherwise compromise a device, network, or service. Common types of malware include:
- **Viruses**: Programs that attach themselves to legitimate software and replicate, spreading to other programs and files.
- **Worms**: Standalone malware that replicates itself to spread to other computers.
- **Trojan Horses**: Malicious software disguised as legitimate software.
- **Ransomware**: Malware that encrypts a user's files and demands a ransom for the decryption key.
- **Spyware**: Software that secretly monitors and collects user information.
### Phishing
Phishing is a social engineering attack that aims to steal sensitive information such as usernames, passwords, and credit card details. Attackers often masquerade as trusted entities in email or other communication channels, tricking victims into providing their information.
### Man-in-the-Middle (MitM) Attacks
MitM attacks occur when an attacker intercepts and potentially alters communication between two parties without their knowledge. This can lead to the unauthorized acquisition of sensitive information.
### Denial-of-Service (DoS) and Distributed Denial-of-Service (DDoS) Attacks
Rethinking Accessibility: Role-based Accessibility of WCAG 2.1
1. 3M Design Center, Maplewood, MN
September 11, 2019
Bill Tyler
Principal Digital Accessibility Engineer, Accessibility Center of Excellence, UX Design Services
Optum Technology @billtyler btyler@optum.com
Rethinking Accessibility:
Role-Based Analysis of
WCAG 2.1
2. Education & Experience
Full-time accessibility professional since 2013
W3C Invited Expert on Role-based Accessibility
UX developer & designer for over 35 years.
My Accessibility Journey
Learned a lot about the challenges of the blind through a friend born without eyes
over 20 years ago.
Started learning and applying accessibility in 2002 and turned into full-time focus a
decade later.
Materials Presented
5+ yrs. of ongoing accessibility research & analysis at Optum Technology
presented at CSUN and other accessibility conferences
Meet your speaker
2
5. • Visual
– Blindness
– Low Vision
– Color Vision
• Auditory
– Degrees (mild to profound)
– Classifications (conductive, neural, high/low tone, deaf-blindness)
• Motor
– Traumatic Injury (spinal cord, loss of limbs)
– Disease or Congenital (Cerebral Palsy, Muscular Dystrophy, Arthritis)
• Cognitive
– Functional (memory, problem-solving, attention, comprehension)
– Clinical (autism, Down Syndrome, brain injury, dyslexia, ADD)
4 Areas of Disability
5
6. WCAG: Web Content Accessibility Guidelines from the W3C
4 (POUR) Principles
1. Perceivable – 4 guidelines
“Information and user interface components must be presentable to users in ways they can perceive.”
2. Operable – 5 guidelines
“User interface components and navigation must be operable.”
3. Understandable – 3 guidelines
“Information and the operation of user interface must be understandable.”
4. Robust – 1 guideline
“Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive
technologies.”
WCAG 2.1 in nutshell
6
7. 78 total success criteria across 3 levels
• A – 30 criteria
• AA – 20 criteria
• AAA – 28 criteria
Conformance Target: WCAG AA
• WCAG 2.0 (2008): 38 (A & AA) criteria
– Current US Section 508 (and many others, including most existing legal cases)
• WCAG 2.1 (2018): 50 (A & AA) criteria
– Coming soon (in EU with EN 301 549, some organizations such as the U of MN)
WCAG 2.1 in nutshell (continued)
7
9. No one thinks about accessibility
… EXCEPT the a11y expert
Accessibility comes at end of development
…by TESTING done by the a11y expert
All issues found are directed to developers to fix
…with HELP from a11y expert
Final Result: “Sort of” Accessible Result
Problem: The Usual Approach to Accessibility
9
17. Who owns it? – Decision Making Roles
• Standard
agile role
• Initiates
project
• Defines
business
requirements
• Approves
results
• Business
liaison
• Writes design
requirements
• Creates low-
fidelity
wireframes
• Expert on
usability and
interaction
• Presentation
owner
• Style expert
• Creates page
layouts
• Enforces
design
standards
• Authors style
guides
• Produces
high-fidelity
comps and
image files
• Author of all
text “large
(section) and
small (words)”
• Proofreads
content
• Writes scripts
for video and
audio content
• Creates audio
and video
files
• Front-end
programmer
• Merges work
from other
roles
• Produces
delivered
pages and
content
• Fixes all bugs
and defects
17
18. Testing Roles
• Accessibility Subject Matter Expert (SME)
• Accessibility Instructor
• Resource for “difficult” a11y issues
• May fill in as A11y approver
• Discoverer of issues
• Writer of defects
• Enforcer of quality
• Last stop before release
• Usually not trained in accessibility
• Can learn it
• Can add it to test suite
18
19. To what level? – Role Ownership Model
Primary – Individual role with “final approval”P
Secondary – actively involved in decisionS
Contributor – affect, but not deeply involvedC
19
20. Example: SC1.4.1 Use of Color (Level A)
Visual Designer
• Is “the expert” with final
say on colors
• Specifies colors in style
guide
UX/IX Designer
• Specifies need to use
colors in wireframes or
requirements
Business Owner
• Provides brand guidelines
with approved color palette
20
21. If one person has multiple roles: Merge
If multiple people share a role: Assign or Delegate
Still not clear: Best guess for your situation
Whatever the case:
Doing the exercise with your own roles and assignments
ensures all WCAG criteria are owned and addressed.
What if roles aren’t the same or separate?
21
24. 24
WCAG 2.1 Primary Success Criteria Ownership
UX Designer: 44% (22)
Content Author: 20% (10)
Visual Designer: 18% (9)
Developer: 16% (8)
Business Owner: 2% (1)
Observations
• Both Designers along with Authors
are the top three owners
• Developers are fourth with slightly
more than 1 in 6 criteria
• Clearly accessibility issues are
design and content, not just code
26. When? – Software Design Lifecycle Entry Points
Code (front-end development: HTML, CSS, JavaScript)
Content (text, terminology, and includes video & audio)
Design Comps (page or feature final presentation)
Style Guides (site presentation, branding, colors, logos)
Wireframes (structure of page, interface, interactions)
User Story / Standard Requirements
26
27. Entry Point Level Model
Primary – single, most significant (typical) entry pointP
Secondary – other significant entry pointsS
Impact – other minor sources of design inputI
27
30. 30
WCAG 2.1 Primary Success Criteria Entry Points
Wireframes: 38% (19)
User Stories: 34% (17)
Style Guides: 20% (10)
Code: 4% (2)
Content: 4% (2)
Design Comps: “0%”
Observations
• 96% of decisions come before code
• Close to 40% are defined in wireframes
• A third are in user stories
• Nearly a fifth in style guide
• Code and content are just 4% each
35. 35
Success Criteria Types
Best Practices: 54% (27)
Primarily A11y: 40% (20)
User Stories: 6% (3)
Observations
• Over half of decisions are
best practices roles should
already know
• Accessibility training could
focus on topics they don’t
37. Example (of what NOT to do): “Press the green button on the right.”
Notes:
• Rare instance of single owner, no secondary owner or contributor
• Example of a “Never” event – should never happened (and preventable)
SC1.3.3 Sensory Characteristics
Content Author None None Accessibility,
“Best Practice”
Content
37
38. Example: “Session times out in 5 minutes. Continue? Yes / No”
Notes:
• Business Owner’s only primary ownership criterion
• Rare Standard Requirement case
SC2.2.1 Timing Adjustable
Business Owner UX/IX Designer None Standard
Requirement
User Story /
Requirements
38
39. Example: Search, Site Map, Breadcrumbs, Top-nav, In-page links
Notes:
• One of several UX/IX Designer-only primary criteria
SC2.4.5 Multiple Ways
UX/IX Designer None None Best Practice,
Standard
Requirement
Wireframes,
Long Content
sections
39
40. (Questionable) Example: “Blue on ‘light’ blue”
Notes:
• One of several Visual Designer primary ownership crits
• Visual Designer has no secondary ownership
SC1.4.3 Color Contrast (Minimum)
Visual Designer None Business Owner Accessibility
(Best Practice?)
Style Guide,
Design Comps
40
41. (Bad) Example: “Missing alt attribute in <img>”
Notes:
• Code reviews should already include code validation
SC4.1.1 Parsing
Developer None None Best Practices Code
41
43. Opportunities to improve efficiency and quality
for both new and existing sites
Involvement should be early in the design process – “Shift Left”
• Includes project intake
Where appropriate Distribute & Assign ownership (resolution)
to roles other than developer & testers
All roles should have training tailored to their role for efficiency
Checklists for reviewing all design deliverables before sign-off
Changes: General
43
44. Distributing common issue remediation to other roles means…
• Agile teams become more self-sufficient
• Design roles make better decisions preventing issues at the start
• Team members can identify & return issues at earlier steps without A11y SMEs
• QA testers can do perform a good portion of a11y testing
This frees Accessibility SMEs to focus on “difficult” issues that require their
expertise
Net Result: Reduce the total number of accessibility SMEs across the
enterprise
• Important for organizations with hundreds of sites
Changes: Accessibility Role
44
46. 46
“Shift Left” Approach for New Projects
QA / A11y Testing
Developers
Content Author
Visual Designer
UX/IX Designer
Business Owner
Add
A11y
here
47. Integrate accessibility early in the design process
Distribute accessibility ownership to key decision makers
Targeted, role-based training
• Refresher on existing best practices
• Accessibility training only on topics they own or impact
Changes: New Projects – “Shift Left”
47
49. SC2.2.1 Timing Adjustable
Session timeouts
• Identify Need
• Select approaches to use
SC2.4.5 Multiple Ways
Initial Requirements / Feature Definitions
• Site search
• Site map
49
Shift Left Criterion Example - Requirements
50. SC2.4.3 Focus Order
Document sequence along with content elements
• Basic overview
• Page- or section-specific as needed
SC2.4.6 Headings & Labels / SC1.3.1 Info & Relationships
Document headings & hierarchies
• On page or as “table of contents” in notes (SC2.4.6)
• Define heading levels (SC1.3.1)
50
Shift Left Criterion Examples - Wireframes
51. SC1.4.3 Contrast (Minimum)
Specify and Test
• Text Colors with…
• Backgrounds
SC2.3.1 Three Flashes or Below Threshold
Define standards
• No blinking content of any kind
• Color thresholds for animation
51
Shift Left Criterion Examples – Style Guides
52. SC1.3.3 Sensory Characteristic
Inform authors to
• Include non-sensory instructions
Encourage Common Writing Standards that are AAA
• SC3.1.3 Unusual Words
• SC3.1.4 Abbreviations
• SC3.1.5 Reading Level
52
Shift Left Criterion Examples – Writing Guides
54. 54
“Shift Left” Approach for Triage Projects
QA / A11y Testing
Developers
Content Author
Visual Designer
UX/IX Designer
Business Owner
Address
A11y here
55. As with new projects, all roles should have targeted role-
based training
As issues are found they should be directed to the correct role
owner, not simply the developer
• Issues directed to specific roles will demonstrate how previous
decisions impacted accessibility
Changes: Triage of Existing Sites
55
56. Expand Team
• Not just developers & testers
• Include designers, content author and (possibly) business owner
Review Checkpoints
• Analyze checkpoints
• Identify typical owner to resolve issues
– Developers & Testers should not “do design”
56
“Shift Left” Remediation
58. Offshoot of Education & Outreach Working Group
Approved at CSUN March 2018
• Team lead: Denis Boudreau (Deque)
• Members: Bill Tyler (me), Sean Kelly (Optum), Lewis Phillips (AT&T)
In the Future
• Midway through a 3-year plan
• Defining deliverables which include decision-tree for groups to do role-based
analysis for their own teams
• Will be open to review and input
58
W3C Accessibility Roles & Responsibilities
59. Available Now
Targeted specifically for UX designers – Not A11y experts!
Design Before Code: Thinking About Accessibility from the Ground Up
by Caitlyn Geier, 2-Part Blog Posting (2017)
• https://www.deque.com/blog/design-code-thinking-accessibility-ground/
Accessibility Heuristics 1.0
by Caitlyn Geier & Denis Boudreau, PDF document (CSUN 2018)
• https://accessibility.deque.com/accessibility-heuristics/
59
Shift Left / UX Designer Materials