Text only browsers cannot open posts
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- css
- Domain
- accessibility, frontend
Research direction
Reproduce the issue in Lynx 2.9.0 on Fedora Linux 40 and inspect how the Source theme exposes article titles during keyboard navigation. The work is done when article titles are selectable links that open the post content, including for posts without image alt text.
Written by the indexing model from the issue text.
Description
Issue Summary
Using the Lynx browser to view the site, I cannot open posts to view the content. The link navigation jumps to the article author and just displays the authors page. Using Lynx Version Lynx Version 2.9.0 (15 Jan 2024) on Fedora Linux 40 (Silverblue).
Steps to Reproduce
1. Install and launch Lynx
2. Press g
3. Enter site URL, press enter
4. Navigate using up/down arrows
5. Watch the selection cursor jump past the titles
I would expect article titles to be links so content pages are navigable.
Technical details:
* Ghost Version: 5.89.0
* Source theme version: 1.3.2
* Browser/OS: Lynx 2.9.0/Fedora Linux 40 Silverblue
This was also reported way back in 2018 in TryGhost/Ghost#9572 when Casper was still the default theme, presumably with that poster using Casper. I could not find a related issue report made for the Casper theme, but I temporarily switched my personal blog to the "casper (legacy)" theme and post links do show up correctly, so it must have been fixed for the legacy Casper theme sometime between when the aforementioned issue was reported and now. Edit: Small correction here, with the Casper theme if a post has an image with alt text set I can select and open those, but the actual article titles are not selectable.
- Dominant language
- CSS
- Stars
- 129
- Forks
- 258
- Avg merge
- 2h 57m
- Merged PRs (30d)
- 36
Contributor guide
No contributing guide indexed for this repository
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 TryGhost/Source
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
[Feature] Dark Mode Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
Similar issues
-
accessibility angular bug good first issue typescript ux
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
apache/fineract-backoffice-ui#584 · 1 comment ·
-
bug
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
spartan-ng/spartan#1763 ·
-
Access Score Gallery Label Map
Difficulty 2/5 Half a day Newbie friendliness 68/100
ProjectSidewalk/SidewalkWebpage#5430 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100