This document provides an introduction to web accessibility for agencies. It begins with defining accessibility and the types of impairments it addresses. It discusses the differences between usability and accessibility, and notes that accessibility focuses on making products extensible to a variety of devices. The document then covers the business case for accessibility, how to implement accessibility, and provides a checklist to determine if a project requires an accessible approach. It emphasizes that accessibility is best incorporated from the start of a project.
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.
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.
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
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
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.
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.
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.
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
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
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.
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.
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.
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!
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.
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.
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
Web Accessibility in its simplest definition is all about making sure websites work for the widest possible audience. This seminar would involve a quick introduction to Web Accessibility, Web Accessibility Issues, Guidelines etc.
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?
A beginners guide to accessibility testing. An overview of common mistakes websites make and highlighting some easy to use tools that anyone can incorporate into their work.
Presented at www.AccessibilityCalgary.com on May 12, 2013.
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?
Designing, Developing & Testing for AccessibilityEric Malcolm
In this talk we will go over the basics of designing, developing and testing for accessibility. Including: Color Contrast, Sizing & Spacing, Device Independent User Input, Page Structure, Headings, Testing Tools, Extensions, Testing with a Screen Reader.
Accessibility Testing Using Screen ReadersRabab Gomaa
Testing websites using screen readers gives web developers the opportunity to make a real evaluation of their code and help identify accessibility issues that could be missed in manual checkup, or neglected by automatic verification tools.
In this session we will demonstrate how blind people navigate the web and will show how to use screen readers for accessibility testing of web pages including interactive components and web forms.
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.
Is it usable for people with disabilities?
We know a lot about how to meet the checkpoints for accessibility, but how well do you understand what makes a good experience for people with disabilities? Only getting out and seeing how people use your product will help you understand what makes it a delight to use --- or a pain. User research and usability testing should be part of your accessible UX toolkit.
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.
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.
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!
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.
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.
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
Web Accessibility in its simplest definition is all about making sure websites work for the widest possible audience. This seminar would involve a quick introduction to Web Accessibility, Web Accessibility Issues, Guidelines etc.
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?
A beginners guide to accessibility testing. An overview of common mistakes websites make and highlighting some easy to use tools that anyone can incorporate into their work.
Presented at www.AccessibilityCalgary.com on May 12, 2013.
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?
Designing, Developing & Testing for AccessibilityEric Malcolm
In this talk we will go over the basics of designing, developing and testing for accessibility. Including: Color Contrast, Sizing & Spacing, Device Independent User Input, Page Structure, Headings, Testing Tools, Extensions, Testing with a Screen Reader.
Accessibility Testing Using Screen ReadersRabab Gomaa
Testing websites using screen readers gives web developers the opportunity to make a real evaluation of their code and help identify accessibility issues that could be missed in manual checkup, or neglected by automatic verification tools.
In this session we will demonstrate how blind people navigate the web and will show how to use screen readers for accessibility testing of web pages including interactive components and web forms.
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.
Is it usable for people with disabilities?
We know a lot about how to meet the checkpoints for accessibility, but how well do you understand what makes a good experience for people with disabilities? Only getting out and seeing how people use your product will help you understand what makes it a delight to use --- or a pain. User research and usability testing should be part of your accessible UX toolkit.
Do you and your team know how to test for accessibility? These slides are from a recent workshop we were invited to present at #A11yTO's recent Meetup. It covers learnings from conducting accessibility testing with users, as well as some tools and tips for automated testing.
Discover some of principles and design considerations geared toward making web experiences accessible, and how to conduct an accessibility focused usability test.
I am a frankfinn studentsthis is the assignment done on travel management by me, so guys frm frankfinn u can use this as a refrence for your assignments, cheers
http://www.scenic.com | The year 2016 will see further technological developments that enhance the travel experience. These various high-tech innovations include further upgrades in “virtual travel” technology, drone photography, Wi-Fi, and more.
Forms for All: Building Accessibility into UiPath App DesignDianaGray10
Explore the world of accessible app design. We'll dive into common accessibility challenges faced by users in online forms and uncover practical solutions. Learn how to identify and rectify barriers that hinder user interaction, ensuring your forms are navigable and usable by all. This session will provide valuable insights into creating more inclusive online experiences, making your apps not just functional, but more accessible.
Topics covered in this session include:
• The Importance of Accessibility
• UX Accessibility Examples
• Adding Accessibility to Apps
Speaker:
David Kroll, Director, Product Marketing @Ashling Partners and UiPath MVP
UXPA2019 Enhancing the User Experience for People with Disabilities: Top 10 ...UXPA International
An estimated 1.3 billion people globally report limitations in their daily activities due to a disability. When it comes to the physical world, businesses have made progress in accommodating customers with disabilities. But in the digital world, websites lack basic accessibility features such as text alternatives describing images, proper heading level structures so individuals who are blind and use screen readers can understand the content on a webpage, or captioning for multimedia content for individuals who are deaf or are hard of hearing – let alone assistive technology for customers who have trouble using mobile devices due to dexterity limitations that arise from a variety of conditions.
In this session, attendees will:
* Understand people with disabilities (PWDs) and how they use the web
* Learn about common barriers, issues and solutions
* Discover the different testing methodologies and their interdependencies
* Uncover ROI
Importance of Accessibility for a Successful and Future-Proof Business - CSUN...Artur Ortega
Importance of Accessibility for a Successful and Future-Proof Business - An analysis based on recent studies about the benefits of accessibility for a robust internet business, with a focus on future-proof revenue. Artur Ortega; Saturday, March 27, 10:40-11:40 AM PST; Annie AB. CSUN International Accessibility Conference
Web Accessibility Audit_ Ensuring Inclusivity Online.pptxEmmaJones273085
Ensure inclusivity online with our Web Accessibility Audit. We assess your website for accessibility compliance, identifying and addressing barriers that may exclude users with disabilities. Empower everyone to access and engage with your digital content seamlessly. For more details, visit the website: https://www.acadecraft.com/accessibility/audit-services/
ATAGTR2017 SPEAKING EYE for differently abled people to see the web contentAgile Testing Alliance
The presentation on SPEAKING EYE for differently abled people to see the web content was done during #ATAGTR2017, one of the largest global testing conference. All copyright belongs to the author.
Author and presenter : Nadeeka Samanthi Wijewantha
Accessibility Overview - 508 and WCAG ComplianceFrank Walsh
This slideshare details approaches to build and validate complex web applications for accessibility and usability relative to Section 508 and WCAG standards.
• How do individuals with disabilities interact with and use the web? Understanding how assistive technologies work.
• Understanding your legal requirements - Section 508, Section 504, the Americans with Disabilities Act, and other state, U.S., and international laws
• Evaluating web site accessibility - automated tools, user testing, using screen readers, and understanding the Web Content Accessibility Guidelines (WCAG) 2.0
Smart Cities- Impact of web accessibility on e-service designSmart Cities Project
This report gives some background information about web accessibility
– an approach to designing web sites, e-applications and services so
that they work well for people with disabilities. It covers information about what accessibility means, what regulations there are in the different North Sea Region countries; suggests how to set up an accessibility project and provides guidelines and links to other resources.
Did you know, nearly 1 in 5 people have disabilities in the U.S. alone? Do you know how to tell if your website is fully accessible to everyone, even those with disabilities?
In this webinar you will learn what web accessibility is, and how to make sure your website is usable by all your constituents, including those with disabilities.
Speakers: Brenda Miele, Creative Director, Charity Dynamics, Adam Kaye, Web Development Manager, Charity Dynamics
Similar to Usability ≠ Accessibility. An intro to web accessibility for agencies. (20)
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...
Usability ≠ Accessibility. An intro to web accessibility for agencies.
1. Usability ≠ Accessibility.
an intro to web accessibility for agencies.
April 30, 2016
Authored by Kate Horowitz
k8horowitz at gmail dot com
Public version 2
2. 1. What is accessibility?
2. Accessibility vs. usability
3. Business case
4. Implementation
5. Accessible project strategy
6. Checklist
7. Questions?
8. Appendix
Agenda
6. There are 4 types of physical
impairments that affect online
access & behavior:
Visual Auditory Motor Cognitive
Difficulty reading small
fonts, distinguishing
similar colors, or inability
to see at all.
Inability to hear audio
of videos, or to
understand auditory
cues.
Difficulty using a mouse,
or tapping a finite area
on a touch screen.
Inability to understand.
Causes may be age
related, browsing in a
non-native language,
cognitive disabilities, or
just being distracted.
7. Kate is a Product Manager. She is in her
mid twenties and healthy, but she has very
bad vision that can sometimes affect her
work. Kate uses visual accessibility
features on her mac while at work.
• Kate spends half to most of her day in
front of a computer screen.
• Kate shops online about once a week.
• Kate increases the font on every web
page she visits, and often has to find
an alternate website if the current
page’s text size cannot be increased.
• Kate is a vision impaired user.
Kate.
9. Infrastructure impairments can
also affect online access &
behavior.
Connection Old equipment Mobile–only Cost
Low bandwidth means
difficultly downloading
media content.
Older browsers break
some code; old
monitors are harder to
read.
Mobile users experience
high latency, smaller
screen size, and slower
processors.
Some users turn off
resource-taxing web
features for lower
connection charges.
11. Ludwick is an entrepreneur from Limpopo
who invented DryBath, a waterless
bathing product that provides a sanitation
option to those without fresh water.
DryBath also prevents diseases such as
Trachoma, which affects 350 million each
year.
• Inventor of DryBath
• Wrote a patent and a 40 page business
plan on his cell phone.
• Only internet access was a Nokia 6234
cell phone connected to wireless at an
internet café.
• See his TED talk here.
• Ludwick is a mobile-only user.
Ludwick.
12. “Everyone operates under some kind
of duress that degrades their
performance.”
Source: A Web for Everyone ( 2013)
24. Some companies, especially financial
companies, are required by law to
comply with accessibility guidelines.
25. But there are strong business cases for
making your project accessible, even if
you’re not required to.
26. There are many direct
financial benefits:
• Interoperable code for devices and new technology can reduce
tech maintenance costs
• Broader user reach
• Higher SEO *
• Reduce support costs by providing more users with online info,
which is cheaper than call center or email support
• Reduce legal risk and avoid costly legal fees down the road
* Source: Article by Liam McGee (August 6, 2009)
http://www.communis.co.uk/blog/2009-08-06-seo-and-accessibility-overlap
27. 1 in 4U.S. adults aged 16 to 64 have
a dexterity (motor) difficulty or
impairment.
1 in 4U.S. adults aged 16 to 64
have a visual difficulty or
impairment
1 in 5U.S. adults aged 16 to 64
have a hearing difficulty or
impairment.
Key stats
Source: Study commissioned by Microsoft, conducted by Forrester Research, Inc., 2003
28. 31%Of U.S. adults access the internet
primarily on a mobile device.
Key stats
Source: Study by Pew Research, 2012,
http://www.pewinternet.org/2012/06/26/cell-internet-use-2012
29. 62%Of U.S. adults, aged 16 to 64, are
likely or very likely to benefit from
the use of accessible technology.
Key stats
Source: Study commissioned by Microsoft, conducted by Forrester Research, Inc., 2003
30. “The findings in this study show that the
majority of [U.S.] working-age adults
are likely to benefit from the use of
accessible technology.”
Source: Study commissioned by Microsoft,
conducted by Forrester Research, Inc., 2003
31. So how do we turn this information into
practical, actionable tasks that result in an
accessible product?
39. What are you making? A website? A
content management system? An
application, such as a multi-player game?
Product:
40. Type of product Which includes things like…
Website • text, images, and sounds
• code or markup that defines structure, presentation, etc.
Rich Internet Applications • dynamic content
• advanced user interface controls developed with Ajax, JavaScript, etc.
Authoring tool • Content Management Systems (CMS)
• WYSIWYG editors
• sites that let users add content, such as blogs, wikis, and social
networking sites
User agent • browsers
• media players
• assistive software
Something interactive with lots
of gestures
• scrolling behaviors that could be performed with a scroll wheel or a
finger swipe
41. Type of product Should follow these guidelines…
Website WCAG
“Web Content Accessibility Guidelines”
Rich Internet Applications ARIA
“Accessible Rich Internet Applications Suite”
Authoring tool ATAG
“Authoring Tool Accessibility Guidelines”
User agent UUAG
“User Agent Accessibility Guidelines”
Something interactive with lots
of gestures
Indie UI
“Independent user interface”
46. Let’s take a look at the 4 Principles that
WCAG Guidelines follow.
47. Principle Which includes things like…
Perceivable • Provide text alternatives for non-text content.
• Provide captions and other alternatives for multimedia.
• Create content that can be presented in different ways,
• including by assistive technologies, without losing meaning.
• Make it easier for users to see and hear content.
Operable • Make all functionality available from a keyboard.
• Give users enough time to read and use content.
• Do not use content that causes seizures.
• Help users navigate and find content.
Understandable • Make text readable and understandable.
• Make content appear and operate in predictable ways.
• Help users avoid and correct mistakes.
Robust • Maximize compatibility with current and future user tools.
58. ”Double A”
More difficult to pull off,
but much more accessible.
Almost identical to Section
508, and other
government standards,
and is the most common
level to build for.
AA.
“Level A”
Basic, easy stuff you can
do to try to make your site
more easily accessible for
all users.
A.
“Triple A”
Is a royal pain in the ass
even more difficult to pull
off, but provides the most
accessible user experience
of all. Your “normal” users
might start to notice
accessible features, which
they probably didn’t notice
in levels A or AA.
AAA.
Conformance Levels:
59. “Double A”
“Audio description is
provided for all
prerecorded video content
in synchronized media.”
AA.
“Level A”
“Captions are provided for
all prerecorded audio
content in synchronized
media, except when the
media is a media
alternative for text and is
clearly labeled as such.”
A.
“Triple A”
“Sign language
interpretation is provided
for all prerecorded audio
content in synchronized
media.”
AAA.
Guideline 1.2: Time-based Media
86. Identify business goals & target
users and recommend an accessible
strategy for them.
Determine which accessibility
conformance level, if any, you are
required to meet.
Design.
Development.Quality assurance. Content strategy.
Recommendation.Conformance audit.
87. Identify business goals & target
users and recommend an accessible
strategy for them.
Craft a solution that includes
accessible visual design and
interactions.
Determine which accessibility
conformance level, if any, you are
required to meet.
Development.Quality assurance. Content strategy.
Recommendation. Design.Conformance audit.
88. Identify business goals & target
users and recommend an accessible
strategy for them.
Craft a solution that includes
accessible visual design and
interactions.
Involve Content Strategy in all
aspects of copywriting, from
marketing to metadata, to ensure
accessibility requirements are met.
Determine which accessibility
conformance level, if any, you are
required to meet.
Development.Quality assurance.
Recommendation. Design.
Content strategy.
Conformance audit.
89. Identify business goals & target
users and recommend an accessible
strategy for them.
Craft a solution that includes
accessible visual design and
interactions.
Ensure that code is semantically
structured and includes accessibility
attributes.
Involve Content Strategy in all
aspects of copywriting, from
marketing to metadata, to ensure
accessibility requirements are met.
Determine which accessibility
conformance level, if any, you are
required to meet.
Quality assurance.
Recommendation. Design.
Development. Content strategy.
Conformance audit.
90. Recommendation. Design.
Development.
Test with assistive devices and
common accessibility software to
ensure a positive user experience.
Quality assurance. Content strategy.
Conformance audit.
Identify business goals & target
users and recommend an accessible
strategy for them.
Craft a solution that includes
accessible visual design and
interactions.
Ensure that code is semantically
structured and includes accessibility
attributes.
Involve Content Strategy in all
aspects of copywriting, from
marketing to metadata, to ensure
accessibility requirements are met.
Determine which accessibility
conformance level, if any, you are
required to meet.
91. The earlier we understand accessibility
requirements, the easier and cheaper
they are to implement.
92. When accessibility is incorporated from
the beginning of a project, it is often a
small percentage of the overall
project cost.
94. Use the following checklist at the
beginning of a project to see if you will
have accessibility requirements.
95. Does this sound like your
client? 1/3
q Is the client a financial institution?
q Is the client currently mandated by law to meet an accessible
standard?
q Is this client subject to broader legislation about discrimination or
equal opportunity?
q Might this client be subject to legal or policy changes in the
future?
q Does this client have a corporate policy that includes
accessibility?
96. Does this sound like your
client? 2/3
q Is the client a government agency?
q Might they do business with a government via this site?
q Does the client receive government funding?
q Is the client an educational institution?
q Is the client a non-profit that might accept government funding
in the future?
97. Does this sound like your
client? 3/3
q Does good PR rely on inclusivity for this client?
q Does this client promise to provide equal opportunities?
q Will many of their users be positively affected by accessibility?
q Does this client plan on using this site for a long time? (greater
than 2 years) Often, coding for accessibility means your site can
more easily keep up with browser updates and newer technology.
q Does their content heavily rely on inaccessible formats (i.e. video)
to relay information?
98. If you said “yes” to any of the checklist
items, there is a good chance that your
client requires an accessible product.
99. If you didn’t say yes to any, can you
confidently say “yes” to this:
q Does the client understand and accept the
risks of failing to provide an accessible website?
103. Resources:
• Web Accessibility Initiative Homepage.
• WCAG 2.0
• Understanding the Four Principles of Accessibility.
• Understanding Levels of Conformance.
• Essential Components of Web Accessibility.
• “A Web for Everyone: Designing Accessible User
Experiences.” [book]
• Accessibility Confluence Space. [internal wiki]
• “The user is drunk“ Hupspot.com review. [blog + video]
104. Referenced documents:
• “The Wide Range of Abilities and it’s Impact on Computer
Technology.” A Research Report Commissioned by Microsoft
Corporation and Conducted by Forrester Research, Inc. 2003.
[PDF]
• “SEO and Accessibility Overlap.” Article by Liam McGee. August
6, 2009. [Web article]
• “Cell Internet Use 2012.” Study by Pew Research. 2012. [PDF]
• “Accessible Information and Communication Technologies:
Benefits to Business and Society.” OneVoice for Accessible ICT.
2009-2010. [PDF]
106. Presentation definitions : (1/3)
• Accessibility refers to the degree to which a software
product, place, service, or website can be accessed and utilized
by it’s users.
• Disability: The deficit between user and system capability.
(proposed definition.)
• Guidelines define what needs to be done to make the
product as accessible to as many users as possible.
• Success Criteria are the instructions for fulfilling a Guideline,
and they are actionable, measurable, testable.
107. Definitions: continued 2/3.
• Sufficient Techniques define implementation tactics that
will meet a Success Criterion.
• Advisory Techniques are preferred tactics that meet and
exceed the Success Criterion, and deliver a better user
experience.
• Accommodation: Creating a separate, accessible version of
the site, similar to creating a mobile-only site version. In this
author’s opinion, accommodation is bad because it creates
separate, and likely not equal, experiences.
108. Definitions: continued 3/3.
• Equivalent use describes one product that has alternative
presentations of the same information.
• Universal Design: One site, same content, works for
everyone.
110. Assistive technology can be anything
from a braille display to reading glasses.
It’s just the extra things we use to get
stuff done.
111. Here are some examples of what it’s like
to rely on more advanced assistive
technology to access the internet.
112. Assistive tech demos:
• In this refreshable braille display demo, Bruce explains how he
shops on Amazon.com. Length is 6:42. Link opens YouTube.
• Tommy the blind film critic demos
how blind people use an iPhone. Length is 3 minutes. Link
opens YouTube.
• Joel is quadriplegic, and he demos how he uses a mouth stylus
to type (really fast!) in this video. Length is 3 minutes. Link
opens YouTube.
113. Assistive tech demos:
• Michelle has limited use of her arms, so she uses a trackpad
with her nose to create professional design work.
Check out how she does it in this video or
read about it in this blog post. Video length is 1:30, might play
an ad first. First link opens YouTube.
• Here is a great screen reader demo. Length 9:30. Link opens
YouTube.
• Here’s a quick blog post about common barriers for deaf web
users, such as videos and audio alerts. No video at this link.
114. Assistive tech demos:
• Here are some personas that illustrate some other common
user impairments, and how it affects their online behavior. Link
opens a website.
• Check out this chrome extension that allows you to view
websites the way color blind users see. Allows you to toggle
between 9 different types of colorblindness. If you can’t see,
you can listen to what it’s like to be color blind in this video. Ad
may play before video. Length is under 3 minutes. Link opens
YouTube.
115. Assistive tech demos:
• Here is a humorous promotional video about a Video Relay
Service that includes in-browser video conferencing to an
interpreter that can “speak” sign language. This is less
common now that video phones are mainstream, but still very
much in use by the deaf community. Video is 1 minute 35
seconds, and does not have audio. Link opens YouTube.
• If you cannot see the video at the link above,
this Wikipedia article can tell you a little more about Video
Relay services.
116. Assistive tech demos:
• This video shows how Johann uses screen magnification
software. Length is 9 minutes. Link open YouTube.
• One assistive feature that most of us are familiar with is
closed captioning, but here is a link to the Wikipedia article if
you are not familiar. You can also check out
this TEDx talk about how the legal focus on quantity, and not
quality, of captioning means that captioning is failing to serve
the deaf community. Video is 10 minutes. Link opens YouTube.
118. Graphics credits:
Translation icon designed by Lek Potharam.
Definition icon designed by Arthur Shlain.
Vision icon designed by Christian Tabacco.
Audio mute icon by Vania Platonov.
119. Graphics credits:
Router icon by Ilsur Aptukov.
Old computer icon by Evgeny Kiverin.
Brain icon by jessie_vp.
Mobile device icon by Mourad Mokrane.
120. Graphics credits:
Dollar sign icon by Yarden Gilboa.
Wheelchair user icon by José Campos.
Audit icon by Miroslav Koša.
Recommendation icon by iconsmind.com.
121. Graphics credits:
Design icon by Vijay Sekhar.
Quality assurance icon by useiconic.com.
Development icon by John Caserta.
Content strategy icon by hunotika.
Note that not all of these users consider themselves disabled.
-- Different countries have different definitions of disabled
-- Some people just deal with their impairments but don’t consider them to be debilitating
-- Some people don’t want to disclose their disability
Cognitive and motor disabilities can both be worse on some days and trivial on others
-- Includes temporary conditions, like recovering from an injury
-- Mental illness
-- Side effects of medication
-- Simply being tired
-- Being drunk or buzzed
Regarding cost and mobile usage as infrastructure impairments, see this recent Wall Street Journal article about Google’s decision to modify sites in certain regions to reduce page weight: http://www.wsj.com/articles/google-modifies-websites-to-hasten-service-1432835838?mod=rss_Technology
Other access factors not listed here are remote access (i.e. having to walk into town for internet access) and censorship.
If you are Ludwick, or know Ludwick, sorry for using your image of Google. Please let me know if this one is okay.
These infrastructure impairments don't have anything to do with disability, but they have the same negative impact on the user's ability to access and utilize the system. So if accessibility addresses disability, we should broaden our definition to say that “Disability” is the deficit between the user’s capabilities to interact with the system, and the system’s capability to interact with that user.
An accessible product addresses any disability that may affect the user's ability to access and utilize your system.
An accessible product addresses any disability that may affect the user's ability to access and utilize your system.
A responsive site only bridges the gap for Mobile users.
Accessibility has to be a broader approach.
We can reasonably assume that a visually impaired user has done what they can to overcome their impairment. They are probably using using a screen-reader, magnification software, or personalized operating system settings, such as text magnification keystrokes and heightened contrast. We can also reasonably assume that they are proficient with these tools. The system must meet them halfway, however, and be flexible enough to interact properly with those personalized settings and assistive devices. For example, If certain content is not going to work well for mobile-only users, the system should degrade gracefully and offer alternative ways of consuming that content. (i.e. Videos are too large to load? Make sure there's another way to consume that info that can be loaded more easily.)
A good accessible product doesn't have to look different from any other product, but it must be built for flexibility so that it can work on a wide range of output devices.
Note that his monitor is not even on, yet this man is still interacting with the computer. This user’s interface is completely devoid of imagery, but is still very much a user interface for him.
Many of you have seen Stephen Hawking give presentations, assisted by a really cool personalized computer rig he has on his chair. This is not “accessibility.” This is a highly usable solution built for a very small audience, often 1 person. Accessibility is built for use by all, where adaptive technology is built to address use cases of a very small subset of users.
Accessibility is device agnostic, where usability techniques are often very device-centric.
Ask your client to consult with their company’s legal team to find out if they are required to meet ADA guidelines. It is important to note that the ADA was written before the web and doesn’t prescribe specific web requirements, so compliance with ADA is highly subjective and requires judicious applications of common accessibility tactics.
t
If your site isn’t mobile optimized, you aren’t serving these users. And mobile-optimized doesn’t mean “it looks good on a comp of an iphone.” It means that it works on a mobile device, isn’t loaded down with unnecessary JavaScript and other resource-taxing code that makes it hard to actually load on a mobile device.
This is a huge number. Most of the people encompassed in this statistic probably don’t think of themselves as using “accessible” features. I’ve seen a lot of people refer to “customizing” a computer to meet their specific needs.
Lots of people have put a lot of time into distilling actionable, measurable, and testable guidelines to help you create an accessible product.
These guidelines come from one of two places: the W3C-WAI, ("Web Accessibility Initiative") which is an international organization, or government guidelines. The US government guidelines are usually referred to as Section 508, which you may have heard of. Let's ignore the government guidelines for now, as there is currently an international push for all governments to stop creating separate guidelines and simply adopt the ones created and maintained by the W3C-WAI anyway.
Authoring tool:
software and services that "authors" (web developers, designers, writers, etc.) use to produce web content (static web pages, dynamic web applications, etc.).
Authoring tool:
software and services that "authors" (web developers, designers, writers, etc.) use to produce web content (static web pages, dynamic web applications, etc.).
This is a Guideline from WCAG 2.0.
This is a Guideline from WCAG 2.0.
These are Success Criteria for this WCAG 2.0 Guideline.
These are Success Criteria for this WCAG 2.0 Guideline.
Conformance levels are highlighted. Note that these are specific to Success Criteria, not the Guideline.
* Double A (AA) conformance is generally recognized as adhering to ADA and section 508 requirements.
Currently, there are no legally enforced accessibility standards in the US. However, the Federal Government requires all of its sites to conform to its own Section 508 standards. This standard is also generally recognized as being met if a web site conforms to the WCAG 2.0 Double A (which is inclusive of Level A and Level AA criterions.)
* Double A (AA) conformance is generally recognized as adhering to ADA and section 508 requirements.
Currently, there are no legally enforced accessibility standards in the US. However, the Federal Government requires all of its sites to conform to its own Section 508 standards. This standard is also generally recognized as being met if a web site conforms to the WCAG 2.0 Double A (which is inclusive of Level A and Level AA criterions.)
Although your project may technically fulfill the acceptance criteria, this alone should not be used as a measure of product quality. For example, an image with alt text would fulfill WCAG 2.0 Guideline 1.1. However, if that alt text was simply the file name of the image, the user experience sucks. Let's take the example of a non-sighted user using a screen reader. Imagine having to sit there and listen to a screen reader read off "1246972559_n.jpg." Or even just "pie_chart.jpg." What's the gist of the pie chart? What is the actual data there? Ideally, the alt text evocatively describes the content of the image to provide the user with meaningful context. While each of these scenarios will technically pass the Guideline's Success Criteria, it's important that testers understand the spirit of the Guidelines to ensure quality.
It stigmatizes. It never provides equal access. If you haven’t internalized this already, I probably can’t convince you within the span of this presentation, but I’m just going to leave with this: whenever possible, we do not settle for accessible accommodation.
We should ensure that we’ve done our research here, and not just rely on information from the client. Lawyers are not know for the technical savvy and may not understand how to interpret guidelines for a digital project. And since we as Huge are often pioneers of the digital frontier, it’s possible for us to end up with a project that has no legal precedent, but could still be subject to the ADA’s broad guidelines.
Work with your teammates in the strategy department and the Business Analyst department to draft an accessible strategy recommendation, if the client does not already have a digital strategy in place.
Make sure to involve design early in the process. I thought I know a lot about this until I spoke with designer Casey Britt, who pointed out a large number of very not-obvious ways that accessibility requirements can affect the design process.
Remember! CMS labels are copy, too! Beware of projects that include migrating large amounts of content to a new platform. If their previous platform was not accessible, chances are, there’s an entirely new project scope required to update older, inaccessible content.
This is something Huge does well. Make sure to talk to your project’s SA about accessibility requirements. If Huge is not doing the development work, make sure to work closely with your BA to accurately capture and document accessible requirements.
Testing for accessibility about doubles the QA work required. The best way to streamline this process is to schedule your project so that your BA can work alongside QA early in the process to ensure that your acceptance criteria will actually validate against accessibility guidelines.