You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each instance acting in the public domain in the Germany/EU (internet + intranet) is responsible for taking care of it. The contact and legal contact depend on the base of the main responsible organization for the instance (mainly related to the domain and/or contract partner organization, self-hosting, -> hosting organization).
We, as BEXIS2, can (will try) provide the test result referring to the standard setting, which could be linked from the instance-specific accessibility statement. It is their responsibility to test/add results if they change the CSS colors, footer, header, or add own modules.
The test and the statements need to be updated yearly. Self-testing is enough (no paid testing by a company is required except you need the certificate for your product - if the customer enforces, you have to go the paid way). Testing all pages on all levels is unnecessary, but you should select a representative selection. User content is a big problem as it is outside your influence.
Institutions' websites are checked randomly (~3 years), and they get a list of improvements back—so far, no big "law" issues.
Our overall main goal during the development is to avoid accessibility issues as long as it is done with a reasonable amount of effort.
language English is fine (will be verified by the university team during the next days)
add as todo to installation instructions (also add adjustment of contact details)
Accessibility statement
Each instance acting in the public domain in the Germany/EU (internet + intranet) is responsible for taking care of it. The contact and legal contact depend on the base of the main responsible organization for the instance (mainly related to the domain and/or contract partner organization, self-hosting, -> hosting organization).
We, as BEXIS2, can (will try) provide the test result referring to the standard setting, which could be linked from the instance-specific accessibility statement. It is their responsibility to test/add results if they change the CSS colors, footer, header, or add own modules.
The test and the statements need to be updated yearly. Self-testing is enough (no paid testing by a company is required except you need the certificate for your product - if the customer enforces, you have to go the paid way). Testing all pages on all levels is unnecessary, but you should select a representative selection. User content is a big problem as it is outside your influence.
Institutions' websites are checked randomly (~3 years), and they get a list of improvements back—so far, no big "law" issues.
Our overall main goal during the development is to avoid accessibility issues as long as it is done with a reasonable amount of effort.
The text was updated successfully, but these errors were encountered: