Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 2 months ago

Conference Ticket generator developed with responsive CSS and JS.

accessibility, pure-css, semantic-ui
Wagner Ricardo de Paula Marcolongo•40
@WagnerRicardo
A solution to the Conference ticket generator challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I am most proud of the development of the form input validation via Javascript, as well as the visual feedback for the user whenever a field had any error and the accessibility for screen readers.

What I would do different is creating a Javascript module with functions I could import in different Javascript scripts, as well as adding validation methods in the ticket class to make the code cleaner and more consistent.

What challenges did you encounter, and how did you overcome them?

The main challenges I encountered were:

  • Creating a custom drag and drop that would update the avatar preview, which I overcame by creating a function that gets the image URL using a FileReader object and updates the preview, being called whenever the file is dropped or changed by clicking the input tag.

  • Validating E-mail and github Usernames, which I overcame by utilizing Regex in a function that would return if the string follows the rules for a valid e-mail or username.

  • Adjusting the layout for smaller phones, in special on the ticket page, whichi I overcame by utilizing media queries and changing the sizes of fonts and images, as well as changing the amount of padding a margin elements in the ticket section.

What specific areas of your project would you like help with?

What I mostly would like help with is creating pages that have a good accessibility for screen readers and better semantics, as well as ways to improve the Readability of my code.

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 Wagner Ricardo de Paula Marcolongo'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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

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

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.