processing / processing/p5.js

Fix broken and missing links in En, Jp, zh-Hans contributior_docs web_accessibility.md

Open
#7,204 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug
Dominant language
JavaScript
Stars
24k
Forks
3.8k
Avg merge
3d 16h
Merged PRs (30d)
25

Description

Most appropriate sub-area of p5.js?
  • Accessibility
  • Color
  • Core/Environment/Rendering
  • Data
  • DOM
  • Events
  • Image
  • IO
  • Math
  • Typography
  • Utilities
  • WebGL
  • Build process
  • Unit testing
  • Internationalization
  • Friendly errors
  • Other (specify if possible)
p5.js version

latest

Web browser and version

all

Operating system

all

Steps to reproduce this
Steps:
  1. Go to https://github.com/processing/p5.js/blob/main/contributor_docs/web_accessibility.md
  2. Missing/incorrect links are in the second and third paragraph
    "If you want to make your sketches screen reader-accessible, visit the How to label your p5.js code tutorial.

If you want to use p5.js with a screen reader, visit the Using p5.js with a Screen Reader tutorial."

Corrections for English version:

Affected docs are in the following languages: English, JP, zh-Hans

Please assign this issue to me and I'll submit PR.

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

Open contributor_docs/web_accessibility.md and review the second and third paragraphs against the issue's replacement URLs. Check the corresponding English, Japanese, and zh-Hans accessibility documents for the same broken or missing links. Done means all affected links point to the intended p5.js tutorials and no listed links remain broken.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
accessibility, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.