Midpoint Review - Accessibility Feedback - Modernized Check-in, Appointments, Travel Claims for Past Appointments

[briandeconinck]

Next Steps for the VFS team

• [x] Assign this ticket to the team member(s) responsible for addressing feedback provided by Platform.
• [x] Comment on this ticket:
  • If the Platform reviewer has any Thoughts/Questions that require responses.
  • When Must feedback has been incorporated. As appropriate, link to any other GitHub issues or PRs related to this feedback.
  • When Should/Consider feedback has been incorporated, or if any feedback will not be addressed. As appropriate, link to any other GitHub issues or PRs related to this feedback.
• [x] Questions? For the most timely response, comment on Slack in your team channel tagging @platform-governance-team-members.
• [x] Close the ticket when all feedback has been addressed.

Thoughts/questions

• Sorry for the delayed feedback, and thank you for your patience.
• Overall this looks great, no major concerns!
• In the meeting I said I'd give you some coding notes, but then looking closer I see that the notes I would give are already included in an annotation in Figma! I totally forgot what I said at Design Intent, glad you all remembered! 😄

Feedback

Practice areas will document their feedback on the VFS-provided artifacts following the Must, Should, and Consider Framework. Platform Governance reviewers may also provide additional notes that don’t comment on the artifacts themselves but are important for implementation (eg. engineering/coding notes).

• [x] Must: On the details page, be careful about heading structure. Visually, it looks like it's structured as:

  • H1: Your travel reimbursement claim...
    • H2: Claim number: TC...
      • H3: Where
      • H3: Claim status: In Process

  Since there's only one claim on the details page, I don't think it makes sense for the claim number to actually be a heading, though, since it's not distinguishing a section of content from another section on the page. Totally fine for the claim number to be big text and prominent on the page, but just make sure the coded headings describe the structure of the content as well.

Governance team actions

• [x] Format feedback as individual tasks (check boxes)
• [x] Assign this ticket to the VFS team member that opened the Slack request
• [x] Add the VFS team product label
• [x] Add the VFS team the feature label (if applicable)
• [x] Add the touchpoint labels
• [x] Add the practice area labels
• [x] Add the Collaboration Cycle initiative milestone

[loripusey]

Hey team! Please add your planning poker estimate with Zenhub @benbrasso-agile6 @zach-park @cgednalske

[benbrasso-agile6]

@briandeconinck what page are you looking at? I feel like you might be looking at something that is outdated.

[benbrasso-agile6]

Oh I got it

[benbrasso-agile6]

@micahtaylor this one's yours

[micahtaylor]

Documented in the Figma file for engineering handoff.