Sponsored by Confiz
Evaluation Criteria
The evaluation for the hackathon project will be based on the following breakdown:
- 25% by Confiz Judges on the 4th day (flexible).
- 75% by Event Heads based on the outlined criteria.
Breakdown of the 75% Criteria
The 75% of the total score is distributed across various aspects of your project. Below is a detailed breakdown:
- 5% - Performance Score: Assessed using tools like Lighthouse to evaluate load times, responsiveness, and overall efficiency. For example, optimizing your app to achieve a Lighthouse performance score of 90+ can maximize your points in this category.
- 5% - Responsiveness: Ensures your application works seamlessly across different devices and screen sizes.
- 10% - Accessibility Score: Evaluates how accessible your application is to all users, including those with disabilities.
- 10% - Proper Deployment:
- Full Score (10%): Achieved by deploying your application on platforms that require manual setup and configuration, such as Linux servers (e.g., AWS EC2, AWS Lambda, Google Cloud Run) or other similar platforms. All deployment steps must be thoroughly documented, including HTTPS setup.
- Penalty (5% Deduction): Applied if you use high-level, one-click deployment tools that directly integrate with your Git repository without significant customization. Examples of such tools include GitHub Pages, Firebase Hosting, Cloudflare Pages, Netlify, and Vercel.
General Rule of Thumb: To maximize your deployment score, opt for platforms that require detailed configuration and provide flexibility, demonstrating a deeper understanding of the deployment process.
- 10% - Usability Testing (UX):
- Manual testing by Event Heads.
- A detailed report will be provided at the end.
- UX Clarification:
There are two types of UX:
- User-Centric UX: Users can intuitively navigate and use the app without needing a demo. Projects with this type of UX can achieve scores close to 100%.
- Demo-Dependent UX: Users require a demo to understand how to use the app effectively. These projects will receive lower UX scores.
Strive to create a user experience that is natural and requires minimal explanation to maximize your UX score.
- 5% - Documentation:
- README file.
- Tech stack and project structure details.
- 30% - Features Implemented: The number and quality of features your project includes.
Note: The scores for Performance, Accessibility, and Usability are multiplied by the total score obtained in the Features Implemented section. For example, if your Features Implemented score is 80 out of 100, and your Performance score is 5%, your effective Performance score will be 4% (5% of 80).
To maximize your Performance score, it's recommended to use tools like Lighthouse to audit and improve your application's performance.
Accessibility
Accessibility evaluation will include the following:
- Semantic accessibility (e.g., keyboard navigation support).
- Contrast ratios:
- AA Standard: 4.5:1 for normal text, 3:1 for large text.
- AAA Standard: 7:1 for normal text, 4.5:1 for large text.
- Use of color must be accompanied by appropriate text indicators (e.g., status colors like red/green).
- Links and ARIA labels:
- Ensure non-text links have appropriate ARIA labels.
- Avoid vague link texts like “here” or “click me.”
- Labels for input fields must be used.
- Additional Guidance: Consider using accessibility evaluation tools such as axe to identify and fix accessibility issues, ensuring your application is usable by everyone.