[all components][docs] Use hard tabs in the source for accessibility
Open
Nobody has claimed this yet.
accessibility
docs
scope: all components
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
- I have searched the issues of this repository and believe that this is not a duplicate.
Summary 💡
Hard tabs allow contributors to choose how many spaces a tab represents, which aids accessibility.
Discussion:
https://github.com/romefrontend/rome/issues/425
Examples 🌈
https://github.com/romefrontend/rome
Motivation 🔦
Material-UI as a user interface component library has a strong accessibility ethic. This should extend to contributor DX.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the issue discussion and the linked Rome example to clarify how hard tabs should apply across Material UI source files and documentation. Identify the repository-wide source scope, then verify that the affected components consistently use hard tabs and that existing checks still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- developer-experience
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100