In the first meeting, we will discuss your questions and plan the content and time frame.

We are happy to consult you in an initial meeting.

We are happy to conduct a workshop with a screen reader demo in order to raise awareness in your project team and to help you build up the necessary know-how.

More information about the content and framework of the workshop

For a review, we set a time frame, e.g. 2 or 3 workdays, within which we identify whether basic accessibility requirements are met. Among other things, we check design style guides, wireframes, contrasts and templates. This allows us to identify problems at the HTML/CSS level at an early stage.

Once the basic barriers have been remediated, the so-called audit maturity is reached, and we carry out a complete audit of WCAG compliance of the fully implemented system. For this purpose, we need comprehensive information from you as the website operator or from the agencies involved:

• List of pages on which as many different content elements as possible can be found
• Information on integrated special applications
• Information on third-party content or multimedia formats

Depending on the complexity, we need about 4 weeks for the audit. A team of accessibility specialists with and without disabilities will perform the audit.

The result is a detailed audit report in which we document whether all WCAG success criteria of conformance levels A and AA are met. In the case of non-fulfillment, we document the findings. We do not record all occurrences, but examples of violations. We provide these including URL, a screenshot of the element, a problem description and a suggested solution, sometimes also with code examples or links to further resources or to examples of accessible implementations. Usually, a discussion of the problems and viable solutions in a workshop can help understand and remediate the barriers, since WCAG and the existing problems allow for different solutions.

After you have remediated the issues uncovered in the audit and any analogous cases on your website, app, or system, you can submit it to us for retesting. At this point, we check the barriers identified in the audit and how they were fixed, and whether the measures were implemented thoroughly and across the board. Only then can a certification be issued.

If, after remediation of all findings, we determine accessibility in full compliance with WCAG, we issue the certification and award the certificate. Depending on whether all checkpoints of conformance level A or AA have been achieved, the corresponding label can be published on your website. The certified website will be added to our index of accessible websites.

When fundamental adjustments need to be made to a website, the accessibility must be tested again. We will clarify with you on a case-by-case basis whether a short test after a major update or a detailed accessibility audit with new certification is required.

• Advantage for clients: The requirement “accessible website” can be precisely defined, neutrally evaluated, and communicated upon achievement. Thus, the required compliance with the WCAG requirements, e.g., for public authority offerings, can be proven.
• Advantage for designers and developers: WCAG requirements are consistent, objectively testable, and transparent.
• Advantage for people with disabilities: Certified websites mean accessible information and services and thus implemented inclusion. For this purpose, every website is subjected to a practical check by accessibility specialists with disabilities.

The test procedure is standardized. There are defined test steps for each success criterion. In this way, every assessment is verifiable.

The test procedure of the “Access for all” foundation is based on the internationally recognized “Web Content Accessibility Guidelines (WCAG)“.

The domain to which the certification applies must be completely transparent to all users. Normally, certification applies to all content under a domain name (e.g.: “www.domain.ch”). However, it is also possible to certify parts of a website if this area is recognizable or separable and communicated transparently in a declaration of conformity.

Within the certified area of a website, we review all web content. All of it must be WCAG-compliant, including embedded PDF, multimedia, and script programming.

WCAG compliance conditions

For compliance of one of the levels A (lowest), AA (recommended) or AAA (highest), the whole website must meet all success criteria of the corresponding level(s) or a level-compliant alternative version is provided. The conformance logo must be accompanied on the website by a brief explanation with required components.

Partial compliance with WCAG

If the website meets all criteria and uncontrolled content of it is not accessible (e.g. the embedded stock market indexes from an external supplier), it can be pointed out by means of a “declaration of partial conformity”.

The requirements are:

• The content is not under the control of the author.
• All parts (pages and sections) are listed and labeled in a way that is easy to understand.

Public sector guidelines

The eCH standard 0059 references WCAG conformance levels A and AA.

“Access for all” compliance regulation for PDF

• If content is accessible on the website and is also available as a PDF, the PDF files do not necessarily have to be accessible.
• If content in PDF files is not accessible and cannot be offered as an alternative, the website will not be compliant accordingly.
• If PDF files are not specifically optimized for accessibility, but the content is understandable with the listed test environments and these cannot be offered as an alternative, A or AA conformance is possible, but not AA+ or AAA.
• If PDF files are optimized for accessibility and meet the success criteria, A-, AA-, AA+- or AAA- conformance is possible.

Basic and advanced techniques according to WCAG

The basic and advanced techniques must ensure accessibility support. Other techniques used must not interfere with accessibility. A test environment is defined for this test procedure.

Each success criterion has defined test steps, which are performed as follows:

1. Expert-based testing with testing tools
2. By users with representative, assistive technologies
3. By HTML and CSS and script code analysis

In case of doubt, “Access for all” gives higher value to the test results by users of representative assistive technologies.

Random samples of websites are selected from a range and tested. In the test report, problems are documented for each success criterion with examples encountered. Improvement measures are recommended for each problem. The examples listed are not comprehensive. When remediating the accessibility violations, it is important to ensure that not only the examples listed are improved, but all problems of this type in each case.

The most common components used by typical and average users serve as the test environment.

• Operating system: Windows 10
• Java Runtime Environment: latest version (no Java applications are tested in the standard test, but the usability within the website is tested)
• Screen resolution: min. 1024 x768 pixels, 32-bit color
• Browser: latest versions of Mozilla Firefox and Google Chrome, for Win HCM (High Contrast Mode) also Edge
• Activated in browser: JavaScript, Java, Cookies
• Standard QWERTZ keyboard

Assistive technologies

• Screen reader NVDA, latest version
• Screen reader JAWS, latest version

Screen reader and browser combinations to be supported

The following screen reader and browser combinations must be supported for a website to be certified:

• JAWS on Firefox and Google Chrome
• NVDA on Firefox and Google Chrome

According to WebAIM Screen Reader User Survey #9 (2021), this covers the largest user groups.

User-side settings

These user-specific settings are also used for testing:

• Enlarge view: Firefox zoom function to 200%
• Mobile viewport: window adjustment on desktop (or in Firefox via Ctrl + Shift + M)
• View with user-defined color settings: in Edge via High Contrast Mode (HCM) (checkable via Shift + Alt + PrtScr)

Test tools and test programs

A variety of tools are used, including:

• For the verification of color contrasts according to the algorithm of the W3C is used: Colour Contrast Analyser
• For checking HTML documents for validity: TotalValidator (the results are comparable with: https://validator.w3.org/)

Many users rely on the ability to customize content, such as font enlargement in the browser, or use a special output device, such as a screen reader. Also, keyboard users who do not use a mouse are often overlooked. The spectrum of people with a disability ranges from age-related mobility and visual impairments to motor-impaired quadriplegics and blindness. There are many soft and individual barriers faced by the many user groups.

Internet-based communication technologies provide these groups of the population with a major opportunity to participate in information, education, and society.

Constitution and law require equality

Because the amount of information published exclusively on the Internet is constantly increasing, the Disability Discrimination Act (DDA) provides for special measures: Since January 1, 2004, Internet offers of the authorities (Confederation, cantons, municipalities, and all other public organizations) must be designed to be accessible so that all people with a disability can use them without barriers.

Changes in the population pyramid

Demographic trends suggest that soon most of the population will be “silver surfers” (see: Development of the Swiss population pyramid, Swiss Federal Statistical Office). Mild and severe disabilities increase with age. This development is a challenge for every communication offer.

Clear trend towards user-friendliness

If for a long time the most feature-rich websites were considered particularly great, today it is those that are the most user-friendly. The maxim for usability is accessibility. This insight is also gaining ground in the marketing strategy of large companies and is already being transferred from web design to the entire customer relationship at some companies.

For these reasons, more websites from the private sector are voluntarily implementing the requirements for accessible web design. Accessibility will eventually be the norm.

Advantages in maintenance and search engines

Because presentation and content must be consistently separated, an accessible website is easier to maintain and expand, a redesign is far more cost-effective. The standards also lead to advantages in search engines, as accessible websites are displayed faster and cleaner and are better indexed.

A physical, mental, or psychological disability can make it difficult or impossible to use the Internet. Depending on the disability, the effects on working with the computer and thus the requirements are different.

Categories of disabilities and their requirements regarding Internet use:

For individual adaptability to work, there are some rules to follow and precautions to take when designing and programming Internet offerings. Accessible websites do not differ outwardly from inaccessible ones.

Accessible web design is very well elaborated and documented for HTML, XHTML and CSS. But it is also applicable today for all content that can be published on the web. The important instructions for accessible web design are freely available on the Internet.

The advantages of certification:

• Clearly defined requirement in the client’s specifications.
• Clearly defined requirement for service providers, e.g. web agencies
• Assured legal compliance of websites according to the DDA
• Best quality test of websites

Isn’t a test with automatic tools also sufficient?

Absolutely not. The numerous testing tools show remarkable deficiencies in their assessment. Most of the criteria in the accessibility guidelines require human judgment, for example: Does the alternative text of an image make sense?

However, automated testing tools are suitable for quantitatively assessing technical aspects of a website.

Can’t a self-assessment also suffice?

Unfortunately, numerous websites that claim to be accessible are insufficiently accessible. Clients often have to trust that the agency will deliver what it promises. We have the impression that contractors often count on clients not being able to check accessibility themselves. Evaluation by an external and independent partner is therefore important.

Whether a website is accessible and complies with the standards is verified in cooperation with disabled accessibility specialists and their assistive devices. Each website to be certified is tested by people with disabilities using various alternative input and output devices.

The test is based on the international WCAG guidelines and offers the guarantee of meeting the Swiss legal requirements. The certificate for accessible websites is a tool for the correct implementation of the standards.

Experience has shown that the documented deficiencies were often not or only partially corrected. The clear rules for awarding the certificate increase the incentive to correct the deficiencies. The label may only be worn by those who fulfill all checkpoints.

The label is a crucial step towards promoting accessibility in Switzerland.

Numerous checkpoints of the guidelines can only be conclusively assessed with practical tests. Certification is therefore carried out with tests by users:

1. Use of experienced accessibility specialists who are themselves affected by a disability (blind, visually impaired and motor-impaired accessibility testers)
2. Technical conformance testing by experienced web specialists ((X)HTML, CSS)
3. Experienced team – more than 20 years of testing experience

The results of the tests are summarized in a report and supplemented with suggestions for improvement measures. A good portion of advice is included in many suggestions.

Every certification is a process and a positive experience for both sides. The employees of the foundation appreciate the esteem in which their work is held.

Certification is not required by law. Website operators can also check compliance with the clearly defined legal requirements for accessibility in other ways. However, the certification has proven itself very well in the evaluation of the federal websites and other official large and small websites as well as many company websites.

In competition with other procedures, the “access-for-all” accessible website certificate has prevailed. It offers the greatest possible assurance of compliance with legal requirements. At the same time, it is practice-oriented and realistic, and thus cost-efficient.

Legal requirements and deadlines

The Disability Discrimination Act (Behindertengleichstellungsgesetz, BehiG) and the Disability Discrimination Directive (Behindertengleichstellungsverordnung, BehiV) have been in force since January 1, 2004.

Law: Internet services provided by the state (federal government, cantons, municipalities) must be accessible to people with disabilities without aggravating conditions.

To implement the law, the federal government has issued an ordinance setting out the criteria. All federal websites must have implemented accessibility according to the Accessibility Standard eCH-0059.

For private and non-governmental Institutions

Law: No discrimination against population groups.

So there is no direct legal obligation for private and non-governmental institutions, but:

Accessible websites are an expression of social responsibility and technical competence.
Accessibility is a quality feature.

Legal sanction options

It is up to organizations of people with disabilities to take legal action against official or private service providers. It is unclear what sanctions would be imposed as no proceedings have yet led to a lawsuit in Switzerland.