WCAG is supposed to give us a reasonably objective way of saying whether or not the sites we are building/auditing are "accessible" (to a particular baseline). However, they are only as useful as our understanding and interpretation of the guidelines' normative text. And, of course, it is not perfect - with some omissions, handwaving, and straight-up loopholes. So where does this leave developers and auditors?
In this talk - a reprise of a previous talk, now updated to cover new SCs from WCAG 2.2 - Patrick may not have all the answers, but he'll have a good rant around the subject anyway...
These aren't the SCs you're looking for ... (mis)adventures in WCAG 2.x inter...Patrick Lauke
WCAG is supposed to give us a reasonably objective way of saying whether or not the sites we are building/auditing are "accessible" (to a particular baseline). However, they are only as useful as our understanding and interpretation of the actual guidelines' normative text. And of course they're not perfect - with some omissions, handwaving, and straight up loopholes. So where does this leave developers and auditors? In this talk, Patrick may not have all the answers, but he'll have a good rant around the subject anyway...
These aren't the SCs you're looking for ... (mis)adventures in WCAG 2.x inter...Patrick Lauke
WCAG is supposed to give us a reasonably objective way of saying whether or not the sites we are building/auditing are "accessible" (to a particular baseline). However, they are only as useful as our understanding and interpretation of the actual guidelines' normative text. And of course they're not perfect - with some omissions, handwaving, and straight up loopholes. So where does this leave developers and auditors? In this talk, Patrick may not have all the answers, but he'll have a good rant around the subject anyway...
Too much accessibility: Good intentions, badly implementedGabriel Porras
En esta excelente presentación, Patrick Lauke (http://www.splintered.co.uk/) presenta varias formas de cómo se pueden aplicar mal los principios de accesibilidad (como el texto alt y el atributo title), y discute algunas técnicas que no puede ser tan buenas como parecen (como el tabindex, los access keys y los controles de aumento de tamaño de los textos).
La presentación en varios formatos se puede descargar de: http://www.splintered.co.uk/documents/presentations/psf_accessibility_08.08.2007/
Arkítektúr fjallar um "structure" og "vision" og ef við ætlum að lýsa kerfinu okkar fyrir öðrum verðum við að teikna það upp. Vandinn er þá hvað skal teikna, hvernig og af hverju. Flestir sem vinna í hugbúnaðargerð hafa alls ekki lært að teikna myndir af kerfinu sínu og búa yfirleitt til stórar, flóknar óskiljanlega myndir sem eru langt frá því vera eins og kerfið sjálft.
Betra er að teikna margar hnitmiðarar myndir sem sýna kerfið með mismunandi flækjustigi, frá því að sýna notendur og niður í klasarit. Í þessu fyrirlestri skoðum við þrjár tegundir af myndum, context, container og component diagrams.
These aren't the SCs you're looking for ... (mis)adventures in WCAG 2.x inter...Patrick Lauke
WCAG is supposed to give us a reasonably objective way of saying whether or not the sites we are building/auditing are "accessible" (to a particular baseline). However, they are only as useful as our understanding and interpretation of the actual guidelines' normative text. And of course they're not perfect - with some omissions, handwaving, and straight up loopholes. So where does this leave developers and auditors? In this talk, Patrick may not have all the answers, but he'll have a good rant around the subject anyway...
These aren't the SCs you're looking for ... (mis)adventures in WCAG 2.x inter...Patrick Lauke
WCAG is supposed to give us a reasonably objective way of saying whether or not the sites we are building/auditing are "accessible" (to a particular baseline). However, they are only as useful as our understanding and interpretation of the actual guidelines' normative text. And of course they're not perfect - with some omissions, handwaving, and straight up loopholes. So where does this leave developers and auditors? In this talk, Patrick may not have all the answers, but he'll have a good rant around the subject anyway...
Too much accessibility: Good intentions, badly implementedGabriel Porras
En esta excelente presentación, Patrick Lauke (http://www.splintered.co.uk/) presenta varias formas de cómo se pueden aplicar mal los principios de accesibilidad (como el texto alt y el atributo title), y discute algunas técnicas que no puede ser tan buenas como parecen (como el tabindex, los access keys y los controles de aumento de tamaño de los textos).
La presentación en varios formatos se puede descargar de: http://www.splintered.co.uk/documents/presentations/psf_accessibility_08.08.2007/
Arkítektúr fjallar um "structure" og "vision" og ef við ætlum að lýsa kerfinu okkar fyrir öðrum verðum við að teikna það upp. Vandinn er þá hvað skal teikna, hvernig og af hverju. Flestir sem vinna í hugbúnaðargerð hafa alls ekki lært að teikna myndir af kerfinu sínu og búa yfirleitt til stórar, flóknar óskiljanlega myndir sem eru langt frá því vera eins og kerfið sjálft.
Betra er að teikna margar hnitmiðarar myndir sem sýna kerfið með mismunandi flækjustigi, frá því að sýna notendur og niður í klasarit. Í þessu fyrirlestri skoðum við þrjár tegundir af myndum, context, container og component diagrams.
This was a 1-hour BPMN Intro/Primer webinar I presented at ASPE. Just to be clear, I design/develop and teach classes for ASPE ("Modeling Processes using BPMN" being one of those classes), so one of goals was to tease audiences into wanting to learn more(and attending my class:-). Beyond that, the main goal was to share useful/interesting information and to ignite questions and curiosity about this important topic. Let me know what you think. Thanks, Razvan:-)
CSUN 2018 Analyzing and Extending WCAG Beyond 3 DigitsBill Tyler
Slide deck from Bill Tyler's presentation of the Benefits of Analyzing & Extending WCAG 2.0 Beyond Three Digits from CSUN 2018 Conference (Friday, March 23, 2017)
WAI-ARIA An introduction to Accessible Rich Internet Applications / CSS Minsk...Patrick Lauke
Vanilla HTML is limiting and boring. Our clients demand highly engaging and interactive web experiences. And wouldn’t you know, with just a bit of HTML and JavaScript we can craft amazing custom controls, widgets and effects that go far beyond the confines of traditional static markup. But how can we ensure that these custom experiences are both understandable and usable for people with disabilities, and in particular those using assistive technologies such as screen readers?
In this talk, we will look at the basics of making some common custom-built components accessible - covering how browsers and assistive technologies interact, the limitations of HTML, and how ARIA can help make interactive experiences more accessible. In addition, we will explore some of the recent additions in ARIA 1.1, as well as some particular challenges when it comes to traditional ARIA patterns and assistive technologies on mobile/tablet/touch devices.
Evergreen slidedeck at https://patrickhlauke.github.io/aria/presentation/ / https://github.com/patrickhlauke/aria/
WAI-ARIA An introduction to Accessible Rich Internet Applications / JavaScrip...Patrick Lauke
Vanilla HTML is limiting and boring. Our clients demand highly engaging and interactive web experiences. And wouldn’t you know, with just a bit of HTML and JavaScript we can craft amazing custom controls, widgets and effects that go far beyond the confines of traditional static markup. But how can we ensure that these custom experiences are both understandable and usable for people with disabilities, and in particular those using assistive technologies such as screen readers?
In this talk, we will look at the basics of making some common custom-built components accessible - covering how browsers and assistive technologies interact, the limitations of HTML, and how ARIA can help make interactive experiences more accessible. In addition, we will explore some of the recent additions in ARIA 1.1, as well as some particular challenges when it comes to traditional ARIA patterns and assistive technologies on mobile/tablet/touch devices.
Evergreen slidedeck at https://patrickhlauke.github.io/aria/presentation/ / https://github.com/patrickhlauke/aria/
This presentation for Inclusive Design 24 (#ID24) explores how to create accessible, usable "floating" labels. Floating labels are where the label moves above form controls based on user interaction.
Too much accessibility - good intentions, badly implemented / Public Sector F...Patrick Lauke
HTML offers many features and attributes that can make your sites more accessible...but only if they're used wisely. Can there really be "too much accessibility"?
Audio recording: https://archive.org/details/Psf8August2007.PatrickH.Lauke-TooMuchAccessibilityGoodIntentions
Accessibility patterns testable requirements during early designAidan Tierney
Shift left for accessibility: get a head-start by identifying requirements early in the design/build cycle, with an aim to reducing defects and overall effort.
There’s a digital design methodology gaining steam that you've likely never heard of, but that could make a big difference in your API design being clean, intuitive, and effortlessly usable for devs who use it. It’s called object-oriented user experience (OOUX).
OOUX is a design power tool that helps us define usable, consistent products that naturally align with end users’ mental models. Similar to its namesake, object-oriented programming, it asks us to define the objects in the real-world problem domain and design the information and relationships in each object before designing how the user might manipulate them. The highly structured nature of OOUX means it directly contributes to clean data modeling and highly portable systems that translate well to exposure via API. It's a powerful tool and it pays dividends fast.
In this session, you’ll get a high-level overview of what OOUX is and why it’s a game-changer, a discussion of the parallels and complementary concerns between OOUX and API design, and an idea of how API design planning could be represented in an OOUX data model.
Presentation originally given at THAT Conference 2021
Pointer Events Working Group update / TPAC 2023 / Patrick H. LaukePatrick Lauke
Update about Pointer Events Level 3 work for the upcoming W3C Technical Plenary and Advisory Committee (TPAC) 2023 in Seville
https://www.youtube.com/watch?v=r0spZl1qaa0
https://w3c.github.io/pointerevents/
https://www.w3.org/TR/pointerevents/
https://www.w3.org/2023/09/TPAC/
https://patrickhlauke.github.io/touch/w3c_tpac2023_pewg/
Cross-posted from https://www.w3.org/2023/09/TPAC/group-updates.html#pointer-events
This was a 1-hour BPMN Intro/Primer webinar I presented at ASPE. Just to be clear, I design/develop and teach classes for ASPE ("Modeling Processes using BPMN" being one of those classes), so one of goals was to tease audiences into wanting to learn more(and attending my class:-). Beyond that, the main goal was to share useful/interesting information and to ignite questions and curiosity about this important topic. Let me know what you think. Thanks, Razvan:-)
CSUN 2018 Analyzing and Extending WCAG Beyond 3 DigitsBill Tyler
Slide deck from Bill Tyler's presentation of the Benefits of Analyzing & Extending WCAG 2.0 Beyond Three Digits from CSUN 2018 Conference (Friday, March 23, 2017)
WAI-ARIA An introduction to Accessible Rich Internet Applications / CSS Minsk...Patrick Lauke
Vanilla HTML is limiting and boring. Our clients demand highly engaging and interactive web experiences. And wouldn’t you know, with just a bit of HTML and JavaScript we can craft amazing custom controls, widgets and effects that go far beyond the confines of traditional static markup. But how can we ensure that these custom experiences are both understandable and usable for people with disabilities, and in particular those using assistive technologies such as screen readers?
In this talk, we will look at the basics of making some common custom-built components accessible - covering how browsers and assistive technologies interact, the limitations of HTML, and how ARIA can help make interactive experiences more accessible. In addition, we will explore some of the recent additions in ARIA 1.1, as well as some particular challenges when it comes to traditional ARIA patterns and assistive technologies on mobile/tablet/touch devices.
Evergreen slidedeck at https://patrickhlauke.github.io/aria/presentation/ / https://github.com/patrickhlauke/aria/
WAI-ARIA An introduction to Accessible Rich Internet Applications / JavaScrip...Patrick Lauke
Vanilla HTML is limiting and boring. Our clients demand highly engaging and interactive web experiences. And wouldn’t you know, with just a bit of HTML and JavaScript we can craft amazing custom controls, widgets and effects that go far beyond the confines of traditional static markup. But how can we ensure that these custom experiences are both understandable and usable for people with disabilities, and in particular those using assistive technologies such as screen readers?
In this talk, we will look at the basics of making some common custom-built components accessible - covering how browsers and assistive technologies interact, the limitations of HTML, and how ARIA can help make interactive experiences more accessible. In addition, we will explore some of the recent additions in ARIA 1.1, as well as some particular challenges when it comes to traditional ARIA patterns and assistive technologies on mobile/tablet/touch devices.
Evergreen slidedeck at https://patrickhlauke.github.io/aria/presentation/ / https://github.com/patrickhlauke/aria/
This presentation for Inclusive Design 24 (#ID24) explores how to create accessible, usable "floating" labels. Floating labels are where the label moves above form controls based on user interaction.
Too much accessibility - good intentions, badly implemented / Public Sector F...Patrick Lauke
HTML offers many features and attributes that can make your sites more accessible...but only if they're used wisely. Can there really be "too much accessibility"?
Audio recording: https://archive.org/details/Psf8August2007.PatrickH.Lauke-TooMuchAccessibilityGoodIntentions
Accessibility patterns testable requirements during early designAidan Tierney
Shift left for accessibility: get a head-start by identifying requirements early in the design/build cycle, with an aim to reducing defects and overall effort.
There’s a digital design methodology gaining steam that you've likely never heard of, but that could make a big difference in your API design being clean, intuitive, and effortlessly usable for devs who use it. It’s called object-oriented user experience (OOUX).
OOUX is a design power tool that helps us define usable, consistent products that naturally align with end users’ mental models. Similar to its namesake, object-oriented programming, it asks us to define the objects in the real-world problem domain and design the information and relationships in each object before designing how the user might manipulate them. The highly structured nature of OOUX means it directly contributes to clean data modeling and highly portable systems that translate well to exposure via API. It's a powerful tool and it pays dividends fast.
In this session, you’ll get a high-level overview of what OOUX is and why it’s a game-changer, a discussion of the parallels and complementary concerns between OOUX and API design, and an idea of how API design planning could be represented in an OOUX data model.
Presentation originally given at THAT Conference 2021
Pointer Events Working Group update / TPAC 2023 / Patrick H. LaukePatrick Lauke
Update about Pointer Events Level 3 work for the upcoming W3C Technical Plenary and Advisory Committee (TPAC) 2023 in Seville
https://www.youtube.com/watch?v=r0spZl1qaa0
https://w3c.github.io/pointerevents/
https://www.w3.org/TR/pointerevents/
https://www.w3.org/2023/09/TPAC/
https://patrickhlauke.github.io/touch/w3c_tpac2023_pewg/
Cross-posted from https://www.w3.org/2023/09/TPAC/group-updates.html#pointer-events
Implementing Web Standards across the institution: trials and tribulations of...Patrick Lauke
Patrick H. Lauke - Implementing Web Standards across the institution: trials and tribulations of a redesign / Institutional Web Management Workshop IWMW / Birmingham / 28 July 2004
Geolinking content - experiments in connecting virtual and physical places / ...Patrick Lauke
Patrick H. Lauke: Geolinking content - experiments in connecting virtual and physical places / Institutional Web Management Workshop IWMW / York / 16 July 2007
All change for WCAG 2.0 - what you need to know about the new accessibility g...Patrick Lauke
Patrick H. Lauke: All change for WCAG 2.0 - what you need to know about the new accessibility guidelines / Manchester Digital Development Agency MDDA / 24 March 2009
Ian Lloyd/Patrick H. Lauke: Accessified - practical accessibility fixes any w...Patrick Lauke
Ian Lloyd/Patrick H. Lauke: Accessified - practical accessibility fixes any web developer can use / South By Southwest SXSW / Austin, Texas, 11 March 2007
WAI-ARIA An introduction to Accessible Rich Internet Applications / AccessU 2018Patrick Lauke
Vanilla HTML is limiting and boring. Our clients demand highly engaging and interactive web experiences. And wouldn’t you know, with just a bit of HTML and JavaScript we can craft amazing custom controls, widgets and effects that go far beyond the confines of traditional static markup. But how can we ensure that these custom experiences are both understandable and usable for people with disabilities, and in particular those using assistive technologies such as screen readers?
In this talk, we will look at the basics of making some common custom-built components accessible - covering how browsers and assistive technologies interact, the limitations of HTML, and how ARIA can help make interactive experiences more accessible. In addition, we will explore some of the recent additions in ARIA 1.1, as well as some particular challenges when it comes to traditional ARIA patterns and assistive technologies on mobile/tablet/touch devices.
Evergreen slidedeck at https://patrickhlauke.github.io/aria/presentation/ / https://github.com/patrickhlauke/aria/
Getting touchy - an introduction to touch and pointer events / Frontend NE / ...Patrick Lauke
Beyond smartphones and tablets, touchscreens are finding their way into laptops and even desktop computers. With hardware support for touch becoming increasingly ubiquitous, it's time to explore what new possibilities are available to developers. This session will cover the basics of handling touch events - from making sure simple single-tap interactions are as responsive as possible, all the way to examples of full multitouch, gesture-enabled elements.
Getting touchy - an introduction to touch and pointer events (1 day workshop)...Patrick Lauke
Beyond smartphones and tablets, touchscreens are finding their way into laptops and even desktop computers. With hardware support for touch becoming increasingly ubiquitous, it's time to explore what new possibilities are available to developers. This session will cover the basics of handling touch events - from making sure simple single-tap interactions are as responsive as possible, all the way to examples of full multitouch, gesture-enabled elements.
Getting touchy - an introduction to touch and pointer events / TPAC 2016 / Li...Patrick Lauke
Beyond smartphones and tablets, touchscreens are finding their way into laptops and even desktop computers. With hardware support for touch becoming increasingly ubiquitous, it's time to explore what new possibilities are available to developers. This session will cover the basics of handling touch events - from making sure simple single-tap interactions are as responsive as possible, all the way to examples of full multitouch, gesture-enabled elements.
Getting touchy - an introduction to touch and pointer events (1 day workshop)...Patrick Lauke
Beyond smartphones and tablets, touchscreens are finding their way into laptops and even desktop computers. With hardware support for touch becoming increasingly ubiquitous, it's time to explore what new possibilities are available to developers. This session will cover the basics of handling touch events - from making sure simple single-tap interactions are as responsive as possible, all the way to examples of full multitouch, gesture-enabled elements.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Designing Great Products: The Power of Design and Leadership by Chief Designe...
These (still) aren't the SCs you're looking for ... (mis)adventures in WCAG 2.x interpretation and audits / #a11yTO / 19 October 2023
1. These (still) aren't the SCs you're looking for …
(mis)adventures in WCAG 2.x interpretation and audits
Patrick H. Lauke / a11yTO / 19 October 2023
2. about me …
▪ principal accessibility specialist at TetraLogical
▪ previously at The Paciello Group (now TPGi)
▪ occasional W3C AGWG member
▪ WCAG trash panda
3. déjà vu?
you may have already seen an earlier version of this talk …
even years later, the same question still bubbles up
(on mailing lists, a11ySlack, mastodon, …)
6. far too often, auditors clearly
dislike something, and look for
a justification to fail it …
and I get it … sometimes it's just to show how smart we are
7. overstep the boundaries of
WCAG SCs
claim something has to be fixed/changed "to pass WCAG"
when it normatively doesn't
8.
9. we are not lawyers (or judges)
but our audits and evaluations often have some legal dimension to them.
▪ evaluations should be as objective as possible
▪ evaluations should be consistent
… of course, this is easier said than done
10. WCAG is built on the idea that
success criteria can be
evaluated clearly, unambiguously
and consistently…
… but that's not always the case
11. with WCAG 2.2 we now have
9 more SCs!
… just more potential for confusion and misinterpretation?
13. WCAG success criteria are often
misunderstood and/or
misinterpreted
leads to wrong, or at least inconsistent, error reporting
14.
15. 2.4.6 Headings and Labels (AA)
Headings and labels describe topic or purpose.
this doesn't mandate the use of headings and labels … only that if a
page uses headings and labels, they must be descriptive.
it also doesn't mandate that headings and labels be correctly marked-up -
that's the job of 1.3.1 Info and Relationships and (where it affects
"accessible name" of controls) 4.1.2 Name, Role, Value .
lastly, if labels aren't there, it's a 3.3.2 Labels or Instructions problem.
“
17. 3.3.2 Labels or Instructions (A)
Labels or instructions are provided when content requires user
input.
again, this doesn't mandate that labels be marked-up as <label> and
properly associated with form controls - that's covered by
1.3.1 Info and Relationships and (where it affects "accessible name" of
controls) 4.1.2 Name, Role, Value .
“
18. <input type="text">
▪ passes 2.4.6 Headings and Labels
▪ fails 3.3.2 Labels or Instructions
▪ fails 4.1.2 Name, Role, Value
19. <p>First name</p>
<input type="text">
▪ passes 2.4.6 Headings and Labels
▪ passes 3.3.2 Labels or Instructions
▪ fails 1.3.1 Info and Relationships
▪ fails 2.5.3 Label in Name
▪ fails 4.1.2 Name, Role, Value
20. <p>First name</p>
<input type="text" aria-label="First name" >
▪ passes 2.4.6 Headings and Labels
▪ passes 3.3.2 Labels or Instructions
▪ passes 2.5.3 Label in Name
▪ passes 4.1.2 Name, Role, Value
▪ passes (arguably) 1.3.1 Info and Relationships
21. 2.1.1 Keyboard (A)
All functionality of the content is operable through a keyboard
interface […]
doesn't say anything about which keys are needed to operate
controls/functionality
“
22. <a href="#" onclick="…" role="button">fake button</a>
▪ passes 2.1.1 Keyboard
even though it doesn't respond to SPACE like real button would
23. <a href="#" role="button">Activate using 'b'</a>
.addEventListener('keypress', function(e) {
if (e.key == 'b') { /* do something */ }
})
▪ passes 2.1.1 Keyboard
even though it can only be triggered using the letter b
24. 1.3.3 Sensory Characteristics (A)
Instructions provided for understanding and operating content do
not rely solely on sensory characteristics of components such as
shape, color, size, visual location, orientation, or sound.
this only relates specifically to instructions … and not whether or not
sensory characteristics are used for content - this is covered by other SCs,
like 1.4.1 Use of Color or even 1.1.1 Non-Text Content .
Fixes for Understanding 1.3.3 Sensory Characteristics #767
“
25. example: buttons with shapes or colours
▪ fail 1.1.1 Non-text Content (if there's no hidden text / accessible name)
▪ fail 1.4.1 Use of Color for the second set
▪ fail 4.1.2 Name, Role, Value (if there's no accessible name)
▪ pass 1.3.3 Sensory Characteristics as there are no instructions
26. example: buttons with shapes or colours
▪ fail 1.1.1 Non-text Content (if there's no hidden text / accessible name)
▪ fail 1.4.1 Use of Color for the second set
▪ fail 4.1.2 Name, Role, Value (if there's no accessible name)
▪ fail 1.3.3 Sensory Characteristics as there are instructions
28. 1.4.1 Use of Color (A)
Color is not used as the only visual means of conveying
information, indicating an action, prompting a response, or
distinguishing a visual element.
both lines contain a link. but only in the first line is colour used.
the first cases fails 1.4.1 Use of Color, but the second passes
auditors pondering failing the previous example for not using colour …
“
29. 1.3.1 Info and Relationships (A)
Information, structure, and relationships conveyed through
presentation can be programmatically determined or are available
in text.
auditors pondering failing the previous example for not conveying things
through presentation …
“
32. cascade of fail
<a href="…"> <img src="…"> </a>
fails multiple criteria , in sequence:
▪ the image itself fails 1.1.1 Non-text content
▪ as a result, link lacks accessible name and fails 4.1.2 Name, Role, Value
▪ arguably, link also fails 2.4.4 Link Purpose (In Context)
need consistency in how this is reported
34. 3.1.1 Language of Page (A)
The default human language of each Web page can be
programmatically determined.
3.1.2 Language of Parts (AA)
The human language of each passage or phrase in the content can
be programmatically determined […]
if you can't determine the language of the page, then you also can't
determine the language of each passage or phrase.
fail one, and you automatically fail the other …
“
“
35. minimum and enhanced
▪ 1.4.3 Contrast (Minimum) → 1.4.6 Contrast (Enhanced)
▪ 2.4.11 Focus Not Obscured (Minimum) → 2.4.12 Focus Not Obscured
(Enhanced)
▪ 2.5.8 Target Size (Minimum) → 2.5.5 Target Size (Enhanced)
▪ 3.3.8 Accessible Authentication (Minimum) → 3.3.9 Accessible
Authentication (Enhanced)
fail one, and you automatically fail the other …
need consistency in how this is reported (if you care about AAA)
36. auditor education / consistency
problems …
internal training and resources can help
37. more problematic are issues caused by
WCAG SCs that are vague ,
incomplete or otherwise
lacking
38. WCAG 2.x is not perfect
written by well-meaning, but fallible humans …
40. subjective interpretation?
▪ 1.1.1 All non-text content […] has a text alternative that serves the
equivalent purpose - but what's the purpose?
▪ 1.2.2 Captions are provided … - but do these captions need to be
exact, identify speakers, etc.?
▪ 1.3.1 Information, structure, and relationships conveyed through
presentation […] - where do you draw the line?
▪ 2.4.6 Headings and labels describe topic or purpose - what's
"descriptive" exactly?
41. what is a list?
<a href="/">home</a>
<a href="…">products</a>
<a href="…">contact</a>
do you fail 1.3.1 Info and Relationships because they didn't wrap this in a
<ul> , even if this isn't conveyed through presentation ?
if you look hard enough, it's lists all the way down
turtles
42. WCAG has a few strange
omissions , ambiguities ,
exemptions …
43. 2.4.4 Link Purpose (In Context) (AA)
The purpose of each link can be determined from the link text
alone or from the link text together with its programmatically
determined link context […]
what counts as "programmatically determined link context"? do preceding
headings count?
“
44. "I think what the
founding fathers/mothers
of WCAG meant to say …"
48. beyond the need for subjective interpretation
WCAG success criteria can have
odd loopholes …
49. 2.4.7 Focus Visible (AA)
Any keyboard operable user interface has a mode of operation
where the keyboard focus indicator is visible.
but what does visible mean? it's not normatively defined…
“
51. WCAG 2.1 decided not to modify
2.0 SCs, patched loopholes
with more SCs
but these new SCs also ended up having some loopholes
52. 1.4.11 Non-text Contrast (AA)
The visual presentation of the following have a contrast ratio of at
least 3:1 against adjacent color(s):
▪ User Interface Components: Visual information required to identify
user interface components and states […]
▪ Graphical Objects: […]
“
53. much better … that pixel has a 3:1 contrast ratio now
55. … but we'll fix focus WCAG 2.2!
2.4.13 Focus Appearance (Level AAA)
Only at Level AAA … where success criteria go to die …
2.4.11 Focus Appearance (Minimum) (Level AA)
2.4.12 Focus Appearance (Enhanced) (Level AAA)
56. 2.4.11 Focus Not Obscured (Minimum) (AA)
New in WCAG 2.2
When a user interface component receives keyboard focus, the
component is not entirely hidden due to author-created content.
“
57. classic example: sticky header …
this passes 2.4.11 Focus Not Obscured (Minimum) (AA)
but how far can we take the "not entirely hidden" aspect?
58. arguably … not entirely hidden
(some disagree whether or not focus indicator is part of the user interface component)
59. 1.4.1 Use of Color (A)
Color is not used as the only visual means of
conveying information , indicating an action, prompting a
response, or distinguishing a visual element.
“
60. if your focus indication just changes colour, 1.4.1 likely applies
If content is conveyed through the use of colors that differ not only
in their hue, but that also have a significant difference in lightness,
then this counts as an additional visual distinction, as long as the
difference in relative luminance between the colors leads to a
contrast ratio of 3:1 or greater.
used to be buried in technique F73, now in understanding for 1.4.1 (#1500)
“
61. beware: if you look hard enough, everything is a use of color .
is it essential for conveying information or just eye candy?
62.
63. SCs that are overly specific …
and then end up only applying to very specific cases
64. 1.4.10 Reflow (AA)
Content can be presented without loss of information or
functionality, and without requiring scrolling in two dimensions for:
▪ Vertical scrolling content at a width equivalent to 320 CSS pixels
▪ Horizontal scrolling content at a height equivalent to 256 CSS
pixels
[…]
to help low vision users. should ideally have been "use responsive design"
instead, it was watered down to 400% zoom on a 1280×1024 display …
and now only normatively applies at those exact values
“
65. 1.4.12 Text Spacing (AA)
In content implemented using markup languages that support the
following text style properties, no loss of content or functionality
occurs by setting all of the following […]:
▪ Line height (line spacing) to at least 1.5 times the font size
▪ Spacing following paragraphs to at least 2 times the font size
▪ Letter spacing (tracking) to at least 0.12 times the font size
▪ Word spacing to at least 0.16 times the font size
[…]
only those exact values and over
do you test the "at least" part here, and up to which values?
what if user changes just a few (e.g. just letter spacing)
“
66. this bookmarklet didn't work to change text styles … can I fail this?
no you can't … the SC doesn't care if a user can or can't change the
metrics, or if a particular bookmarklet or method doesn't work.
only that if the metrics are indeed changed, then content doesn't become
unreadable or unusable.
Understanding 1.4.12: clarify the intent and author responsibility #1687
“
67. 3.3.8 Accessible Authentication (Minimum)
(AA)
New in WCAG 2.2
A cognitive function test (such as remembering a password or
solving a puzzle) is not required for any step
in an authentication process […]
“
70. 2.5.8 Target Size (Minimum) (AA)
New in WCAG 2.2
The size of the target for pointer inputs is at least 24 by 24 CSS
pixels […]
at first glance, the SC defines a minimum target size (it says so in the title)
“
71. 2.5.8 Target Size (Minimum) (AA)
New in WCAG 2.2
The size of the target for pointer inputs is at least 24 by 24 CSS
pixels except where:
▪ Spacing: Undersized targets (those less than 24 by 24 CSS pixels)
are positioned so that if a 24 CSS pixel diameter circle is centered
on the bounding box of each, the circles do not intersect another
target or the circle for another undersized target
…
the first exception turns this into Target Spacing (Minimum)
“
73. 3.2.6 Consistent Help (A)
New in WCAG 2.2
If a Web page contains any of the following help mechanisms, and
those mechanisms are repeated on multiple Web pages within a
set of Web pages, they occur in
the same order relative to other page content , unless a change
is initiated by the user […]:
the understanding document goes in depth listing and explaining help
mechanisms, but the SC doesn't actually require any help mechanisms to
be present at all …
“
74. relative order here means just means a consistent "focus/reading order"
"If the help item is visually in a different location, but in the same
serial order, that is not helpful from a user's point of view, but it
would not fail this criterion."
“
75.
76. even after years of auditing,
I sometimes have weird
moments of realisation
seeing SCs, and what they say/apply to, in a new light
82. no weighting given to impact or
frequency of a particular fail,
or how bad a failure is off the
mark
sometime, you just want to say something's a minor or
soft fail , but distinction doesn't exist
83. fail a single SC and you can't
really claim to be conformant
84. loopholes , omissions and
subjective requirements can
and will be exploited
auditors aren't the only ones who try to find these gaps …
88. join my WCAG Trash Panda Web Ring
github.com/w3c/wcag/issues?q=is%3Aopen%20patrickhlauke
to look for discussions and pending clarifications
89. frustration: most efforts has been going towards new WCAG 2.2 SCs
rather than fixing what's broken in 2.0/2.1
90. w3.org/TR/wcag-3.0 … but still very early days
and it will be quite some time before legislation references 3.0 once it's actually a ratified recommendation …
94. “but unless it's reported as a
WCAG failure
the client won't change it”
then you have more fundamental problem …
95. as auditor, you do your client a
disservice by not making clear
what is and isn't a
normative failure
what happens when a clued-up client rightly challenges your
claim? all your other results lose credibility!
96. be conservative in your
pass / fail assessments
document your hesitation, clearly state when something's
"more of a suggestion" than a hard failure