Timetable for implementation of BFSG

Your path to digitalisation

Schedule for testing and optimising the accessibility of the website

At EGOTEC, we work with Scrum and sprints. A sprint is 2 weeks.

Phase 1: Preparation and planning (1 sprint)

Sprint 1:

    Analysing
  • the website:
      Creating
    • a page overview and identifying critical areas (start page, contact forms, documents).
      • Selecting
    • the test tools to be used (e.g. WAVE, screen reader, Lighthouse).
    • Defining
  • test criteria:
      Orientation
    • to WCAG 2.1 (Level A and AA) and BITV 2.0.

Phase 2: Carrying out the accessibility test (1 sprint)

Sprint 2:

  1. Automated

    testing (1 week):

      Use of
    • automated tools for an initial analysis of barriers (e.g. missing alternative texts, contrasts).
      • First
    • categorisation and prioritisation of the problems found.
  2. Manual

    testing (2 weeks):

      Visual
    • testing: analysis of contrasts, font sizes and visual structure.
    • Screen
      • reader test
    • : Testing the website with screen readers (e.g. NVDA or JAWS).
    • Keyboard
      • test
    • : Testing complete usability via keyboard.
    • Content
      • test
    • : Ensuring that texts, alternative texts and descriptions are meaningful and complete.
    3. %
$6

optional

  1. Review

    of PDF documents (1 week):

      Analyse
    • all documents provided for accessibility using tools such as Adobe Acrobat Pro or PAC 3.

Phase 3: Evaluation and reporting (1 sprint)

Sprint 3:

  • Creation of

    a test report:

      Summary
    • of the identified barriers (automated and manual tests).
      • Prioritisation of
    • the problems according to criticality (e.g. critical, moderate, low).

  • Develop

    solutions

    :

      Recommendations
    • and concrete measures to eliminate the barriers.
    %
$6

Phase 4: Removing the barriers (1-2 sprints)

Sprint 4-5:

    Implementation of
  1. technical adjustments (4 weeks):
      Revision
    • of the source code (e.g. ARIA roles, semantic HTML code, contrasts).
      • Adaptation
    • of PDF documents for accessibility.
    2. Content optimisation
  2. (2 weeks):
      Training
    • of editors to create accessible content (e.g. alternative texts, simple language).
      • Revision
    • of existing content.
    3. %
$6

Phase 5: Review and quality assurance (1-2 sprints)

Sprint 5-7:

    Review
  • the website:
      Repeat
    • automated and manual testing to ensure all issues have been resolved.
    • User
  • feedback:
      Testing
    • by a group of users with disabilities (screen reader users, people with motor disabilities).
  • Final
    • report
  • :
      Documentation of
    • all actions taken and remaining issues (if any).

Phase 6: Ensuring accessibility in the long term (ongoing)

    Regular
  • review (quarterly).
    • Implementation
  • of an accessibility feedback form on the website.
    • Training
  • for editors and developers (of the client) for long-term compliance with the standards.

Total duration

The accessibility check plus any adjustments for accessibility requires 5-7 sprints or 10-14 weeks from preparation and planning to implementation, reporting, remediation and quality check.