creativecommons / creativecommons/vocabulary

[Accessibility] Typeface choices do not have broad globally considered glyphsets, needs updates and/or reevaluation

Open
#18 4 comments 0 reactions 1 assignee Claimed by @possumbilities View on GitHub
💻 aspect: code 📄 aspect: text 🕹 aspect: interface 🛠 goal: fix 🟧 priority: high 🧹 status: ticket work required
Dominant language
HTML
Stars
23
Forks
84
Avg merge
1d 9h
Merged PRs (30d)
3

Description

## Description
The typefaces chosen, while "open" in their use of an OFL (Open Font License) are missing several possible glyphs, accents, pairings, etc, that result in visual errors on names that aren't provided in the baseline glyphs many typefaces (and their font implementations) overlook due to their mostly western centric view of language.

## Reproduction

1. Utilize a character in copy, such as `Ọ`
2. See how the typeface changes to another only for this character.

## Expectation
All characters in copy shouldn't need to render in another typeface singularly, the typeface should have that glyph included.

## Additional context
This is a known issue with fonts and typefaces, based on their history and passed considerations of "success".

Also see:
* #341

## Resolution

- [x] I would be interested in resolving this bug.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.