Standardization Roadmap

From wiki.gpii
Jump to: navigation, search

Note: Passages in italic font are in draft mode, and currently under revision.

Preface

This Wiki page provides an overview on GPII's activities related to standardization. International standards are an important foundation for technological progress, interoperability and accessibility. Both projects, Cloud4all and Prosperity4all, have specific work packages on standardization and concertation actions. In order to make the GPII technology available to everyone, we need to pollinate existing and emerging international standards with the seeds of personalized user interfaces based on personal preference sets.

For an overview on relevant existing standards, refer to Standards related to Personalization.

A compilation of standards and APIs (that might be worth standardizing) used by components in the GPII Developer Space is maintained here: Developer Space/Standards (only partially personalization or accessibility specific).

Top-Level Goals

In general, our top-level goals are:

  1. Reuse existing standards and technologies (in particular by mainstream), wherever possible.
  2. Develop and validate new standards on GPII technologies, wherever necessary.
  3. Work towards harmonization, adoption and inclusion of the GPII standards in standardization, industry, research and governments.

Every activity for standardization should aim for one of these top-level goals, at least.

International standardization

International standardization work is divided into government-driven standards organizations (e.g. ISO, IEC, CEN, CENELEC) and industry-driven standards organizations (also called "consortia", e.g. W3C, UPnP, ETSI). Both are relevant for GPII and its mission.

Standardization committee (link) Description of committee Mode of working Purpose/goals for GPII Partners & roles Project
ISO/IEC JTC1 SC35 User Interfaces

SC35 is the official government-driven committee for standardization of user interface related topics in ICT environments. This includes accessibility related standards in this area. 

Most relevant groups for GPII:

  • WG6: User interface accessibility (convened by Dr. Jim Carter) - includes work on the former SWG-A User Needs Summary (ISO/IEC 29138-1) to incorporate newly-identified user needs and devise an appropriate structure for categorisation of needs as appears to be required to accommodate the new user needs.
  • WG8: User Interfaces for remote interactions (convened by Dr. Gottfried Zimmermann)
  • Mailing lists.
  • Document repository.
  • Electronic voting & commenting process through national bodies.
  • 2 plenary meetings per year, with working group meetings (full week)
  • Irregular (approximately fortnightly) conference calls
  • Develop and extend ISO/IEC 24752, Universal Remote Console (URC), to meet personalization requirements for IoT environment - WG8
  • Impact the development of accessibility related standards - WG6
  • Vote on accessibility related standards - SC35
  • Make sure a revised User Needs Summary standard will be compatible with GPII. Potential mappings from User Needs to GPII preferences (not one to one) should satisfy personal needs in particular ICT contexts.
  • Gottfried Zimmermann, HDM, is a German delegate on SC35, convener of WG8, editor of ISO/IEC 24752, and liaison to SC36)
  • Andy Heath, collaborator of GPII, is a British delegate on SC35. He is actively participating in the User Needs editors team.
 Prosperity4all
ISO/IEC JTC1 SC36 Information technology for learning, education and training
ISO/IEC JTC 1/SC 36 develops international standards for information technologies (IT) used in Learning, Education and Training (LET). A key goal of SC36 standards is to provide for interoperability among different and distributed IT systems, tools and services used in LET contexts.
  • Mailing lists.
  • Document repository.
  • Electronic voting & commenting process through national bodies.
  • 2 plenary meetings per year, with working group meetings (full week)
  • Develop ISO/IEC 24751-1, AccessForAll Framework for Individualized Accessibility. Part 1: Framework and Registry. For GPII, we need to be able to register concepts for personal preferences, context descriptions and resource descriptions.
  • Develop ISO/IEC 24751-4: AccessForAll Framework For Individualized Accessibility - Part 4: Registry server API. We need to be able to exchange concepts between registries, and among development tools and registries.
  • IDRC (Jutta Treviranus is editor)
  • Andy Heath (editor)
  • Gottfried Zimmermann, HDM (German delegate and liaise for SC35)
openURC Alliance

openURC’s mission is to promote the Universal Remote Console (URC) and associated standards and its application. 

While ISO/IEC 24752 is the conceptual basis for URC, openURC's Technical Committee (TC) develops implementation guidance for specific URC technologies in the form of Technical Reports (e.g. the Universal Control Hub).

  • Mailing lists.
  • Repository of standards and drafts.
  • Technical Committee has monthly telecons.
  • Board of Directors has telecons on demand.
  • Executive Committee has telecons on demand.
  • One plenary meeting per year.
  • Further extend and mature the URC concepts to meet the technical needs of personalized user interfaces.
  • Work with existing mainstream IoT platform communities (e.g. Eclipse Smarthome) and build the URC concepts on personalization into these platforms.
  • Make sure URC concepts are compatible with other GPII technologies.
  • HDM: Zimmermann is vice-president of openURC, chair of the Technical Committee, and editor of several Technical Reports. Smirek is a member of the Technical Committee.
 Prosperity4all
W3C Accessible Platform Architecture (APA) Working Group

(former PF WG)

The APA working group looks at Web technologies (protocols, formats, etc.) from an accessibility perspective. The principal output of this working group is feedback to other W3C working groups developing specification, on how to ensure that their work can allow for accessibility.

Other topics include:

  • Extensible media queries as a vehicle for conveying user preferences to Web applications via browser extensions (in discussion with CSS WG)
  • Mailing lists.
  • Weekly telecons.
  • 2 face-to-face meetings per year.
  • Identify current trends in Web technologies (e.g. Web components), and their potentials/risks for GPII.
  • Impact the development of W3C standards to be GPII compatible.
  • Promote GPII concepts within the W3C community.
  • HDM (Zimmermann is invited expert)
 Prosperity4all
W3C Accessibility Guidelines (AG) WG (former WCAG WG) The mission of the Accessibility Guidelines Working Group is to develop guidelines to make Web content accessible for people with disabilities and to develop and maintain implementation support materials for the Web Content Accessibility Guidelines.
  • Mailing lists.
  • Weekly telecons.
  • 2 face-to-face meetings per year.
  • Support W3C in developing useful guidelines.
  • Provide implementation guidance for WCAG using GPII technologies
  • Shadi Abou-Zahra is member
  • Gregg Vanderheiden is member
  • Christophe Strobbe is member
W3C ARIA WG The mission of the Accessible Rich Internet Applications Working Group (ARIA WG) is to develop technologies that enhance accessibility of web content for people with disabilities. This includes continued development of the Accessible Rich Internet Applications (WAI-ARIA) suite of technologies and other technical specifications when needed to bridge known gaps.
  • Mailing lists.
  • Weekly telecons.
  • 2 face-to-face meetings per year.
W3C Independent User Interface (IndieUI) WG

(closed April 2015)

This group is working on two linked specifications, which, when used together, can support adaptation to User Context (accessibility preferences) on mobile devices. The two specifications are: Events 1.0 and User Context 1.0. The Events specification provides an intermediate layer between device- and modality-specific user interaction events, and the basic user interface functionality used by web applications. The User Context specification provides a set of individual preferences designed to work with the Events model supporting the adaptation of interface AND content to the preferences taking account of the device capabilities. Use cases include searching for appropriate content and configuring the device, particularly via providing an abstract way that web technologies can determine what has been requested.
  • Mailing lists.
  • Repository of standards and drafts.
  • Fortnighly telecons and accompanying IRC.
  • 1 face-to-face meeting per year.
  • Make sure that both specifications can work on a GPII-enabled platform.
  • Maximize compatibility between a user's settings, as defined by the User Context specification, and user preference terms, as defined by GPII (via the ISO/IEC 24751 registry).
  • The Events specification is at W3C Working Draft 1.0 and the User Context specification is between First Public Working Draft and W3C Working Draft.
  • Andy Heath report and liaise
The IEEE Actionable Data Book

This IEEE project is doing prototypical exploration of implementation aspects of the use of eBooks in connected environments using xAPI as a central store for fine granularity learner and other events (such as completion of exercises, assessments etc.) in using learning systems whose central delivery mechanism is the eBook. The R&D project is working with EPUB3 in co-ordination with IDPF and others. Alongside storage and retrieval of learner events the project aims to store, retrieve and adapt content/interface to accessibility preferences in the xAPI database. It offers the possibility to explore discovery of preferences analytically alongside learning analytics. It is expected to lead into standards work in IEEE when more advanced.

  • Mailing lists
  • Repository of drafts.
  • Weekly or twice-weekly telecons
  • Participations in other groups and conferences
  • Vendor and organisation implementation support work

Explore implementation implications of preferences in the cloud and in ebooks

  • Andy Heath report and liaise (until 2016)
IMS Accessibility Working Group The IMS Accessibility project Working Group focuses on adaptation or personalization of resources, interfaces and content to meet the needs of individuals. The group believes that the best way to make a system or resource accessible to an individual is by meeting that individual's particular needs at that time in that context. This working group creates IMS specifications and strives to stay harmonized with other groups working on accessibility metadata and preferences.

Major revision to personal needs and preferences spec, released in fall 2016.

  • Mailing lists.
  • Repository of standards and drafts.
  • Weekly telecons.
  • Occasional face-to-face meetings.
  • Creates properties and vocabulary for accessibility metadata and preferences. IMS Global Access for All (AfA)
  • Seeks to harmonize with other standards bodies
  • Madeleine Rothberg
Schema.org Accessibility metadata for Schema.org was developed by the Accessibility Metadata Project, led by Benetech. A version one metadata model was adopted by Schema.org and is documented on the WebSchemas/Accessibility page.

Three new accessibility feature terms in schema.org 3.2: access mode, access mode sufficient, accessibility summary.

  • Mailing list
  • Occasional telecons
  • Schema.org Github
  • Creates properties and vocabulary for accessibility metadata
  • May lead to implementation in mainstream search engines
  • Madeleine Rothberg, IDRC, Benetech, Gates Foundation
W3C Cognitive and Learning Disabilities Accessibility Task Force

The objective of the Cognitive and Learning Disabilities Accessibility Task Force is to improve Web accessibility for people with cognitive and learning disabilities. This will begin with research and gap analysis. Then the group will develop draft proposed guidance and techniques to make web content, content authoring, and user agent implementation accessible and more useable by people with cognitive and learning disabilities. It will also review existing techniques and consider ways to improve them, and build new techniques where necessary. The Cog a11y TF is a joint Task Force of the Protocols and Formats Working Group (PFWG) and the Web Content Accessibility Guidelines Working Group (WCAG WG). It assists these Working Groups to produce techniques, understanding, and guidance documents, as well as updates to existing related W3C material that addresses the cognitive space.

The first publication is Cognitive Accessibility User Research.

  • Mailing list
  • Wiki and GitHub;
  • Issue Tracker;
  • Polls
  • IRC - #coga IRC channel
  • Weekly teleconferences;
  • Regular updates to the PFWG and WCAG WG;
  • Regular deliverables to the WCAG WG and UAWG for approval;
  • Influencing main W3C accessibility activities
  • Inform T203.4 framework for guidelines and starting frameworks for low cognitive and stepping stone applications for low digital literacy.
  • Ditto T301.2: Improving access to technology for dementia sufferers/carer.
  • Steve Lee (OpenDirective)
  • Andy Heath (member)
 Prosperity4All
IDPF

EPUB 3.1 with advances in metadata markup. Proposals to schema.org for new metadata properties to better describe accessible eBooks.

  • Mailing list
  • Weekly teleconferences
  • Wiki and GitHub
  • Create properties and vocabulary for accessibility metadata
  • May lead to implementation in mainstream search engines

Madeleine Rothberg

ISO/IEC JTC1 WG10 Internet of Things (IoT)

(former SWG5)

Some work was done in an earlier group - SWG 5. The extent to which WG10 will just inherit and continue the work in SWG 5 is not completely clear.

SWG 5 produced:

  • a lightweight architectural view in a mindmap of what is and isn't incuded in IoT and how the elements relate. Note that this included addressing of accessibility by a needs and preferences approach
  • An approach to marketing their work, largely based on surveying to market sectors and lists of stakeholder requirements for each sector
  • A template for entry of standards to a listing of relevant standards with the intention of supporting a gap analysis. This was populated by liasing groups to include 418 standards.
  • An initial list of use cases that included at least one accessibility use case (written by Andy Heath)

SWG 10 has taken over this work and is continuing it to include:

  • Developing Terms and Definitions for JTC 1 IoT Vocabulary
  • Developing IoT Reference Architecture and other foundational specifications as JTC 1 standards
  • Continuing the work begun in SWG on IoT on standardization gaps
  • Establishing a liaison with JTC 1, ISO, IEC or other committees or working groups undertaking work related to IoT
  • Encouraging the prompt and efficient exchange of information within JTC 1 and with ISO, IEC, or other committees or working groups working on IoT, as appropriate
  • Monitoring the ongoing IoT regulatory, market, business and technology requirements
  • Developing other IoT standards that build on the foundational standards when relevant JTC 1 subgroups that could address these standards do not exist or are unable to develop them
  • Twice yearly face to face meetings
  • conference calls
  • ad-hocs
  • Support the work on an IoT architecture to include use cases on accessibility. It is planned that the architectural model support a number of views, one of which could take the perspective if User Interfacing. Computational complexity alone (many other factors do also) requires that such is supported by a User Needs/Preferences approach to accessibility of interface since IoT may be expected to be used in/with a huge variety of environments/devices etc.
  • SC35 has set up an ad-hoc to advise WG10 at the interface level.

Andy Heath (liaison for SC35)

IEC SyC AAL

The IEC System Committee on Active Assisted Living shall:

  • Create a vision of Active Assisted Living that takes account of the evolution of the market
  • Foster standardisation which enables usability and accessibility of AAL systems and services; enables cross-vendor interoperability of AAL systems, services, products and components; addresses systems level aspects such as safety, security and privacy; communicates the work of the SyC appropriately to foster a strong community of stakeholders.
  • Bi-yearly plenary meetings with liaison reports
  • Document distribution system
  • Raise awareness on the need for a personal user experience
  • Inform the committee on GPII's personal preferences approach and existing implementations
  • Inform the committee on URC's pluggable user interfaces approach and existing implementations

Gottfried Zimmermann (liaison for ISO/IEC JTC1 SC35)

Prosperity4all

National standardization

National standardization activities can help to spread interoperable technologies within a country, and often support national legislation. It is also common for national standardization committees to support international standardization by national bodies (delegations).

Standardization committee (link) Description of committee Mode of working Purpose/goals for GPII Partners & Roles Project
DIN NA 023-00-02 GA Accessibility

German national standardization committee on accessibility.

German mirror committee for the following international committees:

  • CEN/CLC/JWG 5 Design for All
  • CEN/CLC/ETSI/JWG European Joint WG on eAccessibility under mandate M/376
  • CEN/BT/WG 213 Strategic Advisory Group on Accessibility (SAGA)
  • ISO/TC 159/WG 2 Ergonomics for people with special requirements
  • Mailing list.
  • Document repository.
  • Electronic voting and commenting process.
  • 2 face-to-face meetings per year.
  • Additional telecons on demand.
  • Impact the development of accessibility related standards (national and by international committees that are mirrored) to be compatible to GPII
  • Raise awareness on GPII technologies
 HDM (Zimmermann is member) Prosperity4all
DIN NA 023-00-04 GA Ergonomics for information processing systems

German national standardization committee on ergonomics.

German mirror committee for the following international committees:

  • Ergonomics of human-system interaction
  • ISO/IEC JTC1 SC35 User Interfaces
  • Mailing list.
  • Document repository.
  • Electronic voting and commenting process.
  • 2 face-to-face meetings per year.
  • Additional telecons on demand.
  • Participate in German delegation in JTC1 SC35
  • Impact the development of international accessibility related standards to be compatible to GPII
  • Raise awareness on GPII technologies
 HDM (Zimmermann is member) Prosperity4all
DIN NA 023-00-04-09 AK Ergonomic aspects of AAL and assistive systems German national standardization committee on accessibility issues in the area of AAL. 
  • Mailing list.
  • Document repository.
  • Electronic voting and commenting process.
  • 2 face-to-face meetings per year.
  • Additional telecons on demand.
  • Impact the development of national accessibility related standards in AAL to be compatible to GPII
  • Raise awareness on GPII technologies
 HDM (Henka is member) Prosperity4all
DIN NA 043-01-36 AA Learning Technologies German national standardization committee on eLearning.

German mirror committee for the following international committee:

  • ISO/IEC JTC1 SC36 User Interfaces
  • Mailing list
  • Document repository.
  • Electronic voting and commenting process.
  • Participate in German delegation in JTC1 SC36
  • Raise awareness on GPII technologies
 HDM (Zimmermann is member) Prosperity4all

Cooperation and concertation activities

Less formal cooperation and concertation activities in networks of projects and stakeholders can also pave the way for standardization or quasi-standardization. These activities should also be reported here.

Committee/network (link)
 Description of committee/network Mode of working Purpose/goals for GPII Partners and roles Project
Covenant on Demographic Change

(former AFE-INNOVNET)

The Covenant on Demographic Change has emerged from the former AFE-INNOVNET platform. It aims to gather all local, regional and national authorities, and other stakeholders, that commit to cooperate and implement evidence-based solutions to support active and healthy ageing as a comprehensive answer to Europe’s demographic challenge.

  • Listen in to actual trends and developments in AAL
  • Use opportunities for cooperation and spreading GPII technologies
  • AGE Platform Europe has initiated the Covenant
 Prosperity4all
European Innovation Partnership on Active and Healthy Ageing (EIP-AHA)

Communication and information platform for all actors involved in Active and Healthy Ageing throughout Europe; the place to promote news and events, to meet and exchange ideas with peers and potential partners on innovative projects in this challenging field.

EIP-AHA has a number of action groups in which work is conducted, mainly within task forces for "sprints". The most relevant action groups for GPII are:

  • C2 on the development of interoperable independent living solutions, including guidelines for business models.
  • C2 includes a task force on Personal User Experience (C2.3) with over 30 partners, initiated by Gottfried Zimmermann (HDM). In C2.3, showcases of personal user interfaces are being developed.
  • D4 on innovation for age friendly buildings, cities and environments
  • Electronic communication & repository platform (Yammer).
  • Face-to-face meetings/conferences on European level (2-4 per year).
  • Regular (about monthly) telecons in task forces.
  • Listen in to actual trends and developments in AAL
  • Raise awareness for the need of personalized user interfaces, and how the GPII technology and standards can support these
  • Impact upcoming AAL-related calls for proposals by the European Commission to be GPII and accessibility friendly
  • Use opportunities for future projects and for the application of GPII technologies
  • HDM (Zimmermann is member of C2, and leader of the task force on Personal User Experience)
  • AGE Platform Europe is member of D4
 Prosperity4all
MOOC Accessibility Partnership (MOOCAP)
 This ERASMUS+ Strategic Partnership develops a set of MOOC and online courses on accessible design in ICT. The partnership consists of 8 European universities with excellence in accessibility research and teaching.

New introductory MOOC on Digital Accessibility (5 units) started on Oct. 17, 2016. 

The project is divided up in work packages, with monthly telecons for project-internal communication. Develop an online course on GPII concepts and technologies so that professionals learn about the GPII framework and its opportunities.
  • Course Digital Accessibility on FutureLearn
  • Further 9 courses on specialized topics of accessibility, including "User interface personalization"
  • Gottfried (HDM) is coordinator of MOOCAP
 MOOCAP
Adaptiva, All-nativa and inclusive learning projects
 Consortia working in learning space to implement AccessForAll. Both Spanish and Portuguese resources. Includes teacher training in creating AccessForAll compliant resources.
 Mailing list and Wiki
 Implementation exemplar of matching personal optimization using Access4All
  • University of Girona, IDRC, SmartLab Dublin and others
Preferences for Global Access
 The goal of this project is the design and development of web software to assist users with disabilities in creating online user profiles that specify their needs and preferences for how online information and services should be presented to them. This team develops tools and technologies to support users in specifying their individual needs and preferences in several application settings.
This project fills the gap in the GPII framework on how users can create and maintain their individual sets of personal preferences.
  • ISKME
  • RtF-I
  • IDRC
  • Madeleine Rothberg (subject matter expert)
AFE-INNOVNET - Towards an Age-Friendly Europe (cooperation ended by end of 2015 due to transformation into the Covenant on Demographic Change)

AFE-INNOVNET was a European project/platform aiming at mobilising a EU-wide community of local and regional authorities and other stakeholders to support the scaling-up of innovative solutions for age-friendly environments to support active and healthy ageing across Europe.

  • Mailing list for dissemination
  • Occasional webinars for special topics
  • Listen in to actual trends and developments in AAL
  • Use opportunities for cooperation and spreading GPII technologies
  • AGE Platform Europe coordinated the project
  • HDM was a member of the network
 Prosperity4all
ReAAL (project finished) European-funded project for pilot-testing the AAL technology developed by universAAL. The project works mostly internally as consortium. From time to time it hosts meetings for exchange of knowledge and interoperability planning.
  • Work towards harmonization of the universAAL and GPII technologies.
  • HDM (Zimmermann attends project workshops occasionally)
 Prosperity4all

Collaboration on governmental regulatory agencies

 In this section, report about collaboration activities with organizations/groups dealing with governmental regulatory agencies regarding consistent policies for the promotion of embedded accessibility solutions into mainstream ICT devices/applications and for new ways of financing such solutions.

Committee/network (link)
 Description of committee/network Mode of working Purpose/goals for GPII Partners and roles Project
ANEC Working Group on Design for All

The ANEC Design for All Working Group unites experts from both the consumer movement and the disability/elderly organisations. Its work is based on the ANEC Policy Statement on Design for All. In addition, ANEC initiated or participated in various activities in the European and international standards bodies on this issue. These include most notably the EC Mandate 473, Standardization Mandate to include Design for All in relevant standardization activities.

  • Mailing list;
  • Face-to-fave meeting (once per year).
  • Listen in to actual developments in various activities in the European and international standards bodies on the topic of Design for All
  • Use opportunities for future projects and spreading GPII technologies
  • Provide input to ANEC activities in the European and international standards bodies on this issue
  • AGE Platform Europe (Alice Sinigaglia is a member of the Working Group)
 Prosperity4all
European Multistakeholder Platform on ICT Standardisation

Based on a European Commission Decision to advise on matters related to the implementation of ICT standardisation policies, it deals with:

  • potential future ICT standardisation needs in support of European legislation, policies and public procurement;
  • technical specifications for public procurements, developed by global ICT standards-developing organisations;
  • cooperation between ICT standards-setting organisations;

The MSP is composed of representatives of national authorities from EU Member States & EFTA countries, by the European and international ICT standardisation bodies, and by stakeholder organisations that represent industry, small and medium-sized enterprises and consumers. It is co-chaired by the European Commission Directorates General Enterprise and Industry, and CONNECT. It meets four times per year.

  • Mailing list;
  • Face-to-fave meeting (4 times per year);
  • Skype calls
  • Listen in to actual trends and developments in the field of ICT standardisation and relevant EU policies and projects
  • Impact the update of the Rolling Plan on ICT standardisation. The document lists all the topics identified as EU policy priorities where standardisation, standards, or ICT technical specifications ought to play a key role in the implementation of the policy. It covers technologies of 'horizontal importance', ones whose application have a wide impact across different technical fields, in the context of ICT infrastructures and ICT standardisation.
  • Use the opportunity of the meetings to present the project (to be checked)
  • AGE Platform Europe (Alice Sinigaglia is a member of the platform)
 Prosperity4all
ERPB Working Group on Mobile and Card Based Contactless Proximity Payments

The Working Group on Mobile and Card Based Contactless Proximity Payments received its mandate from the Euro Retail Payments Board (ERPB) in December 2014. The focus of ERPB WG is on innovative payment solutions which rely on contactless technologies to initiate payments or transfer payment related data in proximity payment situations. The aim is to develop a report to the ERPB which contains a concrete action plan to achieve the essential conditions in the cooperative space for the realisation of a vision for mobile and card based contactless proximity payments by November 2015.

  • Mailing list;
  • Face-to-fave meeting (7 in total)
  • Listen in to actual developments in the field of contactless payments
  • Provide input to the activities of the group
  • AGE Platform Europe (Alice Sinigaglia is a member of the Working Group)
 Prosperity4all
Disability rights promotion international
 DRPI offers training in Disability Rights monitoring and is utilizing AccessForAll in the training and information site
 Web site, training portal, global network
 Implementation exemplar of matching personal optimization using Access4All
 IDRC
Access for all Ontario
 The Province of Ontario is implementing AccessForAll in the training portal and workstation setup for 65,000 employees.
 Intranet, training portal
 Large scale implementation exemplar of matching personal optimization using Access4All
 Province of Ontario, IDRC
 Prosperity4all

Outcomes

Main outcomes of all standardization activities are the development and release of public and open standards and guidelines which may later get adopted by legislation.

Note: Items are in chronological order, with the most recent items at the bottom.

Date / Timespan Description of outcome (w/ milestones) Relevance for GPII Contributing committees/networks Contributing partners
2014-01 First release of Schema.org accessibility

The schema.org AccessibilityFeature introduced 4 new accessibility-related properties (accessibilityAPI, accessibilityControl, accessibilityFeature, accessibilityHazard) for the description of object of type CreativeWork. These properties support search engines in finding resources (such as accessible media, alternatives and supported enhancements for accessibility) that match the accessibility requirements of a search engine user. If the user has an existing GPII-compatible preference set, the accessibility requirements could be automatically conveyed to the search engine.

schema.org
  • Madeleine Rothberg, NCAM-WGBH
2014-12

Revision of ISO/IEC 24752 (2nd edition), Universal Remote Console (URC):

  • Part 1: Framework (2nd edition)
  • Part 2: User interface socket description (2nd edition)
  • Part 4: Target description (2nd edition)
  • Part 5: Resource description (2nd edition)

The ISO/IEC 24752 standards specify the basic concepts and document formats for the Universal Remote Console ecosystem. In its second edition, the URC technology has been revised based on lessons learned to be simpler to implement and based on current technologies. 

The URC technology is part of the GPII concepts. Through its separation of frontend and backend, it allows for pluggable user interfaces that may be provided by the manufacturer of a device or by third parties. In the AAL context, URC is a basic technological concept for auto-personalization by preferences.

  • ISO/IEC JTC1 SC35
  • DIN NA 023-00-04 GA (German mirror to SC35)
  • HDM (Zimmermann is editor of 24752)
2014-12

ISO/IEC 24752-6 Web service integration

This new part 6 of ISO/IEC 24752 defines a way for devices/services to expose themselves as SOAP-based Web services in a URC-compliant way.

The URC technology is part of the GPII concepts. Through its separation of frontend and backend, it allows for pluggable user interfaces that may be provided by the manufacturer of a device or by third parties. In the AAL context, URC is a basic technological concept for auto-personalization by preferences.

  • ISO/IEC JTC1 SC35
  • DIN NA 023-00-04 GA (German mirror to SC35)
  • openURC
  • HDM (Zimmermann as editor of 24752-6)
2015-10 European Mandate 473

A suitable draft should be available by the beginning of October. It will be submitted to the National Committees for CEN-CENELEC public enquiry, a procedure, which lasts 5 months. During this national consultation period, National Committees will liaise with their stakeholders (industry, federations, consumer associations, certification bodies, etc.) to constitute a national viewpoint on the draft. These national viewpoints or comments are forwarded to the technical body working on the draft for further consideration and possible incorporation in the draft. The resulting improved draft can then be submitted to a voting procedure.

  • ANEC Working Group on Design for All
  • AGE Platform Europe
2015-12 Recommendations on how to overcome barriers

AGE provided its inputs to a survey that the group elaborated to understand the barriers and issues to consider in order to develop pan-European solutions in the field. AGE also contributed to the group's vision, in consultation with the members and BEUC. In autumn, the group will work on recommendations on how to overcome the barriers. The report will be ready by the end of the year.

  • ERPB Working Group on Contactless and Mobile Payments
  • AGE Platform Europe
2016-01 Updated Rolling Plan on ICT Standardisation

The European Multistakeholder Platform will update during the summer the Rolling Plan on ICT Standardisation that will be published by January 2016. The Rolling Plan is a lively document and comments on the text can always be sent to Rodolphe Wouters, rodolphe.wouters@ec.europa.eu, preferably by October (before the Rolling Plan is updated and published in January 2016). The Multistakeholder Platform is also defining the domains and priority areas for standardisation (KPS) critical to the Digital Single Market. The advice will be ready by December 2015.

  • European Multistakeholder Platform on ICT Standardisation
  • AGE Platform Europe
2016-02 Renovated action plan of EIP-AHA C2

This new action plan covers the plans for the action group C2 for 2016-2018. In particular, sprints are defined for the task force on Personal User Experience (led by Gottfried Zimmermann) which is closely related to the GPII work.

  • EIP-AHA
  • HDM (Gottfried Zimmermann) is coordinator of C2
  • AGE Platform Europe
2016-08 EPUB 3 Accessibility Guidelines Accessibility conformance criteria, based on WCAG 2.0.
  • IDPF
  • Madeleine Rothberg, NCAM-WGBH
2016-09 Personalisation tools by

Preferences for Global Access

The following prototypes are available for demonstration:
  • ISKME
  • IDRC
  • IBM's Accessibility Software Division
  • RtF-I
  • Inclusive Technologies
  • WGBH National Center for Accessible Media
 Madeleine Rothberg, NCAM-WGBH
2016-11 Device templates for URC-compliant targets

Device templates are strongly needed for interoperability of pluggable user interfaces across device models. Device manufacturers can use the appropriate templates as a basis for their products. With the new inheritance feature (see ISO/IEC 24752-2:2014) user interface sockets can be easily extended for product-specific additions. However, the pluggable user interfaces for the device template can still be used for the extended product (albeit hiding the additional features).

The following device templates are currently published:

  • TV Set 1.0
  • Light Bulb 1.0
  • Coloured Light Bulb 1.0
  • openURC
  • HDM (Smirek is editor of multiple device templates)
Expected 2016

[Madeleine?]

Schema.org revision

Adding two new properties in 2016: accessMode and accessModeSufficient. Pending as of September 2016.
  • Madeleine Rothberg, NCAM-WGBH
Expected 2016

[Madeleine?]

EPUB 3.1 release

EPUB 3.1 and EPUB Accessibility 1.0: Conformance and Discovery Requirements for EPUB Publications are under review during the last quarter of 2016. Final documents expected this year. IDPF
  • Madeleine Rothberg, NCAM-WGBH
expected publication in 2017

ISO/IEC 24752-8 User interface resource framework

This document defines a RESTful protocol and data formats in XML and JSON for the provision and delivery of resources that are related to user interface adaptation based on context of use. It addresses requirements and recommendations for the following services:

  • User-context service (for managing descriptions of a user’s needs and preferences)
  • Task-context service (for managing descriptions of a task context, e.g. the user’s goals, the application and functionalities they are using)
  • Equipment-context service (for managing descriptions of a user’s equipment, i.e. devices, software/hardware platforms)
  • Environment-context service (for managing descriptions of a usage environment, e.g. brightness level, noise level, current time)
  • Resource service (for managing user interface resources, e.g. texts, images, icons, pictograms, videos, documents)
  • Resource-description service (for managing descriptions of resources or descriptions of user interface settings)
  • Matching service (for finding appropriate resources based on specific contexts and other match criteria)

Note: Applications using the GPII framework need a way to load user interface resources at runtime that match to a user's personal needs and preferences. Web and other clients will be able to do so via communication with a resource server through this new RESTful protocol.

Status information:

  • DIS vote will soon be open - Feedback welcome through national bodies
  • ISO/IEC JTC1 SC35
  • DIN NA 023-00-04 GA (German mirror to SC35 WG8)
  • openURC Technical Committee
  • HDM (Gottfried Zimmermann is editor of 24752-8)
expected publication in 2018

Revision of ISO/IEC 24751-1: AccessForAll Framework For Individualized Accessibility

Part 1 is currently being revised within ISO/IEC JTC1 SC36 on Information technology for learning, education and training. The revision is needed to make the standard conforming to the concepts of the GPII framework, including:

  • A registry approach for the definition of terms for personal preference concept, context description concepts, and resource description concepts.
  • Set of information items for a registered concept
  • Relation between terms, equivalencies, etc. Similar to a thesaurus.

The GPII registry server conforms to ISO/IEC 24751.

Status information:

  • CD2 vote currently open
  • ISO/IEC JTC1 SC36
  • DIN NA 043-01-36 AA
  • Jutta Treviranus, IDRC, is lead editor for part 1
  • Andy Heath, collaborator of GPII
expected publication in 2017/18

[Andy?]

ISO/IEC 29138-1 User Needs Summary (revision)

This revision of the User Needs Summary standard will be compatible with GPII. Includes potential mappings from User Needs to GPII preferences (not one to one), satisfying personal needs in particular ICT contexts.

  • Individualization is a category of user needs
  • 2017-05-21 CD2 ballot closing, feedback welcome through national bodies
  • Mapping with WCAG 2.1 SCs addressing cognitive? Mapping needs to solutions and vice versa.
  • ISO/IEC JTC1 SC35
  • DIN NA 023-00-02 GA (German mirror to SC35 WG6)
  • Andy Heath, collaborator of GPII
  • HDM (Gottfried Zimmermann)
expected publication in 2018

[Andy?]

ISO/IEC 30071-1 Code of practice for creating accessible ICT products and services

Derived from BSI 8878. Harmonization with GPII and user needs summary (ISO/IEC 29138-1).

  • Process-oriented standard, scope different from WCAG.
  • CD ballot opening May 1, until June 7
  • ISO/IEC JTC1 SC35
  • DIN NA 023-00-02 GA (German mirror to SC35 WG6)
  • Andy Heath, collaborator of GPII
  • HDM (Gottfried Zimmermann)
expected publication in 2018

ISO/IEC 24752-7 RESTful target integration

This part of ISO/IEC 24752 specifies an alternative way of implementing URC-compliant targets as RESTful Web services. This is more lightweight than implementing a target as SOAP-based service (cf. part 6). Also, Web applications can directly connect to RESTful targets.

Note: The Universal Control Hub can be construed as a proxy target that provides access to other targets. The URC-HTTP protocol of the UCH and the URC-HTTP Target protocol are therefore predecessors of the RESTful protocol for targets to be developed.

RESTful Web interfaces have become the de-facto standard in today's heterogenous distributed systems. GPII's architecture builds upon REST.

  • ISO/IEC JTC1 SC35
  • DIN NA 023-00-04 GA (German mirror to SC35 WG8)
  • openURC Technical Committee
  • HDM (Lukas Smirek is editor of 24752-7)
expected publication in 2018 ISO/IEC 24751-4: AccessForAll Framework For Individualized Accessibility - Part 4: Registry server API A concept registry needs to be globally accessible through a well-defined API, and clear format rules must exist for the exchange of concept records. This document specifies a RESTful API for a registry (a.k.a. registry

server), and a JSON format for concept records to be exchanged through the registry API.

The following use cases illustrate the need for a standardized API and concept record format. This list of use cases is not intended to restrict further uses of this document in any way.

–      A human registry client (e.g. developer of an assistive technology solution) registers a term on a registry server. This can be facilitated by either a Web interface of the registry, or by a third-party development application (e.g. an Integrated Development Environment) running on the person's computer. The third-party development application has some advantages over the Web interface since it allows for a tighter integration of development platform and registry server. However, it requires the definition of a registry API and of a concept record format.

–      An infrastructure component (e.g. preference management tool, match-maker) looks up a concept term on a registry server. Thus, the definition of a concept term can be presented to the user, or the value space of a concept term can be taken into account for match-making.

–      A syntax checker (e.g. special lint tool) or a preference server verify the contents of a new need and preference set by validating against the concept records on a registry server. By this procedure, invalid values for concept terms can be detected. In case of an invalid need and preference set, the syntax checker or preference server can notify the user about the error, or make automatic corrections.

–      Two preference servers synchronize their need and preference sets. This could be a full synchronization over all contained need and preference sets, or it could affect only a part of the sets. To avoid the distribution of invalid content, incoming sets can be verified against the concept records of a registry server (e.g. to detect invalid values), and erroneous sets can be skipped or automatically corrected.

–      Two registry servers synchronize their registry entries. This could be a full synchronization over all contained concept records, or it could affect only a part of the entries.

NOTE 1  While ISO/IEC 24751-1 leaves open whether there is a single or multiple registry servers, it is possible to run multiple registry servers globally. Some organizations have built, for security and privacy reasons, self-contained digital infrastructures (such as Intranets) with only very few and well-defined gateways to the external Internet. Such organizations would possibly prefer to have their own registry server running in their infrastructure, and have it synchronize with some global registry server in a secured way from time to time. Also, organizations that develop adaptive user interfaces or assistive technology solutions would likely want to have their own registry server for experimentation purposes.

  • ISO/IEC JTC1 SC36
  • DIN NA 043-01-36 GA (German mirror to SC36)
expected release in June 2018

[Judy?]

[Shadi?]

WCAG 2.1 A slate of additional success criteria are being discussed, including one on personalization:
  • Success Criterion 1.3.4 Support Personalization (minimum) under discussion
  • First public working draft available. Call for comments open now, until end of this week.
  • Mapping with ISO/IEC 30071-1 addressing cognitive? Mapping needs to solutions and vice versa.
  • Harmonization with revision of ETSI EN 301 549 wanted
 W3C AG WG Shadi, Judy
requirements expected in Aug. 2018

[Judy?]

[Shadi?]

W3C AG 3.0 (Silver) Collecting requirements now. Potentially broadening scope beyond Web. W3C AG WG, accessibility guidelines and testing task force Shadi, Judy
expected release in July 2018

[Judy?]

[Shadi?]

WAI-ARIA 1.1 Improvements on ARIA 1.0.
  • Currently in CR state.
W3C ARIA WG
[Judy?]

[Shadi?]

WAI-ARIA 2.0 Some architectural discussion needed. Coordinating with IDPF (SVG accessibility). W3C ARIA WG
Retrieved from "http://wiki.gpii.net/index.php?title=Standardization_Roadmap&oldid=20284"