2.1.1 Popup Tabs- Student- Accessibility Fixes - Level A - Keyboard
- Dominant language
- TypeScript
- Stars
- 29
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
**User Story**
**As a student, I need
**Context:**
- Theses issues were uncovered through accessibility audit via CITZ.
- Detailed Spreadsheet for Student s inserted inline and also attached here: [2024_Student Application_Audit.xlsx](https://api.zenhub.com/attachedFiles/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBN0xsQXc9PSIsImV4cCI6bnVsbCwicHVyIjoiYmxvYl9pZCJ9fQ==--578821d4addd12c1babcafba5c861e1f5456bc9c/2024_Student%20Application_Audit.xlsx)
- All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.
**The Problem**
- Users should be able to tab into any popup (alert, warning, notifications) to dismiss the information on their own accord without disrupting the flow of focus.
**Student**
Adjust the following Accessibility Criteria for the following pages
- [ ] Login 1 and 2
- [ ] Profile
- [ ] Home page
- [ ] Start new application
- [ ] My applications
- [ ] File uploader
- [ ] Request a change
- [ ] Overawards balance
**Acceptance Criteria**
-[ ] In the Student Portal (pages listed above) ensure all elements that can be interacted with by mouse or trackpad can be interacted with via keyboard.

Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the Student Portal pages listed in the issue: Login 1 and 2, Profile, Home, Start new application, My applications, File uploader, Request a change, and Overawards balance. Check the attached accessibility audit for page-specific findings, then verify that popup content and all mouse-interactive elements are reachable and operable by keyboard without disrupting focus.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100