Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

MethodScript.com Accessibility - Labels are not attached to search form fields

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

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
30/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
html

调研方向

从 issue 中链接的 MethodScript.com 文档页面开始,检查 ID 为 theme-select 和 search 的搜索表单字段。以报告的可访问性违规作为基线;当两个字段都有辅助技术能够解释的标签时,即表示完成。

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

描述

accessibility documentation

The search form does not include accessible labels that can be interpreted by a screen reader.

2 violations detected:

<select id="theme-select" name="theme-select">
   <option value="default">Default Theme</option>
   <option value="Dark">Dark</option>
   <option value="Nilleke Dark">Nilleke Dark</option>
</select>
<input id="search" name="search" value="" type="search" class="sb-search-input">

Why is this important?

When on-screen labels are present, they must be programmatically associated with form fields. When on-screen labels are not present, form fields must be given an accessible label.

When form fields do not have a programmatic (accessible) label, assistive technologies may incorrectly render the label or provide no label at all to users. When labels are not present or are incorrect, users of assistive technologies may not be able to complete a form.

The HTML5 specification has a new form field attribute called placeholder. This represents a label or hint, such as a word or short phrase, that is assigned to a form field such as an input field. The label or hint appears within the form field and goes away when users start typing. When the placeholder attribute is used, the label or hint may not be detected by assistive technologies. Therefore, developers should provide off-screen text in the label element of the form field or provide a title

https://www.webaccessibility.com/results/?url=https%3A%2F%2Fmethodscript.com%2Fdocs%2F3.3.4%2Findex.html

主要语言
Java
星标
128
派生
70
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

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

EngineHub/CommandHelper 的其他 Issue

查看 EngineHub/CommandHelper 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

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