Closed (fixed)
Project:
Accessibility Scanner
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
19 Mar 2019 at 15:15 UTC
Updated:
13 Apr 2019 at 02:19 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
WidgetsBurritos commentedDepends on #3042687: Dispatch event upon job completion
Comment #3
WidgetsBurritos commentedThis is a POC patch based on the work done in #3042687: Dispatch event upon job completion. Obviously we'd want to do something more meaningful with the report, but this shows the event subscriber will work.
For example, I just generated the following output:
{"total":26,"pass":0,"fail":26,"num_of_errors":52,"num_of_likely_problems":26,"num_of_potential_problems":104,"guidelines":{"BITV 1.0 (Level 2)":"BITV 1.0 (Level 2)"}Comment #4
WidgetsBurritos commentedOkay #3042687: Dispatch event upon job completion has been merged in so we're good to proceed with this task further.
Comment #5
WidgetsBurritos commentedStill a work in progress but just uploading the latest version of the patch for visibility. This has obvious issues around code styling and things of that nature, but it does the necessary work of storing the results into the DB and provides a simple method for retrieving results.
The next step would be to take these results and output them somewhere. Maybe with a chart (although that might be a separate issue).
We may also want to think about notification services as well (probably should be handled in a separate issue).
Comment #6
WidgetsBurritos commentedThis continues to be a work in progress, but here's the next iteration of this functionality. There's still a bit of room for cleanup and testing here, but just want to get the latest patch uploaded.
Comment #7
WidgetsBurritos commentedI provided an interdiff, but honestly it's long enough, reading the patch itself may just be the easier way of reviewing this.
This is a heavy change, but it should mostly be pretty straightforward.
Comment #9
WidgetsBurritos commentedSo apparently WPA 8.x-2.7 was tagged, but never officially released. I just released the version, but given that dependency I'm gonna mandate WPA 2.7+ for this module in case anyone decides to use it who already has WPA installed.
Comment #10
WidgetsBurritos commentedComment #11
WidgetsBurritos commentedResolving a few issues found with @vessel_adrift during a crash session on this patch.
Comment #12
vessel_adrift commented+1 rtbc
Comment #14
WidgetsBurritos commented