Skip to toolbar

Community & Business Groups

“EN 301 549 vs WCAG” – Study Group Meeting Notes

Meeting Notes – 2024-12-05

Participants

  • Tobias Christian Jensen
  • Erik Gustafsson Spagnoli
  • Simo Hellsten
  • Robin Whittleton
  • Umut Gültekin
  • Thomas Nielsen
  • Anna-Liisa Mattila
  • Stein Erik Skotkjerra
  • Christer Janzon

Summary
This session focused on improving collaboration through the Github repository, drafting test procedures, and managing updates to accessibility standards. Until the next meeting, members should contribute to the repository, review drafts, and highlight key issues. The next session will address unresolved topics, refine methods, and plan the next steps.


Key updates

  1. Github repository
  2. EN 301 549 updates
    • The EU Commission will not update the WAD implementing decision for version 4 of EN 301 549. WAD remains based on version 3.
    • EAA updates are expected, meaning organizations may need to work with both versions simultaneously.

Discussion highlights

  1. Disproportionate burden clause
    • This allows organizations to claim that fixing specific accessibility issues is too costly or difficult compared to the benefits.
    • Claims must be documented and justified, and monitoring agencies will closely review them.
  2. Testing procedures
    • Stein Erik is drafting test procedures for Denmark’s monitoring agency. These will cover all EN criteria and be shared for group feedback.
  3. Monitoring agencies
    • Sweden: DIGG and PTS are merging into one agency.
    • Finland: A similar merger is expected early next year.
    • Denmark has multiple agencies but primarily relies on two main ones.
  4. WCAG and EN standards
    • The group discussed working with WCAG 2.2 (to be included in EN version 4) and preparing for WCAG 3.0.
    • WCAG 2.2 adds clarifications, while WCAG 3.0 will require more significant updates to testing.

Action items until next time

  1. Contribute to the repository
    • Review Stein Erik’s draft test procedures when published and give feedback.
    • Participate in discussions or raise new issues in the repository.
  2. Focus on key topics
    • Identify unresolved or complex issues in the repository for group discussion.
    • Propose areas to prioritize, such as testing challenges or country-specific approaches.

Goals for the next session

  1. Resolve key issues
    • Address unresolved questions or challenges raised in the repository.
  2. Review repository progress
    • Evaluate how the repository is being used and adjust how we think it makes most sense (e.g., should we create Github Issues or Pull Requests).
  3. Refine testing procedures
    • Discuss and improve Stein Erik’s draft procedures to ensure consistency across countries.

Leave a Reply

Your email address will not be published. Required fields are marked *

Before you comment here, note that this forum is moderated and your IP address is sent to Akismet, the plugin we use to mitigate spam comments.

*