Pages have no landmarks (main, banner, contentinfo) and no link to skip to the content

未关闭
#682 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@guidol-ive 已经在做这个了。

开始于 2026年10月28日。

  • #685 来自 @guidol-ive —— 未关闭

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
停滞
技术栈
javascript
领域
accessibility

调研方向

The issue names data/themes/default/hypha.html and the #header, #page, #main, and #footer regions. Read how the theme renders these regions and check the open pull request #685 for work already underway. Done means pages gain the requested landmark roles and a keyboard-focus-only “Skip to content” link while existing theme markup stays unchanged.

由索引模型根据 Issue 内容生成。

描述

Component: User interface Impact: Low Level: Easy Type: Bug Value: Visitors

Problem

A Hypha page has no landmarks: no <main>, <header> or <footer>, and no role attributes on the divs of the theme (#header, #page, #footer in data/themes/default/hypha.html). There is also no link to skip to the content.

  • A screen reader user cannot jump to the main content or the header (Lighthouse and axe: "Document should have one main landmark", "Page should contain a level-one heading inside a landmark", "Bypass blocks").
  • Keyboard users have to tab through the header, the menu and the command bar on every page.
  • Search engines and AI agents that read the HTML cannot tell the content from the navigation around it. A page of a large publisher uses <main>, <header>, <footer>, <nav>, <article> and <time> throughout.

Expected

Without changing the themes (existing themes keep their divs):

  • #header gets role="banner", the content (#page, or #main when a theme has no #page) gets role="main" and #footer gets role="contentinfo", unless the theme already has such an element or role.
  • The first element of <body> is a link "Skip to content" to that main region, visible only when it has the keyboard focus.
主要语言
JavaScript
星标
5
派生
9
平均合并
18 小时 49 分钟
30 天内合并 PR
13

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

PlanBCode/hypha 的其他 Issue

查看 PlanBCode/hypha 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。