Week of 2/2 - Development Standup Thread

[azdak]

6-Month Roadmap

Discussion

• Monthly reporting; should probably do first one this week (and in the first week of the month going forward), prior to the DASE all-hands Feb 9
• Hanging scans: eg this or this
• Test Scheduled Scan (see this)
• Do we want to pre-screen the questions/issues from the intro talk?

Outanding

@azdak To Dos:

• Simplified View of Audit/Blockers Table (from Modified View for End Users - Short term #573 and Modified Functionality for Different User Roles #574). Asked service team for thoughts on what is mission-critical info for reports going to Accessibility Liaisons, etc.
• (@azdak proposed 1/12) New Blocker endpoint, takes Blocker ID as query string, returns blocker with URL, info on how to solve, etc. Link to this Issue on audit blockers table
• Blocker endpoint: Make endpoint public, set external URL flag on link, code should wrap
• WP Plugin spec for @bbertucc
• (@azdak proposed 1/26) Toggles for Blocker Table Columns
• (@azdak proposed 1/26) Blockers Table Simplified View:
  • X of Y pages have accessibility errors. The average page has x.x accessibility errors. Pages with most error
  • The most common accessibility errors:
    | Table |
  • The most common tag/category of error (table w/ count?)
• (From 2/5 Service Team Meeting) Fix code styling in blockers table
• (From 2/5 Service Team Meeting) Fix header, footer menu color contrast
• (From 2/5 Service Team Meeting) Fix audit frequency changer (can't change atm)
• (From 2/5 Service Team Meeting) Audits page filtering
• (From Jemma) Add Y axis to blockers graph

@heythisischris To Dos:

• Debug hung scan errors. Simplest repro is deleting a URL from an audit and then scanning causes a hang, but also should do more testing to trigger hung scan state.
• Equalify Hub v1
• Raga Job Description
• (@azdak proposed 1/12) CSV export for Blocker table
• (@azdak proposed 1/20) Quick scan
• (proposed 1/22) Fix URL for prod Hasura
• (@azdak proposed 1/26) Fix window snapping on filter changes
• (@azdak proposed 2/2) "Not scanned" state for audit screen
• (From 2/5 Service Team Meeting) Look into production email deliverability (reported from testing)
• Add "updates" to Equalify Hub with latest Q&A responses (https://equalify.uic.edu/updates)
• (From 2/5 Service Team Meeting) Add details about how crawling works in Equalify vs other tools
• (From 2/5 Service Team Meeting) Add documentation on user roles to the Equalify Hub

New

• (@azdak / @heythisischris proposed 2/4) Add wiki-style issue descriptions for blocker page, potentially open-source repo.
• (@azdak proposed 2/6) Switch blockers table "Active/Ignore" and "HTML/PDF" filter controls to select boxes instead of custom styled (this should add some more visual uniformity and make styling simpler when we later do a more comprehensive restyle)

Future Sprints

(pending development priority decision, and in no particular order)

FOSS Sprint aka Infrastructure Week (1-2 weeks)

• Determine IaC/Provisioning Framework (Terraform, OpenTofu, whatever): This allows any user to be able to deploy, provisioning the script to run on any external environment.
• Create BUILD SCRIPTS 💀: This sets a template to get the code onto servers that are provisioned.
• Determine deployment strategy: Figure out how to handle deployment
• Provisioning & Deployment Documentation: Technical documentation for deployment
• User Documentation: Developer-focused Readme to introduce how to use the app from a high level.

Design & Maintenance Sprint (1-2 weeks)

• Get alignment on overall visual direction and palette
• Branding: Defining how branding is handled on the system.
• Design System: Atomic system or Storybook for component uniformity
• Darkmode 😎
• Mobile breakpoints
• Style and Code Cleanup: Finish componentizing, minimize global styles, and code cleanup

Onboard Features Sprint (1-2 weeks)

• Site onboarding features
  • Lambda for site crawling
  • Integrate onboarding features into Build Audit
• Allow external, linked CSVs as basis for Audit URLs (with regular or just-in-time on-scan re-scrapes), allowing WordPress plugin integration
• CSV User import

Backlog/Blocked

• Help text first pass
  • ID icon areas
  • Refactor HelperTooltip component
  • Write help text
• Integrate error reporting into "blockers over time" scans table (also possibly the graph?)

[azdak]

Closed in favor of #585