1 00:00:00,000 --> 00:00:04,866 2 00:00:04,866 --> 00:00:08,866 Test Initiatives are the secret sauce in the ARC monitoring solution. 3 00:00:08,866 --> 00:00:12,866 With test initiatives you can break down your accessibility into chunks, 4 00:00:12,866 --> 00:00:16,866 prioritizing what you want to fix and when. You can even 5 00:00:16,866 --> 00:00:20,866 stagger the remediation over a period of months. 6 00:00:20,866 --> 00:00:24,866 So, to start, let's have a look at this website dashboard. 7 00:00:24,866 --> 00:00:28,866 We can see that there's been a spike in issues recently that needs to be addressed. 8 00:00:28,866 --> 00:00:32,866 If we go down to the Top Remediation Priorities 9 00:00:32,866 --> 00:00:36,866 we can see a list of the WCAG failures that ARC has already identified 10 00:00:36,866 --> 00:00:40,866 as the most widespread and critical. 11 00:00:40,866 --> 00:00:44,866 Some of these might take a while to fix, while some of them straightforward. 12 00:00:44,866 --> 00:00:48,866 For example, this iFrame without a title issue has only 13 00:00:48,866 --> 00:00:52,866 fifty-eight instances and is technically quite simple. Let's address that first. 14 00:00:52,866 --> 00:00:56,866 Test Initiatives live 15 00:00:56,866 --> 00:01:00,866 in the Performance Summary panel. The score here is a rollup 16 00:01:00,866 --> 00:01:04,866 of all the initiatives for this site. So out of 4 initiatives 17 00:01:04,866 --> 00:01:08,866 we have 79% overall progress. 18 00:01:08,866 --> 00:01:12,866 They're moving along nicely. Let's take a look. 19 00:01:12,866 --> 00:01:16,866 To create out initiative, we'll choose 'Add a New Initiative'. 20 00:01:16,866 --> 00:01:20,866 Give the initiative a title. I'll call it 21 00:01:20,866 --> 00:01:24,866 'Fix iFrame Issue', just to be clear. 22 00:01:24,866 --> 00:01:28,866 The target date is your goal for completion. I'll make the 31st of next month. 23 00:01:28,866 --> 00:01:32,866 This should be doable. The baseline scan 24 00:01:32,866 --> 00:01:36,866 is your level-set for the initiative. Where do you want to measure progress from? 25 00:01:36,866 --> 00:01:40,866 Since we were looking at the latest scan, let's use that as the baseline. 26 00:01:40,866 --> 00:01:44,866 The rule is our iFrame 27 00:01:44,866 --> 00:01:48,866 title rule. Now here is the key part. 28 00:01:48,866 --> 00:01:52,866 The policy. You can select from three. Zero Tolerance 29 00:01:52,866 --> 00:01:56,866 which means you want to eliminate the issue. Sustain Conformance 30 00:01:56,866 --> 00:02:00,866 meaning don't let it get any worse, or Percent Improvement. 31 00:02:00,866 --> 00:02:04,866 For this last policy, you can set a percentage and the issue 32 00:02:04,866 --> 00:02:08,866 should improve by that percentage with each scan. We're going to 33 00:02:08,866 --> 00:02:12,866 choose Zero Tolerance because we really should be able to eliminate the problem 34 00:02:12,866 --> 00:02:16,733 entirely from the site. All you need to 35 00:02:16,733 --> 00:02:20,733 do then is Submit and there you have your initiative. 36 00:02:20,733 --> 00:02:24,733 You can see we have a bunch of them already. Some of them on track and some of them off. 37 00:02:24,733 --> 00:02:28,733 This is a great way to watch the remediation effort 38 00:02:28,733 --> 00:02:32,733 and intervene if things are not moving along. A practical way 39 00:02:32,733 --> 00:02:36,733 to address accessibility. You can create initiatives 40 00:02:36,733 --> 00:02:40,733 that include more than one issue and policy. For instance, here we have 41 00:02:40,733 --> 00:02:44,733 a Fix Keyboard Problems initiative. It features 42 00:02:44,733 --> 00:02:48,733 two different keyboard issues, each with different policies applied. 43 00:02:48,733 --> 00:02:52,733 By putting them together in this way, you can target specific users or tasks or issue groups. 44 00:02:52,733 --> 00:03:00,733 Lastly, you can call these initiatives through the ARC API. Instead of giving 45 00:03:00,733 --> 00:03:04,733 your developers a full set of accessibility bugs to fix in one go, 46 00:03:04,733 --> 00:03:08,733 target these initiatives by embedding them in their pipeline. 47 00:03:08,733 --> 00:03:20,666 Set a gate at the commit stage and you developers will have to ensure their iframes are titled before releasing code. You can then monitor whether they are on track or off track right here in the ARC dashboard.