Concept for implementation of the BFSG

(BFSG)

Concept for testing accessibility

Objective:

To ensure that your website fulfils the requirements of the Accessibility Improvement Act (BFSG) and the international accessibility guidelines (WCAG 2.1).

Steps for checking accessibility:

1. preparation

  • Inventory:

    • Create a list of all pages and functions of the website (e.g. homepage, contact form, content such as PDF documents, search functions).
    • Analyse the technologies and page types used.

  • Define test criteria:

    • Use WCAG 2.1 guidelines with a focus on conformance levels A and AA.
    • Check for compatibility with national requirements (BITV 2.0).

  • Select testing tools:

    • Automated tools: e.g. WAVE, Axe, Lighthouse.
    • Manual checks: Screen reader (e.g. NVDA or JAWS), keyboard navigation.

2. automated testing

  • Implementation:
    • Apply automated tools to the website to identify initial issues such as missing alternative text, poor contrast, incorrect ARIA roles.
  • Analyse report:
    • Create list of automated issues found.
    • Categorise errors (critical, moderate, minor).

3. manual check

  • Visual inspection:

    • Check the design for sufficient contrast (at least 4.5:1 for text and background).

    • Check legibility of fonts and sizes.

  • Screen reader test:

    • Check website navigation with a screen reader.
    • Ensure that content is read out logically and comprehensibly.

  • Keyboard test:

    • Checking that all interactive elements (e.g. forms, buttons, menus) are fully operable using the keyboard.

  • Content check:

    • Checking whether alternative texts for images are available and make sense.
    • Ensure that multimedia content (e.g. videos) has subtitles or transcriptions.
  • Create report:
    • Create list of issues found.
    • Categorise errors (critical, moderate, minor).

4. checking the documents

  • Check the PDF documentsprovided on the website:
    • Ensure that the PDFs are accessible.
  • Create report:
    • Create list of issues found.
    • Categorise errors (critical, moderate, minor).

5. user feedback

  • Set up an accessibility reporting centre:
    • Contact form or e-mail address on the website so that users can report barriers.
  • Involve a test group:
    • Have people with different disabilities test the website.
    • Obtain feedback on user-friendliness.
  • Create a report:
    • Create list of issues found.
    • Categorise errors (critical, moderate, minor).

6. document the results

  • Summarise reports:
    • Identified barriers and their impact.
    • Suggestions for remediation with prioritisation according to urgency.
  • Document test protocol:
    • Document all tests and tools performed.

Implementing the findings

  • Developing solutions:
    • Work with developers and designers to remove barriers.
    • Ensure that the code is semantically correct and that ARIA roles are used appropriately.
  • Retesting:
    • Re-run all tests once issues have been resolved.

Ensuring accessibility in the long term

  • Regular checks:

    • Check the website for accessibility on a quarterly basis.

  • Training courses:

    • Training of editors in handling accessible content.

  • Monitoring and feedback:

    • Set up a monitoring system to continuously check changes and new content for accessibility.