If there is a biometric identification, alternatives are offered to identify the users. 5.3 EN
The app does not block common user settings, such as colors (e. g dark vs light mode), contrast and font size. 11.7 EN
Exception: If there is documentation that explains that the software is designed to be isolated from its underlying platform.
If there is time limits, which is less than 20 hours for the app, then the limit can be extended, paused or adapted.
2.2.1 Timing Adjustable (A)
The app can be used in all screen orientations (Portrait and Landscape mode).
1.3.4 Orientation (AA)
The layout is responsive and adapts to the viewport size. Should at a minimum go to 320 x 568 size.
1.4.10 Reflow (AA)
No scrolling in more than one direction (no both horizontal and vertical).
Exception: where it is required o-dimensional layout or when a toolbar is manipulating another part of the content.
Headings, labels and buttons are informative
2.4.6 Headings and Labels (AA)
All pages have a unique and descriptive page/screen title
2.4.2 Page title (A)
Example: It does not necessary require a title in the navigation bar. The first heading on the page can also serve as a title.
The order of the content (reading order) does not affects its meaning.
1.3.2 Meaningful sequence (A)
Example: If the order is important for understanding, the same order must also appear in the code.
Content that acts and looks like lists, should be marked as such.
1.3.1 Info and relationships (A)
The status of all switches and similar components that are presented visually, is also reproduced through sound or touch (e. g vibration).
5.6.1 EN
Text that acts and looks like heading, should be marked as a heading element.
1.3.1 Info & Relationships (A)
Text can be resized at least twice as much using Dynamic Type in the phone settings. This without loss of content or functionality
1.4.4 Resize Text (AA)
All meaningful images and graphical oelements have a text alternative that gives equivalent information to a non-sighted user.
1.1.1 Non-text Content (A)
Dynamic feedback is conveyed to screen reader (e. g success or results of an action, page loading, number of search results etc.).
4.1.3 Status Messages (AA)
Different states, role and values on interactive objects is conveyed to screen reader (e. g expanded, selected, checked etc.).
4.1.2 Name, role, value (A)
UI components and graphical objects have a contrast ratio of at least 3,0:1 against the adjacent color.
1.4.11 Non-text Contrast (AA)
Text have a contrast ratio of at least 4,5:1 against the adjacent color.
1.4.3 Contrast (Minimum) (AA)
Interactive elements and information are identified by something more than color.
1.4.1 Use of Color (A)
All automatic movies and animations that last longer than 5 seconds can be paused or stopped.
2.2.2 Pause, Stop, Hide (A)
Reduced animation is not blocked in the phone system settings or it can be turned off in the actual page.
1.4.2 Audio control (A)
There are alternative to multitouch-gestures or complex drag and drop interactions.
2.5.1 Pointer Gestures (A)
Activation on a click event occur on the up-event and not down.
2.5.2 Pointer Cancellation (A)
There are alternative to actions requiring movements.
2.5.4 Motion Actuation (A)
Example:Actions is not triggered by moving a device, such as tilting or shaking, as long as the motion is essential for the function, such as a pedometer.
Functions that requires simultaneous handling have alternate methods. 5.9 EN
Example:Zooming with two fingers can also be operated using two buttons.
Menu, lists of links or functions that are repeated on several pages occur in the same place and relative order.
3.2.3 Consistent Navigation (AA)
Components having the same functionality is used and identified consistently. In general, use the same terminology on the site
Example:Do not use different labels for the same function e. g Download and Share with the same graphical element, and make sure to use the same link text to the same destination.
All interactive elements can be controlled by keyboard
2.1.1 Keyboard (A)
Best practice:Make sure that all content can be reached with TAB and/or ARROW keys and not only using the command SEARCH+TAB to switch between toolbar and content areas.
The tab order is logical. Focus should not g in an unexpected order.
2.4.3 Focus Order (A)
Keyboard users can tab through the page without unexpected changes or interruptions and without focus being moved unexpectedly.
3.2.1 On Focus (A)
Keyboard users can tab through the whole interface without getting trapped in an area.
2.1.2 Keyboard Trap (A)
Attention:Look carefully in modals or overlays.
Visual focus mark must be visible for keyboard navigation and have at least a minimum contrast of 3,0:1.
2.4.7 Focus Visible (AA),1.4.11 Non-Text Contrast (AA)
Navigation behind modals is not possible.
The focus is placed in the new content being uploaded.
Screen reader are not able to reach content outside any modal or other overlapped areas.
The size of an clickable object has a minimum target size of 48 x 48dp. The recommended size for accessibility in apps.
Make sure that all links are properly descriptive.
2.4.4 Link Purpose (In Context) (A)
All buttons have an accessible name.
Example:An icon without any visual text requires a textual description in the code, e. g hamburger menu icon reads out menu for screen readers.
Visible text on interactive elements, should have the same description given to assistive technology.
2.5.3 Label in Name (A)
Example:If there is a need for further description of an interactive object with visible label, the additional description must start with the same visible text.
Required input field is marked up with color, text and programmatically associated.
All interface elements requiring user input have a visible label.
3.3.2 Labels or instructions (A)
Labels and instructions need to be linked to the input field and conveyed to screen reader.
1.3.1 Info & relationships (A)
Provide important instructions or cues for input fields so that the users know that input data is expected.
Input field with recurring information about the user requires automcomplete/autofill.
1.3.5 Identify Input Purpose (AA)
Example:The person’s name, home address, telephone number and email address.
All errors in forms are described in text, explaining what is wrong.
3.3.1 Error identification (A)
Errors are described in text with information on how to correct the error (if possible).
3.3.3 Error suggestions (AA)
Example:3.3.1 requires that the error message have a textual description, while 3.3.3 requires that the description also contains information on how to correct the error.
Error messages need to be conveyed to screen reader.
1.3.1 Info and relationships (A),4.1.2 Name, role, value (A)