Portfolio Website - HTML, CCS, and JavaScript
Designed and built a multi-page responsive portfolio using semantic HTML and modern CSS, showcasing projects, skills, and contact details. Focused on clean structure, accessibility, and cross-browser performance to present work professionally to employers and collaborators.

Tech Stack:
Frontend: HTML5 (semantic), CSS3 (Flexbox/Grid, transitions, animations)
Styling System: Single external stylesheet, CSS variables (or preprocessor)
Practices & Tools: Accessibility (WCAG AA colors & keyboard navigation), W3C HTML validation, Git/GitHub (version control), cross-browser testing (Chrome, Firefox, Safari, Edge, Opera, IE11)
Deployment: Optional web server or static hosting (e.g., GitHub Pages)
User Stories:
As a visitor, I can navigate across Home, About, Work, and Contact to learn about my skills and projects.
As a visitor, I can view work samples in a responsive grid that looks great on desktop and mobile.
As a visitor, I can contact me via a clear contact section/form with accessible labels and inputs.
As a visitor using keyboard or touch, I can navigate the site smoothly with visible focus states and large tap targets.
Key Features:
At least 3 interconnected pages (Home, About, Work; Contact section/page).
Responsive layout (320β1920px) via Grid/Flexbox; image scaling and fluid typography.
Single external CSS file with CSS variables for color, spacing, and typography tokens.
Accessible components: semantic landmarks (header/nav/main/footer), skip links, form labels, ARIA where needed, focus styles.
No third-party CSS librariesβall styles hand-coded for performance and control.
Cross-input support: keyboard, mouse, and touch interactions.
Performance touches: compressed assets, minimal blocking CSS, cautious animation use.
Highlights & Deliverables:
Passed W3C HTML validation and met WCAG AA color-contrast guidelines.
Implemented responsive grid on the Work page; added transitions/animations for subtle polish.
Created contact form with accessible markup and validation messaging.
Versioned with Git/GitHub; conducted cross-browser tests (incl. IE11 fallbacks).
Structured content and navigation for easy future updates as new projects are added.