Using Silktide's Screen Reader Simulator for Chrome, I tested the webpage. The featured listing are especially confusing to understand using the screen reader because although there are only 10 featured listings, the screen reader repeats the featured listings three times (reads all 10 listings, then reads them again, then again). Screen readers are used by people who are blind or visually impaired, so the webpage has to be made in a way that makes it easy for a screen reader to navigate through, which is not the case with this webpage. This violates the "Robust" principal of the Web Content Accessibility Guidelines.

Solution: Look through the code to see if there is any repeated code that is causing the screen reader to read the featured listings multiple times. If there is no repeated code, then it may be a problem with how the featured listings section has been coded, so the format of the featured listings section may need to change. After making the appropriate changes, test the webpage using a screen reader before publishing to make sure that the webpage is easily navigable by a screen reader.

Text is difficult to read because the text colour does not contrast well with the background colour. It would be difficult for people who are colourblind to read this text. This violates the "Perceivable" principal of the Web Content Accessibility Guidelines.

Solution: The grey text colour should be changed to another colour that has good contrast with the background colour.

The Web Content Accessibility Guidelines recommends that for any moving, blinking or scrolling information that starts automatically, lasts more than 5 seconds, and is presented in parallel with other content, the user should be provided an option to pause, stop or hide these animations, unless the animations are essential. For auto-updating information, the requirements are the same except that there there is no 5 second condition and the user should also be given the option to control the frequency of the auto-update. There are multiple places on this webpage where animations are present: the moving text that has been highlighted, the background images behind the moving text, the logos on the top right-hand corner of the webpage, and the featured listings (automatically moves to the left every few seconds and can also be dragged to move to the left or right). Furthermore, hovering over the options like "About Us" and "Register Now" causes the images to move. The animations on this webpage are non-essential and an option to pause, stop, hide, or control the frequency of the animations is not given. Moving and auto-updating content can be a problem for people who have difficulty reading text quickly, and for people who have difficulty tracking objects that move. For some people, moving and blinking objects can also be a serious distraction, especially for people who have attention-deficit disorders. This violates the "Understandable" principal of the Web Content Accessibility Guidelines.

Solution: Add an option to stop, pause, hide, or control the frequency of the animations. When stopping the animations, the moving text can be horizontally centered on the page. Furthermore, changing the images behind the moving text and navigating through the featured listings can instead be accomplished by using clickable arrows.

Need to hover over the headers in order for the sub-menu options to show up. Some of the headers themselves are also links, so navigating to the header using a keyboard and pressing enter will send you to another page instead of opening up the sub-menu. The hover interaction means that the menu is inaccessible using a keyboard. People who are unable to navigate a webpage using a mouse and can only use a keyboard, such as people with a motor impairment, won't be able to access the menu. Furthermore, in general, it is difficult to see where you are on the page while navigating using just the keyboard. All this violates the "Operable" principal of the Web Content Accessibility Guidelines.

Solution: The headers should not be links and instead, the webpage that the user would have been sent to by clicking on the header should just be added as an option to the sub-menu. Also, instead of hovering over the headers to access the sub-menu, the headers should be clickable dropdowns so that when a user navigates to the header using a keyboard and presses enter, the sub-menu should show up, and the user should then be able to access the sub-menu options using the keyboard. Furthermore, the element that the user is currently focused on should have a border around it so that the user can tell where they are on the page while navigating using a keyboard.