Let me know your thoughts.
Hello Alex, your page looks good. Without too much details.
Your page looks good @alexfkaprosy. Some things to revisit;
- Keep the test script when forking the pen (
- The test script, with all tests passing, should be included when you submit your projects.
- Your page passes 3/10 user stories. Click the red button to see which test(s) are failing and text to help you correct the issue.
Be sure and read more than just the first line of the failing message. The ability to read and comprehend error messages is a skill you’ll need to acquire as a developer. Ask questions on what you don’t understand.
- Codepen provides the boilerplate for you. It only expects the code you’d put within the
body element in the HTML editor. (No need to include the
body tags). For anything you want to add to the
<head> element click on the ‘Settings’ button, then HTML and add it into the ‘Stuff for <head>’ box.
- For instance, links to fonts go in the box labeled ‘Stuff for <head>’
- Codepen provides validators for HTML, CSS and JS. Click on the chevron in the upper right of each section and then click on the respective ‘Analyze’ link.
- The one for CSS is good. Use it and address the issue(s).
- (The one for HTML misses things which is why I recommend W3C)
- Accessibility is about being accessible to all users. Review the giving meaningful text to links lesson. For a more thorough explanation read Web Accessibility in Mind.
- “venerable ajahn chah” is not accessible
Thank you for your feedback Roma. I am working on resolving the issues.
This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.