Accessibility Statement

On the other hand, the content of the points listed below are not accessible for the following reasons:

9.1.3.2 Significant sequence (Conditional)

Condition: When ICT is a web page.
When the sequence in which the content is presented affects its meaning, the correct reading sequence can be determined by software.
https://www.w3.org/TR/WCAG/#meaningful-sequence

9.1.3.5 Identification of the purpose of the entry (Conditional)

Condition: When ICT is a web page.
The purpose of each input field that collects information about the user can be determined programmatically when:
– The input field serves an identifying purpose in the input purposes of the user interface components, and
– Content is implemented using technologies with support to identify the expected meaning of input data in forms.

https://www.w3.org/TR/WCAG/#identify-input-purpose

9.1.4.13 Content marked with the pointer or having the focus (Conditional)

Condition: When ICT is a web page.
If receiving and then removing the pointer or focus from the keyboard activates the additional content so that it becomes visible and then hidden, the following is true:

-Can be removed: A mechanism is available to discard additional content without moving the keyboard pointer or focus, unless the additional content communicates an input error or does not obscure or replace other content.
-Hoverable: If the pointer can activate the additional content, then the pointer can move over the additional content without the additional content disappearing.
-Persistent: Additional content remains visible until the cursor or focus trigger is removed, dismissed by the user, or their information is no longer valid.

https://www.w3.org/TR/WCAG/#content-on-hover-or-focus

9.2.1.1 Keyboard (Conditional)

Condition: When ICT is a web page

All content functionality is operable through a keyboard interface without requiring a certain speed for each individual keystroke, except when the internal function requires input that depends on the path of the user’s movements and not only on the start and end points (Level A)

Note 1: This exception refers to the underlying function, not the data entry technique. For example, if text input is done by handwriting, the input technique (handwriting) depends on the stroke (traced path) but the internal function (entering text9 does not.

Note2: This does not and should not discourage authors from providing mouse input or other data entry methods additional to keyboard operability.

https://www.w3.org/TR/WCAG/#keyboard

9.2.1.2 No keyboard focus traps (Conditional)

Condition: When ICT is a web page

If it is possible to move focus to a component on the page using a keyboard interface, then focus can be removed from that component using only the keyboard interface and, if anything other than the arrow or tab keys is required, the user is informed of the appropriate method for moving focus (Level A)

Note: To the extent that any content that does not meet this criterion may interfere with the user’s ability to use the site fully, any content on the website (whether or not it satisfies other compliance criteria) must satisfy this criterion. See Conformity Requirement 5: No interference.

https://www.w3.org/TR/WCAG/#no-keyboard-trap

9.2.1.4 Keyboard Shortcuts (Conditional)

Condition: When ICT is a web page

In the event that to activate the interaction elements (links, buttons, etc.) keyboard shortcuts are used using a single letter, punctuation mark, number or symbol then at least one of the following conditions must be met:

-There is a mechanism that allows you to disable the keyboard shortcut
-There is a mechanism that allows you to reassign the keyboard shortcut to use another non-printable key (e.g. Ctrl, Alt, etc.) instead.
-The keyboard shortcut can only be activated when the component has keyboard focus.

https://www.w3.org/TR/WCAG/#character-key-shortcuts

9.2.4.1 Avoid Blocks (Conditional)

Condition: When ICT is a web page
There is a mechanism to avoid content blocks that are repeated on multiple web pages (Level A)

https://www.w3.org/TR/WCAG/#bypass-blocks

9.2.4.5 Multiple Pathways (Conditional)

Condition: When ICT is a web page
More than one path is provided for locating a web page within a set of web pages except when the page is the result, or an intermediate step, of a process (Level AA)

https://www.w3.org/TR/WCAG/#multiple-ways

9.2.4.7 Visible Focus (Conditional)

Condition: When ICT is a web page

Any keyboard-operable user interface has a way of operating in which the keyboard focus indicator is visible (Level AA)

https://www.w3.org/TR/WCAG/#focus-visible

9.2.5.2 Pointer Cancellation (Conditional)

Condition: When ICT is a web page

For functionality that can be operated with a single pointer, at least one of the following is true:

-No downstream event: The downstream pointer event is not used to execute any part of the function:

-Abort or Undo. The completion of the function is in the up event, and there is a mechanism available to abort the function before it completes or to undo the function after it completes;

-Upward inversion: The upstream event reverses any outcome of the previous downstream event;

-Essential: Completing the function in the downstream event is essential.

https://www.w3.org/TR/WCAG/#pointer-cancellation

9.2.5.4. Motion Activation (Conditional)

Condition: When ICT is a web page

Functionality that can be operated by device movement or user movement can also be operated by user interface components and motion response can be disabled to prevent accidental activation, except when:

-Compatible interface: motion is used to operate functionality through a compatible accessibility interface;

Essential: Movement is essential to function and doing so would invalidate activity.

https://www.w3.org/TR/WCAG/#motion-actuation

9.3.2.2 When receiving entries (Conditional)

Condition: When ICT is a web page

Changing state in any UI component does not automatically cause a change in context unless the user has been warned of that behavior before using the component (Level A)

https://www.w3.org/TR/WCAG/#on-input

9.4.1.1 Processing (Conditional)

Condition: When ICT is a web page

In content implemented through the use of markup languages, elements have full opening and closing tags; the elements are nested according to their specifications; items do not contain duplicate attributes and IDs are unique, except when specifications allow these features (Level A)

Note: Opening and closing tags that are missing a form-critical character, such as a “greater than” sign or missing opening or closing quotation marks in an attribute value, are not considered complete.

https://www.w3.org/TR/WCAG/#parsing

9.4.1.2 Name, Function, Value (Conditional)

Condition: When ICT is a web page

For all user interface components (including but not limited to: form elements, bindings, and scripted components), the name and function can 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

9.6 WCAG Guidelines Conformity Requirements (Conditional)

Condition: When ICT is a web page

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

1. level of compliance;
2. full pages;
3. complete processes;
4. use of technologies only in methods that are compatible with accessibility;
5. No interference.

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

NOTE 2 According to WC3, “The WCAG 2.1 Guidelines extend the Web Content Accessibility Guidelines 2.0 [4], which were published in the form of a WWW Recommendation in December 2008. Content that complies with the WCAG 2.1 Guidelines is also compliant with the WCAG 2.0 Guidelines and, consequently, with the policies that reference the WCAG 2.0 Guidelines [4].

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

11.8.4 Repair Service (Conditional)

Condition: When the web content is an authoring tool.

If the accessibility checking functionality of an authoring tool can detect whether the content does not meet a requirement of chapters 9 (Web) or 10 (Non-Web documents), as applicable, then the authoring tool should provide a suggestion(s) for repair.

NOTE This does not preclude automatic or semi-automatic repair, which is possible (and recommended) for many types of content accessibility issues.