SSWConsulting / SSWConsulting/SSW.Website
🐛 Bug - Video section caption renders as heading due to incorrect markup
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 14
- Forks
- 10
- Avg merge
- 13h 51m
- Merged PRs (30d)
- 38
Description
Requested by: @tiagov8 via YakShaver.ai 🦬
cc: @tiagov8, @brookjeynes-ssw, @babakamyljanovssw @hveraus @PennyWalker @adamcogan
Email thread where I discovered this: Re: SSW Newcastle Directions - video
Hi Team!
🟥 Watch the video (1 min 12 sec)
Url from screen share: https://ssw.com.au/offices/newcastle
Pain
On the Newcastle office page, the video section caption is rendered with the same size and bold styling as the heading, making it more prominent than the actual heading. Investigation shows the heading tag is not correctly closed and is wrapping the entire section. This results in incorrect semantics, styling, and accessibility. The markup for this component should be fixed so the heading ends at the correct point. As this appears to be a shared component, other pages using it should also be checked for the same issue.
Acceptance Criteria
- The video section heading on the Newcastle office page is correctly closed in the markup.
- The caption text is no longer rendered with heading-level size or bold styling.
- Heading and caption styles match the design system and expected hierarchy.
- HTML markup is semantically correct and accessible.
- All pages using the same component are reviewed and confirmed to be free of the same issue.
Reproduce Steps
- Navigate to www.ssw.com.au.
- Open the Newcastle office page.
- Scroll to the video section.
- Observe that the caption text appears the same size and weight as the heading.
- Inspect the HTML and note that the heading tag wraps the entire section instead of ending after the heading text.
Screenshot

Figure: Video section heading markup incorrectly wraps entire section, causing caption to appear as a heading
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 at the Newcastle office page and inspect the video section's rendered HTML, then trace the shared component used there across other pages. Verify the heading boundary, caption styling, semantic hierarchy, and accessibility in the browser; done means the Newcastle page and every page using that component render without the incorrect heading wrapper.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, nextjs
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100