00:00:08:12 00:00:10:14 - [Kari] Thank you for joining us, 00:00:10:14 00:00:12:22 we'll get started here in just a moment. 00:00:12:22 00:00:15:01 Just wanna give a second for every to join. 00:00:47:18 00:00:51:03 All right, good morning, good afternoon. 00:00:51:03 00:00:52:01 My name's Kari. 00:00:52:01 00:00:55:19 I am the Manager of Sales Development here at TPG. 00:00:57:24 00:01:00:06 I just wanna thank everyone for joining us today 00:01:00:06 00:01:02:18 for our webinar, going over our best practices 00:01:02:18 00:01:06:14 for structuring accessibility testing with Aaron Farber. 00:01:06:14 00:01:08:24 Just a few housekeeping items before I pass it on 00:01:08:24 00:01:11:06 and let Aaron introduce himself. 00:01:11:06 00:01:14:03 The session is being recorded and we'll email everyone 00:01:14:03 00:01:16:02 the recording after the event. 00:01:16:02 00:01:17:12 We have captions available, 00:01:17:12 00:01:20:04 so feel free to use them as needed. 00:01:20:04 00:01:23:03 And lastly, we will have time for a live Q&A. 00:01:23:03 00:01:25:13 So please use the Q&A box 00:01:25:13 00:01:27:17 and we'll answer as many of the questions as we can 00:01:27:17 00:01:29:05 at the end of the presentation. 00:01:31:04 00:01:34:14 Also if anyone needs any accessibility support, training, 00:01:34:14 00:01:35:22 usability testing, 00:01:35:22 00:01:38:08 we'll send out an email with a link to schedule time 00:01:38:08 00:01:42:25 to speak with one of our experts after the webinar as well. 00:01:42:25 00:01:45:08 Now with that, I'll let Aaron get started 00:01:45:08 00:01:47:11 and go ahead and introduce himself. 00:01:48:14 00:01:51:11 - Thank you, my name is Aaron Farber. 00:01:51:11 00:01:55:20 I am Senior Platform Consultant here at TPGi. 00:01:55:20 00:02:00:20 In this role I help organizations use the ARC platform 00:02:01:07 00:02:04:07 to manage their accessibility program. 00:02:04:07 00:02:08:14 And in this role I've worked with, in my whole career, 00:02:08:14 00:02:13:10 I've worked with organizations at all ends of the size 00:02:13:10 00:02:18:10 and spectrum, from small businesses 00:02:18:13 00:02:21:23 that are relying on WordPress or Shopify, 00:02:21:23 00:02:24:08 and may not have their own developers, 00:02:24:08 00:02:27:01 to the biggest brands in the world 00:02:27:01 00:02:32:01 with massive technical resources 00:02:33:17 00:02:36:17 to deliver custom complex applications. 00:02:36:17 00:02:38:24 And from these experiences 00:02:38:24 00:02:41:14 I'm gonna share some best practices today. 00:02:43:15 00:02:45:25 Okay, let's look at the agenda for today. 00:02:48:14 00:02:52:22 First of all, everyone before we get started, 00:02:52:22 00:02:57:22 I want for everyone to resolve to do one thing, 00:02:57:25 00:03:00:16 which is that today we're gonna learn many steps 00:03:00:16 00:03:03:14 to setting up an accessibility program. 00:03:03:14 00:03:08:14 Resolve to take one of these steps back to your organization 00:03:09:07 00:03:12:22 and incorporate it into a process. 00:03:14:17 00:03:19:16 So send that email to your colleagues, 00:03:21:17 00:03:25:01 try to experiment on a limited scale. 00:03:27:09 00:03:30:06 Some steps are bigger than others, but all of them 00:03:30:06 00:03:32:18 can be applied to your organization. 00:03:33:16 00:03:38:16 Okay, so first of all, let's introduce the topic. 00:03:38:20 00:03:41:08 Of course, without accessibility 00:03:41:08 00:03:43:22 disabled people are excluded from the economy. 00:03:46:04 00:03:47:21 It's really that simple. 00:03:47:21 00:03:52:01 And that's at the heart of everything that we do 00:03:52:01 00:03:57:01 here at TPGi and you do just by attending this session. 00:03:57:02 00:03:59:12 If everyone on this call understands 00:04:01:02 00:04:03:10 accessibility doesn't happen by accident. 00:04:05:15 00:04:07:16 If you've not considered accessibility, 00:04:07:16 00:04:09:13 something won't be accessible. 00:04:11:14 00:04:16:14 So accessibility occurs because of the leadership and effort 00:04:16:16 00:04:20:09 and organization of people like all of you here today. 00:04:20:09 00:04:21:17 So thank you for attending. 00:04:22:14 00:04:24:18 We're all gonna learn from each other today 00:04:25:21 00:04:28:25 and hopefully have plenty of time for questions at the end. 00:04:28:25 00:04:33:25 So accessibility is a requirement for disabled people 00:04:37:05 00:04:38:18 to be included in the economy, 00:04:38:18 00:04:42:07 yet accessibility benefits everyone. 00:04:42:07 00:04:45:05 Something we really became aware of during this, 00:04:46:07 00:04:48:15 once in a while unprecedented pandemic 00:04:48:15 00:04:52:12 when everyone was home bound and relying on technology, 00:04:52:12 00:04:56:23 accessibility really was a focal point. 00:04:56:23 00:05:01:23 Accessibility is a multifaceted topic 00:05:01:23 00:05:06:23 encompassing design, engineering, law, culture. 00:05:07:18 00:05:09:13 It's a complex challenge. 00:05:10:21 00:05:12:10 And an interesting Rubik's Cube 00:05:12:10 00:05:17:10 that I think is very exciting to be a part of here at TPGi. 00:05:18:17 00:05:20:18 And as you go about a organization, 00:05:20:18 00:05:24:19 I think you'll find a lot of fascinating intersection. 00:05:30:07 00:05:34:02 But accessibility is a mindset, it's ensuring everyone 00:05:34:02 00:05:38:09 has the same experience and derives the same value. 00:05:38:09 00:05:43:03 That ensure the fundamental principle of accessibility, 00:05:43:03 00:05:44:12 it's the same experience. 00:05:46:06 00:05:51:06 In my time implementing accessibility as a web developer, 00:05:52:13 00:05:55:22 as an administrator type, 00:05:55:22 00:05:59:05 I see that a large part of accessibility 00:05:59:05 00:06:02:03 is using your tools as they were intended, 00:06:02:03 00:06:07:03 which is to their fullest potential, I'll explain that. 00:06:07:04 00:06:09:23 When there are accessibility standards, 00:06:09:23 00:06:13:17 that is how something is intended to be used, 00:06:13:17 00:06:17:08 the output is testable, we have conditions to test it again. 00:06:19:22 00:06:23:24 When you're using your tools to this fullest potential, 00:06:23:24 00:06:28:24 there's a foundation to unlock unexpected benefits. 00:06:29:13 00:06:30:24 And that's something 00:06:30:24 00:06:32:24 I think is really important to consider. 00:06:35:21 00:06:39:10 On July 26th, that's on Tuesday 00:06:39:10 00:06:42:05 is National Disability Independence Day. 00:06:42:05 00:06:45:23 That celebrates the 32nd anniversary 00:06:45:23 00:06:48:06 of the Americans with Disability Act. 00:06:48:06 00:06:53:06 And it's a day to reflect and learn more about 00:06:53:06 00:06:55:03 just the disability movement. 00:06:56:00 00:06:59:23 But one thing that stands out to me as we approach this day, 00:07:01:13 00:07:04:18 accessibility expands the economy. 00:07:05:14 00:07:08:17 This day is to commemorate the ADA. 00:07:08:17 00:07:11:12 The ADA is justified by the Commerce Clause, 00:07:11:12 00:07:14:03 just as is the Civil Rights Act. 00:07:14:03 00:07:17:12 When a person can go to any business and expect to receive 00:07:17:12 00:07:19:02 the same experience. 00:07:19:02 00:07:22:07 So that facilitates commerce and trade. 00:07:22:07 00:07:25:17 So accessibility is fundamentally about 00:07:27:10 00:07:31:02 increasing the size of the economy, increasing commerce, 00:07:31:02 00:07:33:15 allowing more people to participate. 00:07:33:15 00:07:38:15 And it's important to have that mindset of thinking about 00:07:38:22 00:07:42:14 that positive, and we're talking about unlocking 00:07:44:09 00:07:47:01 unexpected benefits. 00:07:47:01 00:07:50:03 Consider one organization uploads receipts 00:07:50:03 00:07:51:20 and saves them that way. 00:07:51:20 00:07:56:04 Another organization saves pictures of receipts, 00:07:56:04 00:07:59:06 but attaches texts to those pictures. 00:07:59:06 00:08:01:24 And they have a way to now search all of their receipts. 00:08:01:24 00:08:04:16 You see that's a power being provided by 00:08:04:16 00:08:07:16 this accessibility mindset, 00:08:07:16 00:08:11:03 even if that's furthering a larger business objective. 00:08:12:11 00:08:16:17 So what we know and what I've really learned in this role 00:08:17:18 00:08:22:01 as platform consultant, is that when disabled people 00:08:22:01 00:08:25:13 encounter a hurdle in an online experience, 00:08:25:13 00:08:27:22 the source is not inaccessible code. 00:08:29:00 00:08:31:15 I mean, maybe in a superficial sense, 00:08:31:15 00:08:35:11 the source is the lack of an accessibility program. 00:08:35:11 00:08:37:09 The source of the issue 00:08:37:09 00:08:41:07 is the lack of defined steps and checkpoints 00:08:41:07 00:08:44:02 where accessibility is considered and tested. 00:08:47:08 00:08:50:09 So the objective today is to learn the steps 00:08:50:09 00:08:53:02 to creating an accessibility program. 00:08:53:02 00:08:57:10 And one thing to emphasize today is that each step 00:08:57:10 00:09:02:10 is a defined quantifiable action, each step is trackable. 00:09:02:20 00:09:06:02 Accessibility progress and results are always known 00:09:06:02 00:09:08:04 across the organization. 00:09:08:04 00:09:13:04 Accessibility is not subjective, it's actually objective. 00:09:15:16 00:09:16:20 It's attached to the law. 00:09:16:20 00:09:20:24 These are actual tests that things pass and fail there. 00:09:20:24 00:09:23:00 It's binary in a sense. 00:09:25:13 00:09:30:13 Now the ARC platform provides the tools and resources 00:09:30:17 00:09:34:03 to support every step of an accessibility program. 00:09:34:03 00:09:36:17 Every step that we talk about today. 00:09:38:14 00:09:42:18 So I'll note that about the ARC platform and I'm proud to, 00:09:44:12 00:09:46:15 but today is not all about ARC. 00:09:46:15 00:09:49:11 The lessons today are universal. 00:09:50:12 00:09:55:12 Today's steps are achievable outside of the ARC platform. 00:09:55:13 00:10:00:13 An organization can cobble together an accessibility program 00:10:00:14 00:10:02:11 from the sum of the internet. 00:10:03:15 00:10:05:19 I'd like to say the internet is undefeated. 00:10:08:03 00:10:11:16 So today we'll share solutions from the ARC platform. 00:10:11:16 00:10:14:12 I'll give you examples of how the ARC platform provides 00:10:14:12 00:10:19:12 a really beneficial way of conducting 00:10:20:04 00:10:22:20 that step of your accessibility program. 00:10:22:20 00:10:25:02 But then I'll also provide an alternative 00:10:25:02 00:10:27:13 that is open sourced and freely available. 00:10:27:13 00:10:31:20 And I will say that the ARC platform and Open Source 00:10:33:19 00:10:35:02 are not one to one. 00:10:35:02 00:10:38:10 I believe there are great advantages to the ARC platform, 00:10:38:10 00:10:41:04 but we'll let them speak for themselves today. 00:10:41:04 00:10:42:21 And I think it'll become clear, 00:10:42:21 00:10:44:23 especially during the Q&A session. 00:10:46:11 00:10:51:11 Now, the first steps to an accessibility program. 00:10:52:10 00:10:55:21 Well, the first step is the hardest step by far. 00:10:55:21 00:11:00:21 And again, it depends on the leadership and initiative 00:11:01:12 00:11:04:20 at times of people like you here on this call today. 00:11:04:20 00:11:06:08 And accessibility program 00:11:06:08 00:11:10:03 starts with self-awareness, self-reflection. 00:11:10:03 00:11:15:00 An organization creates a roadmap with formalized steps 00:11:15:00 00:11:18:01 and policies for their accessibility program. 00:11:19:12 00:11:23:03 For the roadmap, an organization must define 00:11:23:03 00:11:27:06 internal level of effort and the steps to undertake 00:11:27:06 00:11:30:00 as part of the accessibility program. 00:11:31:16 00:11:36:16 So when you're doing this stage, you have to consider 00:11:36:16 00:11:41:03 how your organization delivers its online experiences. 00:11:41:03 00:11:44:16 And there's something for everyone, 00:11:44:16 00:11:46:16 something can always be done. 00:11:46:16 00:11:50:06 Today we look at it from the standpoint 00:11:50:06 00:11:51:13 of a larger organization 00:11:51:13 00:11:54:06 delivering more complex applications. 00:11:54:06 00:11:57:10 But if you're an individual WordPress developer, 00:11:57:10 00:12:01:22 something like that, a step that you could define 00:12:01:22 00:12:04:13 is whenever you add a plugin to your site, 00:12:05:12 00:12:08:07 you will look at the reviews in the WordPress marketplace 00:12:08:07 00:12:11:11 and see what accessibility reviews have been said, 00:12:11:11 00:12:13:18 if anybody has any feedback about it. 00:12:13:18 00:12:15:19 Maybe you're non-technical yourself. 00:12:15:19 00:12:19:22 So these are again, steps that can be taken. 00:12:19:22 00:12:23:09 Now, when you're doing this step, 00:12:23:09 00:12:28:09 this initial planning of what your accessibility program 00:12:28:12 00:12:29:23 is going to resemble, 00:12:29:23 00:12:32:25 because again, these need to be defined steps 00:12:35:03 00:12:38:00 at specific checkpoints in your process 00:12:38:00 00:12:41:11 from design and development to deployment. 00:12:41:11 00:12:45:04 So consider the resources that can be allocated 00:12:45:04 00:12:46:16 to addressing accessibility 00:12:46:16 00:12:50:14 and already existing applications, and be realistic. 00:12:53:13 00:12:57:17 Now, when you're setting these initial planning steps, 00:12:57:17 00:13:00:23 as I said systems are greater than goals. 00:13:00:23 00:13:02:22 Honestly, that's a great life lesson. 00:13:02:22 00:13:06:03 Something I've learned in my own life is that, 00:13:06:03 00:13:08:09 so when you're defining accessibility program 00:13:08:09 00:13:12:23 focus more on these specific steps and checkpoints 00:13:12:23 00:13:16:06 and defined action than goals. 00:13:17:06 00:13:21:06 From those action, they will lead inherently to the goals. 00:13:21:06 00:13:26:06 So for example, let's like play this game of systems 00:13:26:06 00:13:29:09 versus goals, system would be, 00:13:30:05 00:13:32:08 we're going to assign each engineer, 00:13:32:08 00:13:33:20 they're gonna have four hours a week 00:13:33:20 00:13:35:18 to conduct manual testing. 00:13:37:02 00:13:40:07 Again, we have no statement about the results necessarily. 00:13:40:07 00:13:42:17 We can measure that later of how much they got done 00:13:42:17 00:13:46:18 and those kind of things, but it's an open-ended action. 00:13:49:19 00:13:53:24 Now a goal would be no automatically detected 00:13:53:24 00:13:56:00 WCAG errors on homepage. 00:13:57:05 00:14:00:25 It's a good goal, but it's not clear how your organization 00:14:00:25 00:14:01:25 will reach it. 00:14:01:25 00:14:04:25 And you as a manager of an accessibility program, 00:14:04:25 00:14:07:19 are potentially setting yourself up 00:14:07:19 00:14:12:03 for falling short of that expectation. 00:14:12:03 00:14:14:03 And that's why when you do the systems, 00:14:15:03 00:14:17:14 you are getting the outcome that you actually expect, 00:14:17:14 00:14:20:08 you're managing expectations, it's very important here. 00:14:21:23 00:14:26:04 Now, another example of a system would be each engineer 00:14:26:04 00:14:30:05 or each new hire completes an accessibility training, 00:14:30:05 00:14:32:06 two to three hours a week for two weeks. 00:14:33:07 00:14:34:23 It's a digestible amount. 00:14:34:23 00:14:39:18 Again, you're signing something that can be achievable 00:14:39:18 00:14:41:00 when you're realistic about 00:14:41:00 00:14:42:17 what the resources can be allocated, 00:14:42:17 00:14:44:22 you can set achievable goals. 00:14:44:22 00:14:47:18 Now, the goal I hear from some 00:14:50:18 00:14:54:08 or more organizations sometimes is to learn accessibility. 00:14:54:08 00:14:58:22 Again, it's a great goal, but it's not defined, 00:14:58:22 00:15:03:22 it's not punctuated by defined action. 00:15:06:02 00:15:09:00 That's really the key here that we'll draw out a lot today, 00:15:10:04 00:15:12:08 especially in our last section here. 00:15:13:10 00:15:18:05 Okay, let's keep moving here. 00:15:22:03 00:15:27:03 Okay, so as you're setting up your accessibility program, 00:15:28:07 00:15:33:07 it is not advisable to make accessibility the responsibility 00:15:35:08 00:15:38:15 of a sole group at an organization. 00:15:38:15 00:15:42:11 And that's what we're talking about with defining systems 00:15:42:11 00:15:44:05 rather than goals. 00:15:44:05 00:15:45:08 When you define a goal, 00:15:45:08 00:15:47:10 in fact, you're really putting the onus on 00:15:47:10 00:15:49:16 the person who set that goal, 00:15:49:16 00:15:53:03 which again would be in accessibility department, 00:15:53:03 00:15:54:13 something like that. 00:15:54:13 00:15:59:12 So when you share the responsibilities of accessibility, 00:16:00:16 00:16:03:20 everyone is invested in the outcome and much more gets done, 00:16:03:20 00:16:07:04 and it facilitates collaboration, it's really key. 00:16:09:01 00:16:14:01 Now onto the next step in, or I should say requirements 00:16:15:09 00:16:17:23 in an accessibility program is a knowledge base. 00:16:19:08 00:16:22:18 Every organization doing accessibility 00:16:22:18 00:16:27:18 needs a store of knowledge, a Wiki, enabling engineers 00:16:27:24 00:16:29:21 to learn about accessibility 00:16:29:21 00:16:32:09 and do a deep dive where necessary. 00:16:34:03 00:16:39:03 Knowledge base is not something that you have a capacity 00:16:40:01 00:16:42:19 to immediately create yourself. 00:16:42:19 00:16:46:17 If you are a big tech company, an aircraft carrier, 00:16:46:17 00:16:49:13 over time you'll create that knowledge base, 00:16:49:13 00:16:53:19 but for most organizations if they don't have it already, 00:16:53:19 00:16:55:23 it takes a long time to build up. 00:16:55:23 00:17:00:23 And TPGi has been working on its own knowledge base 00:17:01:17 00:17:03:20 for 20 years now, 00:17:03:20 00:17:07:04 it's the greatest accumulation of our work actually. 00:17:08:18 00:17:11:18 So when thinking about this knowledge base, 00:17:14:00 00:17:16:16 it must have three areas. 00:17:16:16 00:17:19:05 So when you're creating that knowledge base 00:17:19:05 00:17:20:03 for your organization, 00:17:20:03 00:17:23:03 consider that you need these three parts, 00:17:23:03 00:17:25:13 at least obviously. 00:17:25:13 00:17:28:21 Number one is foundational training. 00:17:28:21 00:17:31:17 Number two is knowledge based about 00:17:31:17 00:17:34:21 manual testing methodology. 00:17:34:21 00:17:38:17 Number three is recommended design patterns. 00:17:38:17 00:17:43:17 These are three areas where the work must be supported 00:17:44:16 00:17:46:11 by this knowledge base. 00:17:46:11 00:17:49:18 If you're an organization, especially if you're newer 00:17:49:18 00:17:52:04 to accessibility or less experienced 00:17:52:04 00:17:53:21 in implementing accessibility, 00:17:55:10 00:17:58:01 your engineers will need these resources. 00:17:58:01 00:18:01:09 It's not something that they will necessarily understand 00:18:01:09 00:18:03:12 or be able to do on their own. 00:18:05:07 00:18:08:15 And to have this knowledge base greatly increases 00:18:08:15 00:18:10:01 the efficiency of your engineers 00:18:10:01 00:18:12:20 and the accuracy of their work. 00:18:12:20 00:18:14:15 So let's talk about them real quick. 00:18:15:11 00:18:17:15 So first of all, foundational trainings, 00:18:17:15 00:18:19:05 what do I mean by that? 00:18:19:05 00:18:22:13 Well, before your engineers start to test 00:18:22:13 00:18:24:17 or fix existing code, 00:18:24:17 00:18:28:10 and you'll notice that most of this presentation today 00:18:28:10 00:18:31:06 is towards that idea of working on 00:18:31:06 00:18:33:11 already existing applications. 00:18:33:11 00:18:38:11 We're not so much covering the design process 00:18:39:10 00:18:43:09 where you would want to engage populations 00:18:43:09 00:18:47:02 and specifically, interview them and do those steps. 00:18:47:02 00:18:50:22 We're not dealing with that use case exactly today. 00:18:50:22 00:18:55:22 So again, with this foundation of accessibility knowledge, 00:18:57:08 00:18:59:17 your engineers will be much more efficient. 00:18:59:17 00:19:02:15 They have an ability to just start their work. 00:19:02:15 00:19:07:15 So many errors, so many issues in accessibility 00:19:08:12 00:19:11:02 or really just due to flaws in front end code, 00:19:11:02 00:19:15:11 flaws that could have been prevented with this understanding 00:19:15:11 00:19:17:18 of the basic principles of accessibility. 00:19:18:17 00:19:22:14 So our platform provides training modules 00:19:22:14 00:19:25:10 on a wide range of accessibility topics 00:19:26:06 00:19:27:16 to provide that foundation. 00:19:27:16 00:19:31:06 And each module is 15 to 45 minutes. 00:19:31:06 00:19:34:19 Again, it's a achievable amount of training, 00:19:34:19 00:19:39:19 it's not giving them the equivalent of passing 00:19:39:22 00:19:42:00 the security plus exam 00:19:42:00 00:19:43:19 or something like their accessibility plus 00:19:43:19 00:19:45:10 if there was such a thing, right? 00:19:47:06 00:19:50:18 And ARC provides a method to track 00:19:50:18 00:19:53:03 and verify completions of training. 00:19:53:03 00:19:54:24 That's very powerful because again, 00:19:54:24 00:19:57:16 for accessibility managers, it provides them a way 00:19:57:16 00:20:01:06 to validate work that they've done on accessibility, 00:20:01:06 00:20:02:21 and it's a very real action. 00:20:02:21 00:20:06:08 It's gonna help prevent errors in the future. 00:20:07:05 00:20:12:05 Now, again so ARC has this great TPGi tutor modules, 00:20:15:03 00:20:17:02 these set of trainings I'm describing. 00:20:17:24 00:20:19:19 But an alternative resource 00:20:19:19 00:20:23:23 would be Google's Udacity course: What is web accessibility? 00:20:23:23 00:20:26:03 It features hands on exercises 00:20:26:03 00:20:28:08 where developers learn by doing. 00:20:28:08 00:20:31:05 I think, it's one of the earliest courses I took 00:20:31:05 00:20:34:17 when I was first really focusing 00:20:34:17 00:20:37:03 on accessibility engineering. 00:20:37:03 00:20:39:23 It's a great resource and I recommend it and it's free. 00:20:41:04 00:20:44:16 But again, you don't have that capacity to track the result. 00:20:45:12 00:20:47:21 So you're assigning it to your engineers 00:20:47:21 00:20:50:07 and it's a great course, but again, it's gonna be hard 00:20:50:07 00:20:52:16 to validate what's actually been achieved. 00:20:54:09 00:20:59:09 Okay, next step, part of a knowledge based resource 00:21:00:11 00:21:02:17 is manual testing methodology. 00:21:04:03 00:21:09:03 So WCAG Level AA, so WCAG, 00:21:09:03 00:21:11:18 the Web Content Accessibility Guideline. 00:21:11:18 00:21:15:03 It's the prevailing online standard for accessibility, 00:21:17:02 00:21:19:10 as the legal establishment has settled on 00:21:19:10 00:21:21:25 as that standard for online accessibility. 00:21:24:14 00:21:29:11 The level of AA compliance is 50 Success Criteria. 00:21:29:11 00:21:31:04 That's 50 individual tests. 00:21:33:03 00:21:37:16 So the ARC platform and this WCAG is, 00:21:40:02 00:21:43:21 it is complicated, there's a lot of nuances and works 00:21:43:21 00:21:48:21 and you have to be aware of the current status of support 00:21:49:07 00:21:52:16 within assisted technologies, those kind of questions. 00:21:52:16 00:21:56:02 So the ARC platform provides step by step instructions 00:21:56:02 00:22:01:02 for how to test every one of these 50 Success Criteria. 00:22:01:17 00:22:04:20 And actually also AAA Success Criteria 00:22:04:20 00:22:09:14 and Success Criteria in the draft WCAG 2.2, 00:22:09:14 00:22:11:14 all within the ARC platform. 00:22:11:14 00:22:14:09 So when TPGi engineers make the determination 00:22:14:09 00:22:17:13 whether a site conforms to WCAG, 00:22:17:13 00:22:21:08 we largely make that determination based on carrying out 00:22:21:08 00:22:23:21 those manual testing procedures. 00:22:27:10 00:22:29:00 And they're written in a way 00:22:29:00 00:22:31:07 that I think is very comprehensible 00:22:31:07 00:22:34:22 and recognizes its audience, it's great. 00:22:36:08 00:22:40:19 But outside the ARC platform, there are options to learn 00:22:40:19 00:22:43:01 the steps to manual testing. 00:22:43:01 00:22:47:07 First of all, is that W3C, of course, 00:22:48:19 00:22:52:08 we've had a very large, it's an organization that's had 00:22:52:08 00:22:55:23 a very large role in the mechanics of the web, 00:22:55:23 00:23:00:23 they are the heart of creating WCAG. 00:23:02:12 00:23:06:08 They provide a resource on evaluation methodology, 00:23:06:08 00:23:10:21 which provides steps to test the Success Criteria, 00:23:10:21 00:23:15:21 but it's kind of tours, and then it shows you to the actual, 00:23:19:22 00:23:22:01 it drives you to the actual documentation 00:23:22:01 00:23:26:06 for the Success Criteria, so it's fairly long winded. 00:23:26:06 00:23:31:06 And again, to me, it's not as friendly 00:23:32:18 00:23:36:09 to a developer necessarily that is newer to accessibility, 00:23:36:09 00:23:37:21 but it is the authority. 00:23:37:21 00:23:41:18 And I give endless credit to WCAG 00:23:41:18 00:23:46:12 for their tomudic approach to sorting out 00:23:49:07 00:23:53:07 these lines and accessibility and quantifying tests. 00:23:55:24 00:23:57:19 But these are two great tools. 00:23:57:19 00:24:01:12 The report tool allows you to generate 00:24:01:12 00:24:05:09 a manual testing report, following those guidelines, 00:24:05:09 00:24:08:05 those instructions that they give you. 00:24:08:05 00:24:13:05 But again, that report is essentially downloaded, 00:24:13:24 00:24:15:19 so it's not saved into the cloud. 00:24:15:19 00:24:19:21 You have to find a place to do that yourselves, 00:24:19:21 00:24:23:18 and if there are changes to the report 00:24:23:18 00:24:25:10 while you're creating a new report 00:24:26:19 00:24:31:19 and accessibility is an ongoing process, it's a journey, 00:24:32:00 00:24:35:24 and you're always going to be making incremental changes 00:24:35:24 00:24:37:18 to your application. 00:24:37:18 00:24:40:16 So that's the benefit of having something 00:24:40:16 00:24:41:19 like the ARC platform, 00:24:41:19 00:24:45:01 where all your results are tracked over time. 00:24:47:02 00:24:50:18 The third part of the knowledge base 00:24:50:18 00:24:54:05 is the accessible design and component pattern. 00:24:54:05 00:24:57:02 So you see, we've covered two steps here. 00:24:57:02 00:25:00:09 We've had how to understand accessibility. 00:25:00:09 00:25:04:08 Then we've had how to test for accessibility, 00:25:04:08 00:25:07:21 but then third step is how do we solve for accessibility. 00:25:07:21 00:25:11:12 So ARC's knowledge base provides recommended techniques 00:25:11:12 00:25:15:00 and accessible code snippets for a very large range 00:25:15:00 00:25:16:02 of UI elements, 00:25:16:02 00:25:19:16 and it even includes iOS and Android patterns. 00:25:20:24 00:25:22:18 So it's great. 00:25:22:18 00:25:27:18 And the instructions are very in depth. 00:25:28:21 00:25:33:00 And now outside the ARC platform, 00:25:34:24 00:25:36:09 the web accessibility initiative, 00:25:36:09 00:25:41:09 ARIA Authoring Practice Guide Patterns 00:25:41:19 00:25:44:10 has been released recently, the APG. 00:25:45:13 00:25:49:20 They've redone the UI, it's very helpful. 00:25:49:20 00:25:54:20 So that is if you're looking for accessible UI elements, 00:25:56:09 00:25:58:22 like you're building a combo box with a list box, 00:25:58:22 00:26:02:09 and you are looking for an acceptable example to compare to, 00:26:03:16 00:26:07:25 this attached resources is a good open source option. 00:26:07:25 00:26:11:03 And it's not to say that it's perfect, 00:26:11:03 00:26:16:03 but nothing is honestly, but it's a great resource. 00:26:16:10 00:26:19:04 Now, tooling is the next step, 00:26:19:04 00:26:21:05 is so you see we've taken on, 00:26:21:05 00:26:23:23 with setting up an accessibility program, 00:26:23:23 00:26:27:16 we've defined the steps, the checkpoint that you're gonna do 00:26:27:16 00:26:28:22 as an organization. 00:26:29:21 00:26:32:02 I hope that you're, again, thinking about that 00:26:32:02 00:26:35:09 you have your notepad or your Moleskine open, 00:26:35:09 00:26:37:17 and you're taking some notes about what steps 00:26:37:17 00:26:41:03 you might consider doing in your organization. 00:26:41:03 00:26:46:03 So after you've defined these steps, 00:26:46:19 00:26:49:13 you've created this knowledge base, 00:26:49:13 00:26:52:14 you've given your engineers some basic trainings. 00:26:52:14 00:26:57:02 The next step is tooling, setting them up to test sites 00:26:57:02 00:27:00:02 and to check their own code. 00:27:00:02 00:27:02:00 So we'll talk about that quickly. 00:27:02:00 00:27:03:23 So for desktop testing, 00:27:05:07 00:27:07:05 JAWS is the most robust screen reader. 00:27:09:11 00:27:14:09 Now, according to WebAIM's non-scientific survey 00:27:14:09 00:27:15:24 of screen reader users, 00:27:19:03 00:27:22:22 is JAWS is the primary screen reader used on the web 00:27:22:22 00:27:25:13 by people that rely on screen readers 00:27:25:13 00:27:29:15 and use them on a daily basis, by a small margin over NVDA. 00:27:30:11 00:27:35:11 NVDA has a lot of use on desktop as well. 00:27:35:23 00:27:38:12 Now, it's great to have a license for JAWS. 00:27:38:12 00:27:42:24 I think that again, it's the most robust screen reader 00:27:42:24 00:27:46:05 for someone that is professionally employed 00:27:46:05 00:27:48:02 and relying on a screen reader. 00:27:49:06 00:27:52:08 They're most likely going to be using JAWS, 00:27:52:08 00:27:55:16 especially given how it works so well 00:27:55:16 00:27:58:06 with things like Microsoft Office. 00:28:00:16 00:28:02:19 But a JAWS license does cost money, 00:28:04:07 00:28:07:02 especially if you're using it in a professional license, 00:28:07:02 00:28:10:07 not a home license, the home license is only $95, 00:28:11:04 00:28:14:13 a professional license costs considerably more. 00:28:14:13 00:28:17:14 But if you do not have a license to JAWS, 00:28:17:14 00:28:20:22 you can still download JAWS and it has a 40 minute mode. 00:28:20:22 00:28:23:00 So you can use it for 40 minutes, 00:28:23:00 00:28:25:25 which is if you're just trying to see how JAWS 00:28:25:25 00:28:27:14 would announce a single element 00:28:28:16 00:28:31:11 or just to audit small component, 00:28:31:11 00:28:33:00 that's more than enough time. 00:28:33:00 00:28:37:09 However, one frustration is of the 40 minute mode is that 00:28:37:09 00:28:41:20 when the 40 minute mode is over you must reboot the computer 00:28:43:09 00:28:46:07 to do another 40 minutes with JAWS. 00:28:46:07 00:28:48:20 But it is an option, it is an option. 00:28:48:20 00:28:53:11 Now, an alternative to using JAWS is NVDA, 00:28:53:11 00:28:56:02 it's the free screen reader for Windows. 00:28:56:02 00:28:59:01 And NVDA has features, I think, 00:28:59:01 00:29:02:11 which actually could be very helpful to sighted testers 00:29:02:11 00:29:04:17 that are unfamiliar with screen readers, 00:29:04:17 00:29:07:05 perhaps less sophisticated with navigating 00:29:07:05 00:29:08:04 with screen reader. 00:29:09:22 00:29:13:10 So just quickly about configuring NVDA, 00:29:13:10 00:29:15:19 I think this is a great slide to just hold onto, 00:29:15:19 00:29:20:19 is whenever people first end things, 00:29:21:05 00:29:23:10 this from the standpoint of a person that is using 00:29:23:10 00:29:24:20 the screen reader for testing, 00:29:24:20 00:29:28:22 they're not using it to navigate the web 00:29:28:22 00:29:32:01 themselves necessarily, is there are some features 00:29:32:01 00:29:36:04 that I always enable or recommend enabling as a tester. 00:29:36:04 00:29:41:04 So first of all, is every screen reader has a modifier key, 00:29:41:11 00:29:44:14 a command key that is used in combination 00:29:44:14 00:29:48:06 with a lot of other keys to do different functionalities 00:29:48:06 00:29:49:25 with the screen reader. 00:29:49:25 00:29:54:25 So after you open up NVDA, use the NVDA modifier key 00:29:56:12 00:30:01:04 plus N to open the NVDA context menu. 00:30:01:04 00:30:05:00 Now, within the context menu expand tools 00:30:05:00 00:30:06:25 and you can activate the speech viewer. 00:30:06:25 00:30:10:06 The speech viewer provides you a live transcript 00:30:10:06 00:30:12:05 of what the screen reader is saying. 00:30:12:05 00:30:13:25 So I like that for multiple reasons, 00:30:13:25 00:30:18:03 because for one, you can have the screen reader volume 00:30:18:03 00:30:19:22 perhaps lower on your computer, 00:30:19:22 00:30:21:25 and you can still see the transcript. 00:30:21:25 00:30:25:17 It also really works well for screenshots. 00:30:25:17 00:30:27:24 You can take a picture of the transcript 00:30:27:24 00:30:31:23 next to the thing that you're auditing or something. 00:30:31:23 00:30:33:08 And that's really helpful. 00:30:34:17 00:30:36:08 Another thing to do with NVDA 00:30:36:08 00:30:39:05 when you're first setting it up for yourself is to, 00:30:39:05 00:30:42:08 again, open that context menu, expand preferences, 00:30:42:08 00:30:47:08 select setting, flag vision, and enable highlighting. 00:30:47:18 00:30:50:12 And what this allows you to do is it allows you to see 00:30:50:12 00:30:53:24 where the cursor of the screen reader is on the screen. 00:30:53:24 00:30:55:25 So I find that's very helpful for people 00:30:55:25 00:30:59:09 that are less skilled, less experienced 00:30:59:09 00:31:01:10 with using the screen reader. 00:31:01:10 00:31:04:12 Now, on the question of desktop testing, 00:31:04:12 00:31:09:12 a word of caution for me is desktop Mac plus VoiceOver 00:31:11:02 00:31:15:17 has low usage for a lot of reasons 00:31:15:17 00:31:20:17 related to how disabled people purchase technology. 00:31:22:17 00:31:26:10 Testing with that combination, Mac and VoiceOver 00:31:26:10 00:31:30:19 does not resemble daily screen reader usage. 00:31:30:19 00:31:32:19 Now I understand I'm a developer, right? 00:31:32:19 00:31:34:04 Developers love their Mac. 00:31:35:02 00:31:36:06 You may not wanna use it 00:31:36:06 00:31:39:24 for conducting screen reader testing. 00:31:39:24 00:31:43:12 VoiceOver actually is, I find NVDA and JAWS 00:31:43:12 00:31:45:08 have very similar behavior quite often, 00:31:45:08 00:31:48:11 but VoiceOver for desktop is quite different. 00:31:48:11 00:31:51:23 And again, it's just has very low usage 00:31:51:23 00:31:54:15 among people that rely on screen readers. 00:31:56:00 00:31:59:20 Now, mobile testing, very little to say about that today. 00:31:59:20 00:32:03:23 That's its own animal, but the same ideas apply. 00:32:05:02 00:32:07:06 Now, VoiceOver and TalkBack 00:32:07:06 00:32:10:01 they dominate mobile screen reader usage. 00:32:10:01 00:32:13:22 There's some phones out there that have Chrome OS, 00:32:13:22 00:32:17:08 but it's a very small number of the phones out there, 00:32:19:09 00:32:21:20 at least the people using screen readers. 00:32:21:20 00:32:26:20 Now, for your team, probably every person has a phone, 00:32:26:24 00:32:30:19 their own personal device, which they could use for testing. 00:32:30:19 00:32:34:07 If your organization is not able to, 00:32:34:07 00:32:38:18 or does not wish to get them a phone for testing. 00:32:38:18 00:32:42:01 And of course an option is also to use an emulator 00:32:42:01 00:32:43:19 on your computer. 00:32:43:19 00:32:48:19 Now, when you're use a simulator, an emulator or whatever, 00:32:48:19 00:32:52:13 you wanna call it, that can be tricky, right? 00:32:52:13 00:32:56:12 Because if you have a Mac computer, 00:32:56:12 00:33:00:16 it can be very difficult to simulate Android 00:33:00:16 00:33:05:14 on that computer and vice versa with Windows to Mac. 00:33:05:14 00:33:07:11 So something to consider there. 00:33:07:11 00:33:11:06 Now, for the people that are using devices for testing, 00:33:11:06 00:33:14:01 I recommend you enable the accessibility shortcuts 00:33:14:01 00:33:17:16 so that it's easier to turn the screen reader on and off. 00:33:18:12 00:33:22:16 So you can go into settings and every phone and most devices 00:33:22:16 00:33:26:04 that have a screen reader will have some functionality 00:33:26:04 00:33:27:15 similar to that. 00:33:27:15 00:33:32:15 My own father's blind, and he was remarking to me 00:33:32:21 00:33:34:16 earlier today that the Roku remote, 00:33:34:16 00:33:38:09 you can press three times to turn on the screen reader. 00:33:38:09 00:33:40:13 So it's the same idea here. 00:33:42:18 00:33:43:22 But you have to enable that feature, 00:33:43:22 00:33:45:16 it doesn't just work by default. 00:33:47:02 00:33:52:02 Okay, now onto more about tooling is color contrast testing. 00:33:52:10 00:33:56:15 Now, TPGi, there's the color contrast analyzer, 00:33:56:15 00:33:58:01 it's free from TPGi, 00:33:58:01 00:34:01:08 and it works at the operating system level. 00:34:01:08 00:34:05:09 So you can select any two pixels on your screen. 00:34:05:09 00:34:08:13 There's many ways to test color contrast within browser. 00:34:08:13 00:34:12:23 Of course, Chrome developer tools, when you open up the CSS, 00:34:12:23 00:34:16:18 you can click on a color swab to open up the color picker, 00:34:16:18 00:34:19:03 and it provides you a small interface 00:34:19:03 00:34:21:06 to test for color contrast. 00:34:21:06 00:34:22:10 So that is a free option, 00:34:22:10 00:34:24:18 but again, it only applies to the web, 00:34:24:18 00:34:26:19 something that renders within your browser. 00:34:26:19 00:34:29:19 With the CCA, you can grab anything on the screen. 00:34:29:19 00:34:31:01 So if you're running an emulator, 00:34:31:01 00:34:33:08 you can grab something from within the emulator. 00:34:33:08 00:34:37:12 If you're working on a PDF, something like that, you can. 00:34:37:12 00:34:42:01 Now, as a best practice is always best to grab 00:34:42:01 00:34:47:01 the actual color values explicitly set in CSS. 00:34:47:09 00:34:48:09 That's not always possible. 00:34:48:09 00:34:51:02 And that's, again, why the color contrast analyzer 00:34:51:02 00:34:55:17 is such a helpful tool because you can just grab the pixel. 00:34:55:17 00:34:58:14 Now one caveat about CCA 00:34:58:14 00:35:02:02 is that your monitor's color profile, 00:35:02:02 00:35:05:01 you sometimes press that button under it, 00:35:05:01 00:35:07:10 and you can set it as like game or movie, 00:35:07:10 00:35:12:10 or I think Cipia, they have different ones, 00:35:13:05 00:35:16:02 but your monitor's color profile may result 00:35:16:02 00:35:20:01 in the color contrast analyzer reporting the same pixel 00:35:20:01 00:35:22:17 as different Hexadecimal values, 00:35:22:17 00:35:27:12 Hexadecimal is the exact color value on different monitors. 00:35:27:12 00:35:29:02 So something to keep in mind there, 00:35:29:02 00:35:31:14 like that thing of buzz speed from years ago, 00:35:31:14 00:35:32:21 is it a blue dress? 00:35:32:21 00:35:34:01 Is it a gold dress? 00:35:34:01 00:35:37:24 Well, again, it's like drawing those color profiles. 00:35:39:17 00:35:41:14 But it can lead to different results for people. 00:35:41:14 00:35:44:18 And that can lead to confusion with color contrast testing. 00:35:46:03 00:35:48:25 Now, we have our team, they have knowledge, 00:35:48:25 00:35:50:03 they got the tools. 00:35:50:03 00:35:54:05 Now, the next step is to test plan, 00:35:54:05 00:35:56:10 and this is a really critical part. 00:35:56:10 00:36:01:10 And first of all, when we're coming up with a test plan, 00:36:02:00 00:36:03:12 I get this question, I'll ask some people, 00:36:03:12 00:36:08:12 is manual versus automated testing, which first? 00:36:10:05 00:36:11:17 Which should you do first? 00:36:11:17 00:36:14:11 Well, as a best practice, I think manual testing 00:36:14:11 00:36:15:08 should come first. 00:36:16:05 00:36:20:16 Manual testing is the only way to detect 100% of issues. 00:36:20:16 00:36:21:20 So if you think about it, 00:36:21:20 00:36:24:13 is that when you manually audit something, 00:36:24:13 00:36:26:19 you'll know of all the issues, 00:36:27:15 00:36:32:05 and then hopefully you're working on these issues, 00:36:32:05 00:36:35:02 but regardless then you can leverage automated testing 00:36:35:02 00:36:39:08 because automated testing is great at preventing regression. 00:36:39:08 00:36:42:08 In theory if you had a component 00:36:42:08 00:36:45:25 that had no accessibility errors, it would be great 00:36:45:25 00:36:47:24 because then if there were any code changes to it 00:36:47:24 00:36:52:07 that was affecting as accessibility that were really clear, 00:36:52:07 00:36:54:19 again, automated testing would make you aware of that, 00:36:54:19 00:36:57:16 because it can be hard to track all of the code changes 00:36:57:16 00:36:58:22 within your application. 00:36:59:21 00:37:03:08 And again, small changes can break accessibility. 00:37:04:09 00:37:09:09 Now, again for testing and this is somewhat related 00:37:09:14 00:37:14:12 to tooling, but when you are setting off on your testing, 00:37:14:12 00:37:18:13 your manual testing, you have to determine your browser 00:37:18:13 00:37:21:00 and assisted technology combination. 00:37:21:00 00:37:24:12 So number one, I recommend is JAWS and Chrome. 00:37:24:12 00:37:28:18 That's the most common combination of screen reader 00:37:28:18 00:37:32:21 and browser for people that scan and use 00:37:32:21 00:37:34:14 the screen reader on a daily basis. 00:37:35:20 00:37:39:14 Then I would also recommend testing with NVDA Chrome 00:37:39:14 00:37:44:14 or NVDA Firefox, NVDA works with both browsers. 00:37:45:04 00:37:49:25 Now here I have my own viewpoint, which is that 00:37:49:25 00:37:54:25 given what we said earlier about Mac OS and VoiceOver, 00:37:57:14 00:38:02:14 I would recommend if possible conducting your web testing, 00:38:02:14 00:38:06:25 you're testing a website on iOS Safari VoiceOver. 00:38:06:25 00:38:10:11 So you're looking at the website in mobile view. 00:38:10:11 00:38:13:05 And again, you're using a screen reader 00:38:13:05 00:38:17:02 that is very commonly used. 00:38:17:02 00:38:19:01 I believe in the WebAIM survey, 00:38:19:01 00:38:23:10 75% of mobile screen reader users use VoiceOver. 00:38:23:10 00:38:28:10 Now, another benefit to, I think doing iOS Safari VoiceOver 00:38:28:20 00:38:32:15 is that I find a lot of times organizations, 00:38:32:15 00:38:36:08 they favor testing on the full desktop layout, 00:38:36:08 00:38:39:00 that gets more of their attention, and it makes sense, 00:38:40:07 00:38:43:17 we all are wired the same way that we work on a laptop, 00:38:43:17 00:38:45:17 engineers probably most likely 00:38:45:17 00:38:47:24 to work on a desktop computer. 00:38:47:24 00:38:51:00 So therefore they pay the most attention to that layout. 00:38:52:16 00:38:57:03 so it's just built into a lot of processes in life 00:38:57:03 00:38:59:20 that we do the things that we're most exposed to. 00:38:59:20 00:39:04:20 But again, when you set it as iOS Safari and VoiceOver 00:39:04:20 00:39:08:05 as one of your testing profiles that you'll use, 00:39:08:05 00:39:10:22 it ensures that you catch mobile testing 00:39:10:22 00:39:13:06 and you'll pay more attention to it. 00:39:13:06 00:39:15:12 It's something to consider there. 00:39:15:12 00:39:18:03 Now, this is really, I hope that 00:39:18:03 00:39:19:23 this is the most critical step 00:39:19:23 00:39:23:04 in this entire short webinar today 00:39:23:04 00:39:25:21 is component-based testing. 00:39:25:21 00:39:30:21 When you are conducting an audit, when you are going about 00:39:31:05 00:39:36:05 your accessibility testing regimen, break your website 00:39:36:14 00:39:39:12 into smaller components and scope results 00:39:39:12 00:39:43:08 to those components rather than to an entire pages. 00:39:44:09 00:39:45:14 This is fundamental. 00:39:46:19 00:39:50:15 So for each component and a component would represent 00:39:50:15 00:39:54:00 something that's probably a template feature on your site, 00:39:54:00 00:39:57:11 like a navigation bar, a footer, 00:39:57:11 00:40:01:07 the Google Ads implementation that you use, 00:40:01:07 00:40:06:07 perhaps a third party element that you have integrated 00:40:06:16 00:40:09:08 into your site, those kind of things, right? 00:40:09:08 00:40:14:01 And for each component, provide a name, 00:40:14:01 00:40:16:14 a name that's easily referred to mind you, 00:40:16:14 00:40:20:14 because again, you're gonna be referring to this component 00:40:20:14 00:40:21:15 probably with other people 00:40:21:15 00:40:24:01 from different parts of your organization. 00:40:24:01 00:40:28:10 Also to provide an ID to that component. 00:40:28:10 00:40:32:22 And that's important for organizing your audits, 00:40:32:22 00:40:37:07 your hand, but it has a role for automated testing, 00:40:37:07 00:40:40:10 and I think we'll talk about that later on here. 00:40:41:13 00:40:44:06 Also a screenshot, I think a screenshot can be very helpful 00:40:44:06 00:40:45:04 for the component. 00:40:47:01 00:40:49:14 Again, for people that don't think in code, 00:40:49:14 00:40:52:08 or maybe haven't looked at the website as much as others, 00:40:52:08 00:40:55:11 it's a very, again, like effective way to communicate. 00:40:57:00 00:40:59:24 Another thing to include for each component 00:40:59:24 00:41:04:07 in your test plan is steps to reach the component. 00:41:04:07 00:41:05:22 How do you trigger it? 00:41:05:22 00:41:09:17 What are values that a person could input into it? 00:41:10:16 00:41:12:19 I find a lot of times in organizations 00:41:12:19 00:41:14:13 especially like e-commerce shops, 00:41:15:19 00:41:19:14 I think one like great hurdle to them doing testing 00:41:19:14 00:41:22:09 on a consistent basis is simply that engineers 00:41:22:09 00:41:25:08 don't know of test credit card numbers 00:41:25:08 00:41:27:05 and those things that they can use. 00:41:28:02 00:41:30:01 So they don't test it, 00:41:30:01 00:41:32:16 they don't go all the way through a user flow, 00:41:32:16 00:41:34:02 something like that. 00:41:34:02 00:41:37:08 And so something to consider there 00:41:38:11 00:41:41:07 is getting those credentials 00:41:41:07 00:41:44:03 and that's part of the steps to reach the component. 00:41:45:17 00:41:50:17 Now, the benefits to components rather than entire pages. 00:41:50:18 00:41:55:03 Well, when you do component based testing for one, 00:41:55:03 00:41:57:07 it matches the way most organizations 00:41:57:07 00:42:00:02 do development nowadays. 00:42:00:02 00:42:01:22 A lot of the most bigger organizations 00:42:01:22 00:42:06:22 seem to have their own component libraries and themselves, 00:42:07:04 00:42:09:08 this matches that. 00:42:09:08 00:42:12:05 Now other benefits are that it sets clear priorities 00:42:12:05 00:42:14:01 when you scope results to components. 00:42:14:01 00:42:18:16 Template components better on every page of your site, 00:42:18:16 00:42:21:09 they're likely to be encountered by disabled people. 00:42:21:09 00:42:23:14 So they represent a high priority. 00:42:23:14 00:42:28:14 And now another great benefit to component-based testing, 00:42:30:21 00:42:35:03 this just facilitates communication and cross collaboration. 00:42:35:03 00:42:38:08 Again, you have a capacity to refer to these components. 00:42:38:08 00:42:42:09 And when you know of accessibility errors on your site, 00:42:42:09 00:42:46:15 you can clearly pinpoint the source of the issue. 00:42:46:15 00:42:48:18 You can state that it is a part of this component. 00:42:48:18 00:42:53:18 And also it provides you a level of flexibility. 00:42:54:02 00:42:57:11 I've seen some organizations that use 00:42:57:11 00:42:59:06 a third party component library, 00:42:59:06 00:43:02:07 perhaps like learning management system 00:43:02:07 00:43:03:23 or something like that. 00:43:03:23 00:43:06:23 And they conduct their own testing on those components, 00:43:06:23 00:43:09:01 and they recognize that some components 00:43:09:01 00:43:10:06 are more accessible than other ones. 00:43:10:06 00:43:13:14 So they favor using those components. 00:43:13:14 00:43:16:16 They try to avoid using, they make it active decision 00:43:16:16 00:43:18:17 to not use components which they know 00:43:18:17 00:43:23:17 are still needing accessibility remediation in a sense. 00:43:24:11 00:43:27:13 Another benefit to component-based testing 00:43:27:13 00:43:30:06 is that increases efficiency for engineers. 00:43:30:06 00:43:32:24 I find when organizations test entire pages, 00:43:32:24 00:43:36:06 what you do is that you put the decision making 00:43:36:06 00:43:40:01 about what to address first on your individual engineers. 00:43:40:01 00:43:43:16 You're making them triage through all the results 00:43:43:16 00:43:46:02 and determine what's most significant. 00:43:46:02 00:43:51:02 To me it's not a reasonable responsibility 00:43:52:23 00:43:55:03 to give on to some developer, 00:43:55:03 00:43:59:13 they're not in charge of setting their schedules 00:43:59:13 00:44:02:24 and their priority generally speaking. 00:44:02:24 00:44:06:17 So when you have the components, you can clearly state, 00:44:06:17 00:44:08:16 "Hey, this component is the first one 00:44:08:16 00:44:10:07 that we are all working on. 00:44:11:09 00:44:12:25 You were gonna conduct manual testing on it. 00:44:12:25 00:44:13:23 We're gonna fix that one. 00:44:13:23 00:44:15:21 And then we'll move on to the next one." 00:44:15:21 00:44:18:07 And again, then administrators, managers, 00:44:18:07 00:44:20:18 can make that decision more easily. 00:44:20:18 00:44:23:22 And again, they're able to communicate the progress 00:44:23:22 00:44:25:22 of accessibility testing. 00:44:27:05 00:44:31:04 Now, onto manual testing, 00:44:31:04 00:44:34:13 the actual mechanics that the manual testing. 00:44:35:18 00:44:40:15 And getting a little late here. 00:44:40:15 00:44:43:04 So I'm going to race through this very quickly. 00:44:44:08 00:44:45:19 You'll receive these slides afterwards. 00:44:45:19 00:44:48:13 But again, manual testing is very time consuming. 00:44:48:13 00:44:52:16 So it's 50 accessibility tests for each component 00:44:52:16 00:44:55:21 in a sense, 50 guidelines, 50 tests. 00:44:55:21 00:44:58:16 Well, one thing you can do to make manual testing 00:44:58:16 00:45:00:24 much more efficient is to group 00:45:00:24 00:45:04:09 the WCAG Success Criteria by topic. 00:45:04:09 00:45:07:13 So you can test the related Success Criteria at once. 00:45:07:13 00:45:09:23 So rather than jump from color contract testing, 00:45:09:23 00:45:13:24 to testing form labels, to testing audio and video, 00:45:16:02 00:45:18:12 whether there's audio description, those sorts of things, 00:45:18:12 00:45:23:12 you can take on form accessibility guidelines 00:45:23:21 00:45:27:05 dealing with forms, you can do all of them at once, 00:45:27:05 00:45:28:06 one train of thought. 00:45:28:06 00:45:30:02 Then you can do color contrast testing, 00:45:30:02 00:45:34:08 then you can do semantics structure, 00:45:34:08 00:45:38:06 test non-interactive elements on the page. 00:45:39:10 00:45:42:08 And again, that'll speed it up quite a bit. 00:45:42:08 00:45:45:17 Now ARC platform through ARC Capture, 00:45:45:17 00:45:49:16 which is basically our tool for guided manual testing, 00:45:49:16 00:45:53:19 our groups, the WCAG Success Criteria by topic. 00:45:53:19 00:45:56:06 So it helps you be more efficient. 00:45:56:06 00:45:58:24 It does this process we're talking about. 00:45:58:24 00:46:01:23 And when a component is completed in our capture 00:46:01:23 00:46:03:22 and the results are recorded 00:46:03:22 00:46:06:04 and viewable by everyone on the team, 00:46:06:04 00:46:09:01 sharing results simply within spreadsheets 00:46:09:01 00:46:11:00 can be problematic, 00:46:11:00 00:46:13:20 especially when you're working at a larger organization. 00:46:13:20 00:46:16:04 And more on that thought in a second, 00:46:16:04 00:46:19:16 is that a spreadsheet for manual testing, 00:46:19:16 00:46:21:09 now, that's really fundamental, 00:46:21:09 00:46:24:08 every organization's probably gonna do something like that. 00:46:25:06 00:46:28:01 Now, when you're doing it outside the ARC platform, 00:46:28:01 00:46:30:02 again, ARC is a one stop shop 00:46:30:02 00:46:31:19 to manage all these activities. 00:46:31:19 00:46:33:19 When you do it outside the ARC platform, 00:46:35:06 00:46:37:19 I recommend that that manual testing spreadsheet 00:46:37:19 00:46:40:25 that is hosted in the cloud, 00:46:40:25 00:46:44:09 something Think Google Drive Quip so that multiple people 00:46:44:09 00:46:47:01 can refer to the spreadsheet at once 00:46:47:01 00:46:49:16 and can make updates on it. 00:46:49:16 00:46:52:17 And it's just very cumbersome to send a document 00:46:52:17 00:46:54:19 through the organization back and forth. 00:46:54:19 00:46:56:21 And even if you're given it a spreadsheet 00:46:56:21 00:47:00:01 by some other accessibility vendor, 00:47:00:01 00:47:03:13 you can still go about this and upload it to the cloud, 00:47:03:13 00:47:08:13 and into a workplace product, what do you call that? 00:47:09:18 00:47:11:18 Like an app like Google Drive basically. 00:47:12:14 00:47:16:05 Now, automated testing, next section. 00:47:16:05 00:47:21:05 Very quickly about automated testing is that ARC platform 00:47:23:09 00:47:27:16 provides two rules engines that you can use, 00:47:27:16 00:47:30:20 that you can use ARC or aXe, which is open source, 00:47:30:20 00:47:32:15 and anyone can use aXe. 00:47:33:17 00:47:37:02 It has node package and just all the different ways. 00:47:38:17 00:47:42:02 You can incorporate it in an application in many ways. 00:47:42:02 00:47:46:04 So some fundamental things to understand 00:47:46:04 00:47:49:04 when comparing these two rules engines. 00:47:49:04 00:47:52:22 aXe their great draw is no false positive, 00:47:52:22 00:47:57:22 so they won't report any issue that, 00:47:58:02 00:48:01:14 again, could be a false positive. 00:48:01:14 00:48:03:25 Now that's a very restrictive standard, 00:48:03:25 00:48:05:22 it sounds great, but it's very restrictive. 00:48:05:22 00:48:09:09 It will overlook some issues. 00:48:09:09 00:48:14:03 And now the benefit is it reports fewer, 00:48:14:03 00:48:17:07 I mean, or downside, however, you wanna look at it, 00:48:17:07 00:48:21:04 but actual results in the reporting of fewer issues. 00:48:21:04 00:48:23:16 It reduces the amount of manual testing your team 00:48:23:16 00:48:26:21 would have to do to deal with just the results of the scan. 00:48:26:21 00:48:28:16 So that's like from the approach, 00:48:28:16 00:48:30:17 if you haven't done manual testing 00:48:30:17 00:48:33:15 and you intend to just do automated testing. 00:48:33:15 00:48:35:09 And that to me is the flaw 00:48:35:09 00:48:36:21 with that way of thinking, right? 00:48:36:21 00:48:39:21 'Cause you have new manual testing regardless. 00:48:39:21 00:48:41:09 Now over time. 00:48:41:09 00:48:43:22 One thing that I've noticed is that the number of aXe rules 00:48:43:22 00:48:47:21 that are automatic and do not require manual verification 00:48:47:21 00:48:50:10 has declined, that number of issues has gotten 00:48:50:10 00:48:53:12 smaller and smaller because of that no false positive. 00:48:53:12 00:48:56:20 That's a very restrictive standard, the web is very complex. 00:48:56:20 00:48:58:08 There's a lot of edge cases. 00:48:58:08 00:49:01:12 ARC is more concerned with code smell, 00:49:01:12 00:49:03:08 code smells like, I don't even like that term, 00:49:03:08 00:49:07:22 but it's a developer term for an issue within code 00:49:09:06 00:49:12:11 and a mistaken pattern that could be indicative 00:49:12:11 00:49:14:22 of larger problems within the application. 00:49:14:22 00:49:16:08 So ARC is more concerned 00:49:16:08 00:49:17:21 with all the different permutations, 00:49:17:21 00:49:20:02 the browser and assistive tech. 00:49:20:02 00:49:23:24 It's not so much about something having zero accessibility 00:49:23:24 00:49:28:24 where you would be sure that it is not a false positive. 00:49:29:06 00:49:32:18 Now, I feel the benefit here is that ARC rules 00:49:32:18 00:49:35:21 provides more value and predictability from your code. 00:49:35:21 00:49:38:00 You're aware of all the issues in a sense. 00:49:38:00 00:49:42:11 Like you end up with more issues, that's true 00:49:42:11 00:49:45:11 but I think the good thing I would want to know. 00:49:45:11 00:49:50:11 So now, and again, these are gonna help you understand 00:49:50:15 00:49:52:11 where to conduct manual testing. 00:49:53:14 00:49:55:22 So again, it's helping you be aware 00:49:55:22 00:49:58:04 of those places to do it. 00:49:58:04 00:50:01:13 And it's drawing your attention to Success Criteria 00:50:01:13 00:50:05:17 that maybe you should apply to a component, for example. 00:50:06:23 00:50:11:01 ARC could tell you that a dialogue has content outside of it 00:50:12:22 00:50:14:22 exposed to assisted tech. 00:50:14:22 00:50:17:14 Well, we are drawing your attention to the fact 00:50:17:14 00:50:19:18 they should also test for focus management 00:50:19:18 00:50:21:03 and those kind of things 00:50:21:03 00:50:26:03 where they can't be so easily tested on an automatic basis. 00:50:26:19 00:50:29:20 Now, automated testing must be scoped to components 00:50:29:20 00:50:31:17 rather than to entire pages. 00:50:31:17 00:50:33:20 Let me reiterate that one last time, 00:50:33:20 00:50:37:13 is that page level scores, they provide signals about 00:50:37:13 00:50:40:05 the overall accessibility health of a website, 00:50:40:05 00:50:42:18 web application, but they don't facilitate 00:50:42:18 00:50:44:12 the remediation process. 00:50:47:00 00:50:49:17 Because again, what happens is engineers end up checking 00:50:49:17 00:50:51:08 the same test multiple times 00:50:51:08 00:50:55:07 because the same element is being flagged on multiple pages. 00:50:55:07 00:50:57:14 There's a level of redundancy. 00:50:57:14 00:51:02:03 So component based testing FTW for the win. 00:51:02:03 00:51:05:23 Now, with component based testing in ARC, 00:51:05:23 00:51:08:18 we call this user flow monitoring, you're going, you're net, 00:51:08:18 00:51:10:17 you're simulating a new user navigating 00:51:10:17 00:51:11:13 through an application 00:51:11:13 00:51:14:10 and you're picking specific segments of the screen. 00:51:14:10 00:51:19:10 Well, this is increasingly available 00:51:19:15 00:51:21:08 with native to the browser. 00:51:21:08 00:51:25:01 So outside the ARC platform, Google Lighthouse now provides 00:51:25:01 00:51:29:10 page level analysis and also user-flow based 00:51:29:10 00:51:31:09 automated testing. 00:51:31:09 00:51:33:18 So using Google Lighthouse, you can create 00:51:33:18 00:51:38:12 your own user-flows now and go deep into your user-flow. 00:51:38:12 00:51:41:14 Now, of course, it's already done through ARC 00:51:41:14 00:51:45:19 and we provide a lot of documentation on how to go about it. 00:51:45:19 00:51:47:24 And also we have the capacity to do it for you 00:51:47:24 00:51:49:16 depending on your subscription. 00:51:50:18 00:51:53:18 Now, the last step to an accessibility program, 00:51:53:18 00:51:55:15 the structuring accessibility program, 00:51:55:15 00:51:57:21 we covered the testing protocols very quickly, 00:51:57:21 00:52:00:18 but it's very important to track your progress. 00:52:00:18 00:52:05:18 Accessibility, it's many things, it's a responsibility, 00:52:06:14 00:52:10:13 it's a challenge, it's an investment also. 00:52:10:13 00:52:12:19 So it is important that it is trackable 00:52:12:19 00:52:15:07 and we're able to validate our efforts. 00:52:15:07 00:52:17:11 So for accessibility program managers, 00:52:17:11 00:52:20:03 one thing that I've learned over time 00:52:20:03 00:52:22:16 is that managers for accessibility 00:52:22:16 00:52:26:18 they are accountable to disabled people using your site. 00:52:26:18 00:52:29:21 They are the first line of people really communicating 00:52:29:21 00:52:32:02 with someone that is unable to use the site. 00:52:32:02 00:52:35:18 They are also accountable to their leadership 00:52:35:18 00:52:38:22 and other stakeholders at their organization. 00:52:38:22 00:52:42:23 You have to be prepared to provide defensible data, 00:52:42:23 00:52:44:14 to validate your work. 00:52:44:14 00:52:47:11 'Cause again, accessibility can be hard to quantify 00:52:47:11 00:52:49:15 exactly what has been done. 00:52:49:15 00:52:53:16 Now, each step define the accessibility program 00:52:53:16 00:52:57:16 we talked about today, they provide that defensible data. 00:52:57:16 00:53:01:17 ARC as a platform supports this tracking and data keeping. 00:53:01:17 00:53:06:03 And that's a great advantage over the cobbled together 00:53:06:03 00:53:07:23 open source tool. 00:53:07:23 00:53:12:01 Now the last thing I'll note today is advanced metrics, 00:53:12:01 00:53:15:00 which is that there's other methods you could track 00:53:15:00 00:53:18:14 your progress, which is track the time spent 00:53:18:14 00:53:20:23 on accessibility tickets. 00:53:20:23 00:53:24:02 JIRA can provide you that functionality if you use that. 00:53:24:02 00:53:26:07 The number of accessibility tickets solved 00:53:26:07 00:53:27:17 if you provide labels to them, 00:53:27:17 00:53:29:14 again, in something like JIRA. 00:53:29:14 00:53:33:09 And another option would be maybe to run automated scan 00:53:33:09 00:53:35:09 on the homepage of other organizations, 00:53:35:09 00:53:36:24 competitors in your sector. 00:53:36:24 00:53:40:25 You can compare your progress with similar minded companies, 00:53:40:25 00:53:43:08 little more of an apples to apples comparison. 00:53:45:05 00:53:49:05 so again, there's so much, this is by no means 00:53:49:05 00:53:51:14 a comprehensive or holistic approach 00:53:51:14 00:53:53:02 to accessibility testing. 00:53:53:02 00:53:56:24 But I hope today you came away with one or two steps 00:53:56:24 00:53:58:15 that you could use or to add 00:53:58:15 00:54:02:12 to bolster your own testing program. 00:54:02:12 00:54:06:24 Now, I apologize it went a little long, 00:54:06:24 00:54:09:06 but we have some time for questions now. 00:54:09:06 00:54:11:16 So let me look at the Q&A here 00:54:11:16 00:54:13:21 and see if we got any good ones. 00:54:16:04 00:54:18:17 "Could Aaron provide an example of a good roadmap?" 00:54:18:17 00:54:20:16 Monica, that's a great point. 00:54:20:16 00:54:23:03 I will share that following this meeting. 00:54:25:25 00:54:28:22 That may take me a little bit of time and I may end up... 00:54:28:22 00:54:31:22 I'll try to send it to everyone, that's a great question. 00:54:33:08 00:54:36:23 Jonathan says, "Some commercial accessibility 00:54:36:23 00:54:40:16 test package owners offer open source versions 00:54:40:16 00:54:45:16 of their rule engines, does or will TPGi do that?" 00:54:46:04 00:54:48:05 We have no plans to at this time. 00:54:49:19 00:54:51:23 But it is something that we consider. 00:54:51:23 00:54:54:10 Now, I will like make you think about this, 00:54:54:10 00:54:58:24 and maybe in a different way is that ARC is proprietary, 00:54:58:24 00:55:00:20 it's private to your organization, 00:55:00:20 00:55:04:06 there's no way someone can use the ARC rules engine 00:55:04:06 00:55:07:09 to test or determine a score for your organization. 00:55:07:09 00:55:09:14 I think that's very liberating for us. 00:55:09:14 00:55:12:17 I think that, given ARC's is vast reach, 00:55:12:17 00:55:16:04 it's built into the browser they have some their, 00:55:17:12 00:55:19:22 I don't know if it's formalizing or, 00:55:19:22 00:55:22:08 but I feel like there's a wariness about 00:55:22:08 00:55:24:10 what's reported given that reach. 00:55:25:13 00:55:26:24 Now, another question here is, 00:55:26:24 00:55:28:19 "How do you go about doing estimates 00:55:28:19 00:55:31:08 for accessibility testing and defining scope? 00:55:31:08 00:55:33:13 We often get requests internally to test something 00:55:33:13 00:55:35:11 with the expectation that accessibility testing 00:55:35:11 00:55:37:23 is you can do it in five hours." 00:55:37:23 00:55:41:21 I can relate Daniel and you don't need any training, 00:55:41:21 00:55:45:03 but it's difficult to respond to that when we don't know 00:55:45:03 00:55:47:10 what we need to test or how, 00:55:47:10 00:55:51:09 or how long any of that would take. 00:55:51:09 00:55:54:23 Well, that's an excellent question. 00:55:54:23 00:55:57:05 And I think when determining 00:55:57:05 00:55:59:06 how long something would take, 00:55:59:06 00:56:01:16 I generally measure that by how interactive 00:56:01:16 00:56:03:14 the application is. 00:56:03:14 00:56:08:06 And also frankly, how convoluted the steps are 00:56:08:06 00:56:09:22 to reach the component. 00:56:09:22 00:56:11:04 That's one of the things that I think 00:56:11:04 00:56:14:03 when you start putting in for each component, 00:56:14:03 00:56:16:07 you put the steps to reach that component. 00:56:16:07 00:56:20:02 It helps validate how much time it takes. 00:56:20:02 00:56:23:14 And by the same token 00:56:23:14 00:56:26:12 this is an issue with also remediation. 00:56:26:12 00:56:30:04 I think organizations strongly underestimate 00:56:30:04 00:56:33:17 how much time it takes to repair a busted UI. 00:56:35:14 00:56:39:23 So that affects all ends of the accessibility process. 00:56:39:23 00:56:42:17 I am curious what Aaron will recommend to developers 00:56:42:17 00:56:44:24 working with product owned by a third party company 00:56:44:24 00:56:47:20 where some internal customization to resolve accessibility 00:56:47:20 00:56:50:23 is possible and other issues, 00:56:50:23 00:56:52:14 or I guess you mean not possible, 00:56:52:14 00:56:55:12 and other issues can only be solved by the vendor. 00:56:55:12 00:56:57:14 Does he have examples of how to best document 00:56:57:14 00:56:59:14 what is tested and resolved in-house? 00:56:59:14 00:57:02:02 Well, I think first of all, is to conduct testing yourself 00:57:02:02 00:57:06:01 on that third party thing, and share it with them. 00:57:06:01 00:57:09:05 I think that's very helpful and can be very powerful. 00:57:11:03 00:57:15:20 But for me, a lot of the stuff with third party tools, 00:57:17:08 00:57:20:13 you have to make those decisions before you use the product. 00:57:20:13 00:57:23:18 So you ask for a V-Path, that's one option. 00:57:23:18 00:57:28:18 Another option is a Shopify or WordPress plugin, 00:57:28:19 00:57:31:04 go to the plugin marketplace and look at the reviews, 00:57:31:04 00:57:32:15 see what others have said. 00:57:33:20 00:57:36:08 Another great resource I like to do is just simply, 00:57:36:08 00:57:38:10 and this is not anything scientific, 00:57:38:10 00:57:43:07 is I like to go to Twitter to research specific UI elements. 00:57:44:11 00:57:48:05 But in terms of third party code, that's what I recommend, 00:57:48:05 00:57:50:24 is again, you just have to share the results with them. 00:57:50:24 00:57:54:18 Maybe you can look at our researching alternative options. 00:57:54:18 00:57:57:04 One other thing that I've done myself 00:57:57:04 00:57:58:21 and this can really only be done 00:57:58:21 00:58:00:23 with simpler WordPress sites, 00:58:00:23 00:58:02:16 something like a Twitter timeline, 00:58:02:16 00:58:06:01 that's a really common widget for WordPress 00:58:06:01 00:58:09:17 is you can actually make your own overlay in a sense. 00:58:09:17 00:58:13:04 You can use JavaScript to change some of the markup 00:58:13:04 00:58:15:24 for that third party component. 00:58:15:24 00:58:19:01 And you think about it, it's not a great way to do things, 00:58:19:01 00:58:22:17 but it can make it accessible in a short term. 00:58:22:17 00:58:25:20 And I wanna really strongly emphasize that overlay word. 00:58:25:20 00:58:29:12 This is a custom overlay, this is your own JavaScript, 00:58:29:12 00:58:31:11 which you're using to apply to a single element. 00:58:31:11 00:58:32:07 It's not automated, 00:58:32:07 00:58:34:21 you're not replacing any browser features. 00:58:34:21 00:58:37:06 How do you include users with disabilities 00:58:37:06 00:58:39:02 in your manual testing? 00:58:39:02 00:58:44:02 Well, I think there's no substitute for having people 00:58:45:09 00:58:48:04 that are daily users of technology. 00:58:48:04 00:58:52:14 You find so many little parts of the process 00:58:52:14 00:58:55:13 that are beyond the perspective 00:58:55:13 00:58:58:20 of just a person that's just testing. 00:58:58:20 00:59:03:20 So I think there's no substitute for hiring disabled people. 00:59:05:24 00:59:06:25 That is the simplest way. 00:59:06:25 00:59:09:20 When you have people on your team that use this technology, 00:59:09:20 00:59:11:21 you'll be aware of the issues. 00:59:11:21 00:59:15:02 Maybe not in an official way or in a formalized way, 00:59:15:02 00:59:17:03 but it's definitely a powerful thing. 00:59:18:02 00:59:21:10 Now, in terms of including users with disabilities 00:59:21:10 00:59:24:00 in manual testing, one thing that I've learned myself 00:59:24:00 00:59:27:10 is that you gotta be careful about doing that 00:59:27:10 00:59:28:22 at the start of the process, 00:59:28:22 00:59:31:19 because if an application is inaccessible, 00:59:31:19 00:59:34:22 highly inaccessible, there's no need necessarily 00:59:34:22 00:59:37:21 to get people's like own user experience, 00:59:37:21 00:59:41:08 you know that the thing is not semantic HEMO, 00:59:41:08 00:59:42:12 you know it's broken. 00:59:42:12 00:59:46:18 So I used to have my own pool of disable testers, 00:59:46:18 00:59:48:05 I thought it was very demoralizing. 00:59:48:05 00:59:50:07 It was very demoralizing to give them applications 00:59:50:07 00:59:52:15 that were broken and know that they were broken 00:59:52:15 00:59:53:19 when they were being given to them. 00:59:53:19 00:59:56:17 So what I would say on that front is like, 00:59:58:15 01:00:02:00 I think it's best to incorporate people again, 01:00:02:00 01:00:03:23 and these are not necessarily official testers, 01:00:03:23 01:00:06:05 but maybe like a testing pool, 01:00:06:05 01:00:08:08 when you think you've remediated the code, 01:00:08:08 01:00:09:22 when you feel it's accessible, 01:00:09:22 01:00:11:09 that's when I think it's best. 01:00:11:09 01:00:13:12 I don't think it makes sense to send people things 01:00:13:12 01:00:16:04 that you know will be inaccessible for them. 01:00:17:25 01:00:19:16 I think that's just inherently frustrating 01:00:19:16 01:00:21:18 and not a great use of their time. 01:00:21:18 01:00:22:20 Now, how do you establish. 01:00:22:20 01:00:26:10 - [Kari] Hey, Aaron, we've hit on time here. 01:00:33:09 01:00:35:23 If you wanna stay on a little longer, 01:00:35:23 01:00:37:09 finish answering some questions, 01:00:37:09 01:00:41:07 but just wanted to fly we're at the end of our session here. 01:00:41:07 01:00:42:17 - Okay, well, all right. 01:00:42:17 01:00:45:13 Let me say I'll continue answering questions, 01:00:45:13 01:00:49:16 but I wanna reiterate if people have, 01:00:49:16 01:00:51:12 I'm very respectful of other people's time, 01:00:51:12 01:00:56:09 this whole session is recorded, so if you have to leave now, 01:00:56:09 01:00:57:20 you can always watch the end of the recording 01:00:57:20 01:00:59:00 and see these questions. 01:00:59:00 01:01:01:00 But I do urge if you have no place to go, 01:01:01:00 01:01:03:11 stick around to these questions, 01:01:03:11 01:01:06:11 I find when we go off script, 01:01:06:11 01:01:08:17 you think people have questions that you didn't know, 01:01:08:17 01:01:10:19 you also have, that's really powerful. 01:01:10:19 01:01:11:22 We all learn from each other. 01:01:11:22 01:01:15:12 And even from these questions from jogging thoughts for me. 01:01:15:12 01:01:17:03 But if you have to go, please go 01:01:17:03 01:01:21:08 and again, thank you so much for attending. 01:01:21:08 01:01:25:04 So now I'm gonna continue with some questions for, 01:01:25:04 01:01:27:06 I think, five more minutes tops. 01:01:27:06 01:01:30:23 I see that we only have a few questions left in the chat. 01:01:30:23 01:01:32:21 We'll see if we can get through them. 01:01:34:02 01:01:38:20 Okay, Jason, well, let me see, actually... 01:01:40:07 01:01:44:01 Jason, well, actually, I'm gonna scroll down here. 01:01:44:01 01:01:46:01 How do you establish testing criteria 01:01:46:01 01:01:48:16 where it's not possible to do HTML accessibility 01:01:48:16 01:01:49:12 the right way? 01:01:49:12 01:01:51:02 We deal with content from authoring tools 01:01:51:02 01:01:54:04 that don't publish very good ARIA HTML, 01:01:54:04 01:01:55:19 so we have to do the best we can, 01:01:55:19 01:01:58:05 like e-learning interactions, like the accordions, 01:01:58:05 01:02:01:10 where we can't make a proper disclosure widget. 01:02:01:10 01:02:04:04 How do you establish testing criteria? 01:02:04:04 01:02:06:18 Well, the testing criteria is universal. 01:02:06:18 01:02:11:18 I mean, it doesn't matter who's made the code, 01:02:12:02 01:02:14:24 whether it's yourself or some other third party developer. 01:02:14:24 01:02:18:09 But what I say is that this drives that idea earlier 01:02:18:09 01:02:21:01 that I was talking the benefits of component-based testing 01:02:21:01 01:02:23:03 and you're describing a third party. 01:02:23:03 01:02:26:06 So I assume you're getting components from that third party 01:02:26:06 01:02:31:06 is that you test each component and you try to avoid 01:02:32:10 01:02:36:02 the components that have accessibility issues. 01:02:36:02 01:02:39:16 So for example, with Captivate, we could say that 01:02:39:16 01:02:42:24 it doesn't have a proper disclosure widget, 01:02:44:00 01:02:45:20 but it could have an accessible tab panel 01:02:45:20 01:02:47:19 and maybe you could change the UI 01:02:47:19 01:02:49:25 to use that accessible component. 01:02:49:25 01:02:52:03 And that's generally, my recommendation, 01:02:52:03 01:02:54:19 is make that organization aware of the issue, 01:02:57:06 01:02:58:10 gauge their response. 01:02:58:10 01:03:01:25 And in the meantime, again, use a component that you know 01:03:01:25 01:03:05:05 to be more accessible, that's being adaptive. 01:03:05:05 01:03:08:06 And when you, again, have results 01:03:08:06 01:03:11:18 scope to specific components, that's what you're able to do. 01:03:11:18 01:03:14:15 Now, Monica Olson, "What resources do you recommend 01:03:14:15 01:03:17:17 to help people learn hands-on ability to use screen reader 01:03:17:17 01:03:19:23 and other assistive technology?" 01:03:19:23 01:03:24:23 Well, Freedom Scientific, the company that produces JAWS, 01:03:25:14 01:03:28:20 which is part of the Sparrow, which TPGi is part of also. 01:03:29:23 01:03:32:00 Freedom Scientific has an online course 01:03:32:00 01:03:34:18 to learn how to use screen readers. 01:03:34:18 01:03:36:20 And I recently went through it 01:03:36:20 01:03:37:22 and I found this to be very helpful. 01:03:37:22 01:03:41:10 I already knew screen readers, so maybe that makes me 01:03:41:10 01:03:43:23 not a great test case, 01:03:43:23 01:03:46:19 but yeah, I think that's a great way to learn it, 01:03:46:19 01:03:48:14 is going through that testing, 01:03:50:01 01:03:52:09 through that course by Freedom Scientific, 01:03:52:09 01:03:55:17 and you can just look up JAWS education 01:03:57:11 01:04:00:18 and also Freedom Scientific has great YouTube videos 01:04:00:18 01:04:04:01 on using a screen reader on using JAWS. 01:04:04:01 01:04:06:21 Another option I feel is that Google Udacity course 01:04:06:21 01:04:09:07 I described, it uses Chrome Box, 01:04:09:07 01:04:11:10 which has basically a zero market share, 01:04:11:10 01:04:14:12 but it is a screen reader and it works like a screen reader, 01:04:15:18 01:04:17:10 and they provide specific steps. 01:04:18:21 01:04:22:19 Why is the ARC tool not authorized by Google? 01:04:22:19 01:04:26:02 I don't know what that's referring to Prince Kumar. 01:04:27:20 01:04:30:11 Google is always doing actions 01:04:30:11 01:04:32:12 related to extension policies, 01:04:32:12 01:04:34:13 so that's not a surprise there, 01:04:34:13 01:04:36:22 but I'll find out more about that question, 01:04:36:22 01:04:39:07 that's really interesting to me. 01:04:39:07 01:04:41:18 Feel free to send me more information about that. 01:04:43:12 01:04:47:03 Yeah, Joanna, I too love the redesign 01:04:47:03 01:04:49:09 of the ARIA Authoring Practice Guidelines, 01:04:49:09 01:04:50:13 I think it looks great. 01:04:52:04 01:04:53:21 Why is the chat disabled? 01:04:53:21 01:04:55:22 Screen reader alerts can be turned on or off 01:04:55:22 01:04:59:23 for the individual user and not decided for every attendee? 01:05:01:01 01:05:04:05 I apologize for that, I really do. 01:05:04:05 01:05:06:17 I'm aware of that issue at times with using Zoom, 01:05:06:17 01:05:09:22 so I just apologize for that. 01:05:12:03 01:05:14:11 Simple as that, thank you for making me aware. 01:05:15:10 01:05:16:23 One thing to note about 01:05:16:23 01:05:19:20 the ARIA Authoring Practice Guidelines, this guide, 01:05:19:20 01:05:23:20 and this is from Jason Klepp, sorry, 01:05:23:20 01:05:26:07 is that it was mentioned as coding patterns. 01:05:26:07 01:05:28:12 The website explains that the patterns shown 01:05:28:12 01:05:30:24 are not tested for any browsers or screen readers 01:05:30:24 01:05:33:13 that do not support ARIA 1.2. 01:05:33:13 01:05:36:03 So these patterns are not backwards compatible 01:05:36:03 01:05:37:23 with older equipment. 01:05:37:23 01:05:39:23 Well, that's good intel, that's good intel. 01:05:39:23 01:05:41:24 And actually that's something I wish I had mentioned 01:05:41:24 01:05:43:17 during this presentation actually though, 01:05:43:17 01:05:48:11 is that when we do testing in browsers 01:05:48:11 01:05:52:12 and assistive technologies, we use the latest version, 01:05:53:20 01:05:58:08 again, I think it's not an unreasonable request 01:05:58:08 01:06:01:06 for people to update their licenses 01:06:01:06 01:06:03:08 to the most recent version. 01:06:03:08 01:06:08:08 Now, there's of course this could be a tricky issue. 01:06:09:17 01:06:12:09 People used to use Internet Explorer for many years 01:06:12:09 01:06:16:04 beyond when they stopped officially supporting it 01:06:17:24 01:06:20:10 or I mean, stop making additions to it. 01:06:22:02 01:06:23:16 So that is a good point. 01:06:23:16 01:06:28:04 But, again is that it's getting used to that cadence 01:06:28:04 01:06:31:00 of doing manual testing on everything. 01:06:31:00 01:06:33:05 And again, what's what we're describing 01:06:33:05 01:06:35:17 with the power of that knowledge base. 01:06:35:17 01:06:37:18 Let's see some more questions. 01:06:38:17 01:06:41:06 Do people who rely on screeners on desktop 01:06:41:06 01:06:43:14 use Windows machines overwhelmingly? 01:06:43:14 01:06:46:12 Yeah, I think that's actually the case 01:06:46:12 01:06:49:16 and I think a lot of that has to do, 01:06:49:16 01:06:52:16 and I speak from my own experience, being a Californian 01:06:52:16 01:06:56:14 is that Department of Rehabilitation here in California 01:06:56:14 01:07:01:01 will not purchase Mac desktop computers 01:07:01:01 01:07:02:23 for visually impaired people. 01:07:02:23 01:07:06:05 So the state bought my family only Windows computers 01:07:06:05 01:07:07:08 through the years. 01:07:07:08 01:07:09:12 So I think that there's a connection there. 01:07:11:12 01:07:13:24 Now, you discussed testing with screeners quite a bit, 01:07:13:24 01:07:15:14 but I'm wondering if the tester isn't familiar 01:07:15:14 01:07:17:09 with WCAG Success Criteria 01:07:17:09 01:07:22:09 and how screener interacts with the accessibility API. 01:07:22:14 01:07:24:20 Is screen reader reading testing results 01:07:24:20 01:07:26:24 more usability testing? 01:07:26:24 01:07:29:12 If so, how do you report this? 01:07:29:12 01:07:32:08 No, I don't consider screen reader testing 01:07:32:08 01:07:34:21 to be usability testing. 01:07:35:24 01:07:40:01 Because again, it's about considering 01:07:40:01 01:07:41:16 what's announced by the screen reader. 01:07:41:16 01:07:44:11 And when you have that understanding, 01:07:44:11 01:07:46:02 that basic understanding of accessibility, 01:07:46:02 01:07:46:23 that's what we're talking about, 01:07:46:23 01:07:50:03 the most key thing is that initial training. 01:07:51:08 01:07:55:18 Then people they can make those assessments, 01:07:55:18 01:07:58:16 that I know this is an interactive development, 01:07:58:16 01:08:00:08 it should be announced as interactive. 01:08:00:08 01:08:02:15 And course this is not a good label, 01:08:02:15 01:08:05:05 those kind of questions, but it is a good question. 01:08:05:05 01:08:08:14 Now someone says, definitely recommend making accessibility 01:08:08:14 01:08:10:09 a precondition for purchase 01:08:10:09 01:08:13:12 and having it independently validated before buying. 01:08:13:12 01:08:16:19 Yes, I agree, that is great, if it is possible, 01:08:16:19 01:08:19:09 especially if you are at a major organization, 01:08:19:09 01:08:20:14 a major corporation. 01:08:20:14 01:08:22:14 You actually do have significant leverage 01:08:22:14 01:08:24:02 to make those kind of requests 01:08:24:02 01:08:26:06 if you do it before purchasing the product. 01:08:27:11 01:08:30:06 And yes, I strongly advise against overlays. 01:08:32:05 01:08:36:16 Yeah, accessibility is you can't automate something 01:08:38:18 01:08:39:21 you don't understand. 01:08:39:21 01:08:42:06 That's what I always say with these overlays and things. 01:08:42:06 01:08:47:06 So they exist for convenience and it doesn't make sense. 01:08:48:17 01:08:51:10 Someone even that doesn't understand technology 01:08:51:10 01:08:54:25 thinking with empathy, people have their own technology, 01:08:54:25 01:08:56:17 their own ways that they interact 01:08:56:17 01:08:57:14 with the world around them. 01:08:57:14 01:09:00:08 Imagine if you went into a store and they said, 01:09:00:08 01:09:03:14 actually, please use our pair of glasses, 01:09:03:14 01:09:07:02 our wheelchair salon, it'd be a ridiculous request. 01:09:07:02 01:09:09:17 And that's what the overlays are doing in a sense. 01:09:09:17 01:09:13:10 So yeah, thanks for reminding us of that. 01:09:14:09 01:09:17:03 Now, last question says, when do you use a domain scan 01:09:17:03 01:09:19:17 and when do you use the user-flow scan in ARC? 01:09:19:17 01:09:22:12 And is there any special setting required 01:09:22:12 01:09:27:10 from application code side to use a domain scan? 01:09:28:12 01:09:32:09 ARC can test everything 01:09:32:09 01:09:34:10 that really occurs within a web browser. 01:09:36:11 01:09:40:01 So even if it's on a VPN or some private thing, 01:09:40:01 01:09:42:02 we have a lot of ways to reach that. 01:09:42:02 01:09:44:16 Now, when to use a domain scan versus a user-flow, 01:09:44:16 01:09:48:05 domain scan is for again, the overall health of a site, 01:09:48:05 01:09:50:12 it's the easiest way to start getting results. 01:09:50:12 01:09:53:14 And it's the top level of analysis. 01:09:53:14 01:09:56:17 Like, hey, here's our score, but it's just a score, 01:09:56:17 01:10:00:16 it's just something to facilitate communication internally 01:10:00:16 01:10:02:12 as an organization. 01:10:02:12 01:10:06:10 I think you use a user-flow for every site 01:10:06:10 01:10:08:05 where there's template, where there's components 01:10:08:05 01:10:09:13 that are reused throughout site. 01:10:09:13 01:10:12:20 So again, the nav bar, that's when to use a user-flow 01:10:12:20 01:10:15:08 because you can select specific components. 01:10:15:08 01:10:17:16 I think you use a user-flow when you know 01:10:17:16 01:10:21:04 that there is content that only appears based on user action 01:10:21:04 01:10:26:01 because a domain scan in ARC works the same way 01:10:26:01 01:10:29:07 as Google Lighthouse used to do or still does, 01:10:29:07 01:10:31:07 which is it just evaluates the page 01:10:31:07 01:10:33:08 as it appears on page load. 01:10:33:08 01:10:35:16 So anything that is dynamically triggered 01:10:35:16 01:10:38:03 would not be evaluated in a domain scan 01:10:38:03 01:10:41:08 or again, the Google Lighthouse scan. 01:10:42:05 01:10:46:13 So that's when you use the user-flow 01:10:46:13 01:10:49:22 is when you know that there is content that is significant, 01:10:49:22 01:10:53:16 that only appears based on user initiated action. 01:10:53:16 01:10:55:15 So those are the situations. 01:10:57:21 01:11:00:24 All right, everyone, so that's the extent of our question. 01:11:00:24 01:11:02:16 Thank you for sharing them. 01:11:02:16 01:11:07:01 We'll share the recording later today, as well as the slides 01:11:07:01 01:11:11:19 and I wanna get back to that question. 01:11:11:19 01:11:13:05 Someone asked about a good roadmap. 01:11:13:05 01:11:16:09 I think that's a great thing to share with everyone. 01:11:16:09 01:11:19:04 All right, everyone, so enjoy the rest of your day, 01:11:19:04 01:11:20:12 thanks for attending. 01:11:23:17 01:11:25:22 Feel free to connect with me on Twitter or LinkedIn, 01:11:25:22 01:11:28:23 and so on, I'd be happy to hear from you. 01:11:28:23 01:11:31:12 All right, everyone, have a good one, bye-bye.