Doors Phase 3: author profile links and headings, and two small review items

Ouverte
  • Quelque chose ne va pas ?
#983 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
55/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
html
Domaine
accessibility

Piste de recherche

Read layouts/authors/list.html and the Phase 3 redesign context; compare the social links with layouts/partials/social_links.html and the fix in #975. Check keyboard access to contents links under the cookie banner at 1440 px and heading wrapping at 390 px with text at 200%. Done when the profile links have accessible names, heading order is corrected, and the two review issues are addressed in the redesign.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

[!NOTE]
🤖 Claude Opus 5.5 responding on behalf of Lukas Wallrich

Found by the independent review of the Doors preview. The first two are also on main, in the retained author profile template layouts/authors/list.html, for example at /authors/lukas-wallrich/.

  • Social links can't be reached by screen readers: the icons sit in ul.network-icon[aria-hidden=true], and the links have no names. Article author cards were fixed in #975 through layouts/partials/social_links.html, which this template doesn't use.
  • Heading order: the role and organisations are h3 directly under the h1.

Phase 3 redraws this template, so both can be fixed there.

Smaller, from the same review:

  • Contents links under the cookie banner: at 1440 px, the last link of a long contents card can sit behind the banner when reached by keyboard, until the banner is dismissed. The banner is restyled in Phase 3.
  • A single letter left on a line: at 390 px with text simulated at 200%, the Resources heading breaks as "Teachin" and "g". There is no overflow, so this is only polish.
Langage dominant
HTML
Étoiles
42
Forks
33
Merge moyen
16 h 3 min
PR mergées (30 j)
121

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de forrtproject/forrtproject.github.io

Toutes les issues de forrtproject/forrtproject.github.io

Issues similaires

Plus d'issues Accessibility

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.