Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Responsive QR Generator APP - UI

accessibility, animation, bootstrap
Chitranshi17•10
@Chitranshi17
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


QR Generator App Create by HTML & CSS.

Technologies Used:

  1. HTML: Utilized for structuring the content and creating input forms.
  2. CSS: Employed for styling and enhancing the app's visual appeal.

Key Features:

  1. Input Form: A user-friendly input form to enter the data (text or URL) for the QR code.
  2. Generate Button: A button that triggers the generation of the QR code based on they provided input.
  3. QR Code Display: A dedicated area to display the generated QR code. Project Implementation:

---> HTML Structure: Created the basic HTML structure, including the head and body. Utilized form elements (<input> and <button>) for user interaction.

---> CSS Styling: Applied styles to enhance the visual appeal and ensure a clean layout. Used CSS for responsiveness and optimal display on different devices.

----> QR Code Generation: Integrated an external QR code generation library (e.g., qrcode.js) using JavaScript. Implemented a JavaScript function to handle user input and generate QR codes dynamically.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Chitranshi17's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.