feat: Add <noscript> fallback message for users with JavaScript disabled

[Harshada-Yele]

Summary

This PR adds a <noscript> fallback message to templates/index.html so that
users with JavaScript disabled see a clear explanation instead of a silently
broken form.
The warning banner is styled in static/style.css using existing
CSS custom properties and appears directly below the navbar. Without this change, the skill chip input system renders but is completely non-functional for
JS-disabled users with no feedback shown.

Related Issue [required]

Closes #256

Type of Change

• Bug fix — resolves a broken behaviour
• Feature — adds new functionality
• Data — adds new projects to data/projects.json
• Documentation — updates docs, README, or code comments only
• Style — CSS or visual changes only, no logic change
• Refactor — restructures code without changing behaviour
• Test — adds or updates tests

What Was Changed

File	Change made
templates/index.html	Added <noscript> block below <nav> to display fallback message when JS is disabled
static/style.css	Added .noscript-warning class styled with warning colours and margin-top: 64px to account for fixed navbar height

How to Test This PR

1. Clone this branch: git checkout feat/noscript-fallback
2. Install dependencies: pip install -r requirements.txt
3. Run the app: python app.py
4. Open Chrome and go to chrome://settings/content/javascript
5. Under "Not allowed to use JavaScript" click Add and enter 127.0.0.1:5000
6. Open http://127.0.0.1:5000 — you should see a yellow warning banner below the navbar
7. Remove 127.0.0.1:5000 from the blocked list and reload — banner should disappear
8. Run the tests: pytest tests/test_basic.py -k "not test_health_check"

Expected test output:

30 passed, 0 failed 

Test Results

Screenshots

Before	After
Form renders silently broken with no message

| Yellow warning banner appears below navbar when JS is disabled |

Self-Review Checklist

• I have read CONTRIBUTING.md and followed all guidelines
• My branch name follows the convention: fix/noscript-fallback
• I have run pytest tests/test_basic.py and 30 tests pass
• I have not introduced any print() or console.log() debug statements
• I have not modified files outside the scope of the linked issue
• If I changed the UI, I tested it at 375px (mobile) and 1280px (desktop)

Notes for Reviewer

The <noscript> tag is placed between the <nav> and <section class="hero">
so it appears at the top of the page content. The margin-top: 64px in CSS
accounts for the fixed navbar height to prevent the banner being hidden behind it.

[vercel]

@Harshada-Yele is attempting to deploy a commit to the komalsony234-1530's projects Team on Vercel.

A member of the Team first needs to authorize it.

[Harshada-Yele]

Hi @komalharshita
Ready for review.
All 29 tests pass and before/after screenshots are included.

Note: test_health_check has a pre-existing fixture bug unrelated to this PR.
A separate issue should be raised for it.

[komalharshita]

@Harshada-Yele sync your branch with the latest main and ensure all checks pass

[Harshada-Yele]

Hi @komalharshita
All checks pass
Ready for Review

[komalharshita]

Good contribution overall. The <noscript> fallback is a useful accessibility and progressive-enhancement improvement, and the implementation is clean and properly scoped.

The warning message is clear, the styling is lightweight and maintainable, and the navbar offset handling was thoughtfully considered. This improves the experience for users browsing with JavaScript disabled or restricted environments.

Minor future enhancement suggestion: consider adding an accessibility role such as role="alert" and slightly refining the wording depending on which site features actually require JavaScript.

Approved for merge.

[Harshada-Yele]

@komalharshita
Thank you for the review and feedback!
I'll keep the role="alert" suggestion in mind for future contributions."