layer5io / layer5io/layer5

Filter checkboxes lack proper label associations on Resources page

Open
#8,063 1 comment 0 reactions 1 assignee View on GitHub

@tejaswiverma121-byte is already working on this.

Since Sep 14, 2026.

framework/gatsby help wanted kind/bug
Dominant language
JavaScript
Stars
1.1k
Forks
1.6k
Avg merge
2d 10h
Merged PRs (30d)
18

Description

Description

On the Resources page, Chrome DevTools reports:

  • No label associated with a form field across the filter categories (Type, Product, Technology, Service Mesh).
    In src/sections/Resources/Resources-grid/filters.js, the <input type="checkbox" /> elements are rendered within JSX fragments nested inside generic <label> tags without explicit id and htmlFor pairings. Consequently, assistive technologies cannot reliably bind each checkbox to its respective category count and label.
Expected Behavior

Each checkbox should have a unique id attribute (e.g. id={filter-${x.value}}) and its corresponding <label> element should explicitly reference it via htmlFor={filter-${x.value}}.

Screenshots
flowchart TD
    subgraph Current ["❌ Current: Implicit / Broken Association"]
        direction TB
        L1["&lt;label&gt; (No htmlFor)"]
        F1["&lt;Fragment&gt;"]
        I1["&lt;input type='checkbox' /&gt; (No id)"]
        T1["&lt;span&gt; Blog (48) &lt;/span&gt;"]
        
        L1 --> F1
        F1 --> I1
        F1 --> T1
        I1 -.->|"❌ Screen readers cannot bind"| T1
    end
    subgraph Proposed ["✅ Proposed: Explicit 1-to-1 Binding"]
        direction TB
        L2["&lt;label htmlFor='filter-blog'&gt;"]
        I2["&lt;input id='filter-blog' type='checkbox' /&gt;"]
        T2["&lt;span&gt; Blog (48) &lt;/span&gt;"]
        
        L2 --> T2
        I2 <===>|"✅ Explicit HTML association via id & htmlFor"| L2
    end
Environment:
  • Host OS:macOS
  • Browser:Chrome

Contributor Resources and Handbook

The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch.

Join the Layer5 Community by submitting your community member form.

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.