atronse
commented
3 weeks ago @andyyanggov this is the ticket for role management. It needs some details but I believe the idea is that from the Dashboard screen, a Property Host/ Strata Hotel/ Platform would be able to add or remove any of the roles that were assigned/unassigned previously (they need to retain a minimum of one)
mbertucci
📖 User Story
As a user who has realized that I have selected the wrong role (either platform or host) I want to go back and change my selected role if I realize I have chosen the wrong one,
so that I can ensure I am submitting the application under the correct role.
Context:
This feature allows users who have navigated to either the Platform Dashboard, Host Dashboard, or Host Application Form to go back and change their selected role. However, this option is only available if the user has not yet submitted any applications under the currently selected role. This ensures that users can correct mistakes in their role selection without compromising the integrity of submitted applications.
🎨 UX/UI Link: https://www.figma.com/design/R9GF5wvwq2TrnbnsbhPfvV/STR-Application-Tickets?node-id=6866-24402&t=ZCmTngyqaj41bG09-1
Roadmap and Storymap links
Roadmap: STRR Application and Registration Roadmap - Miro Story Board: STRR Application and Registration Story Map - Miro📏 Business Rules
🎭 Story Scenarios
Scenario 1: Navigating to the Manage Role Screen without Submitted Applications
Given a user has navigated to either the Platform Dashboard, Host Dashboard, or Host Application Form,
When the user realizes they selected the wrong role and navigates back to the "Manage Role" screen,
Then the user can change their selected role,
And the new role will display a blue check mark (✔️) to indicate it is selected.
Scenario 2: Attempting to Change Role After Submitting an Application
Given a user has submitted an application under the currently selected role,
When the user tries to navigate back to the "Manage Role" screen to change their role,
Then the system must prevent the user from changing roles,
And the screen must display a message explaining that roles cannot be changed due to existing submitted applications,
And the current role will continue to display a blue check mark (✔️).
Scenario 3: Changing Roles Before Submitting an Application
Given a user has selected a role but has not yet submitted any applications,
When the user navigates back to the "Manage Role" screen,
Then the user can select a different role,
And the newly selected role will display a blue check mark (✔️) to indicate it is active.
Scenario 4: Role Change Retention After Navigation
Given a user has successfully changed their role,
When the user navigates back to the "Manage Role" screen via the breadcrumb trail,
Then the screen must display the newly selected role with a blue check mark (✔️),
And the previously selected role should not be active.
Scenario 5: Role Selection with No Previous Applications
Given a user is selecting a role for the first time,
When the user selects either "Host" or "Platform" on the "Manage Role" screen,
Then the selected role will display a blue check mark (✔️) to indicate it is active,
And the user can proceed with their application or dashboard navigation.
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.