This document discusses accessibility for people with disabilities on web apps. It notes that around 15-20% of people have some kind of disability like visual impairment, color blindness, or motor impairments. It emphasizes that web content needs to be perceivable, operable, understandable, and robust. Specifically, it recommends providing text alternatives, adaptable content, distinguishable content, keyboard accessibility, enough time for users, avoiding seizures, navigability, readable text, predictability, input assistance, and robustness that works for assistive technologies.
Do you plan to host an usability testing session? Would you like to convice your coworkers to attend this session? This presentation answers frequently asked questions about usability testing.
503 web accessibility - best practicesJoanna Wiebe
This document provides guidelines for developing accessible web and mobile content. It states that 1 in 4 users have a vision difficulty, 1 in 4 have a dexterity difficulty, 1 in 5 have a hearing difficulty, and 16% have a cognitive difficulty or impairment. The key recommendations are to use descriptive tags for images and videos, provide text alternatives and captions, limit Flash content, and allow users to choose embedded or external viewing options. A "Get accessibility help" link should also be included to provide additional support.
This document discusses key concepts around usability, accessibility, and professional practices for web development. It defines usability as how easy a website is to use and emphasizes the importance of considering the intended audience. Accessibility involves measures to make websites usable for people with disabilities. Professional practices include following web standards, validating code, testing websites thoroughly, and keeping up-to-date with developments in the field through publications and mailing lists.
This document provides guidance on improving website accessibility. It discusses making websites accessible to people with disabilities, including those who are color blind, have low vision, difficulty using their hands, are deaf, have low English proficiency, are unfamiliar with technology, or have slow internet speeds. It provides six steps for an accessible website: 1) make text accessible, 2) provide alternatives to images, 3) use high contrast text, 4) accommodate screen readers, 5) support non-mouse users, and 6) code according to standards. Compliance with W3C and Section 508 standards can help ensure websites are accessible to all.
The document discusses the importance of making web content accessible to all users regardless of ability, outlining guidelines for designing websites that are perceivable, operable, understandable and robust. It provides tips for making content accessible to users with visual impairments, physical/motor disabilities, cognitive issues, hearing loss, and other access needs through techniques like descriptive text alternatives, proper heading structure, keyboard navigation, simple language and adjustible text size. Ensuring accessibility is important for legal compliance, an inclusive user experience, and reaching the broadest possible audience.
This document discusses web accessibility and provides guidance on making web content accessible to people with disabilities. It defines accessibility and discusses why it is important to consider, including legal requirements. It outlines various disabilities and how they may impact accessing information online. The document then provides best practices and techniques for making web design more accessible for people who are blind, have low vision, color blindness, hearing loss, physical or cognitive disabilities. It emphasizes using semantic HTML, separating design from content, providing text alternatives and captions. The document also introduces the WCAG guidelines for web accessibility.
Accessibility for Ontarians with Disabilities Act- What is it, how well Shar...Haniel Croitoru
Accessibility is on the minds of most public sector and many private sector organizations in Ontario, Canada that are creating new or significantly upgrading their existing websites. The government is mandating conformance to strict guidelines defined by WCAG 2.0. Does SharePoint have what it takes to do the job?
In this presentation I provide you with an overview of the Accessibility to Ontarians with Disabilities Act (AODA) and its relationship to WCAG 2.0, and outline the key areas that need to be considered when building AODA-compliant sites. Finally I will present results of short experiments I did on SharePoint 2010 and 2013 as it relates to accessibility.
Do you plan to host an usability testing session? Would you like to convice your coworkers to attend this session? This presentation answers frequently asked questions about usability testing.
503 web accessibility - best practicesJoanna Wiebe
This document provides guidelines for developing accessible web and mobile content. It states that 1 in 4 users have a vision difficulty, 1 in 4 have a dexterity difficulty, 1 in 5 have a hearing difficulty, and 16% have a cognitive difficulty or impairment. The key recommendations are to use descriptive tags for images and videos, provide text alternatives and captions, limit Flash content, and allow users to choose embedded or external viewing options. A "Get accessibility help" link should also be included to provide additional support.
This document discusses key concepts around usability, accessibility, and professional practices for web development. It defines usability as how easy a website is to use and emphasizes the importance of considering the intended audience. Accessibility involves measures to make websites usable for people with disabilities. Professional practices include following web standards, validating code, testing websites thoroughly, and keeping up-to-date with developments in the field through publications and mailing lists.
This document provides guidance on improving website accessibility. It discusses making websites accessible to people with disabilities, including those who are color blind, have low vision, difficulty using their hands, are deaf, have low English proficiency, are unfamiliar with technology, or have slow internet speeds. It provides six steps for an accessible website: 1) make text accessible, 2) provide alternatives to images, 3) use high contrast text, 4) accommodate screen readers, 5) support non-mouse users, and 6) code according to standards. Compliance with W3C and Section 508 standards can help ensure websites are accessible to all.
The document discusses the importance of making web content accessible to all users regardless of ability, outlining guidelines for designing websites that are perceivable, operable, understandable and robust. It provides tips for making content accessible to users with visual impairments, physical/motor disabilities, cognitive issues, hearing loss, and other access needs through techniques like descriptive text alternatives, proper heading structure, keyboard navigation, simple language and adjustible text size. Ensuring accessibility is important for legal compliance, an inclusive user experience, and reaching the broadest possible audience.
This document discusses web accessibility and provides guidance on making web content accessible to people with disabilities. It defines accessibility and discusses why it is important to consider, including legal requirements. It outlines various disabilities and how they may impact accessing information online. The document then provides best practices and techniques for making web design more accessible for people who are blind, have low vision, color blindness, hearing loss, physical or cognitive disabilities. It emphasizes using semantic HTML, separating design from content, providing text alternatives and captions. The document also introduces the WCAG guidelines for web accessibility.
Accessibility for Ontarians with Disabilities Act- What is it, how well Shar...Haniel Croitoru
Accessibility is on the minds of most public sector and many private sector organizations in Ontario, Canada that are creating new or significantly upgrading their existing websites. The government is mandating conformance to strict guidelines defined by WCAG 2.0. Does SharePoint have what it takes to do the job?
In this presentation I provide you with an overview of the Accessibility to Ontarians with Disabilities Act (AODA) and its relationship to WCAG 2.0, and outline the key areas that need to be considered when building AODA-compliant sites. Finally I will present results of short experiments I did on SharePoint 2010 and 2013 as it relates to accessibility.
Creating accessible information using Microsoft Word: hints and tips for ever...Jisc Scotland
Most people who work in colleges regardless of their role produce Word documents. They are used to create learning and teaching material, to produce information about services, to communicate information across the organisation.
There is a legal obligation for colleges to ensure that no-one is disadvantaged because of a disability, to anticipate the needs of people who might be accessing your information and your services and to make reasonable adjustments to accommodate their needs. One simple thing that everyone can do to meet these obligations is to ensure that the material that they create using Microsoft Office is created inclusively, doing so will ensure that it is accessible to a wide range of people who use assistive technologies or who have difficulty accessing text based information.
This presentation will highlight some simple ways to make your documents accessible using Word 2010 and how well designed Word documents can be converted into accessible PDFs.
A11yLDN 2011 - Introduction to Web AccessibilityGraham Armfield
This document provides an introduction to web accessibility. It defines web accessibility as enabling the web so that everyone can access its content when they want to and how they need to. The document discusses why web accessibility is important for knowledge sharing, interaction, commerce and social inclusion. It also notes that web accessibility is important for profit and required by law. The document then covers who influences web accessibility and common issues with building accessible sites. It focuses on cognitive impairments, defining them and discussing common difficulties users face and potential solutions to aid comprehension. It raises the challenge of incorporating all accessibility needs into one website.
The document provides an overview of web accessibility. It discusses requirements for making websites accessible to blind, partially sighted, motor impaired, and cognitively impaired users. True statements are that websites should use descriptive alt text, headings, lists and large visible links. Benefits of accessibility include reaching a larger demographic including disabled users and older adults, improving SEO and usability, and complying with laws. The document recommends organizations test for accessibility using expert reviews and tools, raise awareness through training, and embed accessibility practices internally.
The document discusses web accessibility and its importance for people with disabilities. It defines web accessibility and outlines key principles of perceivability, operability, understandability, and robustness. It then describes various types of disabilities and how they relate to accessibility challenges on the web, providing solutions to those challenges.
If your business has a publicly facing website, it should be usable for users with all sorts of accessibility needs. It is the fair, considerate, just, inclusive thing to do. We all want to do the right thing by society, right?
The Web Content Accessibility Guidelines (WCAG) are great but I have seen them regarded as optional rather than underpinning the design process for new websites. It's a complex area with a lot of nuance and can feel intimidating to those new to the subject.
So how do you get started in this area? In this talk, I go through my experiences in accessibility testing over the last 10 years, address some of the myths that prevail, cover how to persuade your peers to invest in accessibility, show what good accessible design looks like and give some practical advice on what to do if you have to retrospectively build in accessibility to an already live offering.
Key takeaways include:
• An understanding of what accessibility is
• How to advocate for accessibility
• An understanding of who benefits from accessible design
• Examples of the bad things that happen when accessibility is not considered (and how to avoid them)
• Understand what the WCAG accessibility guidelines are and how to use them in design and testing
• Develop the skills carry out an audit for accessibility on your own publicly facing website
Accessibility testing kailash 26_nov_ 2010Kailash More
The document discusses accessibility and its importance on the web. It defines accessibility as designing websites to be usable by people with disabilities. The aim is to ensure that people with any disability can perceive, understand, navigate and interact with content. Guidelines like WCAG provide priorities for making web content accessible for disabled users and all devices. Ensuring accessibility involves careful attention to navigation, separation of design from content, and support for assistive technologies.
A small presentation I put together based on research carried out over this months 'ribot days'. Subject to changes, but for now I've covered the basics of accessibility. There is so much to talk about by voice to support these slides, but I hope the content uploaded proves of use to someone.
Check out the references for the source of my findings.
1 out of 5 people have some kind of disability, and although not all disabilities make it difficult to use and access the web, many do. We should keep this in mind when designing and developing websites.
The document discusses web accessibility heuristics for people with disabilities. It covers guidelines in visual, motor/mobility, auditory, and seizures areas. For visual disabilities, it recommends ensuring proper text formatting and colors, use of alt text for images, captions for videos, etc. For motor/mobility issues, it suggests support for voice control, large click targets, keyboard navigation. For auditory disabilities, closed captions and text transcripts. It also advises avoiding flashy images that could trigger seizures. The document provides a checklist of factors to evaluate when testing for accessibility.
This document discusses accessibility for content designers. It defines accessibility as removing barriers that prevent people with disabilities from interacting with websites and services. It notes that 1 in 5 people have a disability and outlines various types of disabilities including visual, auditory, cognitive and mobility impairments. The document stresses that accessibility benefits everyone and is required by law. It provides guidance on making content perceivable, operable, understandable and robust. It recommends getting an accessibility specialist to evaluate services and including people with disabilities in user research.
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
1. The document establishes Eve Designs Limited as an accessibility specialist that focuses on making websites accessible for people with impairments.
2. Over 15% of the UK population has a disability, and an accessible website is important for their independence, access to information, and quality of life. It also promotes inclusion and is good for business.
3. An accessible website is easier to use for everyone, including those with visual impairments, limited mobility, cognitive impairments, slower internet connections, outdated equipment, or who access the internet outside the home. It also ranks higher on search engines and avoids potential legal issues.
Why I Hate The Interweb - Kath Moonan at Scripting EnabledChristian Heilmann
Kath Moonan's presentation at Scripting Enabled in London, September 2008. She covers the outcome of research done by Abilitynet with people with visual impairments and web sites.
Top 10 Tips for Making Your Website AccessibleAEL Data
The document provides top 10 tips for making a website accessible, including selecting an accessible content management system (CMS) and theme, using descriptive headings, providing alt text for images, writing descriptive links, maintaining sufficient color contrast, using accessible forms and tables, ensuring keyboard navigation, following rules for ARIA labels, and making dynamic content accessible. Accessible design benefits people with disabilities and also others by creating a better experience for all users.
Creating accessible information using Microsoft Word: hints and tips for ever...Jisc Scotland
Most people who work in colleges regardless of their role produce Word documents. They are used to create learning and teaching material, to produce information about services, to communicate information across the organisation.
There is a legal obligation for colleges to ensure that no-one is disadvantaged because of a disability, to anticipate the needs of people who might be accessing your information and your services and to make reasonable adjustments to accommodate their needs. One simple thing that everyone can do to meet these obligations is to ensure that the material that they create using Microsoft Office is created inclusively, doing so will ensure that it is accessible to a wide range of people who use assistive technologies or who have difficulty accessing text based information.
This presentation will highlight some simple ways to make your documents accessible using Word 2010 and how well designed Word documents can be converted into accessible PDFs.
A11yLDN 2011 - Introduction to Web AccessibilityGraham Armfield
This document provides an introduction to web accessibility. It defines web accessibility as enabling the web so that everyone can access its content when they want to and how they need to. The document discusses why web accessibility is important for knowledge sharing, interaction, commerce and social inclusion. It also notes that web accessibility is important for profit and required by law. The document then covers who influences web accessibility and common issues with building accessible sites. It focuses on cognitive impairments, defining them and discussing common difficulties users face and potential solutions to aid comprehension. It raises the challenge of incorporating all accessibility needs into one website.
The document provides an overview of web accessibility. It discusses requirements for making websites accessible to blind, partially sighted, motor impaired, and cognitively impaired users. True statements are that websites should use descriptive alt text, headings, lists and large visible links. Benefits of accessibility include reaching a larger demographic including disabled users and older adults, improving SEO and usability, and complying with laws. The document recommends organizations test for accessibility using expert reviews and tools, raise awareness through training, and embed accessibility practices internally.
The document discusses web accessibility and its importance for people with disabilities. It defines web accessibility and outlines key principles of perceivability, operability, understandability, and robustness. It then describes various types of disabilities and how they relate to accessibility challenges on the web, providing solutions to those challenges.
If your business has a publicly facing website, it should be usable for users with all sorts of accessibility needs. It is the fair, considerate, just, inclusive thing to do. We all want to do the right thing by society, right?
The Web Content Accessibility Guidelines (WCAG) are great but I have seen them regarded as optional rather than underpinning the design process for new websites. It's a complex area with a lot of nuance and can feel intimidating to those new to the subject.
So how do you get started in this area? In this talk, I go through my experiences in accessibility testing over the last 10 years, address some of the myths that prevail, cover how to persuade your peers to invest in accessibility, show what good accessible design looks like and give some practical advice on what to do if you have to retrospectively build in accessibility to an already live offering.
Key takeaways include:
• An understanding of what accessibility is
• How to advocate for accessibility
• An understanding of who benefits from accessible design
• Examples of the bad things that happen when accessibility is not considered (and how to avoid them)
• Understand what the WCAG accessibility guidelines are and how to use them in design and testing
• Develop the skills carry out an audit for accessibility on your own publicly facing website
Accessibility testing kailash 26_nov_ 2010Kailash More
The document discusses accessibility and its importance on the web. It defines accessibility as designing websites to be usable by people with disabilities. The aim is to ensure that people with any disability can perceive, understand, navigate and interact with content. Guidelines like WCAG provide priorities for making web content accessible for disabled users and all devices. Ensuring accessibility involves careful attention to navigation, separation of design from content, and support for assistive technologies.
A small presentation I put together based on research carried out over this months 'ribot days'. Subject to changes, but for now I've covered the basics of accessibility. There is so much to talk about by voice to support these slides, but I hope the content uploaded proves of use to someone.
Check out the references for the source of my findings.
1 out of 5 people have some kind of disability, and although not all disabilities make it difficult to use and access the web, many do. We should keep this in mind when designing and developing websites.
The document discusses web accessibility heuristics for people with disabilities. It covers guidelines in visual, motor/mobility, auditory, and seizures areas. For visual disabilities, it recommends ensuring proper text formatting and colors, use of alt text for images, captions for videos, etc. For motor/mobility issues, it suggests support for voice control, large click targets, keyboard navigation. For auditory disabilities, closed captions and text transcripts. It also advises avoiding flashy images that could trigger seizures. The document provides a checklist of factors to evaluate when testing for accessibility.
This document discusses accessibility for content designers. It defines accessibility as removing barriers that prevent people with disabilities from interacting with websites and services. It notes that 1 in 5 people have a disability and outlines various types of disabilities including visual, auditory, cognitive and mobility impairments. The document stresses that accessibility benefits everyone and is required by law. It provides guidance on making content perceivable, operable, understandable and robust. It recommends getting an accessibility specialist to evaluate services and including people with disabilities in user research.
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
1. The document establishes Eve Designs Limited as an accessibility specialist that focuses on making websites accessible for people with impairments.
2. Over 15% of the UK population has a disability, and an accessible website is important for their independence, access to information, and quality of life. It also promotes inclusion and is good for business.
3. An accessible website is easier to use for everyone, including those with visual impairments, limited mobility, cognitive impairments, slower internet connections, outdated equipment, or who access the internet outside the home. It also ranks higher on search engines and avoids potential legal issues.
Why I Hate The Interweb - Kath Moonan at Scripting EnabledChristian Heilmann
Kath Moonan's presentation at Scripting Enabled in London, September 2008. She covers the outcome of research done by Abilitynet with people with visual impairments and web sites.
Top 10 Tips for Making Your Website AccessibleAEL Data
The document provides top 10 tips for making a website accessible, including selecting an accessible content management system (CMS) and theme, using descriptive headings, providing alt text for images, writing descriptive links, maintaining sufficient color contrast, using accessible forms and tables, ensuring keyboard navigation, following rules for ARIA labels, and making dynamic content accessible. Accessible design benefits people with disabilities and also others by creating a better experience for all users.
Similar to Accessibility of Common Web Applications (20)
Top Benefits of Using Salesforce Healthcare CRM for Patient Management.pdfVALiNTRY360
Salesforce Healthcare CRM, implemented by VALiNTRY360, revolutionizes patient management by enhancing patient engagement, streamlining administrative processes, and improving care coordination. Its advanced analytics, robust security, and seamless integration with telehealth services ensure that healthcare providers can deliver personalized, efficient, and secure patient care. By automating routine tasks and providing actionable insights, Salesforce Healthcare CRM enables healthcare providers to focus on delivering high-quality care, leading to better patient outcomes and higher satisfaction. VALiNTRY360's expertise ensures a tailored solution that meets the unique needs of any healthcare practice, from small clinics to large hospital systems.
For more info visit us https://valintry360.com/solutions/health-life-sciences
When it is all about ERP solutions, companies typically meet their needs with common ERP solutions like SAP, Oracle, and Microsoft Dynamics. These big players have demonstrated that ERP systems can be either simple or highly comprehensive. This remains true today, but there are new factors to consider, including a promising new contender in the market that’s Odoo. This blog compares Odoo ERP with traditional ERP systems and explains why many companies now see Odoo ERP as the best choice.
What are ERP Systems?
An ERP, or Enterprise Resource Planning, system provides your company with valuable information to help you make better decisions and boost your ROI. You should choose an ERP system based on your company’s specific needs. For instance, if you run a manufacturing or retail business, you will need an ERP system that efficiently manages inventory. A consulting firm, on the other hand, would benefit from an ERP system that enhances daily operations. Similarly, eCommerce stores would select an ERP system tailored to their needs.
Because different businesses have different requirements, ERP system functionalities can vary. Among the various ERP systems available, Odoo ERP is considered one of the best in the ERp market with more than 12 million global users today.
Odoo is an open-source ERP system initially designed for small to medium-sized businesses but now suitable for a wide range of companies. Odoo offers a scalable and configurable point-of-sale management solution and allows you to create customised modules for specific industries. Odoo is gaining more popularity because it is built in a way that allows easy customisation, has a user-friendly interface, and is affordable. Here, you will cover the main differences and get to know why Odoo is gaining attention despite the many other ERP systems available in the market.
SMS API Integration in Saudi Arabia| Best SMS API ServiceYara Milbes
Discover the benefits and implementation of SMS API integration in the UAE and Middle East. This comprehensive guide covers the importance of SMS messaging APIs, the advantages of bulk SMS APIs, and real-world case studies. Learn how CEQUENS, a leader in communication solutions, can help your business enhance customer engagement and streamline operations with innovative CPaaS, reliable SMS APIs, and omnichannel solutions, including WhatsApp Business. Perfect for businesses seeking to optimize their communication strategies in the digital age.
UI5con 2024 - Boost Your Development Experience with UI5 Tooling ExtensionsPeter Muessig
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
Hand Rolled Applicative User ValidationCode KataPhilip Schwarz
Could you use a simple piece of Scala validation code (granted, a very simplistic one too!) that you can rewrite, now and again, to refresh your basic understanding of Applicative operators <*>, <*, *>?
The goal is not to write perfect code showcasing validation, but rather, to provide a small, rough-and ready exercise to reinforce your muscle-memory.
Despite its grandiose-sounding title, this deck consists of just three slides showing the Scala 3 code to be rewritten whenever the details of the operators begin to fade away.
The code is my rough and ready translation of a Haskell user-validation program found in a book called Finding Success (and Failure) in Haskell - Fall in love with applicative functors.
Transform Your Communication with Cloud-Based IVR SolutionsTheSMSPoint
Discover the power of Cloud-Based IVR Solutions to streamline communication processes. Embrace scalability and cost-efficiency while enhancing customer experiences with features like automated call routing and voice recognition. Accessible from anywhere, these solutions integrate seamlessly with existing systems, providing real-time analytics for continuous improvement. Revolutionize your communication strategy today with Cloud-Based IVR Solutions. Learn more at: https://thesmspoint.com/channel/cloud-telephony
WWDC 2024 Keynote Review: For CocoaCoders AustinPatrick Weigel
Overview of WWDC 2024 Keynote Address.
Covers: Apple Intelligence, iOS18, macOS Sequoia, iPadOS, watchOS, visionOS, and Apple TV+.
Understandable dialogue on Apple TV+
On-device app controlling AI.
Access to ChatGPT with a guest appearance by Chief Data Thief Sam Altman!
App Locking! iPhone Mirroring! And a Calculator!!
SOCRadar's Aviation Industry Q1 Incident Report is out now!
The aviation industry has always been a prime target for cybercriminals due to its critical infrastructure and high stakes. In the first quarter of 2024, the sector faced an alarming surge in cybersecurity threats, revealing its vulnerabilities and the relentless sophistication of cyber attackers.
SOCRadar’s Aviation Industry, Quarterly Incident Report, provides an in-depth analysis of these threats, detected and examined through our extensive monitoring of hacker forums, Telegram channels, and dark web platforms.
What to do when you have a perfect model for your software but you are constrained by an imperfect business model?
This talk explores the challenges of bringing modelling rigour to the business and strategy levels, and talking to your non-technical counterparts in the process.
UI5con 2024 - Keynote: Latest News about UI5 and it’s EcosystemPeter Muessig
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
8 Best Automated Android App Testing Tool and Framework in 2024.pdfkalichargn70th171
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
Artificia Intellicence and XPath Extension FunctionsOctavian Nadolu
The purpose of this presentation is to provide an overview of how you can use AI from XSLT, XQuery, Schematron, or XML Refactoring operations, the potential benefits of using AI, and some of the challenges we face.
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...XfilesPro
Wondering how X-Sign gained popularity in a quick time span? This eSign functionality of XfilesPro DocuPrime has many advancements to offer for Salesforce users. Explore them now!
Malibou Pitch Deck For Its €3M Seed Roundsjcobrien
French start-up Malibou raised a €3 million Seed Round to develop its payroll and human resources
management platform for VSEs and SMEs. The financing round was led by investors Breega, Y Combinator, and FCVC.
20. How is it to have a motor
impairment?
Up to 5% of all people
21. Imagine there is no mouse
• You have at most keyboard to browse a web site.
• You cannot reach non-interactive elements.
• All clickable elements on the site are in a sequence.
• You are dependent on focus representation of the actual element.
60. Visit the page and try to find all accessibility violations.
61. Content must be robust enough that it can be interpreted reliably by a wide
variety of user agents, including assistive technologies
Web content must be
robust
Slide about people with disabilities
Yellow – blind people (about 0,5%, 39 milions)
Orange – decreased ability to see the indelible glasses or lenses (about4,39%, 285 milions)
Purple – color blindness (daltonismus)
Most common are the problems with the perception of green and red colors. Problems with the perception of blue color are quite rare.
9% of men and 0,4% women
Complete color blindness is very rare, 99% color blind persons do see some color.
Also to add:
Hearing disabilities – 10%
Motor functions disabilities - 5%
Total number of disabled people: 15-20%
USA 19%
Australia 18,5%
More statistics on http://www.disabled-world.com/disability/statistics/
Slide about Macular degenerations
Macular degeneration, often age-related macular degeneration (AMD or ARMD), is a medical condition that usually affects older adults and results in a loss of vision in the center of the visual field (the macula) because of damage to the retina.
It is a major cause of blindness and visual impairment in older adults, afflicting 30-50 million people globally.
Slide about Cataract
A cataract is a clouding of the lens in the eye leading to a decrease in vision. It can affect one or both eyes. Often it develops slowly. Symptoms may include faded colors, blurry vision, halos around light, trouble with bright lights, and trouble seeing at night.
Cataracts are the cause of half of blindness and 33% of visual impairment worldwide.
Slide about Diabetic Retinopathy
Diabetic Retinopathy is the leading cause of blindness for people aged 20 to 64 years. Each year in the United States, diabetic retinopathy accounts for 12% of all new cases of blindness.
Slide about Glaucoma
Glaucoma is a term describing a group of ocular (eye) disorders that result in optic nerve damage, often associated with increased fluid pressure in the eye.
Glaucoma can permanently damage vision in the affected eye(s), first by decreasing peripheral vision (reducing the visual field), and then potentially leading to blindness if left untreated.
Glaucoma has been called the "silent thief of sight" because the loss of vision often occurs gradually over a long period of time, and symptoms only occur when the disease is quite advanced.[4] Once lost, vision cannot normally be recovered, so treatment is aimed at preventing further loss.
Slide about How do we feel colors
Rods – contrast perception and peripheral vision
Cones – color perception
Slide about Achromatopsia
Achromatipsia – missing all the cones
Slide about Protanopia
Protanopia – missing the red cones
Slide about Deuteranopia
Deuteranopia – missing the green cones
Slide about Tritanopia
Tritanopia – missing the blue cones
Slide about motor impairment
We will only discuss the disabilities of upper body parts. In such a case the user cannot use a mouse or maybe even keyboard.
Writing a software that is accessible to keyboard helps these kind of people:
Blind people because a reader machine can easier navigate in the application flow.
Motoric disabled people because they can control the application themselves.
Advanced users who thus can use for example keyboard shortcuts.
Slide with an example of proceeding links with keyboard
An example of how many times does a user need to hit the tab button to proceed to the desired link.
Slide with an example of a keyboard trap
An example of a keyboard trap
Slide about existing acessibility norms
Section 508 Standards apply to electronic and information technology procured by the federal government, including computer hardware and software, websites, phone systems, and copiers.
Web Content Accessibility Guidelines (WCAG) 2.0 covers a wide range of recommendations for making Web content more accessible. Made by W3C.
Mandate 376 is a future EU norm.
Slide about text alternatives
Sensory characteristics such as shape, size, visual location, orientation, or sound should not be the only way of conveying important information.
Slide about adaptable content
Meaningful information should not be conveyed solely via sensory characteristics. Sensory characteristics such as shape, size, visual location, orientation, or sound should not be the only way of conveying important information.
If you want to convey that a button will delete content, for example, make sure that this is also written in text. Do not rely solely on color and icons
Slide about existing distinguishable content
Text should be resizable using the default browser mechanisms up to 200% without a loss of content or functionality.
Contrast ratio of text to background should be at least 4.5:1, preferably 7:1.
Slide with example of adaptable content
Text should be resizable using the default browser mechanisms up to 200% without a loss of content or functionality.
Normal text
Slide with example of an adaptable content
200% increased text – you cannot reach the button next to the e-mail input, you don‘t even know there is one
Slide with example of a distinguishable content
Contrast ratio of text to background should be at least 4.5:1, preferably 7:1.
Normal text
Slide about keyboard accessible content
Many people are unable to navigate the web using a mouse. Therefore, all functionality should be operable through the standard keyboard interface without requiring specific timings for individual keys.
Ensure all functional elements have a clear focus state. For people navigating a website using the tab key only, focus states are how they know their location on the page.
Avoid keyboard traps. Tab through the content of your website from start to finish to ensure that the keyboard focus is not trapped on any of the content.
Slide about providing enought time for timed content
Provide controls for timed content. For any interactions related to timing - including moving information, auto-updating, or page time-outs.
Possible implementations:
Users can turn off the time limit
Users can adjust time limit to at least 10 times the length of the default setting
Users is warned before time expires and given at least 20 seconds to extend the time limit with a simple action
Slide about seizures
Flashing light should not occur more than three times per second. Or, the flash should be below thegeneral flash and red flash thresholds. You can use photosensitive epilepsy analysis tools or flash tests to test your site if you are unsure.
Slide with seizures example
Flashing light should not occur more than three times per second. Or, the flash should be below the general flash and red flash thresholds. You can use photosensitive epilepsy analysis tools or flash tests to test your site if you are unsure.
Slide about navigable content
Provide a link for users to skip to the page’s main content. One of the first links on every page of a website should include a link for users to bypass repeated blocks of content, such as the navigation. This is especially important for pages that have large, multi-layered navigation menus. The link itself does not need to be visible when out of focus.
Titles should be meaningful. The title of the web page, as well as the page heading, section headings, and labels, should describe the topic or purpose of the page.
Link purpose can be determined from link text. As far as is possible, the purpose of a link should be able to be determined from the text that is within the anchor tag itself.
Provide more than one way to locate a web page. The same page should be accessible by more than just one link on one page.
Complete site map on a single page
Search function to access all content
Navigation with links to all pages
Slide about readable content
Specify the language(s) of the page. Specify the language of the current page on the HTML element, and any languages of specific parts.
Provide meanings of unusual words and pronunciations of difficult words. You can use the titlea ttribute to provide the meaning of abbreviations and unusual words. For definitions, you can use the dl element to provide a definition list.
Make content available at a lower secondary education reading level. Teenagers aged between 11-14 should be able to understand the content, even if specific terminology and concepts are new.
Slide about navigable content
Consistent navigation. Navigation elements should be repeated in a consistent way throughout the website.
Consistent identification. Terminology and repeatable elements should appear consistently throughout the website.
No unprovoked changes of context. Any changes of context should only happen on request by the user. Things like redirects, popups and other similar interactions should be communicated clearly beforehand.
Slide about input assistance
Provide labels and instructions - Provide labels or instructions for input elements. Where there is a commonly made error, provide suggestions that users can model their answers against.
Error messages in simple language. Errors made should be described to the user in plain, understandable text, not error codes.
Error prevention. Where a user is submitting information, at least one of the following must be true -
The submission of information is reversible
The answers is checked for errors and the user is given the opportunity to correct before submission.
The user is given the opportunity to confirm the information before submission
Slide with an example of not understandable web app
https://www.ruelala.com/boutique/
Focus and context changes right after page was loaded
Body focus means a context change to a place with a keyboard trap
Placeholders are used as labels – bad usability.
Slide about robust content
Valid code and semantic web pages
Slide about robust content
Write valid code. Ensure the compatibility of your HTML by making sure it passes validations checks.
Specify the purpose of elements. Specify the name, role and value for user interface components where appropriate. For forms in particular, labels should be used where possible -
Slide about tesing the software
Test your software for accessibility
Browser add-ons
Accessibility tools
Specialized centers