search

EqualifyEverything / equalify

A web accessibility platform, managing issues by integrating with A11Y services.
https://equalify.app
Other
117 stars 21 forks source link

Rollercoaster Equalify Statistics Over Time #486

Open bbertucc opened 4 days ago

bbertucc commented 4 days ago

Overview

This page wasn't updated to the best of Joel's knowledge. Why is there a rollercoaster? New issues shouldn't have been added or fixed after the fact. What went wrong where? And how can we fix it?

Here is the URL: https://registrar.duke.edu

Here is a screenshot:

Screenshot 2024-11-18 at 1 41 38 PM

Bountied

Since this is a bountied issue, Assignees should post an estimate that is then approved as per this note in the handbook: https://github.com/EqualifyEverything/handbook?tab=readme-ov-file#how-are-bounties-budgeted

heythisischris commented 3 days ago

@bbertucc This one is tricky... deals with how we're processing scans in general. We'll have to run through the lifecycle of a scan, test, and see what's going on. My hunch is 6 hours.

bbertucc commented 3 days ago

@heythisischris would it help if we approve an hour or two for investigation to get at a better understanding of what is going on? I imagine we'll need to run the URL over 2-3 different days and track where the issue is starting before you come up with a fix.

If that is the case, I would be curious to know what you're looking at over the amount of time you need to determine where the issue is.

bbertucc commented 1 day ago

@heythisischris said that 2 hours is reasonable on our call to get a sense of the problem. He'll then post a summary of the problem and additional notes on how to fix with a budget for that. Approved.