Skip to content

Week of 1/26 - Development Standup Thread #582

@azdak

Description

@azdak

6-Month Roadmap

Discussion

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

@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

New

  • (@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

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

Metadata

Metadata

Labels

PunchlistOmnibus thread for tracking sprint/to-do progress

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions