Request Appointment- Create UI screen 'Facility Type'

[MekoHong]

Description

As a Veteran, who is registered at both VA Facilities & Community Care Centers, I want to have the option to select (when eligible ) to receive my treatments at the VA or Community Care.

As part of this story we want to:

• We will need to create a new screen for a user to select where they want to receive care VA facility or Community Care when the option is available

  Data Schema

  API Docs: https://department-of-veterans-affairs.github.io/va-mobile-app/api/#operation/CreateNewAppointment

  Field name: kind Values:

  [
  {
  "label": "VA medical center or clinic",
  "value": "va"
  },
  {
  "label": "Community care",
  "value": "cc"
  }
  ]

  Note: If va is selected, they will be taken to the Visit Type screen where they will choose between clinic, telehealth and home, which will overwrite the va value in our form data.

  Acceptance Criteria

  **Screen Fields and elements** 1. - [ ] Create UI Screen Facility Type 2. - [ ] Verify 'Cancel' is displayed at the top left corner of the screen 3. - [ ] Verify ? help icon is displayed at the top right of the screen 4. - [ ] Verify Title Header reads: Where would you like to receive care? 5. - [ ] Verify the following Radio Button list of Facility Type options are displayed

• [ ] VA medical center or clinic

• [ ] Community care

  6. Verify action buttons Back and Continue are shown on the bottom of the page

  Accessibility Requirements

  Requirements

  1. For all lists with more than 1 option/result, screen reader should specify count of each option as it reads the option

  Example: V-A medical center or clinic, option 1 of 2 Community care, option 2 of 2

  2. Screen reader should read VA in 'VA medical center or clinic' as an acronym.

  3. Cancel AccessibilityHint: Cancel Appointment request

  4. Help icon - AccessibilityHint: Get scheduling help

  5. Continue Button AccessibilityHint: Navigate to the next page

  6. Back Button AccessibilityHint: Navigate to the previous page

  Standard:

  1. Everything on the page should be read by the screen reader. If anything is being conveyed visually only (buttons, menu items, list, tables, images, headings, forms, etc) the component type needs to be announced by the screenreader. (Include name (title), role, value) Each page should support text resizing based on the OS font scaling settings without loss of content, content overlap, or horizontal scroll.

  2. Each touch target must be at minimum 44px by 44px

  3. All elements on a page should be able to be traversed by an auxiliary keyboard. As a user uses the keyboard to navigate a page, its focus element should be clear.

  4. The app needs to support operability by tap (no gestures) or voice control only. In cases where gestures occur, e.g. scroll, ensure these simple gestures are operable through the OS’ built-in capabilities.

  Wireframe Sketch-Facility Type

  

  Notes & Open Questions

• Dependencies/Roadblocks:

• Any internal/external dependencies?

• Test accounts needed?

• Does this require QA?

• Dev Notes:

  Ticket Checklist

• [X] Acceptance criteria defined

• [X] Labels added (front-end, back-end, feature)

• [X] Linked to an Epic

[TKDickson]

Test run 3463

[MekoHong]

Closing ticket, feature not being currently worked and due to lapse in time it was decided to close all scheduling tickets. No testing of tickets and will revisit in future