KAMİS
AAA Level Principles
Sign Language (Pre-recorded)
Principle
Sign language interpretation should be provided for audio content.
Description
Sign language is a universal method used by deaf individuals to access audio content. Translations provided in sign language can be more effective than captions because they support the audio content with gestures and facial expressions. Therefore, it is expected that sign language interpretation be provided for all audio content on websites.
References
- WCAG 2.0 – Level AAA / 1.2.6
Example
As seen on the example website, sign language interpretation is expected in pre-recorded videos to ensure accessibility for deaf users.
Extended Audio Description (Pre-recorded)
Principle
Audio descriptions should provide detailed information.
Description
In cases where video content on websites is complex or where visual content cannot be adequately explained through narration, it may be challenging for visually impaired users to understand the content solely through listening. Therefore, when there is a need for more detailed explanations of visuals, video content should be paused, and additional information and descriptions should be provided to users through audio.
References
- WCAG 2.0 – AAA Level / 1.2.7
Example
As seen on the sample website, video content is interspersed with information about the video in detail, provided to users through audio.
Media Alternative (Pre-recorded)
Principle
Videos should have detailed alternative representations.
Description
In order for visually and hearing impaired users to effectively and efficiently use video content on websites, detailed media alternatives should be provided. Video content and visual elements within the media should be described in detail, including sounds and effects that are not part of the on-screen dialogue. Additionally, providing media alternatives in text form is recommended for ease of use with assistive technologies (e.g., screen reader programs, etc.).
References
- WCAG 2.0 – AAA Level / 1.2.8
Example
As shown on the sample website, the text version of the video content is provided to enhance accessibility. The text should cover not only the content but also details about the media (e.g., gestures made by people while speaking, on-screen changes, etc.).
Audio Content (Live)
Principle
Text alternatives should be provided for live audio content.
Description
Text alternatives should be provided for live audio content on websites. For example, topic headings and presentation notes can be shared with users for a live speech. This allows hearing-impaired users to have information about the audio content.
References
- WCAG 2.0 – AAA Level / 1.2.9
Example
The example website provides the content of the audio recordings to users.
Contrast (Enhanced)
Principle
Text and visual elements should have appropriate contrast ratios.
Description
To achieve AAA compliance for websites, the contrast ratio between text and visual elements and the background should be 7:1. However, a contrast ratio of 4.5:1 may be sufficient for large-scale images and graphics. Contrast ratios are not required for organization logos and images used for decorative purposes.
References
- WCAG 2.0 – AAA Level / 1.4.6
Example
Background colors and text colors to be used on websites should be tested. In the example image, the chosen colors do not provide adequate contrast for accessibility. Contrast tests can be conducted online at http://snook.ca/technical/colour_contrast/colour.html.
Low or No Background Sound
Principle
Background sounds should be used carefully.
Description
The use of background sounds in audio and video elements on websites can make it difficult for disabled users to focus on content. Therefore, the use of background sounds should be avoided unless necessary. In cases where background sounds are used, users should be provided with an option to turn off the background sound, and the background sound should be at least four times lower (minimum 20dB lower) than the foreground speech content.
References
- WCAG 2.0 – AAA Level / 1.4.7
Example
The example image is taken from a university promotional video. While there is a narration in the video, the sound of the water seen in the image is also playing in the background. This can make it difficult for users to understand the content being conveyed in the promotion, especially if it continues for an extended period.
Visual Presentation
Principle
Text should be formatted to be readable.
Description
When formatting text blocks on websites, consider disabled users. Users should be able to adjust text and background colors to meet their needs. Each line should have a maximum of 80 characters (e.g., letters, numbers, symbols, glyphs, etc.), and text should not be justified. Ensure a minimum line spacing of 1.5 lines, and paragraph spacing should be at least 1.5 times the line spacing.
References
- WCAG 2.0 – AAA Level / 1.4.8
Example
In the example website, each line contains a maximum of 80 characters, and the line spacing is greater than 1.5.
Text Images (No Exception)
Principle
Text should not be presented as images.
Description
Except for text used for purely decorative purposes and logos, text should not be presented as images on websites. Text presented in image format cannot be perceived by screen reader programs and can adversely affect the accessibility of the website.
References
- WCAG 2.0 – AAA Level / 1.4.9
Example
In the example website, all content is added as plain text. There are no text converted into image format.
Keyboard (No Exception)
Principle
All content must be operable by a keyboard.
Description
All content and functions on websites must be operable by a keyboard. According to this principle, the entire website must be operable by a keyboard under all conditions.
References
- WCAG 2.0 – AAA Level / 2.1.3
Example
In the example website, operations can be carried out using the keyboard, and instructions on how to perform these operations are provided to users.
Timing Not to be Used
Principle
Time limits should be avoided.
Description
Having time limits for content and actions on websites can prevent disabled users from effectively using the content or completing tasks. Therefore, website content should be designed without time limits. It is advisable to inform users that there are no time limits for the actions performed.
References
- WCAG 2.0 – AAA Level / 2.2.3
Example
In the example website, the imposition of a time limit to complete a survey negatively affects the accessibility of the website. Whenever possible, time limits should be avoided on websites, and in cases where time limits are necessary, users should be allowed to extend or stop the time.
Chapter Breaks
Principle
Users should be able to disable non-emergency updates.
Description
Automatic updates of alert messages and content on websites can cause confusion for disabled users. Therefore, users should be provided with the option to disable automatic updates of alert messages and content. However, exceptions can be made for situations of high importance to users.
References
- WCAG 2.0 – AAA Level / 2.2.4
Example
In the example website, users are given the option to stop automatic updates of content, which can be disabled if desired.
Renewal of Authentication
Principle
Users should be able to continue their processes without data loss when the session expires.
Description
In websites where a session is established by authentication, when the session expires, users should be able to renew the authentication and continue their processes without losing data. Users whose session has expired should be informed, and after entering their username and password, they should be able to resume their processes from where they left off.
References
- WCAG 2.0 – AAA Level / 2.2.3
Example
In the example website, a user whose session has expired lost the information previously entered when they renewed their session.
Three Flashing
Principle
Websites should not contain content that flashes more than three times in any one-second period.
Description
It is known that elements flashing more than three times in one second can trigger seizures in epilepsy patients. Therefore, regardless of the purpose, content, color, or size of elements, websites should not use elements that flash more than three times in one second.
References
- WCAG 2.0 – AAA Level / 2.3.2
Example
The use of elements that flash more than three times in one second on websites can create medical problems for some users. The example images are taken from animated graphics. On the internet, these images flash more than three times per second and can be disturbing to the user.
Location
Principle
Users should be informed about their locations on the website.
Description
The locations and the current page information on the website should be shared with the users. The breadcrumb feature can be used for this purpose. With the breadcrumb feature, the pages that users have navigated to reach the current page are listed in order, allowing users to understand their location on the website.
References
- WCAG 2.0 – AAA Level / 2.4.8
Example
In the example website, users are provided with information about where they are located using the breadcrumb feature.
Link Purpose (Link Only)
Principle
Link text should describe the purpose of the link.
Description
The purpose of links should be understandable just by looking at the link text on websites. Link text should be clear, understandable, and designed to explain the purpose of the link. Avoid using expressions that users may not understand or that may cause confusion.
References
- WCAG 2.0 – AAA Level / 2.4.9
Example
As seen in the example image, instead of using only the text "Find" in the button label, it is better to use the label "Find the Nearest Bus Station" to provide an idea about the action to be taken when the button is clicked.
Section Headings
Principle
Section headings should be used to structure content.
Description
Content on websites should be divided into small, meaningful sections. Additionally, the entire content and subsections should be labeled in an explanatory and understandable manner. This allows users to better comprehend content and navigate between sections more easily.
References
- WCAG 2.0 – AAA Level / 2.4.10
Example
As seen on the example website, the content is appropriately structured with headings. Using relevant headings that are related to the content will enhance comprehensibility.
Uncommon Words
Principle
Provide explanations for unfamiliar or unknown words.
Description
If websites contain expressions that users may not be familiar with, may not understand, or include jargon, it is necessary to provide explanations for these expressions. Links can be provided to dictionaries or explanation pages that can also be used by assistive technologies like screen readers.
References
- WCAG 2.0 – AAA Level / 3.1.3
Example
In the example website, links are provided for words that users may not be very familiar with, directing them to pages that explain the meanings of these words.
Abbreviations
Principle
Provide expansions and meanings for abbreviations.
Description
Expressions containing abbreviations in website content may not be understood by disabled users. Therefore, the expansions and meanings of abbreviations should be indicated in the HTML code in a way that screen reader programs can perceive.
References
- WCAG 2.0 – AAA Level / 3.1.4
Example
As shown on the example website, to ensure that abbreviations are read smoothly by screen readers, their full forms need to be explicitly stated in the HTML code.
Reading Level
Principle
Content should be simple and understandable.
Description
Content on websites should be designed to be simple and understandable. When creating content, short and well-known expressions should be used, and if possible, summary texts should be provided for the content. Simplifying content will be useful for users who have difficulty perceiving text. In addition, supporting text with images and visuals enhances content comprehensibility and is recommended.
References
- WCAG 2.0 – AAA Level / 3.1.5
Example
As seen on the example website, content should be simple and straightforward. The use of images related to the content will help users grasp the content more quickly and easily.
Pronunciation
Principle
If the meaning of words is affected by how they are pronounced, appropriate pronunciations should be clearly specified.
Description
On websites, if words have different meanings when pronounced differently, the correct pronunciation of the word should be explained. For example, the word "lead" can mean different things depending on whether it's pronounced as "leed" or "led." Additionally, homographs, which are words that are spelled the same but have different meanings, should be used carefully. It's expected that words are explained and pronounced in a way that users do not get confused.
References
- WCAG 2.0 – AAA Level / 3.1.6
Example
In the example website, a link is provided that includes an explanation and pronunciation of a word with different pronunciations.
Change on Request
Principle
Automatic changes should only be initiated or stopped at the user's request.
Description
On websites, elements such as sliders or automatic content updates can be disturbing for disabled users when content changes automatically. Therefore, changes and updates related to content should only be initiated and stopped at the user's request.
References
- WCAG 2.0 – AAA Level / 3.2.5
Example
In the example website, users are provided with the ability to control automatic updates. Users who cannot read a website quickly may find automatic updates disturbing. To cater to users with reading difficulties, the option to turn off automatic updates should be provided.
Help
Principle
Aid function should be provided according to the content.
Description
On websites, an aid option should be provided, taking into consideration the users' needs and actions. When offering an aid option, users should not be forced to search for help content on different pages. Instead, help text that is easily accessible from the current page and directly related to the actions taken should be provided to the users.
References
- WCAG 2.0 - AAA Level / 3.3.5
Example
In the example website, links to help content on how users who have forgotten their password or have never received a password can get a new one have been provided.
Prevention of Errors (All Errors)
Principle
Users should be prevented from making errors as much as possible.
Description
Measures should be taken on websites to prevent users from making errors. Users should be able to review, revise, or cancel their actions.
References
- WCAG 2.0 - AAA Level / 3.3.6
Example
In the example website, users are allowed to go back to the previous steps and update the entered information.
Determining Element Purpose
Principle
The type and purpose of all elements in the interface should be determined and reflected in the coding process.
Description
The purpose of all elements such as sections, buttons, icons, etc., in the interface should be determined, and these properties should be reflected in the coding process. This is especially important for screen reader technologies and other assistive technologies that read web interfaces in a textual manner. It will make it easier for these users to understand the functions of the elements on the screen and enable them to use the website more effectively.
References
- WCAG 2.1 - AAA Level / 1.3.6
Example
On websites, navigation links and icons are marked up to allow users to use their own icon sets.
Timeouts
Principle
Users should be warned in advance about any user inactivity time that could lead to data loss.
Description
Users should be warned in advance when a timeout occurs that could result in data loss. Because disabled users may require extra time to perform functions such as reading content or filling out an online form, restricted timeframes can pose significant barriers for these users. If users are aware of the time given for a task, they can avoid data loss.
References
- WCAG 2.1 - AAA Level / 2.2.6
Example
There should not be a timeout period set for filling out and submitting online forms on a website. The information entered into the form should be saved in the background and should be sent only when the user prefers. The contact form should only be closed when the user chooses to do so.
Animation Interaction
Principle
Motion animations triggered by interaction can be disabled unless they are necessary for animation functionality or conveyed information.
Description
Animations on web pages should not be designed to cause seizures or physical reactions. Animations should be able to be turned off or stopped when desired.
References
- WCAG 2.1 - AAA Level / 2.3.3
Example
Animations that do not serve the purpose of providing information or content on the screen should not be included. If an animation is added, it must serve a purpose, and users should be able to disable the animation if they prefer not to view it.
Target Size
Principle
The size of buttons and targets for pointer inputs should be large enough.
Description
The size of the button for pointer inputs should be at least 44 x 44 pixels. When users need to access content on a small-screen touchscreen device, the clickable area should still be large enough for easy interaction with the content under all conditions.
References
- WCAG 2.1 - AAA Level / 2.5.5
Example
If there are 3 buttons on a screen, the clickable area for each of the 3 buttons is made 44 x 44 pixels.
Simultaneous Input Mechanisms
Principle
Unless restrictions are necessary for security purposes or to comply with user settings, the use of available input methods should not be restricted.
Description
Users should be able to use and switch between different input mechanisms when interacting with content. Users can use various input mechanisms, such as a keyboard, mouse, stylus, or touch screen when interacting with content. Users should be able to change their input mechanisms if they find that specific tasks and interactions are easier to perform using an alternative input mechanism. They should have the flexibility to switch between input mechanisms as they prefer.
References
- WCAG 2.1 - AAA Level / 2.5.6
Example
A user opens a menu on a website using mouse interaction and then navigates through the menu items using arrow keys.