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...
These (still) aren't the SCs you're looking for ... (mis)adventures in WCAG 2...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 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...
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/
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
Beginner’s Guide to WCAG 2.0 – Know Your Way Around Web Accessibility RulesJohn McNabb
Need to settle an argument on when alt text is required? Ever wonder how text size relates to colour contrast? When is link text good enough? Look it up in the official reference – WCAG 2! Don’t rely on opinions – defend your findings by pointing to actual Success Criteria. Learn when to fall back on a Guideline, or even a Principle.
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/
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 (still) aren't the SCs you're looking for ... (mis)adventures in WCAG 2...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 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...
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/
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
Beginner’s Guide to WCAG 2.0 – Know Your Way Around Web Accessibility RulesJohn McNabb
Need to settle an argument on when alt text is required? Ever wonder how text size relates to colour contrast? When is link text good enough? Look it up in the official reference – WCAG 2! Don’t rely on opinions – defend your findings by pointing to actual Success Criteria. Learn when to fall back on a Guideline, or even a Principle.
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.
WCAG2 Guidelines and Cognitive Impairment a11y ldn 2011Graham Armfield
A collection of some of the WCAG2.0 accessibility guidelines that relate to those with cognitive impairments. Note: this is a selection - not a full list.
BDD (Behavior-driven development), also known as ATDD (Acceptance test–driven development) is a software development process that helps Agile teams design, develop, test and deliver software efficiently, it's about how to implement agile acceptance testing and binding business requirements to code. BDD helps to bridge the communication gap between stakeholders and implementation teams, build quality into software from the start, design, develop and deliver systems fit for purpose. SpecFlow is the official tool to implement BDD on the .NET platform.
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.
Ruby on Rails from the other side of the tracksinfovore
A 20-minute chat at the London Ruby User Group (from August 2006) about how to get client-side-developers, and even designers, involved in the process of making applications with Rails - helping them get involved in the templating process. It then diverges into a client-side perspective on Rails, looking in particular at issues around Javascript and Ajax, and XHTML testing. Because of its slide-heavy nature, it’s fairly self explanatory, but obviously you’ll miss out on some of the discussion around the talk (which was excellent).
No more Three Tier - A path to a better code for Cloud and AzureMarco Parenzan
Three Tier is no more a model for Cloud and in general Scalable Web Applications. Scaffolding from SQL Database is, sure, the worst way to do. A road to do this is changing modeling activity, from scaffolded DB model to Command/DTO model, through ViewModel pattern. Command and DTOs are pillars of CQRS model.
Scaling Plugins in Critical Systems - Jon MortAtlassian
So you built a plugin. But will it succeed at scale? During this session, we’ll walk through the five easiest ways to build plugins. Along the way, we'll explore techniques that will help you develop quality extensions that can scale with your company.
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:-)
Streamlining the Client's Workflows (in Joomla)Randy Carey
When our client or their staff login to manage their site and content, they have specific tasks in mind. This presentation demonstrates how we can identify these tasks and develop each into an intuitive set of streamlined steps. We will be examining ways to reduce the number of steps, reduce clutter, and make the entire process intuitive for our client.
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.
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 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.
WCAG2 Guidelines and Cognitive Impairment a11y ldn 2011Graham Armfield
A collection of some of the WCAG2.0 accessibility guidelines that relate to those with cognitive impairments. Note: this is a selection - not a full list.
BDD (Behavior-driven development), also known as ATDD (Acceptance test–driven development) is a software development process that helps Agile teams design, develop, test and deliver software efficiently, it's about how to implement agile acceptance testing and binding business requirements to code. BDD helps to bridge the communication gap between stakeholders and implementation teams, build quality into software from the start, design, develop and deliver systems fit for purpose. SpecFlow is the official tool to implement BDD on the .NET platform.
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.
Ruby on Rails from the other side of the tracksinfovore
A 20-minute chat at the London Ruby User Group (from August 2006) about how to get client-side-developers, and even designers, involved in the process of making applications with Rails - helping them get involved in the templating process. It then diverges into a client-side perspective on Rails, looking in particular at issues around Javascript and Ajax, and XHTML testing. Because of its slide-heavy nature, it’s fairly self explanatory, but obviously you’ll miss out on some of the discussion around the talk (which was excellent).
No more Three Tier - A path to a better code for Cloud and AzureMarco Parenzan
Three Tier is no more a model for Cloud and in general Scalable Web Applications. Scaffolding from SQL Database is, sure, the worst way to do. A road to do this is changing modeling activity, from scaffolded DB model to Command/DTO model, through ViewModel pattern. Command and DTOs are pillars of CQRS model.
Scaling Plugins in Critical Systems - Jon MortAtlassian
So you built a plugin. But will it succeed at scale? During this session, we’ll walk through the five easiest ways to build plugins. Along the way, we'll explore techniques that will help you develop quality extensions that can scale with your company.
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:-)
Streamlining the Client's Workflows (in Joomla)Randy Carey
When our client or their staff login to manage their site and content, they have specific tasks in mind. This presentation demonstrates how we can identify these tasks and develop each into an intuitive set of streamlined steps. We will be examining ways to reduce the number of steps, reduce clutter, and make the entire process intuitive for our client.
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.
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.
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.
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.
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.
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.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Unsubscribed: Combat Subscription Fatigue With a Membership Mentality by Head...
These aren't the SCs you're looking for ... (mis)adventures in WCAG 2.x interpretation and audits / a11yTO / 24 October 2019
1. These aren't the SCs you're looking for...
(mis)adventures in WCAG 2.x interpretation and audits
Patrick H. Lauke / a11yTO / Toronto / 24 October 2019
2. about me...
▪ principal accessibility engineer at The Paciello Group
▪ occasional W3C AGWG member
▪ WCAG trash panda
▪ known for my rants, not my brevity...
3. what really grinds my gears...
▪ doing accessibility audits
▪ advising and reviewing the work of other engineers doing audits
▪ being active on accessibility mailing lists (WebAIM, W3C, ...)
...and far too often, the same question always bubbles up
7. far too often, auditors clearly
dislike something, and look for
a justification to fail it ...
8. overstep the boundaries of
WCAG SCs
claim something has to be fixed/changed "to pass WCAG"
when it normatively doesn't
9.
10. 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
11. WCAG is built on the idea that
success criteria can be
evaluated clearly, unambiguously
and consistently...
...but that's not always the case
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. <p class="heading1">I'm a heading</p>
<p>First name</p>
<input type="text">
passes 2.4.6 Headings and Labels
fails 1.3.1 Info and Relationships
fails 4.1.2 Name, Role, Value
18. 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 .
“
20. 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
“
21. <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
22. 3.2.3 Consistent Navigation (AA)
Navigational mechanisms that are repeated on multiple Web pages
within a set of Web pages occur in the same relative order each
time they are repeated, unless a change is initiated by the user.
this only normatively requires the relative order of navigation (in relation
to other page components) to be consistent - nothing more.
doesn't mandate that navigation should be same, work the same, etc
across pages
“
23. 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 - this is covered by other SCs, like
1.4.1 Use of Color or even 1.1.1 Non-Text Content .
“
25. cascade of fail
<a href="..."> <img src="..."> </a>
fails multiple criteria ...need to consistently report these, but easy to
forget and tedious to do...
26. "speculative" cascade of fail
<div>Read more</div>
fails 2.1.1 Keyboard ... but also 4.1.2 Name, Role, Value
and if it acts as a link, also 2.4.4 Link Purpose (In Context) ?
27. auditor education / consistency
problems...
internal training and resources can help
28. more problematic are issues caused by
WCAG SCs that are vague ,
incomplete or otherwise
lacking
29. WCAG 2.x is not perfect
written by well-meaning, but fallible humans (after all)
31. subjective interpretation?
▪ 1.1.1 All non-text content [...] has a text alternative that serves the
equivalent purpose - but what's the purpose?
▪ 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?
32. <div class="footer"> ... </div>
do you fail 1.3.1 Info and Relationships because they don't use
<footer> or role="contentinfo" ? is it not clear from context?
<a href="/">home</p>
<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 when styled as an inline set of three links?
33. "I think what the
founding fathers of WCAG
meant to say..."
37. beyond the need for subjective interpretation
WCAG success criteria can have
odd loopholes ...
38. 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...
“
40. 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
41. 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: [...]
“
43. 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):
[...]
note that this only applies normatively to adjacent colors ... doesn't
apply to contrast between different colors used for states of the same
control
“
47. 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.
but there's an escape clause in the non-normative F73 failure technique
that tries to redefine, by the backdoor, what "color" means...
“
48. F73: Failure of Success Criterion
1.4.1 due to creating links that are
not visually evident without color
vision
Note 1: Red and Pink are the same color (hue) but they have
different lightness (which is not color ). So red and pink would pass
the requirement for "not distinguished by color (hue) alone" since
they differ by lightness (which is not color) - as long as the
difference in lightness (contrast) is 3:1 or greater
WAT?
“
49.
50. ...but we'll fix it in WCAG 2.2 (?)
2.4.11 Focus Visible Enhanced (Level AA)
51. SCs that are overly specific...
and then end up only applying to very specific cases
52. 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
[...]
meant to help low vision users that require up to 400% zoom, but ended up
too specific - only normatively applies at those exact values
“
54. 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 and by changing no other style
property:
▪ 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 - if content breaks/stops working at line
height of 1.4 instead of 1.5, not a failure...
“
55. use JavaScript to detect line height and fix only if 1.5 or higher
codepen.io/patrickhlauke/pen/jgVGOp
56. even after years of auditing,
I sometimes have weird
moments of realisation
seeing SCs, and what they say/apply to, in a new light
62. 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
63. fail a single SC and you can't
really claim to be conformant
64. loopholes , omissions and
subjective requirements can
and will be exploited
auditors aren't the only ones who try to find these gaps...
77. 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...
78. be conservative in your
pass / fail assessments
document your hesitation, clearly state when something's
"more of a suggestion" than a hard failure
80. join my WCAG Trash Panda Webring :
▪ Fixes to WCAG 2.1 Understanding 2.4.6 and 3.3.2 #612
▪ Edits to 135 failure #890
▪ Proposal for color and contrast (1.3.1, 1.4.1, 1.4.3., 1.4.6, 1.4.11) #901
▪ Should role button and input button be a WCAG fail if cannot be activated
using space? #857
▪ Does SC 1.4.11 require comparing focused and non-focused states #541
▪ Ambiguity in understanding for 1.3.3 sensory characteristics #750
▪ Bad/incomplete example for Understanding 3.3.2 #755
81. ▪ "at least" should be "at most" in WCAG 2.1 SC 1.4.12 #635
▪ Expand 1.4.10 to apply 'down to' instead of 'at' #698
▪ 2.4.7 Focus Visible - what counts as "visible"? #302
▪ Must the tooltip of icons match the accessible name? (for "Label in Name",
SC 2.5.3) #891
▪ Keyboard operation with assistive technology: 2.1.1 or 4.1.2? #878
▪ Can title on links (e.g. linked icon) as sole source of accName ever pass
1.1.1? #867 (side discussion about high contrast mode and reponsibility of
user agents)
▪ Error of the User Agents part of WCAG or not #866
82. ▪ 1.4.5 / 1.4.9 Image of Text and <text> inside SVGs #773
▪ Revisiting imbalance between 1.2.4 Captions (Live) (AA) and 1.2.9 Audio-
only (Live) (AAA) #795
▪ ARIA in HTML conformance to conform WCAG ? #717
▪ Failure technique F94 (1.4.4 resize text): remove "1280 pixels wide" step in
test procedure #704
▪ Contrast Ratio Math and Related Visual Issues #695
▪ Include font weight for color contrast tests #665
▪ Accessible P Tag Usage (WebAim)
83. ▪ Must the tooltip of icons match the accessible name? (for "Label in Name",
SC 2.5.3) #891
▪ Are Reflow, Text Size and Orientation cumulative? #391
▪ What does "support the following text style properties" mean (1.4.12)?
#884
▪ Does using the placeholder with a value alone pass 3.3.2 Labels or
Instructions? #864
▪ Using color ALONE as focus indicator #757
▪ New SC for keyboard operation? #872