SSWConsulting / SSWConsulting/SSW.Rules
🦙 Bug - TinaCMS Dependency - Editing - Adding a link on Embedded Box Accessibility Issue
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
Requested by: @tiagov8 via YakShaver.ai 🦬
cc: @tiagov8, @Marxoz, @PothieuG, @Freego1783
Hi Team!
🟥 Watch the video (1 min 39 sec)
Url from screen share: https://ssw.com.au/rules/admin#!rules/prefix-job-title
Pain
Fix the issue where links added to the first sentence of a paragraph in an embedded box are inaccessible due to paragraph formatting.
Acceptance Criteria
- Links added to the first sentence of a paragraph in an embedded box should be accessible.
- The paragraph formatting should not obscure or overlap the link.
- Ensure that the link remains clickable and visible without requiring additional line breaks.
Reproduce Steps
- Open the embedded box editor.
- Attempt to add a link to the first sentence of any paragraph.
- Observe that the paragraph formatting overlaps the link, making it inaccessible.
- Attempt to fix the issue by breaking the line and editing again.
Screenshot

Figure: Link in first sentence inaccessible due to paragraph overlap
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.
Research direction
Start by reproducing the issue in the embedded box editor using the linked SSW Rules URL or the attached video, then trace the TypeScript/Next.js editing code involved in paragraph formatting and link insertion. Done means a link in the first sentence remains visible and clickable without line breaks or overlapping paragraph formatting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- accessibility, frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100