linebender / linebender/parley

Exposing the font family name to AccessKit

Open
#441 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
736
Forks
120
Avg merge
1d 3h
Merged PRs (30d)
53

Description

It's common for accessibility APIs to expose the font family name for each run of text. But unless I'm missing something, this information isn't available to Parley's layout code. Specifically, all that's available in the LayoutData struct is a Vec<FontData>, and FontData only has the font data itself, not a name. Any suggestions about how to solve this?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how LayoutData and its Vec are produced and consumed, then check how AccessKit receives text-run information. Determine where a font family name can be carried without losing existing font data, and verify that the accessibility output exposes the name for each text run.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
accessibility
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.