1. Recognition rather than recall
1.1. Met ✓
1.1.1. Options of tickets are apparent
1.1.1.1. Location
1.1.1.2. Section
1.1.1.3. Number of tickets
1.1.1.4. Price
1.1.1.5. Type
1.2. Not met x
1.2.1. No obvious button to purchase tickets
1.2.1.1. "Find Tickets"
1.2.1.1.1. Can be misleading
2. Error prevention
2.1. Met ✓
2.1.1. Links on unavailable tickets are removed
2.1.2. Error message written below unavailable tickets
2.1.2.1. Users won't be left wondering if the tickets are available
2.1.3. Auto correction of mis-spelled words on search bar
2.2. Not met x
2.2.1. No message indicating if event is sold out
2.2.1.1. Links to select tickets are removed but the page says nothing about "sold out"
2.2.1.1.1. Users might wonder if the event is still going on or the availability of the tickets
3. Help and documentation
3.1. Met ✓
3.1.1. Help bar
3.1.1.1. Questions not provided with answers
3.1.1.1.1. Search on advanced search
3.1.1.2. Frequently asked questions
3.1.1.2.1. Questions are answered
3.1.2. Able to search anything on the search bar
3.1.2.1. Artistes' names
3.1.2.2. Events' names
3.1.2.3. Venue's names
3.1.3. Search the name of the event on search bar and links to the event will be listed
4. Match system to the real world
4.1. Met ✓
4.1.1. Reviews linked to Facebook
4.1.1.1. Facebook is the largest social media on the Internet
4.1.2. Real names of events and artistes are used
4.1.3. No technical words
4.1.4. No difficult words
5. User control and freedom
5.1. Not met x
5.1.1. Not able to leave the site without submitting information
5.1.2. Cannot undo or redo
5.1.2.1. Needs to re-enter everything
5.1.3. Time limit
5.1.3.1. Non IT savvy users might take a longer time to fill in particulars and they might get time out because of the time limit.
6. Consistency and standards
6.1. Met
6.1.1. Same procedures to purchase tickets from all sorts of events
7. Flexibility and efficiency to use
7.1. Met
7.1.1. Allows scroll of page using keyboard arrows
7.1.2. Allows control + c and control + v