Skip to content

Commit

Permalink
Fix typo and remove scare quotes
Browse files Browse the repository at this point in the history
  • Loading branch information
paulrobertlloyd authored and colinrotherham committed Oct 9, 2023
1 parent fc700dc commit 9dec1aa
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions src/components/task-list/index.md.njk
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ Only use hint text if there is evidence that the user needs more information abo

Keep hint text to a single, short sentence. Screen readers read out the entire text when users interact with the task link. This could frustrate users if the text is long.

Do not include links within the hint text. The whole task row links users to the task itself, so any links within the hint text will not work.
Do not include links within the hint text. The whole task row links users to the task itself, so any links within the hint text will not work.

#### Grouping tasks

Expand All @@ -82,23 +82,23 @@ Read the [complete multiple tasks pattern guidance](/patterns/complete-multiple-

This component was created by a cross-government group using research from the existing task list pattern.

### Linking the whole task row to the task
### Linking the whole task row to the task

User feedback from the task list pattern has shown that some users currently try to select task statuses, thinking they are buttons or links. The statuses have been redesigned to look less like buttons, and now the whole task row is linked so that users can select anywhere within it to enter and begin the task.
User feedback from the task list pattern has shown that some users currently try to select task statuses, thinking they are buttons or links. The statuses have been redesigned to look less like buttons, and now the whole task row is linked so that users can select anywhere within it to enter and begin the task.

### Formatting of statuses

The use of uppercase in task statuses makes them harder to read. User research has also shown that once a few tasks have been completed, it is harder for users to scan the page and spot incomplete tasks.

Statuses are now written in sentence case to make them easier to read. The ‘Completed’ task now uses black text with no background colour, which will draw more attention to asks that require action.
Statuses are now written in sentence case to make them easier to read. The ‘Completed’ task now uses black text with no background colour, which will draw more attention to tasks that require action.

We have also introduced a new colour palette for statuses, using colour contrasts that meet accessibility guidance.

### Known issues and gaps

While this new component is based on user research from the task list pattern, we still need to carry out user testing with this new component. In particular, we would like to test the following assumptions:

* the benefits of linking the whole task row outweigh the risks of accidental clicking
* the benefits of linking the whole task row outweigh the risks of accidental clicking
* the contrast of the statuses is sufficient
* the suggested wording of the statuses make the most sense to users

Expand Down

0 comments on commit 9dec1aa

Please sign in to comment.