ARIA (Accessible Rich Internet Applications) allows web developers to make their complex web applications accessible. This presentation will introduce ARIA attributes and how they establish landmarks, states, and roles. Learn how to use the basic elements that belong on every application. This presentation will also show more advanced topics, such as invalid form inputs, live regions, and fixing divitis.
View this presentation with accessible transcript: http://www.last-child.com/accessibility-high-notes-aria/
Discover the Possibilities of the Jira Cloud Asset API
With the new assets management API for Jira Cloud, developers can bring a lot more context into Jira to create a faster and more powerful issue resolution experience.
Join Andrea, a developer on Jira Service Desk, as she gives a holistic overview of asset management in Jira Cloud. We’ll step through an ideal end-to-end user experience from help seekers raising a request for their laptop, to an agent resolution. In this talk, you’ll learn what powers these experiences and exactly how to create them using the Jira Cloud Assets API and integration points.
#ATAGTR2018 Presentation "Manual and Automated Accessibility Testing Implemen...
Rakesh Kondreddy who is a Senior STE at Ellucian, took a Session on "Manual and Automated Accessibility testing implementation" at Global Testing Retreat #ATAGTR2018
please refer our linkedin post for session details
https://www.linkedin.com/pulse/manual-automated-accessibility-testing-implementation-alliance/
This presentation introduces HTML5 and ARIA accessibility. It also introduces best practices and common problems. It was created for Intuit and PayPal/eBay engineers.
The document discusses web accessibility, providing information on the following key points in 3 sentences:
1) It defines 5 main categories of disabilities that can be affected by accessibility barriers: vision, deaf/hard-of-hearing, motor, cognitive, and seizure-related.
2) It summarizes the Web Content Accessibility Guidelines (WCAG) 2.0, which contains principles, guidelines, and success criteria to make web content more accessible to people with disabilities.
3) It provides tips for making web content more accessible, such as using alternative text for images, adding table headers, ensuring sufficient color contrast, and using clear form labels.
Web access for users with disabilities is an important goal and challenging problem for web content developers and designers.
Essential open source api projects to ease the developing & testing for web accessibility.
The document summarizes a presentation on accessibility, mobile design, and responsive design given at the 2015 jQuery Conference in Berlin. It discusses how these topics are related but not the same, and provides examples of how to design for them individually and together. Key points include that responsive design helps with accessibility but does not ensure it, and that content should be accessible on any device without barriers.
This document discusses web accessibility and adjustments that can be made to content management systems like AEM to comply with Section 508 standards. It provides an overview of common disabilities like sight impairments and cognitive disabilities. Programmatic adjustments that can be made include adding alt text to images, proper labeling of form fields, and ensuring keyboard navigation. Color contrast, captioning videos, and organizing content in a logical structure can also improve accessibility. Testing with screen readers and disabling CSS is recommended. Resources for creating accessible content are provided.
This session will highlight the capabilities within AEM 6.2 that allow you to create accessible web content and how to meet the important requirements of WCAG 2.0.
This presentation highlights common accessibility issues in modern web applications and how YUI makes it easy to build accessible, dynamic applications. You will learn about ARIA, focus management, and keyboard accessibility. The presentation will show how the Yahoo registration form uses YUI and accessibility best practices to make sure everyone can enjoy Yahoo products. You will learn how YUI's node and focus management makes it easy to build sophisticated, accessible interactions.
The document discusses best practices for search on museum websites. It recommends using Google search for the website but also implementing internal search to better understand the museum's unique content. It provides examples of autocomplete, faceted search, highlighting search terms, and correcting spelling to improve the user search experience. Solr is recommended as an open source tool for implementing these search features.
This is a longer version of my presentation "Responsible Design: Accountable Accessibility" but with a catchier name :)
This talk tells my story of how I went from front end developer who knew nothing about accessibility to an accessibility advocate.
Included in this talk are my "10 Tips" that any developer can use on day one without any experience authoring accessible HTML.
This talk was originally presented at the Accessibility Conference in Guelph, Ontario, Canada on May 29, 2013.
Twig is a template engine for PHP that is described as flexible, fast, and secure. Some key features of Twig include being concise yet powerful, with a template-oriented syntax. It aims to be easy to learn yet extensible. Twig provides features like inheritance, blocks, automatic escaping, and inclusion. It also focuses on being secure, with descriptive error messages and the ability to sandbox templates.
In this session we'll review the checks you must go through before deciding whether to use an ARIA role or attribute, reveal our favorites, discuss the ones that need more user agent support, and show you how you can help us make it happen.
A presentation for Dundee University's Hack Day explaining the technologies to use and how to hack your own APIs by using Yahoo! Pipes and scraping RSS feeds.
The document discusses HTML5 and WAI ARIA, including current and future features. Key points include:
1) WAI ARIA allows adding accessibility information to any element using attributes. It can be used with HTML, XHTML, SVG and others.
2) HTML5 will include new semantic elements like <nav> and <article> to provide structural information, though they are not yet supported widely.
3) WAI ARIA roles like landmarks can currently chunk pages into perceivable regions to aid navigation.
4) The <canvas> element poses challenges for accessibility without alternatives provided outside the element. ARIA and HTML5 integration defines their relationship going forward.
Introduce Trauma-Informed Design to Your Organization - CSUN ATC 2024
Historically, accessibility specialists focused on a narrow set of disabilities. We focused on the senses, such as sight, sound, and touch. We focused on abilities, like hearing, movement, and seeing.
We expanded to include cognitive, mental health, and neurodiversity. This is significant. We now have tools to build inclusive products and services for an estimated 25% of the population. What about the other 75%?
As accessibility professionals, we understand unique experiences and needs. We are best equipped to expand customer research and design at our companies. Universal design was described as a one size fits all solution. Inclusive design is one size fits one. Intersectional design is one size fits one, but also accounts for price, texture, availability, cultural appropriateness, and more.
This presentation introduces the next layer of inclusive design; one that recognizes trauma.
Trauma-Informed Design (TID) started in education, health, and community spaces. It focuses on the person’s experiences, recognizing trauma’s impact, anxiety, and restoring personal control. Architects embraced TID to develop spaces that are comfortable instead of confrontive.
While the earlier stages of TID focused on individualized experiences, we can still take the principles and apply them to web and mobile application design. This is especially critical for emerging AI powered experiences where transparency and collective understanding are rarely considered.
Transforming Accessibility one lunch at a tiime - CSUN 2023
Try to remember March 2020. The COVID epidemic was raging and businesses sent everyone home to work remotely. Ted Drake and Sagar Barbhaya were at the 2020 CSUN ATC conference. Returning to our homes, we wondered if we could continue the energy and curiosity found at a conference, only transforming it for a virtual work environment. The following week, we launched Intuit’s Zoom-based Accessibility Lunch and Learn series. It was an experiment planned to last only a few weeks. We reached out to our Accessibility Champion network and quickly arranged daily lectures, mostly based on presentations already given at onboarding and other training events. As the epidemic grew, we turned inward and focused less on accessibility and more on our mental health, living with a disability, and celebrating our diversity. The key transformation came with a talk about sobriety in the workplace. The speaker’s courage to discuss her journey led to heartfelt conversations about mental health, the loss of community, and the struggle where colleagues were trying to encourage hope with “happy hours” and alcohol-related team building activities. This presentation led to immediate improvements in our workplace language and pandemic policies. It also showed a lunch and learn was more than a lecture. It could be the community we were aching for. With more than 100 presentations and thousands of participants, we continue to learn something new every week.
Inclusive Design for cognitive disabilities, neurodiversity, and chronic illness
Learn how to design for people with short term memory loss, problems focusing on a task, struggling with anxiety, and dealing with chronic pain. This presentation will introduce you to the people you need to include in your designs. You will also have clear action items for inclusive design.
This talk was presented at the San Diego Accessibility Meetup on August 1, 2022. It explains the basics of affordances, signifiers, cognitive load, and how we can design to reduce the effort needed by our customers to understand and use our products. This also includes updated information on Long COVID and why we need to focus more of our attention on cognitive accessibilty.
1. The document discusses Long COVID and brain fog, which can occur in some people after a COVID-19 infection. Symptoms can include shortness of breath, fatigue, joint pain, changes in smell/taste, brain fog, anxiety, and inability to focus. Approximately 20% of COVID patients experience long-term symptoms.
2. The document shares experiences of people living with long COVID and brain fog symptoms. This includes difficulty concentrating, short-term memory loss, anxiety and panic attacks.
3. The document discusses designing inclusively for those with long COVID. This includes minimizing cognitive load, using recognition over recall, highlighting selections, and following guidelines like WCAG that promote cognitive accessibility. A
Automated accessibility testing can greatly improve the product experience by empowering developers and designers to eliminate repetitive, mundane errors and focus on the challenging and interesting elements. This presentation focuses on the customer experience and how it can be improved by using automated testing throughout the software development cycle.
Ask any accessibility leader about accessible colors and they’ll wince from the pain of struggling for a solution. Why is it so difficult to ensure your product meets WCAG 2.1 AA color contrast requirements? Ted Drake, Intuit’s Global Accessibility Leader, will explain the basics of color accessibility requirements. He will also talk about the conflict of overlapping requirements, dealing with brand colors, using color to denote hierarchy of information, and instances where adequate contrast impedes readability. You will have a better understanding of why accessible color usage is a journey and strategies for making continual progress.
About the Speaker – Ted Drake
Photo of Ted Drake
Ted Drake is the Global Accessibility Leader for Intuit, a financial software company. Intuit’s small and centralized accessibility team has created a culture of inclusive development and design with more than 600 champions. Customer interviews and feedback is key to their development.
Ted started working in accessibility almost 20 years ago, when he was the web site manager for the San Diego Museum of Art. He was also an early adopter of standards-based web development, which treated accessibility as core to engineering. While at Yahoo!, Ted was a front-end engineer, developer evangelist, and co-founded Yahoo’s Accessibility Lab. Ted’s benefited from ample International travel, including many trips to India and two years working out of Europe. Connect with Ted Drake on linkedin.
Artificial Intelligence and Accessibility - GAAD 2020 - Hello A11y
This presentation is for the Hello A11y conference celebrating Global Accessibility Awareness Day 2020. It introduces how artificial intelligence and machine learning is being used in assistive technology for people with disabilities.
Expand your outreach with an accessibility champions program
This document discusses Intuit's Accessibility Champion program, which aims to increase accessibility engagement and knowledge across the company. It outlines three levels of the program - Getting Started, Build Empathy, and Subject Matter Expert. Level 1 focuses on basic awareness training. Level 2 trains on empathy and auditing. Level 3 develops expertise through documentation, training, and certification. The program provides recognition, resources, and rewards to champions at each level to encourage participation and accessibility leadership across teams.
Intuit's Accessibility Champion Program - Coaching and Celebrating
This presentation was created for the Accessibility Online webinar series. It explains the goal of Intuit's Accessibility Champion program and explains the steps and successes of this program. The presentation will help you set up a similar problem at your company. Get the full details at this article: http://www.last-child.com/intuits-accessibility-champion-program/
This presentation was created for the Rotary Club of San Francisco to highlight research being done today for assistive technology and how it could appear in mainstream products and services in the future.
Inclusive customer interviews make it your friday task
Customer research has been a core part of Intuit from the earliest days of the company. In the 1980’s Intuit engineers would hang out at computer stores to find people buying Quicken software and ask if they could follow them home to watch their installation process to learn
about pain points and opportunities. Kurt Walecki, Intuit VP of Design, described the importance:
From the very beginning, Intuit has done user research both to understand how customers are using their current products and to identify customers’ unmet needs, allowing them to introduce new products to the market to satisfy them.
Every product and team at Intuit uses customer research and interviews to design and build products and new functionality. Intuit’s use of Lean Startup includesthe mantra “fall in love with
the problem, not the solution”
.
The goal is to understand the customer’s pain points and missed opportunities first, expand on the problem, build prototypes, continually review with the customer to test solutions, and then promote it to a product feature. This customer focus ensures the product grows with useful features and doesn’t bloat with unnecessary technology.
Accessibility is
extremely
impor
t
ant
when it comes to developing applications. It is the
right of every customer to get the same experience when they interact with a product and
disability is something t
hat should never come in the way.
Engineers are the folks
responsible for making this hap
pen and hence it is extremely important for them to
be
motivated and passionate around this technology. Let us learn how Intuit does this.
Accessibility statements and resource publishing best practices csun 2019
Accessibility features, products and services are of limited benefit if
consumers do not know
what is available, or how to access and use them. Companies that have taken the step of
creating a website focused on accessibility are reaching out to users who need that
information. Knowing the essential components to provide a sup
portive and positive
experience for users with disabilities will enable companies to develop or improve their
accessibility websites.
Intuit is in the process of developing an acc
essibility statement and resource center.
Rather
than reinvent the wheel, decided to research what other technology, e
-
commerce, finance,
transportation, and educational companies have done to see what works and what does not.
This presentation was given for the Bay Area Accessibility and Inclusive Design Meetup group to share Intuit's journey to expand accessibility education and ownership.
This document summarizes a presentation on accessibility and inclusive design. It discusses building products with and for people with disabilities to benefit all users. It provides examples of companies designing inclusively, like Amazon's focus on accessibility first and Nike's FlyEase shoes. The presentation encourages attendees to data mine for hidden customer feedback, reach out to diverse customer groups, test content for readability, and use resources like Microsoft's Inclusive Design Toolkit.
Matt May tweeted an observation in 2016 introducing Trickle-Down Accessibility and recognized prioritizing our blind customers could lead to less support for others.
Focusing on screen reader accessibility has distinct advantages for product developers. If your application works with a screen reader, it should also be usable with a keyboard, voice recognition, and switch control devices. Screen reader accessibility also falls in line with automated testing tools.
However, there are many disabilities, and assistive technologies, that are not necessarily benefited by this focus on the blind/low-vision community. Color contrast, closed captioning, readability, consistency in design, user customization, session timeouts, and animation distraction are just a few examples of concerns that often go unaddressed.
Accessibility metrics Accessibility Data Metrics and Reporting – Industry Bes...
Accessible version: http://www.last-child.com/a11y-data-metrics/
Learn how top companies are tracking and graphing product accessibility progress and incorporating data from automated, manual, and user testing to create management dashboards.
Mystery Meat 2.0 – Making hidden mobile interactions accessible
Mystery Meat was the unsavory term for hiding menus behind a parent link. Learn about today’s mobile version and how to make it accessible.
Accessible version: http://www.last-child.com/mystery-meat-2-accessible/
React Native Accessibility - San Diego React and React Native Meetup
This presentation was created by Poonam Tathavadkar and Ted Drake for the San Diego React and React Native meetup to introduce mobile accessibility and how to use React Native's functions to build accessible Android and iOS applications.
論文紹介:A Systematic Survey of Prompt Engineering on Vision-Language Foundation ...
Jindong Gu, Zhen Han, Shuo Chen, Ahmad Beirami, Bailan He, Gengyuan Zhang, Ruotong Liao, Yao Qin, Volker Tresp, Philip Torr "A Systematic Survey of Prompt Engineering on Vision-Language Foundation Models" arXiv2023
https://arxiv.org/abs/2307.12980
This presentation for AllyCamp 2020, looks at accessible names, how they are exposed in the browsers accessibility tree, and their importance to assistive technologies. There is also a deep dive into simple examples, advanced examples using ARIA, and an overview of the W3C's Accessible Name and Description Computation.
This presentation covers various methods for making your infographics not only accessible, but also shareable. This presentation was developed for the CSUN 2013 conference. The accessible version of this presentation is at http://www.last-child.com/accessible-infographics/csun-2013-presentation/
The document discusses the importance of web accessibility and provides tips to improve accessibility. It emphasizes that web content should be perceivable, operable, understandable, and robust for all users, including those with disabilities. The tips include using proper semantics with HTML5 elements and ARIA roles, adding descriptive text alternatives, ensuring sufficient color contrast and font sizes, and enabling keyboard navigation and screen reader support. The overall message is that an accessible web is open and inclusive for everyone.
Discover the Possibilities of the Jira Cloud Asset APIAtlassian
With the new assets management API for Jira Cloud, developers can bring a lot more context into Jira to create a faster and more powerful issue resolution experience.
Join Andrea, a developer on Jira Service Desk, as she gives a holistic overview of asset management in Jira Cloud. We’ll step through an ideal end-to-end user experience from help seekers raising a request for their laptop, to an agent resolution. In this talk, you’ll learn what powers these experiences and exactly how to create them using the Jira Cloud Assets API and integration points.
#ATAGTR2018 Presentation "Manual and Automated Accessibility Testing Implemen...Agile Testing Alliance
Rakesh Kondreddy who is a Senior STE at Ellucian, took a Session on "Manual and Automated Accessibility testing implementation" at Global Testing Retreat #ATAGTR2018
please refer our linkedin post for session details
https://www.linkedin.com/pulse/manual-automated-accessibility-testing-implementation-alliance/
HTML5 and ARIA accessibility - Bangalore 2013Ted Drake
This presentation introduces HTML5 and ARIA accessibility. It also introduces best practices and common problems. It was created for Intuit and PayPal/eBay engineers.
The document discusses web accessibility, providing information on the following key points in 3 sentences:
1) It defines 5 main categories of disabilities that can be affected by accessibility barriers: vision, deaf/hard-of-hearing, motor, cognitive, and seizure-related.
2) It summarizes the Web Content Accessibility Guidelines (WCAG) 2.0, which contains principles, guidelines, and success criteria to make web content more accessible to people with disabilities.
3) It provides tips for making web content more accessible, such as using alternative text for images, adding table headers, ensuring sufficient color contrast, and using clear form labels.
Web access for users with disabilities is an important goal and challenging problem for web content developers and designers.
Essential open source api projects to ease the developing & testing for web accessibility.
jQuery: Accessibility, Mobile und ResponsivePeter Rozek
The document summarizes a presentation on accessibility, mobile design, and responsive design given at the 2015 jQuery Conference in Berlin. It discusses how these topics are related but not the same, and provides examples of how to design for them individually and together. Key points include that responsive design helps with accessibility but does not ensure it, and that content should be accessible on any device without barriers.
This document discusses web accessibility and adjustments that can be made to content management systems like AEM to comply with Section 508 standards. It provides an overview of common disabilities like sight impairments and cognitive disabilities. Programmatic adjustments that can be made include adding alt text to images, proper labeling of form fields, and ensuring keyboard navigation. Color contrast, captioning videos, and organizing content in a logical structure can also improve accessibility. Testing with screen readers and disabling CSS is recommended. Resources for creating accessible content are provided.
This session will highlight the capabilities within AEM 6.2 that allow you to create accessible web content and how to meet the important requirements of WCAG 2.0.
YUI + Accessibility: Welcome the whole worldTed Drake
This presentation highlights common accessibility issues in modern web applications and how YUI makes it easy to build accessible, dynamic applications. You will learn about ARIA, focus management, and keyboard accessibility. The presentation will show how the Yahoo registration form uses YUI and accessibility best practices to make sure everyone can enjoy Yahoo products. You will learn how YUI's node and focus management makes it easy to build sophisticated, accessible interactions.
The document discusses best practices for search on museum websites. It recommends using Google search for the website but also implementing internal search to better understand the museum's unique content. It provides examples of autocomplete, faceted search, highlighting search terms, and correcting spelling to improve the user search experience. Solr is recommended as an open source tool for implementing these search features.
How Accessibility Made Me a Better DeveloperBilly Gregory
This is a longer version of my presentation "Responsible Design: Accountable Accessibility" but with a catchier name :)
This talk tells my story of how I went from front end developer who knew nothing about accessibility to an accessibility advocate.
Included in this talk are my "10 Tips" that any developer can use on day one without any experience authoring accessible HTML.
This talk was originally presented at the Accessibility Conference in Guelph, Ontario, Canada on May 29, 2013.
Twig is a template engine for PHP that is described as flexible, fast, and secure. Some key features of Twig include being concise yet powerful, with a template-oriented syntax. It aims to be easy to learn yet extensible. Twig provides features like inheritance, blocks, automatic escaping, and inclusion. It also focuses on being secure, with descriptive error messages and the ability to sandbox templates.
In this session we'll review the checks you must go through before deciding whether to use an ARIA role or attribute, reveal our favorites, discuss the ones that need more user agent support, and show you how you can help us make it happen.
A presentation for Dundee University's Hack Day explaining the technologies to use and how to hack your own APIs by using Yahoo! Pipes and scraping RSS feeds.
The document discusses HTML5 and WAI ARIA, including current and future features. Key points include:
1) WAI ARIA allows adding accessibility information to any element using attributes. It can be used with HTML, XHTML, SVG and others.
2) HTML5 will include new semantic elements like <nav> and <article> to provide structural information, though they are not yet supported widely.
3) WAI ARIA roles like landmarks can currently chunk pages into perceivable regions to aid navigation.
4) The <canvas> element poses challenges for accessibility without alternatives provided outside the element. ARIA and HTML5 integration defines their relationship going forward.
Similar to Hitting the accessibility high notes with ARIA (20)
Introduce Trauma-Informed Design to Your Organization - CSUN ATC 2024Ted Drake
Historically, accessibility specialists focused on a narrow set of disabilities. We focused on the senses, such as sight, sound, and touch. We focused on abilities, like hearing, movement, and seeing.
We expanded to include cognitive, mental health, and neurodiversity. This is significant. We now have tools to build inclusive products and services for an estimated 25% of the population. What about the other 75%?
As accessibility professionals, we understand unique experiences and needs. We are best equipped to expand customer research and design at our companies. Universal design was described as a one size fits all solution. Inclusive design is one size fits one. Intersectional design is one size fits one, but also accounts for price, texture, availability, cultural appropriateness, and more.
This presentation introduces the next layer of inclusive design; one that recognizes trauma.
Trauma-Informed Design (TID) started in education, health, and community spaces. It focuses on the person’s experiences, recognizing trauma’s impact, anxiety, and restoring personal control. Architects embraced TID to develop spaces that are comfortable instead of confrontive.
While the earlier stages of TID focused on individualized experiences, we can still take the principles and apply them to web and mobile application design. This is especially critical for emerging AI powered experiences where transparency and collective understanding are rarely considered.
Transforming Accessibility one lunch at a tiime - CSUN 2023Ted Drake
Try to remember March 2020. The COVID epidemic was raging and businesses sent everyone home to work remotely. Ted Drake and Sagar Barbhaya were at the 2020 CSUN ATC conference. Returning to our homes, we wondered if we could continue the energy and curiosity found at a conference, only transforming it for a virtual work environment. The following week, we launched Intuit’s Zoom-based Accessibility Lunch and Learn series. It was an experiment planned to last only a few weeks. We reached out to our Accessibility Champion network and quickly arranged daily lectures, mostly based on presentations already given at onboarding and other training events. As the epidemic grew, we turned inward and focused less on accessibility and more on our mental health, living with a disability, and celebrating our diversity. The key transformation came with a talk about sobriety in the workplace. The speaker’s courage to discuss her journey led to heartfelt conversations about mental health, the loss of community, and the struggle where colleagues were trying to encourage hope with “happy hours” and alcohol-related team building activities. This presentation led to immediate improvements in our workplace language and pandemic policies. It also showed a lunch and learn was more than a lecture. It could be the community we were aching for. With more than 100 presentations and thousands of participants, we continue to learn something new every week.
Inclusive Design for cognitive disabilities, neurodiversity, and chronic illnessTed Drake
Learn how to design for people with short term memory loss, problems focusing on a task, struggling with anxiety, and dealing with chronic pain. This presentation will introduce you to the people you need to include in your designs. You will also have clear action items for inclusive design.
This talk was presented at the San Diego Accessibility Meetup on August 1, 2022. It explains the basics of affordances, signifiers, cognitive load, and how we can design to reduce the effort needed by our customers to understand and use our products. This also includes updated information on Long COVID and why we need to focus more of our attention on cognitive accessibilty.
Covid 19, brain fog, and inclusive designTed Drake
1. The document discusses Long COVID and brain fog, which can occur in some people after a COVID-19 infection. Symptoms can include shortness of breath, fatigue, joint pain, changes in smell/taste, brain fog, anxiety, and inability to focus. Approximately 20% of COVID patients experience long-term symptoms.
2. The document shares experiences of people living with long COVID and brain fog symptoms. This includes difficulty concentrating, short-term memory loss, anxiety and panic attacks.
3. The document discusses designing inclusively for those with long COVID. This includes minimizing cognitive load, using recognition over recall, highlighting selections, and following guidelines like WCAG that promote cognitive accessibility. A
Automated accessibility testing can greatly improve the product experience by empowering developers and designers to eliminate repetitive, mundane errors and focus on the challenging and interesting elements. This presentation focuses on the customer experience and how it can be improved by using automated testing throughout the software development cycle.
Ask any accessibility leader about accessible colors and they’ll wince from the pain of struggling for a solution. Why is it so difficult to ensure your product meets WCAG 2.1 AA color contrast requirements? Ted Drake, Intuit’s Global Accessibility Leader, will explain the basics of color accessibility requirements. He will also talk about the conflict of overlapping requirements, dealing with brand colors, using color to denote hierarchy of information, and instances where adequate contrast impedes readability. You will have a better understanding of why accessible color usage is a journey and strategies for making continual progress.
About the Speaker – Ted Drake
Photo of Ted Drake
Ted Drake is the Global Accessibility Leader for Intuit, a financial software company. Intuit’s small and centralized accessibility team has created a culture of inclusive development and design with more than 600 champions. Customer interviews and feedback is key to their development.
Ted started working in accessibility almost 20 years ago, when he was the web site manager for the San Diego Museum of Art. He was also an early adopter of standards-based web development, which treated accessibility as core to engineering. While at Yahoo!, Ted was a front-end engineer, developer evangelist, and co-founded Yahoo’s Accessibility Lab. Ted’s benefited from ample International travel, including many trips to India and two years working out of Europe. Connect with Ted Drake on linkedin.
This presentation is for the Hello A11y conference celebrating Global Accessibility Awareness Day 2020. It introduces how artificial intelligence and machine learning is being used in assistive technology for people with disabilities.
Expand your outreach with an accessibility champions program Ted Drake
This document discusses Intuit's Accessibility Champion program, which aims to increase accessibility engagement and knowledge across the company. It outlines three levels of the program - Getting Started, Build Empathy, and Subject Matter Expert. Level 1 focuses on basic awareness training. Level 2 trains on empathy and auditing. Level 3 develops expertise through documentation, training, and certification. The program provides recognition, resources, and rewards to champions at each level to encourage participation and accessibility leadership across teams.
Intuit's Accessibility Champion Program - Coaching and Celebrating Ted Drake
This presentation was created for the Accessibility Online webinar series. It explains the goal of Intuit's Accessibility Champion program and explains the steps and successes of this program. The presentation will help you set up a similar problem at your company. Get the full details at this article: http://www.last-child.com/intuits-accessibility-champion-program/
This presentation was created for the Rotary Club of San Francisco to highlight research being done today for assistive technology and how it could appear in mainstream products and services in the future.
Inclusive customer interviews make it your friday taskTed Drake
Customer research has been a core part of Intuit from the earliest days of the company. In the 1980’s Intuit engineers would hang out at computer stores to find people buying Quicken software and ask if they could follow them home to watch their installation process to learn
about pain points and opportunities. Kurt Walecki, Intuit VP of Design, described the importance:
From the very beginning, Intuit has done user research both to understand how customers are using their current products and to identify customers’ unmet needs, allowing them to introduce new products to the market to satisfy them.
Every product and team at Intuit uses customer research and interviews to design and build products and new functionality. Intuit’s use of Lean Startup includesthe mantra “fall in love with
the problem, not the solution”
.
The goal is to understand the customer’s pain points and missed opportunities first, expand on the problem, build prototypes, continually review with the customer to test solutions, and then promote it to a product feature. This customer focus ensures the product grows with useful features and doesn’t bloat with unnecessary technology.
Coaching and Celebrating Accessibility ChampionsTed Drake
Accessibility is
extremely
impor
t
ant
when it comes to developing applications. It is the
right of every customer to get the same experience when they interact with a product and
disability is something t
hat should never come in the way.
Engineers are the folks
responsible for making this hap
pen and hence it is extremely important for them to
be
motivated and passionate around this technology. Let us learn how Intuit does this.
Accessibility statements and resource publishing best practices csun 2019Ted Drake
Accessibility features, products and services are of limited benefit if
consumers do not know
what is available, or how to access and use them. Companies that have taken the step of
creating a website focused on accessibility are reaching out to users who need that
information. Knowing the essential components to provide a sup
portive and positive
experience for users with disabilities will enable companies to develop or improve their
accessibility websites.
Intuit is in the process of developing an acc
essibility statement and resource center.
Rather
than reinvent the wheel, decided to research what other technology, e
-
commerce, finance,
transportation, and educational companies have done to see what works and what does not.
Raising Accessibility Awareness at IntuitTed Drake
This presentation was given for the Bay Area Accessibility and Inclusive Design Meetup group to share Intuit's journey to expand accessibility education and ownership.
This document summarizes a presentation on accessibility and inclusive design. It discusses building products with and for people with disabilities to benefit all users. It provides examples of companies designing inclusively, like Amazon's focus on accessibility first and Nike's FlyEase shoes. The presentation encourages attendees to data mine for hidden customer feedback, reach out to diverse customer groups, test content for readability, and use resources like Microsoft's Inclusive Design Toolkit.
Matt May tweeted an observation in 2016 introducing Trickle-Down Accessibility and recognized prioritizing our blind customers could lead to less support for others.
Focusing on screen reader accessibility has distinct advantages for product developers. If your application works with a screen reader, it should also be usable with a keyboard, voice recognition, and switch control devices. Screen reader accessibility also falls in line with automated testing tools.
However, there are many disabilities, and assistive technologies, that are not necessarily benefited by this focus on the blind/low-vision community. Color contrast, closed captioning, readability, consistency in design, user customization, session timeouts, and animation distraction are just a few examples of concerns that often go unaddressed.
Accessibility metrics Accessibility Data Metrics and Reporting – Industry Bes...Ted Drake
Accessible version: http://www.last-child.com/a11y-data-metrics/
Learn how top companies are tracking and graphing product accessibility progress and incorporating data from automated, manual, and user testing to create management dashboards.
Mystery Meat 2.0 – Making hidden mobile interactions accessibleTed Drake
Mystery Meat was the unsavory term for hiding menus behind a parent link. Learn about today’s mobile version and how to make it accessible.
Accessible version: http://www.last-child.com/mystery-meat-2-accessible/
React Native Accessibility - San Diego React and React Native MeetupTed Drake
This presentation was created by Poonam Tathavadkar and Ted Drake for the San Diego React and React Native meetup to introduce mobile accessibility and how to use React Native's functions to build accessible Android and iOS applications.
論文紹介:A Systematic Survey of Prompt Engineering on Vision-Language Foundation ...Toru Tamaki
Jindong Gu, Zhen Han, Shuo Chen, Ahmad Beirami, Bailan He, Gengyuan Zhang, Ruotong Liao, Yao Qin, Volker Tresp, Philip Torr "A Systematic Survey of Prompt Engineering on Vision-Language Foundation Models" arXiv2023
https://arxiv.org/abs/2307.12980
Scaling Connections in PostgreSQL Postgres Bangalore(PGBLR) Meetup-2 - MydbopsMydbops
This presentation, delivered at the Postgres Bangalore (PGBLR) Meetup-2 on June 29th, 2024, dives deep into connection pooling for PostgreSQL databases. Aakash M, a PostgreSQL Tech Lead at Mydbops, explores the challenges of managing numerous connections and explains how connection pooling optimizes performance and resource utilization.
Key Takeaways:
* Understand why connection pooling is essential for high-traffic applications
* Explore various connection poolers available for PostgreSQL, including pgbouncer
* Learn the configuration options and functionalities of pgbouncer
* Discover best practices for monitoring and troubleshooting connection pooling setups
* Gain insights into real-world use cases and considerations for production environments
This presentation is ideal for:
* Database administrators (DBAs)
* Developers working with PostgreSQL
* DevOps engineers
* Anyone interested in optimizing PostgreSQL performance
Contact info@mydbops.com for PostgreSQL Managed, Consulting and Remote DBA Services
An invited talk given by Mark Billinghurst on Research Directions for Cross Reality Interfaces. This was given on July 2nd 2024 as part of the 2024 Summer School on Cross Reality in Hagenberg, Austria (July 1st - 7th)
Quantum Communications Q&A with Gemini LLM. These are based on Shannon's Noisy channel Theorem and offers how the classical theory applies to the quantum world.
Coordinate Systems in FME 101 - Webinar SlidesSafe Software
If you’ve ever had to analyze a map or GPS data, chances are you’ve encountered and even worked with coordinate systems. As historical data continually updates through GPS, understanding coordinate systems is increasingly crucial. However, not everyone knows why they exist or how to effectively use them for data-driven insights.
During this webinar, you’ll learn exactly what coordinate systems are and how you can use FME to maintain and transform your data’s coordinate systems in an easy-to-digest way, accurately representing the geographical space that it exists within. During this webinar, you will have the chance to:
- Enhance Your Understanding: Gain a clear overview of what coordinate systems are and their value
- Learn Practical Applications: Why we need datams and projections, plus units between coordinate systems
- Maximize with FME: Understand how FME handles coordinate systems, including a brief summary of the 3 main reprojectors
- Custom Coordinate Systems: Learn how to work with FME and coordinate systems beyond what is natively supported
- Look Ahead: Gain insights into where FME is headed with coordinate systems in the future
Don’t miss the opportunity to improve the value you receive from your coordinate system data, ultimately allowing you to streamline your data analysis and maximize your time. See you there!
YOUR RELIABLE WEB DESIGN & DEVELOPMENT TEAM — FOR LASTING SUCCESS
WPRiders is a web development company specialized in WordPress and WooCommerce websites and plugins for customers around the world. The company is headquartered in Bucharest, Romania, but our team members are located all over the world. Our customers are primarily from the US and Western Europe, but we have clients from Australia, Canada and other areas as well.
Some facts about WPRiders and why we are one of the best firms around:
More than 700 five-star reviews! You can check them here.
1500 WordPress projects delivered.
We respond 80% faster than other firms! Data provided by Freshdesk.
We’ve been in business since 2015.
We are located in 7 countries and have 22 team members.
With so many projects delivered, our team knows what works and what doesn’t when it comes to WordPress and WooCommerce.
Our team members are:
- highly experienced developers (employees & contractors with 5 -10+ years of experience),
- great designers with an eye for UX/UI with 10+ years of experience
- project managers with development background who speak both tech and non-tech
- QA specialists
- Conversion Rate Optimisation - CRO experts
They are all working together to provide you with the best possible service. We are passionate about WordPress, and we love creating custom solutions that help our clients achieve their goals.
At WPRiders, we are committed to building long-term relationships with our clients. We believe in accountability, in doing the right thing, as well as in transparency and open communication. You can read more about WPRiders on the About us page.
Comparison Table of DiskWarrior Alternatives.pdfAndrey Yasko
To help you choose the best DiskWarrior alternative, we've compiled a comparison table summarizing the features, pros, cons, and pricing of six alternatives.
TrustArc Webinar - 2024 Data Privacy Trends: A Mid-Year Check-InTrustArc
Six months into 2024, and it is clear the privacy ecosystem takes no days off!! Regulators continue to implement and enforce new regulations, businesses strive to meet requirements, and technology advances like AI have privacy professionals scratching their heads about managing risk.
What can we learn about the first six months of data privacy trends and events in 2024? How should this inform your privacy program management for the rest of the year?
Join TrustArc, Goodwin, and Snyk privacy experts as they discuss the changes we’ve seen in the first half of 2024 and gain insight into the concrete, actionable steps you can take to up-level your privacy program in the second half of the year.
This webinar will review:
- Key changes to privacy regulations in 2024
- Key themes in privacy and data governance in 2024
- How to maximize your privacy program in the second half of 2024
RPA In Healthcare Benefits, Use Case, Trend And Challenges 2024.pptxSynapseIndia
Your comprehensive guide to RPA in healthcare for 2024. Explore the benefits, use cases, and emerging trends of robotic process automation. Understand the challenges and prepare for the future of healthcare automation
Sustainability requires ingenuity and stewardship. Did you know Pigging Solutions pigging systems help you achieve your sustainable manufacturing goals AND provide rapid return on investment.
How? Our systems recover over 99% of product in transfer piping. Recovering trapped product from transfer lines that would otherwise become flush-waste, means you can increase batch yields and eliminate flush waste. From raw materials to finished product, if you can pump it, we can pig it.
BT & Neo4j: Knowledge Graphs for Critical Enterprise Systems.pptx.pdfNeo4j
Presented at Gartner Data & Analytics, London Maty 2024. BT Group has used the Neo4j Graph Database to enable impressive digital transformation programs over the last 6 years. By re-imagining their operational support systems to adopt self-serve and data lead principles they have substantially reduced the number of applications and complexity of their operations. The result has been a substantial reduction in risk and costs while improving time to value, innovation, and process automation. Join this session to hear their story, the lessons they learned along the way and how their future innovation plans include the exploration of uses of EKG + Generative AI.
Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Em...Erasmo Purificato
Slide of the tutorial entitled "Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Emerging Trends" held at UMAP'24: 32nd ACM Conference on User Modeling, Adaptation and Personalization (July 1, 2024 | Cagliari, Italy)
Choose our Linux Web Hosting for a seamless and successful online presencerajancomputerfbd
Our Linux Web Hosting plans offer unbeatable performance, security, and scalability, ensuring your website runs smoothly and efficiently.
Visit- https://onliveserver.com/linux-web-hosting/
The Increasing Use of the National Research Platform by the CSU Campuses
Hitting the accessibility high notes with ARIA
1. Hitting the high notes
with ARIA
Ted Drake, Intuit Accessibility
Silicon Valley Code Camp,
October 2013
Sunday, October 6, 13
This presentation on ARIA was created for the Silicon Valley Code Camp, 2013 by Ted Drake.
2. Goals
• Screen Reader Introduction
• Introduce ARIA
• Use it today
• Examples
Sunday, October 6, 13
The goal of this talk to to de-mystify ARIA and encourage engineers to make their sites more
accessible by using it correctly. This talk will be focused on new users, but should also
provide interesting content and examples for more advanced users.
3. Screen
Readers
Sunday, October 6, 13
Screen readers are used primarily by people with vision disabilities. However, they are also
used as a middle layer for automated testing and for people with cognitive and physical
disabilities.
Screen readers interpret the user’s interaction and the applications responses.
4. Sunday, October 6, 13
This short video shows how a screen reader announces the content and role of an element,
such as a link or form input.
5. Sunday, October 6, 13
This short video shows how a screen reader announces the content and role of an element,
such as a link or form input.
6. Sunday, October 6, 13
This short video shows how a screen reader user can navigate around a page by examining
the header tags. The user can also navigate via landmarks, form elements, links, images, and
other types of elements on the page.
7. Sunday, October 6, 13
This short video shows how a screen reader user can navigate around a page by examining
the header tags. The user can also navigate via landmarks, form elements, links, images, and
other types of elements on the page.
9. a·ri·a
ˈärēə/
noun Music
noun: aria; plural noun: arias
1.
a long, accompanied song for a solo voice,
typically one in an opera or oratorio.
Sunday, October 6, 13
An aria is the solo performance during an opera that brings people to their feet.
10. A·RI·A
ˈärēə/
nounTechnology
noun: aria;
1.
WAI-ARIA (Web Accessibility Initiative -
Accessible Rich Internet Applications) is a draft
technical specification published by the World
Wide Web Consortium that specifies how to
increase the accessibility of dynamic content and
user interface components
Sunday, October 6, 13
WAI ARIA is a web standard established as a bridging technique to provide accessibility to
dynamic web sites.
11. Basics
• HTML attributes
• Good support
• Easy
• Bridge to HTML5
• No visual impact
Sunday, October 6, 13
ARIA is a set of HTML attributes that provide information to the user via the browser and
assistive technology.
ARIA has good support via browsers and screen readers, but not as good for other assistive
technology.
Don’t depend on ARIA if possible.
ARIA’s basic elements are easy to understand and code
ARIA is a bridge technology until HTML5 is completely supported. It’s ok to combine and
should be future proof.
12. ARIA Rules
1. Don’t use ARIA if
native tag is available.
2. See #1
Sunday, October 6, 13
The best user experience is created with the semantic HTML tags. ARIA is meant to fix areas that
cannot use existing native elements.
Use <button> instead of role=”button”, <table> instead of role=”grid”, and <img> instead of
role=”img”
too many people are using crap code because it is part of a platform, given in a demo, or think it’s
easier to style a blank element.
Don’t do this. Use the correct tag to give your site structure. If you are stuck using bad code, use ARIA
to make it work, but you are still stuck with a bad foundation.
http://www.w3.org/TR/aria-in-html/#first-rule-of-aria-use
13. ARIA > HTML
Sunday, October 6, 13
ARIA has more importance than HTML.
When you put ARIA on a tag, it will supercede the tag’s value.
This includes role, state, and properties.
14. I’m a link that points to
the same page and
says “Button”
Before ARIA
Sunday, October 6, 13
In this example, we have a link that has been styled to look like a button.
<a href=”#”>Button</a>
15. <a href=”#”>
! Button
</a>
Sunday, October 6, 13
This is the code for the link that looks like a button. It will be announced as an internal link,
as the href value is #.
16. I’m a button that says
“Button”
After ARIA
Sunday, October 6, 13
In this example, we have a link that has been styled to look like a button.
<a href=”#” role=”button”>Button</a>
17. <a href=”#” role=”button”>
! Button
</a>
Sunday, October 6, 13
In this example, we are using the ARIA role attribute to redefine a link as a button. This will
cause the screen reader to ignore the href.
Links should take the user to a new page or chunk of content.
Buttons should trigger an action.
18. Roles
• Widget: role=”alert”
• Composite: role=”grid”
• Document Structure: role=”img”
• Landmark: role=”search”
• w3.org/TR/wai-aria/roles
Sunday, October 6, 13
Alert is a widget role. Adding this role suggests an interface and may be standalone or part of
a group. Alert will prompt the browser to announce the content when this object changes,
such as when an alert appears on a page.
Grid is a composite role. There’s a complex arrangement of sub-roles. Grid allows a set of
divs to act like a table.
Img is a structure role. It describes the structural elements and are not interactive.
Landmarks are regions that can be used for navigation to key elements of an application.
http://www.w3.org/TR/wai-aria/roles
19. Landmarks
• Search Form: role=”search”
• Main: role=”main”
• Nav: role=”navigation”
• Header: role=”banner”
Sunday, October 6, 13
landmarks define content areas on a page. These match HTML5 tags and can be combined.
They provide alternate navigation opportunities for users.
Firefox is the only browser that currently surfaces the native HTML5 tag roles to assistive
technology.
So <nav role=”navigation”> is good.
20. Landmarks
<form role=”search”>
<label for=”q”>Search</label>
<input type=”search” id=”q” name=”q”>
<button>submit</button>
</form>
Sunday, October 6, 13
Adding role=”search” to the form tag allows a user to quickly move to the search form from
anywhere in the page. Note, this goes on the form, not the input.
21. States
• aria-disabled=”true | false”
• aria-expanded=”true | false | undefined”
• aria-hidden=”true | false”
• aria-invalid=”true | false | grammar | spelling”
• aria-selected=”true | false | undefined”
Sunday, October 6, 13
States represent the current state of an object and can change as the user interacts with the
application.
Many are tied to specific roles and cannot be used indiscriminately.
Many of these states are already commonly used in HTML elements
22. I’m a disabled button
that says “Disabled
Button”
After ARIA
Sunday, October 6, 13
In this example, we have a span that has been styled to look like a button.
<a href=”#” role=”button”>Button</a>
23. <a href=”#”
role=”button” aria-disabled=”true”>
! Disabled Button
</a>
Sunday, October 6, 13
In this example, we added aria-disabled=”true” to the link to let users know this isn’t just a
button, it’s a disabled button.
It would be easier to simply use <button disabled>Disabled Button</button>
24. <button disabled>
Disabled Button
</button>
Sunday, October 6, 13
This shows how it is much easier to use the native tags and avoid fixing stuff with ARIA
http://www.w3.org/TR/html401/interact/forms.html#h-17.12
25. Properties
• aria-live=”polite | assertive | off”
• aria-label=”string”
• aria-describedby=”string”
• aria-haspopup=”true | false”
Sunday, October 6, 13
Properties attributes don’t change frequently. They describe special features for an object
aria-live: describes how a browser/screen reader should announce content when it changes, ie polite waits for
the user to pause.
aria-label: provides a label when the standard text label is not available. It will also over-write any existing text
labels.
aria-describedby: is treated similar to the title attribute. It announces optional information that provides context.
aria-haspopup: clicking on this link or button will generate a new chunk of content, such as a dropdown menu or
dialog window.
26. Live Regions
• aria-live=”polite”: announced after user
stops interacting with page.
• aria-live=”assertive”: interrupts user
• aria-live=”off”: no announcement
• role=”alert”: inherits aria-live=”assertive”
Sunday, October 6, 13
27. Sunday, October 6, 13
This example from the University of Illinois Urbana-Champagne shows how aria-live
announced new content.
There is a message box that will interrupt the reading of the text box.
The message box is using aria-live=”assertive”
http://test.cita.illinois.edu/aria/live/
28. Sunday, October 6, 13
This example from the University of Illinois Urbana-Champagne shows how aria-live
announced new content.
There is a message box that will interrupt the reading of the text box.
The message box is using aria-live=”assertive”
http://test.cita.illinois.edu/aria/live/
30. Sunday, October 6, 13
This shows how pseudo buttons are not focusable via tab key and are announced as a text
string, not an interactive element
test page: http://fyvr.net/a11y/fake-real-buttons.html
31. Sunday, October 6, 13
This shows how pseudo buttons are not focusable via tab key and are announced as a text
string, not an interactive element
test page: http://fyvr.net/a11y/fake-real-buttons.html
32. Sunday, October 6, 13
This short video shows a common pattern where the search form has no label. Further, the
input is using the value attribute to contain a pseudo-placeholder. The value is cleared when
the user places focus into the input.
This fails because the input now has no label, no placeholder, and no value.
The placeholder attribute is not consistently supported and will not be announced if a user
moves back into the input after a value has been entered.
33. Sunday, October 6, 13
This short video shows a common pattern where the search form has no label. Further, the
input is using the value attribute to contain a pseudo-placeholder. The value is cleared when
the user places focus into the input.
This fails because the input now has no label, no placeholder, and no value.
The placeholder attribute is not consistently supported and will not be announced if a user
moves back into the input after a value has been entered.
34. Sunday, October 6, 13
This video is a bit more difficult to understand. It shows a data table that uses divs instead of
a standard table markup. the screen reader announces the content as a series of simple
strings. The selected icons are not announced, as they are empty spans with background
images.
Test page: http://fyvr.net/a11y/payroll-table.html
35. Sunday, October 6, 13
This video is a bit more difficult to understand. It shows a data table that uses divs instead of
a standard table markup. the screen reader announces the content as a series of simple
strings. The selected icons are not announced, as they are empty spans with background
images.
Test page: http://fyvr.net/a11y/payroll-table.html
36. ARIA to the
Rescue
Sunday, October 6, 13
Let’s go back to our earlier examples and show how ARIA can fix those common issues.
37. Sunday, October 6, 13
This video shows how role=”button” makes a link sound just like a real button.
<a href=”#” role=”button”>foo</a>
38. Sunday, October 6, 13
This video shows how role=”button” makes a link sound just like a real button.
<a href=”#” role=”button”>foo</a>
39. Sunday, October 6, 13
This form fixes the search form by adding role=”search” to the form tag. This sets it as a
landmark.
The input receives a label via aria-label=”search”
The placeholder attribute is not a substitute for a label.
40. Sunday, October 6, 13
This form fixes the search form by adding role=”search” to the form tag. This sets it as a
landmark.
The input receives a label via aria-label=”search”
The placeholder attribute is not a substitute for a label.
41. Sunday, October 6, 13
This example isn’t perfect. But it does show how these divs can be given the data table
semantics by using the role=”grid” and appropriate children roles. The blue dots are also
given text: supported and not supported.
This could have been built with a basic data table in the start.
42. Sunday, October 6, 13
This example isn’t perfect. But it does show how these divs can be given the data table
semantics by using the role=”grid” and appropriate children roles. The blue dots are also
given text: supported and not supported.
This could have been built with a basic data table in the start.
43. ARIA Form
• role=”alert”
• aria-describedby=”emailerror”
• aria-invalid=”true”
Sunday, October 6, 13
So far, this presentation has given examples of using ARIA to restore semantics and add
landmarks. Let’s see how a few small changes can make significant usability improvements
that were not possible with basic html.
This example will use role=”alert” on an input’s error message. The invalid form input will
also get aria-invalid=”true” and aria-describedby to point to the error message.
44. Sunday, October 6, 13
This form has an email input that is validated as the user leaves the input (onBlur). The video
shows how the screen reader will announce the alert as soon as it appears. When the user
goes back to the input, they are told the input is invalid and the error message is repeated.
45. Sunday, October 6, 13
This form has an email input that is validated as the user leaves the input (onBlur). The video
shows how the screen reader will announce the alert as soon as it appears. When the user
goes back to the input, they are told the input is invalid and the error message is repeated.
46. role=”alert”
<p role="alert" id="emailerror">
Please enter a valid email
address
</p>
Sunday, October 6, 13
Adding role=”alert” to an element will trigger the screen reader to announce the content
whenever it changes. In this page, the content is announced when the display status is
changed from display:none to display:block.
Also note, there is an id on this element. This will be used by aria-describedby attribute.
51. Key Takeaways
• ARIA is easy and safe to use.
• Use basic HTML before reaching into the
ARIA bag
• ARIA provides information on role, state,
and property
• Make your forms more accessible with
ARIA
• Stop the div-itis
Sunday, October 6, 13