bcgov / bcgov/cas-reporting

Accessibility: add underline to hyperlink style + logout button

Open
#647 0 comments 0 reactions 0 assignees View on GitHub
BACKLOG Design Backlog Task
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

#### Describe the task
Style all links so they meet accessibility standards by underlining or using other styling that's appropriate such as underline appearing on hover (links in the footer) or buttons (for logging out).

#### Acceptance Criteria: Log out in header

- [ ] Change the link 'Log out' to a button (white button, blue font)

#### Acceptance Criteria: Underline links header/footer/breadcrumbs

- [ ] User's name (remove bold)
- [ ] Links in footer
- [ ] All breadcrumb links

#### Acceptance Criteria: Underline links in application

- [ ] Dashboard: all links in tiles
- [ ] Administration > Operations: Links in 'Facilities' and 'Actions' columns
- [ ] Administration > Contacts: Links in 'Actions' column
- [ ] Reporting > Submit report > Review operator information: 'Administration'
- [ ] Reporting > Submit report > Person responsible: 'Contacts'
- [ ] Reporting > Submit report > Facilities: Links in 'Actions' column
- [ ] Reporting > Attachments > 'Upload attachments' - change font colour to blue link colour, keep underline

#### Additional context

Having multiple formats for links creates inconsistency, increases cognitive load for users, requires users
to guess if text is static or interactive and waste time discovering what they can do.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the header, footer, breadcrumb, dashboard, administration, reporting, and attachment views listed in the acceptance criteria. Update the specified logout control and links so their appearance and interaction match the criteria, then verify every listed location and check that the user's name is no longer bold.

Written by the indexing model from the issue text.

Assessment

Domain
accessibility, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.