Theme styling: touch targets, contrast, etc.
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 48/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- css
研究方向
Start by reviewing the theme-specific issues linked here, especially Berlin's input styles and Seasons' contrast notes, then inspect the corresponding styles for the listed themes. Check touch target sizes, text contrast, link behavior, and input boundaries against the stated requirements. Done means the listed issues meet those accessibility checks across the affected themes; no test files or style entry points are named in the issue.
由索引模型根據 Issue 內容生成。
描述
- All themes must ensure Flag/Unflag and Reply actions as well as user website links meet the minimum standards (24 x 24 px) for touch target sizing. In the case here, most themes are under the 24px height requirement.
- Noted by specific theme, other areas with target sizing issues include:
- Berlin: Submit button, text inputs
- Noted by specific theme, other areas with target sizing issues include:
- There is a quirk across all themes (Berlin, Lively, Freedom, etc.) that properly display links with underlines, in which the Flag/Unflag link displays with only a partial underline:
However, I believe these links should be converted to buttons anyway. - Noted by specific theme, areas with contrast issues include:
- Center Row: Submit button (4.2:1, should be 4.5:1 at min)
- Seasons:
- Inputs as described in theme issue https://github.com/omeka/theme-seasons/issues/52#issuecomment-6783426922
- "Flagged inappropriate" text:
- Night: 1:1
- Winter: 4.484:1
- Summer: 2.991:1
- Night: 1:1
- Freedom and Lively: "Flagged inappropriate" text (3.7:1)
- We also need to ensure text inputs have accessible boundary styles, as already described in theme-specific issues (e.g. https://github.com/omeka/theme-berlin/issues/42) regarding inputs in search forms. I would imagine those corrected styles should carry over for this, but if not, I can note specific issue areas here.
- 主要語言
- PHP
- 星號
- 4
- 分支
- 5
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
omeka/plugin-Commenting 的其他 Issue
-
a11y
難度 2/5 1-3 小時 新手友好度 65/100
omeka/plugin-Commenting#70 ·
-
a11y
難度 2/5 1-3 小時 新手友好度 65/100
omeka/plugin-Commenting#67 ·
-
a11y
難度 2/5 1-3 小時 新手友好度 64/100
omeka/plugin-Commenting#64 ·
-
a11y
難度 2/5 1-3 小時 新手友好度 65/100
omeka/plugin-Commenting#63 ·
-
a11y
難度 2/5 1-3 小時 新手友好度 75/100
omeka/plugin-Commenting#62 ·
查看 omeka/plugin-Commenting 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
sync-en
難度 1/5 1 小時以內 新手友好度 85/100
維護者通常 1 天內回覆
-
sync-en
難度 1/5 1 小時以內 新手友好度 85/100
維護者通常 1 天內回覆
-
Перевод устарел
難度 2/5 1-3 小時 新手友好度 70/100
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 72/100
nplhse/collaborative-ivena-statistics#1464 · 1 則留言 ·
維護者通常 1 天內回覆