bcgov / bcgov/entity

Strata Hotel User - Terms of Service

Open
#23,478 0 comments 0 reactions 0 assignees View on GitHub
STR CHEFs
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

### 📖 User Story

**As a team lead, I want the Strata Hotel user to either accept or decline the "Terms of Service" right after they log in with BC Services Card Account, so that I know Strata Hotel users acknowledge that they understand and agree to the rules of using the service.**

### Context:

[Add context here]

### 📏 Business Rules

- [ ] Check if the Terms of Service (TOS) has been updated; if changed, all users (new and existing) must accept the new terms.
- [ ] Existing SBC Connect accounts that have not accepted the TOS must accept it before they get to the account selection screen.
- [ ] Users must accept the TOS if they haven't accepted it before.
- [ ] New accounts cannot proceed to the next step—create or select an account in SBC Connect—if they don't accept the TOS.
- [ ] HOUS Staff (e.g., examiners) do not need to accept the TOS.

### 🎭 Story Scenarios

**Scenario 1: Authenticated and Logged in to STR**

- **Given** the Strata Hotel user has been authenticated via SBC Connect,
- **When** it's the first time for the user to log in or use the service,
- **Then** the user needs to view the Terms of Service.

**Scenario 2: Accept TOS**

- **Given** the Strata Hotel user has logged into SBC Connect,
- **When** the user accepts the Terms of Service,
- **Then** the user will proceed to the application form.

**Scenario 3: Decline TOS**

- **Given** the Strata Hotel user has logged into SBC Connect,
- **When** the user decides to decline the Terms of Service,
- **Then** the user will not be able to proceed to the application form.

**Scenario 4: TOS Has Been Updated**

- **Given** the Strata Hotel user has previously accepted the Terms of Service,
- **When** there is a new version of the Terms of Service,
- **Then** the user will view the new version of the Terms of Service,
- **And** the user will have to accept the new version in order to start a new application or go to their dashboard.

### Accessibility Scenarios

#### Keyboard Users

**Scenario 5: 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 6: 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 7: 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 8: 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 9: 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 10: 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 11: 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 12: 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.

---

**Note:** For global scenarios and additional details, please refer to the appropriate documentation.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.