Week of 3/9 - Development Standup Thread

[azdak]

6-Month Roadmap
Hung Scan Postmortem

New

• (2/18 roadmap meeting) Need to add specifics on which rulesets veraPDF and axe-core are using to scan to documentation
  • PDF: PDF/UA-2, ISO 16684-2
  • HTML: Default Axe-Core ruleset, with additional checks for empty alt tags for images and warning for any PDF link
• (@azdak proposed 3/4) Evaluate https://github.com/EqualifyEverything/equalify-uic-utilties
• (@azdak proposed 3/5) Better loading state for summary view; on large scans it can take a bit to update (which can be refactored later) but in the meantime should have better feedback for the user that it's loading
• (Michael 3/5) Inconsistent Last Scan Date #589
• (Michael 3/5) Email Notification Not Sent #590 Double-check email delivery fix is working
• (@azdak / @heythisischris proposed 2/4) Add wiki-style issue descriptions for blocker page, potentially open-source repo.
• (Optional/modular) LLM for single blocker issue description and next steps generation
• After testing Remote CSV, merge into main

Outstanding

@azdak To Dos:

• (@azdak proposed 2/9) Audits screen: Add Sort by to table view

@heythisischris To Dos:

• (From 2/5 Service Team Meeting) Look into production email deliverability (reported from testing)
• (proposed 1/22) Fix URL for prod Hasura
• Coordinate meeting w/ Helen & Michael on documentation workflow AND ask about how Equalify communications are handled, what team is responsible, and how we can properly coordinate updates / FAQ / etc.
• Monthly reporting; need Hub functionality for this and to get on a regular schedule
  • Ability to collect and report on KPIs from 1st of each month
  • First report delivered March 1st, 2026
  • Should be able to take in markdown content and format pretty, export to PDF (we can even re-use Equalify Hub Updates page template)
  • It's just like updates, but we are calling it REPORTS. equalify-docs/reports.
• Have a conversation with Blake & Dean to separate out PDF costs from Equalify costs in AWS account, also get a sense of what our cost ceiling is, limits, their recommendations, etc.
• Work on DB Schema version control and Hasura metadata version control
• (@azdak proposed 3/4) Testing for CSV integration prior to merge

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?)