Open mbertucci opened 3 months 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)
Alexis and Andy is currently designing for this
@andybcgov I've added the story
User Story
As a user who has realized that I have selected the wrong role (e.g., Platform Manager, Host, Property Manager, or Strata Hotel Manager),
I want to change my selected role if I realize I have chosen the wrong one,
So that I can ensure I am submitting applications under the correct role.
Context
This feature allows users who have navigated to the Platform Dashboard, Host Dashboard, Strata Hotel Dashboard, or Property Manager dashboard to change their selected role using the "Change Role" link at the top of the dashboard. However, this option is only available if the user has not yet submitted any applications under the currently selected role. If applications have been submitted, the "Change Role" link will not be displayed.
🎨 UX/UI Link: STR Application Tickets on Figma
🔗 Miro Links
- **Roadmap:** [STRR Application and Registration Roadmap - Miro](#) - **Story Board:** [STRR Application and Registration Story Map - Miro](#)Business Rules
Story Scenarios
Scenario 1: Changing Role Before Submitting an Application
Scenario 2: Applications exist for the user under the current account and role
Scenario 3: Role Change Retention After Navigation
Scenario 4: Role Selection with No Previous Applications
🌐 **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 site, - **Then** all interactive elements, including the **"Change Role"** link, are accessible and highlighted, - **And** I can 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 different pages and sections, - **Then** all content is fully accessible using the keyboard alone, - **And** there are no traps preventing 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 has 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 is structured with proper headings, - **And** the reading order is 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 is clearly labeled with descriptive text, - **And** instructions are 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 displays with high color contrast suitable for low vision, - **And** the layout remains 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 resizes without loss of information or functionality, - **And** the page layout adapts 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 are applied consistently across all pages, - **And** the changes persist during my entire session or until altered by me.🌍 **Global Scenarios**
### 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 loads completely within 2 seconds, ensuring a fast and efficient user experience. #### Low-Speed Internet - **Given** I access the **"Application Details View"** with a low-speed internet connection defined as under [specific speed] Mbps, - **When** I attempt to load and interact with the dashboard page, - **Then** the **"Application Details View"** prioritizes critical content and functionality, loading essential elements first to ensure usability. ### Mobile Responsiveness #### Scenario: Mobile Access to Application Details - **Given** I am accessing **"Application Details View"** on a mobile device, - **When** I click on any link, - **Then** the content displays correctly and is easily navigable on my device, ensuring a responsive design.