Are you from the public sector?
Are you from the public sector?
Test the complete functionality of AccessGO risk-free for 7 days free of charge.
An accessible website checklist provides those responsible for web projects with clear, structured guidance for implementing digital accessibility. It bundles all relevant requirements and criteria clearly, allowing you to understand step-by-step which measures are necessary to make websites accessible.
The checklist is based on the legal requirements of the BFSG, BITV 2.0, and the international standards of WCAG 2.1 AA. It contains practical checkpoints and specific implementation tips that help you systematically and efficiently anchor accessibility in your project.
An accessible website checklist is clearly structured and differs significantly from general to-do lists or simple test reports. It follows a systematic structure based on recognized standards and legal requirements. The focus is on the organization according to the requirements of the BFSG, BITV 2.0, and the criteria of WCAG 2.1 AA.
The individual checkpoints of such a checklist are divided into logically sequential categories. Typical categories include, for example, perceivability, operability, understandability, and robustness. Each category includes specific criteria relevant to the accessibility of a website. This provides those responsible with a transparent and practical guide specifically aimed at implementing legal requirements.
| Category | Example Checkpoints |
|---|---|
| Perceivability | Alt text for images, sufficient color contrasts |
| Operability | Keyboard accessibility, logical focus order |
| Understandability | Clearly understandable forms, unambiguous navigation |
| Robustness | Correct HTML structure, compatibility with assistive technologies |
The basic logic behind accessibility checklists is based on the four internationally recognized guiding principles: perceivability, operability, understandability, and robustness. These principles are directly linked to the requirements of the WCAG and serve as the foundation for developing practical test criteria. The checklist ensures that all relevant aspects of an accessible website are systematically considered.
In the testing process, these checklists fulfill a dual objective: they provide a transparent structure for reviewing individual components and support the sustainable implementation of accessibility throughout the entire web project. The consistent application of the principles makes it possible not only to meet short-term requirements but also to ensure a high level of accessibility in the long term.
7 days unrestricted access. No payment details required.
Success criteria in an accessible website checklist are precisely formulated requirements derived directly from legal mandates such as BFSG, BITV 2.0, and WCAG 2.1 AA. These criteria specify which aspects of a website must be checked to meet the minimum accessibility requirements. This ensures that the review remains not only complete but also transparent and comparable.
Various systems are used to evaluate individual success criteria. Simple scales such as “met/not met” are often used to clearly document implementation. Additionally, prioritization can be carried out, such as “critical”, “important”, or “recommended”. These types of evaluation help to plan measures in a targeted manner and systematically demonstrate compliance with minimum legal standards.
| Success Criterion | Evaluation Type |
|---|---|
| Alt text for images present | Met / Not met |
| Sufficient color contrast | Critical / Important / Recommended |
| Keyboard accessibility provided | Met / Not met |
| Form fields correctly labeled | Met / Not met |
The systematic testing of a website using an accessible website checklist takes place in several steps. First, all relevant checkpoints are processed using the checklist, employing both manual and automated methods. The combination of both procedures enables a comprehensive assessment, as not all aspects of accessibility can be checked automatically.
Complete documentation of the test results is crucial for transparency. Every finding – whether through a tool or human testing – is recorded in detail. This creates a transparent overview that can be used for both internal quality assurance and external audits. The structured process supports the sustainable improvement of accessibility.
| Manual Testing | Automated Testing |
|---|---|
| Evaluation of user experiences, e.g., through screen reader tests | Automated detection of technical errors, e.g., missing alt text |
| Identifies complex, context-dependent barriers | Fast checking of large volumes of pages |
| Requires expertise and time | Covers only machine-testable criteria |
| Indispensable for final assessment | Ideal for regular interim checks |
The practical implementation of an accessible website checklist begins with a clear step-by-step approach. First, the checklist is adapted to the specific requirements of the web project in question. The individual checkpoints are then worked through systematically, ideally as a team with clearly assigned responsibilities. Results are documented directly to make progress transparent and enable targeted follow-up action.
For integration into existing workflows, it is advisable to make use of established tools and resources. These include testing tools such as WAVE, axe, or the accessibility checker built into browsers, as well as project management software for task tracking. The process becomes more efficient when the checklist is regularly incorporated into the development cycle and all those involved are made aware of its importance. Short review cycles and targeted follow-up training support sustainable implementation.
| Step | Practical Tip / Tool |
|---|---|
| Adapt checklist to project requirements | Customize templates, add specific requirements |
| Work through checkpoints systematically | Distribute tasks within the team, document progress |
| Perform automated tests | Use tools such as axe, WAVE, and Lighthouse |
| Supplement with manual reviews | Screen reader tests, keyboard control, expert feedback |
| Evaluate results and initiate measures | Use project management tools, conduct regular reviews |
Schedule a free consultation and speak with one of our experts.
Website accessibility checklists are based on clearly defined legal foundations.
Website accessibility checklists are based on clearly defined legal foundations. In the German-speaking world, the most relevant frameworks are the Barrierefreiheitsstärkungsgesetz (BFSG), the Barrierefreie-Informationstechnik-Verordnung (BITV 2.0), and the international Web Content Accessibility Guidelines (WCAG 2.1 AA). These standards define the requirements that websites must meet in order to be accessible to all user groups.
While the legal requirements differ in their details, they share a common goal: enabling digital participation for everyone.
While the legal requirements differ in their details, they share a common goal: enabling digital participation for everyone. The BFSG website checklist primarily applies to private companies, while BITV 2.0 is binding for public bodies. The WCAG forms the substantive foundation of both frameworks and serves as the international standard. Checklists help to implement the respective requirements in a structured manner and document compliance in a transparent and traceable way.
| Law / Standard | Relation to the checklist |
|---|---|
| BFSG | Obliges private providers to implement accessible websites; checklist as an implementation tool |
| BITV 2.0 | Regulates accessibility for public bodies; checklist as a basis for verification and testing |
| WCAG 2.1 AA | International standard, forms the basis for checkpoints in checklists |
When using an accessible website checklist, misunderstandings and common errors frequently arise.
When using an accessible website checklist, misunderstandings and common errors frequently arise. These include the assumption that simply checking off all items automatically results in full accessibility, or that all requirements can be verified through purely technical means. The interpretation of individual checkpoints can vary depending on experience and prior knowledge, which may lead to inconsistent results.
Checklists reach their limits in everyday use when complex usage scenarios or the individual needs of people with disabilities are not adequately taken into account. The application of general checkpoints to specific website functions is also not always straightforward. To avoid these sources of error, it is advisable to update checklists regularly, work collaboratively as a team, and seek expert advice when uncertainties arise.
Various formats are available for implementing an accessible website checklist. Common options include static PDF checklists, interactive online forms, and tool-based solutions that can be integrated directly into the development process. Each format has its own advantages and disadvantages, which carry different weight depending on the project requirements and team structure.
The choice of the appropriate format depends on factors such as team size, technical infrastructure, and the desired degree of automation. While PDF checklists are easy to distribute, interactive and tool-based variants offer advantages for collaboration and documentation. For sustainable implementation, a format that can be flexibly integrated into existing workflows is recommended.
| Format | Pros and Cons |
|---|---|
| PDF Checklist | + Easy to create and distribute – No direct interaction or progress monitoring |
| Interactive Online Checklist | + Collaboration and progress tracking possible – Dependent on online access and platform |
| Tool-based Checklist | + Integration into development environment, automation – Training and technical requirements necessary |
7 days unrestricted access. No payment details required.
Integrating an accessible website checklist into the development process opens up numerous opportunities to systematically consider accessibility from the very beginning. In agile projects, the checklist can serve as a fixed component of every sprint planning and review phase, while in classic models it is specifically integrated into the design, development, and quality assurance phases. Close coordination between teams ensures that accessibility is not just checked at the end, but implemented continuously.
Early involvement benefits everyone involved: designers can take requirements into account directly, developers receive clear specifications, and quality assurance can perform targeted checks. Practical examples show that collaborative work on the checklist—for instance, through joint review sessions and the exchange of implementation tips—significantly increases efficiency and result quality.
An accessible website checklist is typically adapted to national legal requirements such as BFSG or BITV 2.0 and contains specific checkpoints for implementation in Germany. A WCAG checklist is based exclusively on international WCAG criteria and is often more general. For users, this means: the accessible website checklist offers practical guidance for meeting specific legal requirements, while the WCAG checklist serves as an internationally applicable technical standard.
An accessible website checklist is a central tool for implementing digital accessibility requirements in a structured and transparent manner. It is based on national and international standards such as BFSG, BITV 2.0, and WCAG 2.1 AA, providing practical support for the planning, implementation, and monitoring of accessible web projects.
Key aspects include the systematic structuring of checkpoints, integration into existing workflows, and the regular maintenance and adaptation of the checklist. Through the targeted use of tools, the combination of manual and automated testing, and cross-team collaboration, accessibility can be ensured efficiently and sustainably.
Check your homepage with the AccessGO quick check.
Identify risks and barriers according to WCAG standards.
An accessible website checklist is a central tool for preparing for a BFSG audit. It enables a structured review of all relevant requirements and facilitates the systematic documentation of implementation. In the context of an audit, the checklist serves to provide evidence of compliance with legal requirements and to systematically address typical checkpoints.
An accessible website checklist is a central tool for preparing for a BFSG audit. It enables a structured review of all relevant requirements and facilitates the systematic documentation of implementation. In the context of an audit, the checklist serves to provide evidence of compliance with legal requirements and to systematically address typical checkpoints.
An accessible website checklist should be reviewed and updated at least once a year. In the event of changes to the law, new standards, or technical developments, prompt adjustment is advisable. Ideally, responsibility for maintenance lies with a designated contact person or an interdisciplinary team within the company.
Compliance with an accessible website checklist during ongoing operations is achieved through the use of suitable tools and regular checks. Automated solutions such as axe, WAVE, or Lighthouse efficiently check technical criteria, while manual tests with screen readers or expert feedback remain indispensable. When selecting tools, you should focus on up-to-dateness, integration options, and the coverage of relevant checkpoints.
Tools such as axe, WAVE, Lighthouse, or Siteimprove are suitable for supporting the application of an accessible website checklist. These can be integrated into maintenance and update processes, enabling regular reviews. Additionally, monitoring solutions are helpful for continuously identifying improvements and ensuring long-term quality. A structured use of these tools promotes sustainable accessibility.
