D503.5 Tagging Decision Meeting 2017-09-20

From wiki.gpii
Jump to: navigation, search

Note: This meeting is focused on discussing the progress on D503.5, and planning of the GPII standardization workshop in Brussels.

Connection Info

  • Wed Sep 20 at 3-4pm CEST Translate to local date & time
  • Connect by browser: Gotomeeting room 3
  • Connect by phone: Meeting ID and access code: 161-482-213
    • Belgium: +32 (0) 92 98 0592
    • France: +33 (0) 182 880 456
    • Germany: +49 (0) 811 8899 6975
    • Netherlands: +31 (0) 208 080 379
    • Spain: +34 911 82 9782
    • Switzerland: +41 (0) 225 3314 51
    • United Kingdom: +44 (0) 203 535 0621
    • United States: +1 (786) 358-5410


Present: Gottfried, Till, Matthias, Ignacio, Gregg

Regrets: -

Status: D503.5 Implementation Resources for ETSI EN 301 549

Original title (DoW): "Application Guidelines, policy and standards recommendations"


Levels of support between DSpace components and ETSI EN 301 549 provisions:

  1. Background information
  2. Guidance on how to fulfill a provision
  3. Tool/library/code to partially fulfill a provision (WCAG 2.0 language: "advisory technique")
  4. Tool/library/code to fully fulfill a provision (WCAG 2.0 language: "sufficient technique")

In addition, we mark those items where we do not provide a mapping, by "no mapping" ("L0") + a free text for explanation. An explanatory text can be added, explaining the relationship, and other things (optionally).

Process for contributing to the DSpace:

  • Experts search for appropriate DSpace items, going through the ETSI provisions.
  • New entries: Developers can post their components as candidates for the DSpace, and describe it in a web form. Experts review the queue of candidates (curation), and do some additional tagging. Developers are notified about the curation.

We expect a maximum number of 600 for DSpace items (queue to be curated).

Deliverable will be a report on the exercise of the mapping table, including lessons learned:

  • Look at people that apply the standard.
  • Maximum ability to find things for developers: wisdom, practice, tools.
  • Needs to be maintainable.

Big Question: How to tag the DSpace?

Issues to be considered:

  • How to implement the mapping? As separate document, or as tagging in the DSpace?
  • How deep should the mapping be? 2 or more digits into the structure.
  • Should we quote the ETSI provision for better understanding?

Two options:

  1. Use textual tags on DSpace items, indicating the support level and the ETSI standard provision. Example: "ETSI301549-9.2-L3" = Partial fulfill (L3) for provision 9.2.
    • Pro: Users can search for components by provision in the DSpace itself, everything linked together.
    • Con: New DSpace items need to be tagged.
    • Example page for RoboBrailleWebAPI. Needed:
      • The Success Criterion and Level need additional nonnumeric info.
      • The discussion & explanation part should become some kind of tooltip for the level and the criterion respectively to unclutter the view.
  2. Separate document (table) listing the mappings, sorted by ETSI standard provision.
    • Pro: Less effort in setting up and maintenance.
    • Con: More cumbersome to look up mappings in a separate place. New DSpace components will likely not be mapped (since developers won't care about a separate mapping table).

How do developers get to the DSpace item pages?

  • Search for provision in the DSpace
  • Link from the Procurement tool?

It would be useful to have a webpage with the ETSI provisions listed to point to.

DECISION: Add tags to DSpace according to option 1.


  • 2017-09-06: Freezing of mapping table
  • 2017-09-07: Gottfried to produce a provision-sorted table from the mapping table.
  • 2017-09-13 (AAATE): Public DSpace launched
  • 2017-09-20: Web conference on DSpace tagging (decision: go for tags)
  • 2017-10-12: Add tags to DSpace
  • 2017-10-13: Standardization workshop in Brussels - get feedback from commission and policy makers
  • 2017-11-15: Document D503.5 ready for P4a-internal review
  • 2017-11-30: Feedback from P4a-internal review
  • 2017-12-15: Deliverable D503.5 ready for submission to European Commission

Appendix: Background: D503.5 Application Guidelines, policy and standards recommendations

Task: T503.3 Standardization and concertation activities

Delivery date: Jan. 2018 (month 48)

Description: In the DoW, what comes closest to a description for this deliverable is as follows:

  • "This task will also propose a set of guidelines valid for the applications considered in the project and applicable also to new applications and mainstream ICT devices. These guidelines will provide best practices associated with the role and responsibilities of all stakeholders in the design, development and deployment of accessibility solutions."

At the all-hands meeting 2017 in Stuttgart, we decided to work on an annotation tool for ETSI 301 549 as an implementation guidance for developers and project managers. It should tell them how to make it easy to comply with ETSI 301 549. This is of particular interest to us since ETSI 301 549 is the technical basis for the European Directive on Accessibility of the websites and mobile applications of public sector bodies of Oct. 2016. We believe that this directive will be a major driver for accessibility of Websites and mobile apps in Europe in the coming years. And for us, it seems to be a good opportunity to describe how the P4a tools and tutorials can be used to fulfill specific provisions of ETSI 301 549.

Note: ETSI EN 301 549 is planned to be revised in the coming 15 months to better address the new scope of the directive, i.e. including mobile apps.