As an Examiner
I want to view LTSA information system pulled from LTSA AP
So that I can see the LTSA information to review, confirm and make decisions on the application
[x] on the application details page, examiner will see a header named "LTSA information" and a link to see more details
[x] Examiner can click on the link to get more LTSA details
[x] Once clicking on the link, a new tab will open to show the details.
[x] LTSA details will show general information (including tax authority, description of land, ownership group, joint tenancy, date when LTSA info gets pulled, PID and parcel status) and all owners on title (including given name, last name, address and occupation).
π Story Scenarios
Scenario 1:View LTSA information
Given the examiner has opened the application in read-only mode from the dashboard,
When the examiner navigates to the LTSA information section or tab
Then the examiner should see a link for more details
When the examiner clicks on the link
Then the examiner will see details information about LTSA information the system pulled and received from API call in a new tab
π Accessibility Scenarios
### Keyboard Users
Scenario: Comprehensive Keyboard Navigation
Given I am a keyboard user on the website
When I use the Tab key to navigate through the website
Then all interactive elements should be accessible and highlighted
And I should be able to activate these elements using the Enter or Space key
Scenario: Full Content Accessibility via Keyboard
Given I am a keyboard user navigating the website
When I traverse through different pages and sections
Then all content should be fully accessible using the keyboard alone
And there should be no traps that prevent me from navigating away using the keyboard
### Screen Reader Users
Scenario: Accessible Image Descriptions
Given I am using a screen reader on the website
When I encounter images
Then each image should have descriptive alt text that conveys the same message as the image
Scenario: Structured Navigation for Screen Readers
Given I am navigating the website using a screen reader
When I move through different page elements
Then the content should be structured with proper headings
And the reading order should be logical and sequential
Scenario: Descriptive Form Fields
Given I am filling out a form using a screen reader
When I navigate through the form fields
Then each field should be clearly labeled with descriptive text
And instructions should be directly associated with their respective inputs
### Low Vision Users
Scenario: Effective High Contrast Mode
Given I am a user with low vision on the website
When I enable high contrast mode
Then all content should display with high color contrast suitable for low vision
And the layout should remain coherent and unchanged
Scenario: Text Resizing Accommodation
Given I am a user with low vision on the website
When I increase the text size
Then the text should resize without loss of information or functionality
And the page layout should adapt accordingly without disrupting the user experience
Scenario: Personalized Styling Preferences
Given I am a user with low vision adjusting settings on the website
When I customize my styling preferences, including colors, fonts, and spacing
Then these adjustments should be applied consistently across all pages
And the changes should persist during my entire session or until altered by me
##
π Global Scenarios
## Data Validation
# Mikaela to confirm: Do we need to do these for MVP - data validation required for inputing data in the right format - as defined by business rules.
### Internet Connection
#### Standard Internet Connection
Given I am accessing the website from a standard internet connection
When I navigate to any page on the site
Then the page should load completely within 2 seconds, ensuring a fast and efficient user experience.
#### Low-Speed Internet
Given a user accesses "Application Details View" with a low-speed internet connection defined as under [specific speed] Mbps
When the user attempts to load and interact with the dashboard page
Then the "Application Details View" should prioritize critical content and functionality, loading essential elements first to ensure usability.
#### Mobile Responsiveness
Given I am accessing "Application Details View" on a mobile device
When I click on the "any" link
Then "_____ " should display correctly and be easily editable on my device, ensuring a responsive design.
π User Story
As an Examiner I want to view LTSA information system pulled from LTSA AP So that I can see the LTSA information to review, confirm and make decisions on the application
Context:
[add context]
π¨ UX/UI Link: https://www.figma.com/design/R9GF5wvwq2TrnbnsbhPfvV/STR-Host-Application-Tickets?node-id=4871-6780&t=SH0GF0XKUKUk6xnG-4
π Business Rules
π Story Scenarios
Scenario 1:View LTSA information Given the examiner has opened the application in read-only mode from the dashboard, When the examiner navigates to the LTSA information section or tab Then the examiner should see a link for more details When the examiner clicks on the link Then the examiner will see details information about LTSA information the system pulled and received from API call in a new tab
π Accessibility Scenarios
### Keyboard Users Scenario: Comprehensive Keyboard Navigation Given I am a keyboard user on the website When I use the Tab key to navigate through the website Then all interactive elements should be accessible and highlighted And I should be able to activate these elements using the Enter or Space key Scenario: Full Content Accessibility via Keyboard Given I am a keyboard user navigating the website When I traverse through different pages and sections Then all content should be fully accessible using the keyboard alone And there should be no traps that prevent me from navigating away using the keyboard ### Screen Reader Users Scenario: Accessible Image Descriptions Given I am using a screen reader on the website When I encounter images Then each image should have descriptive alt text that conveys the same message as the image Scenario: Structured Navigation for Screen Readers Given I am navigating the website using a screen reader When I move through different page elements Then the content should be structured with proper headings And the reading order should be logical and sequential Scenario: Descriptive Form Fields Given I am filling out a form using a screen reader When I navigate through the form fields Then each field should be clearly labeled with descriptive text And instructions should be directly associated with their respective inputs ### Low Vision Users Scenario: Effective High Contrast Mode Given I am a user with low vision on the website When I enable high contrast mode Then all content should display with high color contrast suitable for low vision And the layout should remain coherent and unchanged Scenario: Text Resizing Accommodation Given I am a user with low vision on the website When I increase the text size Then the text should resize without loss of information or functionality And the page layout should adapt accordingly without disrupting the user experience Scenario: Personalized Styling Preferences Given I am a user with low vision adjusting settings on the website When I customize my styling preferences, including colors, fonts, and spacing Then these adjustments should be applied consistently across all pages And the changes should persist during my entire session or until altered by meπ Global Scenarios
## Data Validation # Mikaela to confirm: Do we need to do these for MVP - data validation required for inputing data in the right format - as defined by business rules. ### Internet Connection #### Standard Internet Connection Given I am accessing the website from a standard internet connection When I navigate to any page on the site Then the page should load completely within 2 seconds, ensuring a fast and efficient user experience. #### Low-Speed Internet Given a user accesses "Application Details View" with a low-speed internet connection defined as under [specific speed] Mbps When the user attempts to load and interact with the dashboard page Then the "Application Details View" should prioritize critical content and functionality, loading essential elements first to ensure usability. #### Mobile Responsiveness Given I am accessing "Application Details View" on a mobile device When I click on the "any" link Then "_____ " should display correctly and be easily editable on my device, ensuring a responsive design.