WCAG 2.0 checklist Level Ain this link.
You must also create a release on your repo where the code is located. This will give us a snapshot in time and allow us to grade it.
The release does not need to include pull requests or commits from every member. The body does not even need any content, just ensure it is there and appropriately labeled.
It is suggested to use a folder and multiple files, just like this CSC491 repo, to contain this assignment.
|[Product] Applications, Use Cases, and Dynamic Content||All applications present in the architecture diagram have a repository and an MVP is implemented.|
The product coherently functions (buttons do as expected, a user could reasonably answer questions they want to answer using the app) and achieves the intended goal.
All main use cases/flows have been delivered and are functional.
The majority of the content is functional and dynamic. The app(s) do not rely on hard-coded static data.
Login credentials or registration system provided. Details listed in the release.
|[Product] Design & Accessibility||The application has a consistent look and feel. You didn’t rely on default styles (see below). The flows are not incoherent. This will be a highly subjective area, so feel free to ask for advice before submission (please don’t ask the day before, or day of, submission). Checklist for accessiblity is filled out and submitted in the team repo||15.0|
|[Infrastructure] Test Coverage||Tests should cover at least 65% of your application and upload to Code Climate.||15.0|
|[Infrastructure] Code Quality||All repositories have at least a “B” Grade on Code Climate.||15.0|
|[Infrastructure] Operational Excellence||CI, Exceptions, Logging, and all other services listed in the requirements & ||5.0|
|[Assignment Meta] Video||A short video (~1.5 to 3 min) with a short write up (some bullet points explaining the video) has been provided that indicates the flows that have been implemented. This allows the teaching staff to mark and is often highly valued in a production company. Please note any areas which are still under development, or not fully implemented. Keep in mind the majority of the paths should be implemented.||5.0|
Things you’ll lose marks on
< 50%= 0
nparts of the app (e.g. frontend, backend, data pipeline, etc.), regardless of if they are in different repos or just different folders, each section will be worth roughly
(total marks worth) / (n parts of the app)for each part of the app.
This scale is used for each line of the rubric above.
|Outstanding, Thoughtful and thorough||100% of pts|
|Strong, Provides some thought||80% of pts|
|Acceptable, Simple explanation||60% of pts|
|Insufficient, Little effort was made to give explanations||40% of pts|
|Unacceptable, No effort was made or the section was missing||0% of pts|