Fix accessible name for GSoC member filter

[sujalswaraj-lab]

What

The GSoC member selector now has an accessible name so screen readers can identify its purpose.

Fixes #72

How I tested it

I verified the aria-label is on the member select and the diff only changes this issue. I could not run npm lint, tests, or build locally because Node 24 is unavailable; GitHub Actions will run CI. No screenshot: this is a non-visual accessibility change.

Checklist

• I was assigned the issue before I started
• npm run lint and npm run build pass locally (not run; Node 24 is unavailable)
• The diff only touches what the issue asked for

[vercel]

Someone is attempting to deploy a commit to the Geetansh Goyal's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

📸 How this looks

Built from this PR, so you can see the change without checking it out.

/

Desktop (1280px), top 3000px

Mobile (390px), top 3000px

/learn/open-source

Desktop (1280px), top 3000px

Mobile (390px), top 3000px

_{Screenshots are taken from a production build of this PR, signed out. Pages behind sign-in show the signed-out view. Build log}

[apsian4352-coder]

I reviewed the diff and component statically against issue #72 and verified the GitHub Actions CI workflow logs.

The fix is minimal and directly satisfies the requirement by adding aria-label="Show PRs by member" to the <select> in components/gsoc-stats.tsx:441.

A quick observation and question:

1. CI Status: In your PR checklist you noted being unable to run checks locally due to Node version; all core repository CI checks (Lint, Test, Type-check & build, and PR description) passed cleanly in GitHub Actions. The single failing check is just the external Vercel preview bot awaiting maintainer authorization.
2. Accessible name pairing: Since the first <option value="all"> is "All Members", screen readers announce "Show PRs by member, All Members, menu popup", which gives clear context.
3. Question: Did you test with Chrome DevTools Elements -> Accessibility pane or an OS screen reader (like VoiceOver with Cmd+F5) to verify how the announcement sounds when switching between individual members?

[kanaseprathamesh568-a11y]

Checked out pr-182 locally and verified:

• npm test runs cleanly (all 121 tests across 13 suites pass).
• npm run build completes successfully with no TypeScript or lint regressions.
• The <select> element now has a clear accessible name satisfying WCAG 4.1.2 (Name, Role, Value).

One question:
Have you considered whether the PR list container below should include aria-live="polite" (or have the select announce the filtered count), so screen reader users are notified when changing the selected member updates the list?

[kanaseprathamesh568-a11y]

Nice catch on adding the accessible name to this <select>!

For consistency across DevForge, components/quality-prs-list.tsx uses aria-label="Filter by member". Would "Filter PRs by member" or "Filter by member" be a closer match to the terminology used across the rest of the app?