Issue	Location	WCAG Guideline	Severity	Description	Impact	Action
The user may have difficulty reading some of the text due to low contrast.	All pages - Body - ‘Take Action’ button Take Action - Body - Section id=comp-lfv91mqb	1.4.3 Contrast Minimum (Level AA)	3 - High	The ‘Take Action’ button in the navigation bar has a contrast of 2.2:1. Moreover, the hero of the Take action page has a low contrast due to white text being placed in front of a bright green picture	The issue prevents people with low vision or low contrast perception from reading the text included in the menu and on top of the hero.	Ensure that the contrast between text and background is at least 4.5:1 for less than 18px or less than bold 14px; contrast must be at least 3:1 for 18px+ text or bold 14px+ text.
The user may have difficulty reading and accessing some of the elements on the site if using a screen magnifier or using landscape orientation.	All pages - all page	1.3.4 Orientation (Level AA)1.4.10 Reflow (Level AA)1.4.4 Resize Text (Level AA)	3 - High	Some elements of the navigation bar are not visible once zoomed in over 175%; past the 175% level of magnification, the website requires the user to scroll vertically and horizontally.	People who benefit from screen magnification are not able to use all the intended functionalities of the website - e.g. they cannot access the menu button. This can also impact this category of users as people can easily get lost when reading text while having to scroll horizontally.	Because this website is built using wix.com, the most appropriate solution to this issue is to ensure that all the content of the website is included within the constraint recommended by Wix itself as seen in Appendix C. This will guarantee adherence to the WCAG guidelines.
The user cannot understand what information is contained on the page nor how it is organised by examining the headings.	Homepage - Body - Section id=comp-lfv91mpi1	2.4.10 Section Headings (Level AAA)2.4.6 Headings and Labels (Level AA)	3 - High	The information in the table is formatted in an unclear way; headings 1 have been used to tag the first parts of the information presented, followed by paragraph tags for the remainder of the text.	Screen reader users cannot understand the information given from the context, and the paragraphs are not read in the correct order, with the first part of all sentences being omitted by the screen reader and only the second part of the sentences being scanned by the assistive technology. A low vision or blind person has no way to access the information in the way it is intended.	It is strongly recommended to adopt only one <h1> for each webpage; for this reason and for what has been mentioned above, the suggested action is to format the entire text using paragraph tags in HTML, and style the sections with the use of CSS. Headings should not be used exclusively for styling purposes, instead, they should convey formatting and relationship meanings; more importantly, it is advisable not to divide sentences using different types of headings as assistive technologies will read those sentences separately, and in a disconnected way.
The user cannot appropriately operate the website with the sole use of keyboard tabs.	All pages - all page	2.4.3 Focus Order (Level A)	3 - High	When tabbing through the website pages, focus is placed only on the interactive elements of the page. The headings and main non-interactive landmarks of the page do not receive focus	This issue impacts users who navigate using a keyboard, as they may have difficulty understanding the context of the webpage and operating within it.	Many of the elements that should receive focus have been manually disabled through the use of tabindex=-1. A recommended action is to modify the code where necessary; tabindex should be made equal to 0 for those elements that need to be focusable.
The user cannot understand the content of the page by its title	Homepage - Head - <title> tag	2.4.2 Page Title (Level A)2.4.8 Location (Level AAA)	2 - Medium	The title of the homepage includes an unnecessarily long list of the organisation's activities, without giving any reference to the page name.	The issue prevents screen reader users from understanding which page they are on, which means they may find it difficult to understand how to navigate the website.	Modify the title to contain both the name of the page (homepage) and any metadata relevant to the page.
The user cannot understand the destination of some links due to a lack of appropriate alt text and or role attributes.	All pages - Navigation Bar - logo.png Homepage - Body - Section id=comp-lfv91mpk2	2.4.4 Link Purpose In Context (Level A)2.4.6 Headings and Labels (Level AA)2.4.9 Link Purpose Link Only (Level AAA)4.1.2 Name Role Value (Level A)	2 - Medium	The logo in the navigation bar contains a link that redirects the user to the homepage; however, this is not clear to screen reader users as they are not informed of the destination of the link. In the ‘projects’ display, there is a series of arrows, which are used to redirect the user to each specific project page, however, due to a lack of appropriate role information this can only be assumed from visual context.	Both the examples mentioned above, badly affect the user experience of screen reader users, as well as less confident technology users. The lack of clear labelling for the images, impedes these categories of users from navigating freely, as the links purpose may not be clear to some.	Include relevant alt text and role for the clickable elements; labels should also be included, especially in the section where the arrows redirect the user.
The user is not given appropriate error handling tools, in case of incorrect input in a form	All pages - Body - Contact Form  Take Action - Body - Make an Impact	1.4.1 Use of Colour (Level A)3.3.1 Error Identification (Level A)3.3.3 Error Suggestion (Level AA)3.3.6 Error Prevention All (Level AAA)	2 - Medium	If a user input is incorrect, the input field changes border colour from black to red. When trying to submit incorrect information an automated validation text appears for less than one second; this is not believed to be appropriate.	This issue impacts a wide range of users; many individuals, especially low vision users may not notice the change, and no user can read the validation message as it disappears too quickly.	The recommended action is to add static messages to inform users of the incorrect input appropriately; the information message should be placed near the error and give clear instructions on correcting the error.
The user is not given appropriate error handling tools, in case of incorrect input in a form	All pages - Body - Contact Form Take Action - Body - Make an Impact	1.4.1 Use of Colour (Level A)3.3.1 Error Identification (Level A)3.3.3 Error Suggestion (Level AA)3.3.6 Error Prevention All (Level AAA)	2 - Medium	If a user input is incorrect, the input field changes border colour from black to red. When trying to submit incorrect information an automated validation text appears for less than one second; this is not believed to be appropriate.	This issue impacts a wide range of users; many individuals, especially low vision users may not notice the change, and no user can read the validation message as it disappears too quickly.	The recommended action is to add static messages to inform users of the incorrect input appropriately; the information message should be placed near the error and give clear instructions on correcting the error.
Screen reader users need to know if their form submission is successful.	All pages - Body - Contact Form Take Action - Body - Make an Impact	4.1.3 Status Message (Level AA)	1 - Low	Once a user submits a form, a confirmation message appears near the form, below the last input field. However, this text does not receive focus automatically and it is impossible for a screen reader user to navigate to the message.	Screen reader users currently are not informed of successful submissions and are therefore left unaware of important communications.	Using the ARIA22 technique, the role “status to present status message” should be added to the message element in the HTML code, as this can help place focus on the element when needed.
Blind or low vision users are not informed of the content of images and videos, as there is a lack of alt text.	Homepage - Body - Section id=comp-lfv91mpi Take Action - Body - Section id=comp-lfv91mqb	1.1.1 Non-text Content (Level A)1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	1 - Low	On the homepage of the website, in the hero section (at the top of the page) a series of videos and pictures are displayed in sequence every ten seconds. However, none of these elements have associated alt text or audio tracks describing the videos.	Blind and low vision users do not have appropriate access to the video and image elements as they are not clearly formatted for these types of users. This could cause confusion in many individuals and could foster a sense of frustration in some users.	The most appropriate action, in this case, is to include alt text to all static images included on the website, as well as including an audio track to describe the content of the video - if the visual elements are deemed to be decorative and not content relevant, then an appropriate description of “decorative element” should be included for the screen reader users to be aware of this.
Users cannot pause or stop the videos that are automatically playing on the homepage.	Homepage - Body - Section id=comp-lfv91mpi	2.2.2 Pause Stop Hide (Level A)	1 - Low	When the homepage of the website is opened, in the hero section, a new video is automatically played every ten seconds; in the current solution of the website, these videos cannot be paused, stopped or hidden.	This issue can have an impact on a range of users; for the purpose of the audit, it is assumed that the previous issue was solved by following recommended actions. Users who may want to benefit from the audio track or description of the video played on the homepage, cannot listen to the full track as only ten seconds are allocated for each video.	It is recommended that a media player's control bar is added in relation to the videos being played. This allows users who may want to listen to the audio track to pause the video and fully listen to the description. Moreover, users who want to should be able to hide the videos - this could be useful for those users who are not interested in the audio description or those who may have already been through the description and do not want to go through the videos again. Hiding videos may especially help with page loading and speed of interactivity, as oftentimes videos can cause high bandwidth usage.