This page informs about the points of WCAG 2.1 which is covered in the application

1.1.1 There are text alternatives for all non-text elements. The reason for this is to communicate the purpose of the element in different and equivalent ways.

Example: In the input fields we present default placeholder which describe the expected input

Not relevant for our application as it does not provide audio or video

1.3.1 The content in the application is readable and understandable.
1.3.2 It is easy to navigate through the application, because it is has descriptive buttons.
1.3.3 the various instructions that apply to understanding and operating content do not depend on shape, color, size, visual placement, orientation or sound.
1.3.4 The design is dynamic and resizable in a sensible way so the formatting makes sense.
1.3.5 A field for inputs is decided when the information collected serves a well-defined purpose.
1.3.6 The markup language used to produce the aspects pertaining to the User Interface was FXML.

1.4.1 Color is used to convey information in addition to text. Example: On Submit buttons the usage of green color indicate that the button confirms an action
1.4.2 No audio control is provided in our application. Therefore, this point in irrelevant
1.4.3 There is implemented a contrast between visual presentation of a contrast over 4.5:1. The applications contrast between text and images of text has a contrast of
1.4.4 A 200% zoom can be accomplished without losing information.
1.4.5 The visual presention does not consist of pictures, but written text instead.
1.4.6 The application has high contrast between text and pictures
1.4.7 The application does not contain any background sounds.
1.4.9 The application consist of limited use of pictures of text; however, when such images are used, they are solely decorational.
1.4.10 The application uses scrolling functionality to prevent loss of information. This functionalities can be especially found when using list and table for crucial information
1.4.11 Usage of colors, or images with small contrast is avoided in consideration of low vision disability.
1.4.12 The application uses larger spacing between text fields to avoid confusion. Example: Spacing between text fields when during team registration.
1.4.13 Implementation of focus point used in list and tableview. This functionality is multithreaded especially in auto selection. Example: Selection of focused/selected match autofills information.

It is possible to operate user interface components and navigation features.
2.1.1 Keyboard All functionality in the application is possible to operate from the keyboard. User can operate the program through tab and arrow keys.
2.1.2 No keyboard trap The user can navigate through the application with the keyboard interface. If it is needed to press another button than tab or arrow keys, the user will be notified what press next.
2.1.3 Keyboard There are no functions in the program that is depending on when a button is pressed.
2.1.4 Character Key Shortcuts There are no key shortcuts in out program.

2.2.1 The only time limits existing in the program are the loading of tournaments and the 20 Hour Exception based on the end date. The first limit abides by the essential exception, where altering the time when the deadline approaches would remove its inherent value. Furthermore, due to the natural length of a tournament, the user will always have the option of changing the limit. EXAMPLE

2.2.2 The program does not automatically update the user or information nor are there any blinking animations/changes. The user has full control over the movements within the application, which includes scrolling.
2.2.3 There are no actions within the application that are reaction-dependent. Therefore, the user does not have to be concerned with timing of interaction.
2.2.4 The application only provides interruptions when warning the user about invalid input or invalid actions. However, even with these warnings (pop-up), once the user has acknowledged the error, they may proceed with using the application as before.
2.2.5 Currently, the accessibility of the application is not dependent on authorization and authentication. Therefore, session expiration is not a concern; however, once a user logs out, the data entered within the session is automatically saved.
2.2.6 Since there are no instances when inactivity causes the loss or corruption of data, the user does not receive any warning. Again, the data is automatically saved when the user logs out, but the user is never forcefully logged out.

2.3.1 No elements blink more than 3 times per second.

2.4.2 All pages have a descriptive title that describe the topic or purpose.
2.4.3 The order in which the user navigates through the application does not affect the function of the application.
2.4.4 all links such as buttons and dropdown have an appropriate and descriptive title.
2.4.5 The application guides the user through a path to achieve a result.
2.4.6 headings and labels describe the subject or purpose of the text.
2.4.7 The application has visible indication of selected input field.
2.4.8 Application shows pagelocation by headers.
2.4.9 Consistency is used to avoid linking misunderstanding.
2.4.10 The application uses headers for content purposes.

3.1.1 Accessible text and accessible help is used frequently to ensure understanding of content.

3.2.1 The application does not change context when focused.
3.2.2 Context changes does not occur on input, but data is registered..
3.2.3 Consistency in navigation is applied.
3.2.4 Consistency in functionalities is applied.

3.3.1 The application takes usage of user feedback when error occurs.
3.3.2 Information through text or labels is included.
3.3.3 Error feedback provides informative text messages.

4.1.1 View should be without error, and duplication is only used where specifications allow this.
4.1.3 Application is documented, and user is informed about changes in program. Example: When team is added a confirmation box is presented