Return back to the README.md file.
I have used the recommended HTML W3C Validator to validate all of my HTML files.
| Page | Screenshot | Notes |
|---|---|---|
| Home | ![]() |
Empty heading |
| Page | W3C URL | Screenshot | Notes |
|---|---|---|---|
| Home | W3C | ![]() |
Pass: No Errors |
| Characters | W3C | ![]() |
Pass: No Errors |
| Glossary | W3C | ![]() |
Pass: No Errors |
| Streaming | W3C | ![]() |
Pass: No Errors |
| Subscribe | W3C | ![]() |
Pass: No Errors |
| Subscribed | W3C | ![]() |
Pass: No Errors |
I have used the recommended CSS Jigsaw Validator to validate my CSS file.
| File | Jigsaw URL | Screenshot | Notes |
|---|---|---|---|
| style.css | Jigsaw | ![]() |
Pass: No Errors |
I've tested my deployed project on multiple browsers to check for compatibility issues.
| Browser | Index | Characters | Glossary | Streaming | Subscribe | Subscribed | Notes |
|---|---|---|---|---|---|---|---|
| Chrome | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Works as expected |
| Firefox | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Works as expected |
| Edge | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Works as expected |
| Brave | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Works as expected |
| Opera | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Works as expected |
Additional test performed on Safari:
| Browser | Characters | Notes |
|---|---|---|
| Safari | ![]() |
Works as expected |
I've tested my deployed project on multiple devices to check for responsiveness issues.
I've tested my deployed project using the Lighthouse Audit tool to check for any major issues.
body {
margin: 0;
}-
Inline button
- To fix this, I needed to override user agent stylesheet by setting the display to block.
#submit-button {
display: block;
}Resolved Issues
| Bug | Status |
|---|---|
When validating HTML with a semantic section element, the validator warns about lacking a header h2-h6. |
Closed after adding aria-label to the h2-h6 elements. |
| Image size slows down the page loading time. | Closed after compressing images. |
Class image-position creates overflow-x on smaller screens. |
Closed after removing horizontal padding. To note, this issue was not showing during testing and was captured by my mentor. |
Open Issues
| Issue | Explanation |
|---|---|
| Early commits often contain 50+ characters | This was left unresolved to present the learning curve. |
| Bug | Reason for not resolving |
|---|---|
| Nav elements span over two lines on devices smaller than ~ 300px in width | Low chances of the user encountering this issue. |
Header styling creates overflow-x issue on devices smalle than ~ 300px in width. |
Low chances of the user encountering this issue. |

































































