@yozidst
Submitted
"Feedback welcome!"
Looking to hire developers?
@Finney06
@MelvinAguilar
Submitted
Hi there π, Iβm Melvin, and this is my solution for this challenge. π
π Features:
π» Two Solutions in Two Branches:
<details>
and <summary>
tags without the need for JavaScript. ππ οΈ Built With:
π Further Resources:
If you're interested in creating an Accessible Disclosure, I recommend checking out this informative article by Grace Snow: Tutorial: Let's Build an Accessible Disclosure
Any suggestions on how I can enhance this solution or achieve even better performance are welcome!
Thank you. πβοΈ
@Finney06
Posted
Isn't the button meant to close when another button is been click...?
@musanurbadr
Submitted
@Finney06
Posted
Hello Musa π. Good job on completing the challenge !
Here are some suggestions regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
The error message "ul
and ol
must only directly contain li
, script
, or template elements" typically appears when there is invalid HTML markup in the code. This error indicates that either an <ul>
or <ol>
element contains an element other than <li>
,
, or <template>
elements as direct children.
If you need to include other types of elements within a list, you can nest them within an <li>
element.
Use a validator tool to check your HTML code for other possible errors.
Here's an example of valid HTML markup for an ordered list:
<ol>
<li>Item 1</li>
<li>Item 2</li>
<li>Item 3</li>
</ol>
And here's an example of valid HTML markup for an unordered list:
<ul>
<li>Item 1</li>
<li>Item 2</li>
<li>Item 3</li>
</ul>
By ensuring that your HTML markup follows the specifications, you can avoid errors and ensure that your web page is accessible to all users.
<div>
element with class "attribution" is not a landmark or a footer element, and therefore it does not provide any navigation aid for users.To fix this error, you can do the following:
Use HTML5 landmarks: HTML5 introduced several new elements that can be used to define the different sections of a web page, such as <header>
, <nav>
, <main>
, <aside>
, and <footer>
. By using these elements, you can create a clear hierarchy of content that is easy to navigate for users.
Include a footer element: A footer element should be included at the end of the document and contain information about the website or document, such as copyright information or contact details.
Here is a [**web accessibility evaluation tool**](https://wave.webaim.org/)π to check your webpage for any remaining errors or warnings related to landmarks.
I hope you find it helpful!π Above all, the solution you submitted is π.
πHappy coding!
Marked as helpful
@aratinau
Submitted
I'm happy with the way I made my triangle. I used ::after
on the bubble.
.space-left-bubble::after {
content: " ";
position: absolute;
bottom: 0;
right: 0;
height: 15px;
width: 15px;
/* triangle part */
--size-triangle: 20px;
border-top: var(--size-triangle) solid white;
border-left: var(--size-triangle) solid transparent;
transform: translateY(var(--size-triangle));
}
@Finney06
Posted
Hello Aymeric π. Good job on completing the challenge !
Here are some suggestions regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
Images should have alternate text.
<img class="img-bubble" src="images/icon-upload.svg" alt="upload icon">
this provides alternative text descriptions of images for people who are visually impaired and rely on screen readers to navigate the web. Screen readers can read the alt text aloud, enabling these users to understand what the image represents and how it relates to the content on the page. Overall, including alt text in HTML is an important best practice for creating accessible and user-friendly web content.
Wrap the page's whole main content in the <main>
tag.
Always avoid skipping heading levels; Starting with <h1>
and working your way down the heading levels (<h2>
, <h3>
, etc.) helps ensure that your document has a clear and consistent hierarchy.
Use HTML5 semantic elements such as <header>
, <nav>
, <main>
, <aside>
, and <footer>
to define these sections.
I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
Marked as helpful
@mnacfil
Submitted
@Finney06
Posted
Hello Melvinπ. Good job on completing the challenge !
Here is a suggestion regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
<h1>
and working your way down the heading levels (<h2>
, <h3>
, etc.) helps ensure that your document has a clear and consistent hierarchy.I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
@Jalal-Aljhny
Submitted
@Finney06
Posted
Hello Jalal-Aljhny π. Good job on completing the challenge !
Here is a suggestion regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
<h1>
and working your way down the heading levels (<h2>
, <h3>
, etc.) helps ensure that your document has a clear and consistent hierarchy.I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
Marked as helpful
@Omart4
Submitted
@Finney06
Posted
Hello Omarπ. Good job on completing the challenge !
Here are some suggestions regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
Wrap the page's whole main content in the <main>
tag.
Use HTML5 semantic elements such as <header>
, <nav>
, <main>
, <aside>
, and <footer>
to define these sections.
Use ARIA landmarks such as <header role="banner">
and <footer role="contentinfo">
to provide additional information about the purpose of each section to assistive technologies.
Here is a web accessibility evaluation toolπ to check your webpage for any remaining errors or warnings related to landmarks.
I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
@AKSTHIRUMURUGAN
Submitted
@Finney06
Posted
Hello there π. Good job on completing the challenge !
Here are some suggestions regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
Wrap the page's whole main content in the <main>
tag.
Always avoid skipping heading levels; Starting with <h1>
and working your way down the heading levels (<h2>
, <h3>
, etc.) helps ensure that your document has a clear and consistent hierarchy.
Use HTML5 semantic elements such as <header>
, <nav>
, <main>
, <aside>
, and <footer>
to define these sections.
Use ARIA landmarks such as <header role="banner">
and <footer role="contentinfo">
to provide additional information about the purpose of each section to assistive technologies.
Here is a web accessibility evaluation toolπ to check your webpage for any remaining errors or warnings related to landmarks.
I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
@Yogesh-Kumarr
Submitted
@Finney06
Posted
Hello Yogesh-Kumarr π. Good job on completing the challenge !
Here are some suggestions regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
Wrap the page's whole main content in the <main>
tag.
Use HTML5 semantic elements such as <header>
, <nav>
, <main>
, <aside>
, and <footer>
to define these sections.
Use ARIA landmarks such as <header role="banner">
and <footer role="contentinfo">
to provide additional information about the purpose of each section to assistive technologies.
Here is a web accessibility evaluation toolπ to check your webpage for any remaining errors or warnings related to landmarks.
I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
@webgeek2021
Submitted
This project was quite challenging for me because it involved three different breakpoints. However, through this project, I learned a lot about responsiveness and how to approach Figma designs. Additionally, I had the opportunity to use Three.js SphereGeometry on the destination page, which was a new and exciting experience.
While building the project, I found it difficult to make the font size responsive. Despite using the clamp function, I was not satisfied with the output. Furthermore, I was unable to implement how to change the background image based on pages and device width. I would greatly appreciate any guidance on these issues.
As this was my first time implementing Three.js, I may encounter issues related to the size of geometry. Therefore, I am unsure about certain areas of my code.
@Finney06
Posted
Hello there π. Good job on completing the challenge !
Here are some suggestions regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
Wrap the page's whole main content in the <main>
tag.
Use HTML5 semantic elements such as <header>
, <nav>
, <main>
, <aside>
, and <footer>
to define these sections.
I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
@yamenmaani
Submitted
tried to finish this page in 1:30 hours
@Finney06
Posted
Hello there π. Good job on completing the challenge !
Here are some suggestions regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
Wrap the page's whole main content in the <main>
tag.
Use HTML5 semantic elements such as <header>
, <nav>
, <main>
, <aside>
, and <footer>
to define these sections.
I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
@stzivel
Submitted
@Finney06
Posted
Hello there π. Good job on completing the challenge !
Here are some suggestions regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
Images should have alternate text.
Wrap the page's whole main content in the <main>
tag.
Use HTML5 semantic elements such as <header>
, <nav>
, <main>
, <aside>
, and <footer>
to define these sections.
Use ARIA landmarks such as <header role="banner">
and <footer role="contentinfo">
to provide additional information about the purpose of each section to assistive technologies.
Here is a web accessibility evaluation toolπ to check your webpage for any remaining errors or warnings related to landmarks.
I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
@anshjeengar
Submitted
@Finney06
Posted
Hello there π. Good job on completing the challenge !
Here are some suggestions regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
Wrap the page's whole main content in the <main>
tag.
Use HTML5 semantic elements such as <header>
, <nav>
, <main>
, <aside>
, and <footer>
to define these sections.
Use ARIA landmarks such as <header role="banner">
and <footer role="contentinfo">
to provide additional information about the purpose of each section to assistive technologies.
I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
@DrainGK
Submitted
@Finney06
Posted
Hello there π. Good job on completing the challenge !
Here are some suggestions regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
Wrap the page's whole main content in the <main>
tag.
Always avoid skipping heading levels; Starting with <h1>
and working your way down the heading levels (<h2>
, <h3>
, etc.) helps ensure that your document has a clear and consistent hierarchy.
Use HTML5 semantic elements such as <header>
, <nav>
, <main>
, <aside>
, and <footer>
to define these sections.
Use ARIA landmarks such as <header role="banner">
and <footer role="contentinfo">
to provide additional information about the purpose of each section to assistive technologies.
I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
@andemx
Submitted
@Finney06
Posted
Hello there π. Good job on completing the challenge !
Here are some suggestions regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
Images should have alternate text.
<img src="images/icon-memory.svg" alt="memory icon">
this provides alternative text descriptions of images for people who are visually impaired and rely on screen readers to navigate the web. Screen readers can read the alt text aloud, enabling these users to understand what the image represents and how it relates to the content on the page. Overall, including alt text in HTML is an important best practice for creating accessible and user-friendly web content.
Wrap the page's whole main content in the <main>
tag.
Always avoid skipping heading levels; Starting with <h1>
and working your way down the heading levels (<h2>
, <h3>
, etc.) helps ensure that your document has a clear and consistent hierarchy.
Use HTML5 semantic elements such as <header>
, <nav>
, <main>
, <aside>
, and <footer>
to define these sections, you can use ARIA landmarks such as <header role="banner">
and <footer role="contentinfo">
to provide additional information about the purpose of each section to assistive technologies.
I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
@beatsbydan
Submitted
@Finney06
Posted
Hello Danielπ. Good job on completing the challenge !
Here are some suggestions regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
Wrap the page's whole main content in the <main>
tag.
Use HTML5 semantic elements such as <header>
, <nav>
, <main>
, <aside>
, and <footer>
to define these sections.
I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
Marked as helpful
@mohamedibrahim5776
Submitted
@Finney06
Posted
Hello Ibrahimπ. Good job on completing the challenge !
Here are some suggestions regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
Wrap the page's whole main content in the <main>
tag.
Use HTML5 semantic elements such as <header>
, <nav>
, <main>
, <aside>
, and <footer>
to define these sections. You can also use ARIA landmarks such as <header role="banner">
and <footer role="contentinfo">
to provide additional information about the purpose of each section to assistive technologies.
I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
Marked as helpful
@5AMO7
Submitted
@Finney06
Posted
Hello there π. Good job on completing the challenge !
Here are some suggestions regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
Wrap the page's whole main content in the <main>
tag.
Use HTML5 semantic elements such as <header>
, <nav>
, <main>
, <aside>
, and <footer>
to define these sections you can also use ARIA landmarks such as <header role="banner">
and <footer role="contentinfo">
to provide additional information about the purpose of each section to assistive technologies.
I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
@KasparPanmei
Submitted
@Finney06
Posted
Hello there π. Good job on completing the challenge !
Here are some suggestions regarding your code that may be of interest to you.
HTML π·οΈ:
To clear some of the Accessibility report:
Wrap the page's whole main content in the <main>
tag.
Use HTML5 semantic elements such as <header>
, <nav>
, <main>
, <aside>
, and <footer>
to define these sections.
Always avoid skipping heading levels; Starting with <h1>
and working your way down the heading levels (<h2>
, <h3>
, etc.) helps ensure that your document has a clear and consistent hierarchy.
I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
Marked as helpful
@adriel-mp3
Submitted
@Finney06
Posted
Hello Adriel π. Good job on completing the challenge !
Here is a suggestion regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
<h1>
and working your way down the heading levels (<h2>
, <h3>
, etc.) helps ensure that your document has a clear and consistent hierarchy.I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
@Stephenpleasant
Submitted
Please how can i put the send icon into the input below my chat
@Finney06
Posted
Hello Stephen π. Good job on completing the challenge !
Here are some suggestions regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
Wrap the page's whole main content in the <main>
tag.
Always avoid skipping heading levels; Starting with <h1>
and working your way down the heading levels (<h2>
, <h3>
, etc.) helps ensure that your document has a clear and consistent hierarchy.
Use HTML5 semantic elements such as <header>
, <nav>
, <main>
, <aside>
, and <footer>
to define these sections.
I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
Marked as helpful
@RiinSeresuto
Submitted
@Finney06
Posted
Hello Reneπ. Good job on completing the challenge !
Here are some suggestions regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
Wrap the page's whole main content in the <main>
tag.
Use HTML5 semantic elements such as <header>
, <nav>
, <main>
, <aside>
, and <footer>
to define these sections.
Use ARIA landmarks such as <header role="banner">
and <footer role="contentinfo">
to provide additional information about the purpose of each section to assistive technologies.
Here is a web accessibility evaluation toolβ to check your webpage for any remaining errors or warnings related to landmarks.
I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
@AhmedMedhat77
Submitted
@Finney06
Posted
Hello Ahmed π. Good job on completing the challenge !
Here are some suggestions regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
Wrap the page's whole main content in the <main>
tag.
Use HTML5 semantic elements such as <header>
, <nav>
, <main>
, <aside>
, and <footer>
to define these sections you can also use ARIA landmarks such as <header role="banner">
and <footer role="contentinfo">
to provide additional information about the purpose of each section to assistive technologies.
I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
Marked as helpful
@Erick-86
Submitted
Making the number, date and pin inputs alert users that wrong format, numbers. Couldn't do it for all but managed to do for the number input with the help of ChatGPT
@Finney06
Posted
Hello FreeManπ. Good job on completing the challenge !
Here's a suggestion regarding your code that may be of interest to you.
HTML π·οΈ:
To clear the Accessibility report:
<h1>
and working your way down the heading levels (<h2>
, <h3>
, etc.) helps ensure that your document has a clear and consistent hierarchy.I hope you find it helpful!π Above all, the solution you submitted is π. πHappy coding!
Marked as helpful