Accessibility statement

Condition: When the ICT is a web page.

For each time limit imposed by the content, at least one of the following is true: (Level A)

• Shut down: User can stop the time limit before reaching the time limit; either
• Adjust: The user can adjust the time limit before reaching the limit in a wide range that is at least ten times greater than the originally set time; either
• Extend: The user is warned before the time expires and is given at least 20 seconds to extend the time limit with a simple action (for example, “press space bar”) and the user can extend that time limit at least ten times; either
• Exception for being essential: The time limit is essential and, if extended, would invalidate the activity; either
• 20 hour exception: The time limit is more than 20 hours.

Note: This success criterion helps ensure that users can complete tasks without unexpected changes to content or context that are the result of a time limit. This criterion should be considered in conjunction with conformance criterion 3.2.1, which places limits on changes to content or context as a result of a user action.

https://www.w3.org/TR/WCAG/#timing-adjustable

Condition: When ICT is a web page.

For information that moves, flickers, scrolls, or updates automatically, all of the following cases are true: (Level A)

• For all moving, blinking, or scrolling information that (1) starts automatically, (2) lasts longer than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to put it into action. pause, stop or hide unless the movement, blinking or scrolling is part of an activity for which it is essential.
• Auto-Update: For all auto-update information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, hide, or control the frequency of the update. update unless the update is part of an activity where it is essential.NOTE. For requirements related to blinking or flashing content, see Guideline 2.3.

NOTE. Because any content that does not meet this success criterion may interfere with the user’s ability to use the entire page, all content on the web page (whether used to meet other success criteria or not) must meet with this success criterion. See Compliance Requirement 5: Non-interference.

NOTE. Content that is periodically updated by software or transmitted to the user agent is not required to retain or present information that is generated or received between the start of the pause and the resumption of presentation, as this may not technically be possible and in many situations it could be misleading to do so.

NOTE. An animation that occurs as part of a preload phase or similar situation may be considered essential if the interaction cannot occur during that phase for all users and if it does not indicate progress it could confuse users or make them think that the content has frozen or broke.

https://www.w3.org/TR/WCAG/#pause-stop-hide

Condition: When the ICT is a web page

The language of each passage or phrase in the content may be determined by software, except for proper nouns, technical terms, words in an undetermined language, and words or phrases that have become a natural part of the surrounding text. (Level AA).

https://www.w3.org/TR/WCAG/#language-of-parts

Condition: When the ICT is a web page

For all user interface components (including but not limited to: form elements, links, and script-generated components), the name and function may be determined by software; the states, properties and values ​​that can be assigned by the user can be specified by software; and changes to these elements are available for consultation by user applications, including technical aids. (Level A)

NOTE. This success criterion is primarily intended for web authors who develop or program their own user interface components. For example, standard HTML controls automatically satisfy this criterion when used according to their specification.

https://www.w3.org/TR/WCAG/#name-role-value

Condition:When the ICT is a web page

The following five WCAG Guidelines 2.1 conformance requirements [5] must be satisfied at level AA:

1. conformity level
2. full pages
3. complete processes
4. use of technologies exclusively according to methods that are compatible with accessibility
5. without interference

NOTE 1. In the event that a web page meets all requirements 9.1 to 9.4 or an alternative version is provided conforming to level AA (as defined in WCAG Guidelines 2.1 [5]), conformance requirement 1 will be met.

NOTE 2. According to WC3, “The WCAG 2.1 Guidelines expand on the Web Content Accessibility Guidelines 2.0 [4], which were published in WWW Recommendation format in December 2008. Content that conforms to the WCAG 2.1 Guidelines also they are with the WCAG 2.0 Guidelines and, consequently, with the policies that refer to the WCAG 2.0 Guidelines [4].

NOTE 3. Compliance requirement 5 states that all content on the page, including content that would not otherwise serve as a basis for compliance, complies with sections 9.1.4.2, 9.2.1.2, 9.2.2.2 and 9.2.3.1.

Condition: When the web content is an authoring tool.

To the extent that the information necessary for accessibility is compatible with the format used for the output of the authoring tool, the authoring tools must comply with sections 11.8.2 to 11.8.5.