🐛 Bug Report: Screen Reader cuts off before comments
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- ios, rust
- Domain
- accessibility, frontend
Research direction
Start by reproducing the issue in iOS Safari using “Listen to Page” on a post with comments, then inspect the post and comment markup and accessibility structure. The report says Safari reads the title and post but stops before top level comments; done when it reads those comments while continuing to skip miscellaneous page content.
Written by the indexing model from the issue text.
Description
iOS safari screen reader reads the post title (flair too!) and the content of the post, but cuts off before the comments. Would be great to hear the top level comments.
Steps to reproduce the bug
Safari page options
Press “listen to page”
What's the expected behavior?
Safari properly ignores a lot of miscellaneous stuff and reads the post title, content, vote count, top level comments.
Additional context / screenshot
- I checked that the instance that this was reported on is running the latest git commit, or I can reproduce it locally on the latest git commit
- Dominant language
- Rust
- Stars
- 3.9k
- Forks
- 293
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 1
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from redlib-org/redlib
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
redlib-org/redlib#604 · 6 comments · 9 reactions ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
redlib-org/redlib#571 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
redlib-org/redlib#557 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
redlib-org/redlib#609 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 57/100
redlib-org/redlib#608 · 1 reaction ·
Maintainers usually reply within 1 day
All issues in redlib-org/redlib
Similar issues
-
priority middle
Difficulty 1/5 Under an hour Newbie friendliness 62/100
KATO-Hiro/AtCoderClans#12940 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
o8 next debug build aborts on Glass to Dark appearance switch (nil identifier messaged before check)Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hurttlocker/o8#5112 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day