|
|
## Process
|
|
|
The graphical user interface was built using Don Norman’s principles of universal design in mind.
|
|
|
|
|
|
The team also had the WCAG 2.1 in mind. WCAG 2.1 addresses barriers that patrons with disabilities may experience when using a digital tool. Following is a bullet-list which addresses important matters that the team had in mind when creating the user interface.
|
|
|
|
|
|
- Providing text alternatives for any non-text content to alternative formats according to specific needs. Examples of such needs can be larger text print, braille, speech and sounds, relevant symbols or a simplified language.
|
|
|
|
|
|
- Time-based media, such as videos, GIFs, or audios, can be a challenge for some users. Developers should make alternatives for getting information from such formats.
|
|
|
|
|
|
- Create alternative content which presents information and structure in a different and simpler manner. It is important not to loose structure or information when implementing such alternative contents.
|
|
|
|
|
|
- Create possibilities for a user with needs to see and hear content more easily.
|
|
|
|
|
|
- Separation of foreground from background and use of colors will make it easier for people with colorblindness or reduced vision to use an application.
|
|
|
|
|
|
## Perceivable
|
|
|
- All buttons have labels. Colors are not uniquely describing a functionality.
|
|
|
- Sounds does not play a role in our program.
|
|
|
- There are minimal images so alternative text is not used.
|
|
|
|
|
|
## Operable
|
|
|
- All buttons and fields are tab-able
|
|
|
- No functionality is time sensitive
|
|
|
|
|
|
## Understandable
|
|
|
- Font for standard text is set to 22px. Titles are 36px.
|
|
|
- Labels of buttons are descriptive
|
... | ... | |