mbertucci
commented
8 months ago For future accessibility iteration:
- [ ] Scenario 4: Visual Impairment
Given a host with visual impairments is logged in and authenticated. When the user navigates to the dashboard page. Then the dashboard should be fully compatible with screen readers, ensuring all text, links, buttons, and images (with descriptive alt text) are accessible. And the layout should be navigable through keyboard shortcuts alone, allowing users to access all dashboard features without the need for a mouse. And any interactive elements like modals or dropdowns should announce themselves to the screen reader, with clear instructions on how to interact with them. And the dashboard should adhere to WCAG (Web Content Accessibility Guidelines) Level AA, ensuring contrast ratios, font sizes, and navigation order support users with different types of visual impairments.
As an individual host, I want to edit my host contact and address and information in my profile so that the examiner reviewing my file knows how to contact me if they have any questions
Scenario 1: Access Profile page Given the user is on the STR application page, When the user clicks My profile button, Then they should be directed to the My profile page, And the profile page displays their current contact and address information populated from SBC-Connect.
Scenario 2: Update Contact Information Given the user is on the contact and address information page, When the user selects the "Edit" button, Then they should be able to click a Edit button for making changes And the address and contact information can be edited
Scenario 3: Automatic Saving of Contact Information Given the user has edited their contact or address information, When the user pauses for 2 seconds after typing, Then the system automatically saves the changes, And a notification or visual cue confirms the successful save.
Scenario 4: Manual Save Contact Information Given the user has edited their contact or address information but has not triggered the automatic save, When the user selects the "Save" button, Then the system saves the changes, And the updated contact and address information is reflected on the profile page.
Scenario 5: Language Selection (Alexis I am not sure if we can do this or not and it would be great to see if we can) Given the user is on any page within the STR application, When the user selects their preferred language from the language dropdown, Then the application content is dynamically updated to reflect the selected language.
Scenario 8: Submitting Feedback Given the user wants to provide feedback on the application, When they select the "Feedback" option from the main menu, Then they are directed to a feedback form where they can submit comments, And upon submission, their feedback is securely transmitted to the product team.
Scenario 9: Security and Privacy of Information Given the user submits or updates their contact information, When the data is transmitted over the internet, Then the transmission is secured via HTTPS, And the information is stored in compliance with relevant data protection regulations.
Scenario 10: Optimizing Dashboard for Users with Low Internet Connectivity Given a host accesses the dashboard with a low-speed internet connection. When the user attempts to load and interact with the dashboard page. Then the dashboard should prioritize critical content and functionality, loading essential elements first to ensure usability. And the page should implement efficient data usage strategies, such as compressing images, using caching for repeat visits, and minimizing the load of heavy scripts. And the interface should provide feedback on loading progress for interactive elements, informing users of the current status and expected wait times. And an option should be available for users to access a more simplified version of the dashboard that requires less bandwidth, ensuring that users can perform their necessary tasks even under constrained internet conditions.
Accessibility Scenarios
Scenario 11: Scenario: Navigating through interactive elements using the Tab key
When the user presses the "Tab" key repeatedly Then the focus should move through all interactive elements in a logical order And the currently focused element is visually highlighted
Scenario 12: Using the "Skip to Main Content" link Given the "Skip to Main Content" link is the first focusable element When the user presses the "Tab" key once And the user presses the "Enter" key Then the focus moves directly to the main content area
Scenario 13: Scenario: Interacting with form fields using the keyboard Given the user has navigated to a form with multiple input fields When the user presses the "Tab" key to navigate through the input fields And enters data using the keyboard And presses the "Enter" key after filling out the form Then the form data is submitted And the user receives confirmation through keyboard-accessible feedback
Scenario 14: Scenario: Navigating dropdown menus using arrow keys Given the user has focused on a dropdown menu When the user presses the "Down Arrow" key Then the dropdown expands And the user can navigate the options with the "Up Arrow" and "Down Arrow" keys When the user presses the "Enter" key on an option Then the option is selected And the dropdown collapses
Scenario 15: Closing modals using the Escape key
Given a modal window is open and focused When the user presses the "Escape" key Then the modal closes And focus returns to the element that opened the modal
Scenario 16: Scenario: Navigating paginated content using keyboard shortcuts
Given the user is viewing a page with paginated content When the user presses a predefined keyboard shortcut for "next page" Then the next page of content is displayed And focus is set to the top of the new page content When the user presses a predefined keyboard shortcut for "previous page" Then the previous page of content is displayed And focus is set to the top of the new page content
Text Fields:
First Name: [Required] Full name of the user. Last Name: [Required] Full name of the user. Address: [Required] Mailing address, with separate fields for street, city, state/province, and zip/postal code. Email: [Required] User's email address, with format validation. Phone Number: [?] User's primary contact number. Fax Number: [?] User's fax number, if applicable.
The following should be moved to the property section part of the application Housing Status: [Required] Dropdown selection for Own/Rent/Other.
The next should be moved to the documentation part of the application BC Business Number/GST Registration Number: [Optional] If applicable, for users conducting business.