Skip to content

fix: Correctly punctuate a status content description#808

Merged
nikclayton merged 3 commits intopachli:mainfrom
nikclayton:791-status-content-description
Jul 6, 2024
Merged

fix: Correctly punctuate a status content description#808
nikclayton merged 3 commits intopachli:mainfrom
nikclayton:791-status-content-description

Conversation

@nikclayton
Copy link
Contributor

Previous code blindly inserted commas and semi-colons as separators between the components of a content description. If some of those components were null you could have a content description that looked like "... , , , ..." or similar, and the repeated reading of "comma" by screen readers was jarring and reduced accessibility.

Fix this by inserting punctuation only where necessary, building up the string piece by piece instead of using a string resource with hardcoded punctuation.

Fixes #791.

Previous code blindly inserted commas and semi-colons as separators
between the components of a content description. If some of those
components where null you could have a content description that
looked like "... , , , ..." or similar, and the repeated reading of
"comma" by screen readers was jarring and reduced accessibility.

Fix this by inserting punctuation only where necessary, building up
the string piece by piece instead of using a string resource with
hardcoded punctuation.

Fixes pachli#791.
@nikclayton nikclayton merged commit 0f80ec4 into pachli:main Jul 6, 2024
@nikclayton nikclayton deleted the 791-status-content-description branch July 22, 2024 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Status content description has spurious punctuation

1 participant