SeleniumHQ / SeleniumHQ/seleniumhq.github.io

[🚀 Feature]: Fixing Accessibility Issues On Selenium Website

Open
#2,486 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted needs-triaging
Dominant language
HTML
Stars
1.4k
Forks
1.6k
Avg merge
18h 3m
Merged PRs (30d)
56

Description

Feature and motivation

The main website of Selenium has accessibility issues, raised as bugs as well . #2479, #2231, #1976 .
Created a script to find the accessibility issue on website, using axe and the report shows issues on the main links on page.
This feature proposal lists the concerns in each page and as identified fix for these issues will be attempted.

selenium_report_20250923_133948.txt

these two are the common concern across website-

  • To Fix ARIA attributes site-wide.
  • To Improve color contrast - Affects user readability across the site [2]

Most likely concern is at the template level, in the .scss files. The website is built using hugo docsy theme. Fixing color contrast in file variables project . scss file might fix issue 2.

code used to find accessibility issue - [to help explore]

findAccessibilityIssuesSeleniumWebSite.py

or use this - https://wave.webaim.org/

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.

Research direction

Start with the attached accessibility report and the provided Python script or WAVE results to identify the reported ARIA and color-contrast findings. Inspect the Hugo Docsy templates and project variables in the SCSS files; done means the listed site-wide accessibility issues are addressed and the checks no longer report them.

Written by the indexing model from the issue text.

Assessment

Tech stack
html, scss
Domain
accessibility, documentation
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.