From 28465db60f87fc0219157519c2ebc2ca3401dd16 Mon Sep 17 00:00:00 2001 From: Matthew Tylee Atkinson Date: Wed, 3 Apr 2024 21:52:24 +0000 Subject: [PATCH] AC2024 slides on well-known destinations (#267) SHA: f91872cc41b4503a976a53dbe847a507ba0bc7e6 Reason: push, by matatk Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- index.html | 6 +- tools/index.html | 966 +++-------------------------------------------- 2 files changed, 48 insertions(+), 924 deletions(-) diff --git a/index.html b/index.html index b1cb000a..aa3f7919 100644 --- a/index.html +++ b/index.html @@ -167,15 +167,15 @@ ], "group": "apa", "github": "w3c/adapt", - "publishISODate": "2024-03-12T00:00:00.000Z", - "generatedSubtitle": "W3C Editor's Draft 12 March 2024" + "publishISODate": "2024-04-03T00:00:00.000Z", + "generatedSubtitle": "W3C Editor's Draft 03 April 2024" }

WAI-Adapt Explainer

-

W3C Editor's Draft

+

W3C Editor's Draft

More details about this document
diff --git a/tools/index.html b/tools/index.html index 2e714d43..82652487 100644 --- a/tools/index.html +++ b/tools/index.html @@ -1,278 +1,22 @@ - - - - - - - - -WAI-Adapt: Tools Module - - - - - - - - - - - - - -
-

-

WAI-Adapt: Tools Module

-

W3C Editor's Draft

-
- More details about this document -
-
This version:
- https://w3c.github.io/adapt/content/ -
-
Latest published version:
- https://www.w3.org/TR/adapt-tools/ -
-
Latest editor's draft:
https://w3c.github.io/adapt/content/
-
History:
- https://www.w3.org/standards/history/adapt-tools/ -
- Commit history -
- - - - - -
Editors:
- -
- (Benetech) -
- (Invited Expert) -
- (W3C) -
- (W3C) -
- Richard Schwerdtfeger (Knowbility) (Editor until October 2017) -
- - -
Feedback:
- GitHub w3c/adapt - (pull requests, - new issue, - open issues) -
- - -
-
- - -

- Copyright - © - 2022-2024 - - World Wide Web Consortium. - W3C® - liability, - trademark and - document use rules apply. -

-
-
-

Abstract

+ + + +

This specification provides web content authors a standard approach to support web users who are persons with various cognitive and learning disabilities, including users who:

  • may get overwhelmed with the volume of on-screen messages, and wishes to filter out low priority messages and concentrate on critical priority messages;
    • @@ -281,67 +25,33 @@

    WAI-Adapt: Tools Module

The technology described in this specification is intended to be used to programmatically transform the appearance of typical web content including form controls, icons, and other user interface elements into a rendering more familiar and comprehensible to an individual user. Use cases and relevant vocabulary terms are defined which allow user agents to augment or adapt content to better fit a particular user's particular needs. This helps users with varying needs to understand web content more readily, by simplifying the web interaction, or by avoiding forcing the user to grapple with unfamiliar representations they are ill equipped to comprehend.

-

This WAI-Adapt: Tools Module is a component of the WAI-Adapt series introduced in the WAI-Adapt Explainer document [personalization-semantics-1.0].

+

This WAI-Adapt: Tools Module is a component of the WAI-Adapt series introduced in the WAI-Adapt Explainer document [[personalization-semantics-1.0]].

-

Status of This Document

This section describes the status of this - document at the time of its publication. A list of current W3C - publications and the latest revision of this technical report can be found - in the W3C technical reports index at - https://www.w3.org/TR/.

- This document was published by the Accessible Platform Architectures Working Group as - an Editor's Draft. -

Publication as an Editor's Draft does not - imply endorsement by W3C and its Members.

- This is a draft document and may be updated, replaced or obsoleted by other - documents at any time. It is inappropriate to cite this document as other - than work in progress. - -

- - This document was produced by a group - operating under the - W3C Patent - Policy. - - - W3C maintains a - public list of any patent disclosures - made in connection with the deliverables of - the group; that page also includes - instructions for disclosing a patent. An individual who has actual - knowledge of a patent which the individual believes contains - Essential Claim(s) - must disclose the information in accordance with - section 6 of the W3C Patent Policy. - -

- This document is governed by the - 03 November 2023 W3C Process Document. -

+
-

1. Introduction

This section is non-normative.

- -

1.1 Background

- -

This specification module enables authors to add semantic information about content at the element level, in order to indicate the priority level of a message for the individual user, or programmatically enumerate tasks that the user is required to complete, so that users who have memory issues can keep track of the steps previously completed. It is anticipated that multiple screen renderings (transformations) will be supported in order to meet the differing needs of different users. Final renderings — generated via helper apps or 3rd-party tools — will be ultimately defined by the user's configuration settings.

+
+

Introduction

+
+

Background

+

This specification module enables authors to add semantic information about content at the element level, in order to indicate the priority level of a message for the individual user, or programmatically enumerate tasks that the user is required to complete, so that users who have memory issues can keep track of the steps previously completed. It is anticipated that multiple screen renderings (transformations) will be supported in order to meet the differing needs of different users. Final renderings — generated via helper apps or 3rd-party tools — will be ultimately defined by the user's configuration settings.

This document lists examples of the personalized tools properties, an extension of WAI-Adapt Explainer, including the properties of messageimportance, messagefrom, messagecontext, messagetime, and stepindicator.

-

1.2 WAI-Adapt: Tools Module

- -

WAI-Adapt: Tools Module is the third and final part of the WAI-Adapt technical specification, which provides WAI-Adapt semantics and vocabularies that can be used to mark-up web content with additional semantic information, enabling user agents to augment or adapt content to various user-scenarios based on the user’s personalization settings or preferences. The Tools Module enhances web content by providing additional information about message importance (for filtering), and tracking multi-step activities. User agents can use these semantics to augment or adapt content to the user’s scenario — for example allowing for the prioritization or filtering of on-screen messages. This helps users with varying needs to filter content by providing support for managing distractions.

+
+

WAI-Adapt: Tools Module

+

WAI-Adapt: Tools Module is the third and final part of the WAI-Adapt technical specification, which provides WAI-Adapt semantics and vocabularies that can be used to mark-up web content with additional semantic information, enabling user agents to augment or adapt content to various user-scenarios based on the user’s personalization settings or preferences. The Tools Module enhances web content by providing additional information about message importance (for filtering), and tracking multi-step activities. User agents can use these semantics to augment or adapt content to the user’s scenario — for example allowing for the prioritization or filtering of on-screen messages. This helps users with varying needs to filter content by providing support for managing distractions.

-

1.3 Vocabulary Structure and Implementations

- +
+

Vocabulary Structure and Implementations

All the vocabulary in WAI-Adapt: Symbols Module is constructed of properties and their values. Please see our WAI-Adapt Explainer.

The vocabulary implementations included in this document are available at our implementations wiki page.

-

1.3.1 Properties

- +
+

Properties

Properties are the main units of WAI-Adapt types supported by the vocabulary. A given property supports a specific type of WAI-Adapt. That property would only be used once on a given piece of content, but multiple different properties could be used on the same piece of content to address different needs.

-

1.3.2 Values

- +
+

Values

Values provide the specific personalization information for the property. The possible values for each property are elaborated in the definition of the property in the modules. Some properties require the value to come from a predefined list of possible values, others can accept arbitrary strings, and some may accept multiple values. The attribute value may be one of the following types:

ID reference
@@ -363,614 +73,28 @@

WAI-Adapt: Tools Module

Note that the attributes and values in this specification do not overide the semantics exposed in the accessibility tree, but rather augment them. In the case of conflict between an element's semantics and the attribute values, validation algorithms should issue a warning but not an error.

-
Editor's note
Since implementations have not yet been finalized, any examples in this document are illustrative only, and are provided to help in understanding the concept. All examples will be updated once implementation examples are finalized.
+
Since implementations have not yet been finalized, any examples in this document are illustrative only, and are provided to help in understanding the concept. All examples will be updated once implementation examples are finalized.
-

1.4 Use Cases and Requirements

- +
+

Use Cases and Requirements

The Requirements for Personalization Semantics describes use cases and requirements. This module provides properties to fulfill requirements related to user support tools.

-

2. Terms

- +
+

Terms

This document uses a number of specific terms related to various cognitive disabilities and related user-needs. Those terms have been defined by the Cognitive and Learning Disabilities Accessibility Task Force. See the COGA Glossary for specific definitions.

-

3. Vocabulary

- -

3.1 All the Step Indicator Properties

- - -

3.1.1 Step Indicator Usage

- -
3.1.1.1 Description
- -

The stepindicator defined values should be used whenever there is a sequence of - tasks that the user is required to complete, so that users who have memory issues can keep - track of the steps previously completed.



-

Note that there is no default value.

- -
-
3.1.1.2 Example
- -

Note, the specific mechanism to apply these defined values has not been decided:

-
-
- Example 1: stepindicator using adapt- - 
<div adapt-stepindicator="book trip">
-  <div adapt-status="complete" aria-label="select flight" adapt-step="1" adapt-steplocation="uri" />
-  <div adapt-status="current" aria-label="book hotel" adapt-step="2" adapt-steplocation="uri" />
-  <div adapt-status="" aria-label="book car" adapt-step="3" adapt-steplocation="uri" />
-  <div adapt-status="" aria-label="purchase trip" adapt-step="4" steplocation="uri" />
-</div>
-
-
-
-or the step number can be implied by the DOM
-
-
-
-  <div adapt-stepindicator="book trip">
-    <div adapt-status="complete" aria-labelledby="select flight">
-      <a href="uri">Select flight</a>
-    </div>
-    <div adapt-status="current" aria-labelledby="book hotel">
-      <a href="uri">Book Hotel</a>
-    </div>
-    <div adapt-status="" aria-labelledby="book car">
-      <a href="uri">Book car</a>
-    </div>
-    <div adapt-status="" aria-labelledby="purchase trip">
-      <a href="uri">Purchase trip</a>
-    </div>
-  </div>
-
-
-
-
- - - - - -

3.2 All the message properties

- - -

3.2.1 messageimportance

- -
3.2.1.1 Description
- -
-

The messageimportance attribute is used to indicate the priority level of a message . This can be helpful for a person who gets overwhelmed with messages and filter out low messages and concentrate on critical priority messages.

-

Supported values: low, medium(Default), critical

- -
-
-
3.2.1.2 Example
- -

The specific mechanism to apply these defined values has not been decided

-
-
- Example 2: messageimportance using adapt- - 
<div role="alert" adapt-messageimportance="medium">
-    It is your daughter's birthday tomorrow
-</div>
-
- -
-
3.2.1.3 Characteristics
- - - - - - - - - - - - - - - - - - - - - - - - - - -
CharacteristicValue
Related Concepts:SVG [SVG2] and DOM [DOM4] active
Used in Roles:All elements of the base markup
Inherits into Roles:Placeholder
Value:token
-
-
3.2.1.4 Values
- - - - - - - - - - - - - - - - - - - - - - -
ValueDescription
criticalTo be critical a message needs to be both urgent and content that the user is very likely to consider important. For example, a system may send a message that it is going to reboot in one minute to install updates.
medium (default)Important messages that needs the user's attention at their convenience. For example, a relatively important chat message.
lowA message that does not need time sensitive attention. For example, a typical chat message.
-
-
- - - -

3.2.2 messagefrom

- -
3.2.2.1 Description
- -
-

The messagefrom attribute can be used to help identify who a message a user receives is from.

-

Supported values: a string value that identifies the sender of the message. If multiple names are used they can be separated by a comma.

-

Note that there is no default value.

-
-
-
3.2.2.2 Example
- -

The specific mechanism to apply these defined values has not been decided

-
-
- Example 3: messagefrom using adapt- - 
<div role="alert" adapt-messageimportance="low"
-    adapt-messagefrom="lisa seeman, lseeman">
-    I posted a new version on GitHub for you to review
-</div>
-
-
-
3.2.2.3 Characteristics
- -

The specific mechanism to apply these defined values has not been decided

- - - - - - - - - - - - - - - - - - - - - - - - - -
CharacteristicValue
Related Concepts:SVG [SVG2] and DOM [DOM4] active
Used in Roles:All elements of the base markup
Inherits into Roles:Placeholder
Value:string text
-
-
- - - -

3.2.3 messagecontext

- -
3.2.3.1 Description
- -
-

The messagecontext attribute can help clarify where a message is coming from. Knowing who the message is from as well as in which context the message was written are both importent in understanding the meaning of the message received.

-

Supported values: a string value that identifies the location that makes this message relevant. Typical values are "home" and "work". If multiple locations are relevant they can be separated by a coma.

-

Note that there is no default value.

-
-
-
3.2.3.2 Example
- -

The specific mechanism to apply these defined values has not been decided

-
-
- Example 4: messagecontext using adapt- - 
<div role="alert"
-    adapt-messageimportance="low"
-    adapt-messagefrom="lisa seeman, lseeman"
-    adapt-messagecontext="work">
-    I posted a new version on GitHub for you to review
-</div>
-
-
-
3.2.3.3 Characteristics
- - - - - - - - - - - - - - - - - - - - - - - - - - -
CharacteristicValue
Related Concepts:SVG [SVG2] and DOM [DOM4] active
Used in Roles:All elements of the base markup
Inherits into Roles:Placeholder
Value:string text
-
-
-

3.2.4 messagetime

- -
3.2.4.1 Description
- -
-

The messagetime attribute helps clarify when the message was sent.

-

Supported values: 24 hour date time format. DD.MM.YEAR.HOUR.MM - DD.MM.YEAR.HOUR.MM where the second date is an optional exclusive expiry date.

-

Note that there is no default value.

-
-
- -
3.2.4.2 messagetime
- -

The specific mechanism to apply these defined values has not been decided

-

@@1-line description

-
-
- Example 5: messagetime using adapt- - 
    <div role="alert"
-        adapt-messageimportance="medium"
-        adapt-messagefrom="my calender"
-        adapt-messagecontext="work"
-        adapt-messagetime="10.02.2017.00.00-16.02.2017.00.00">
-        Renew your driving license this week
-    </div>
-
-
-
-    <div role="alert"
-        adapt-messageimportance="critical"
-        adapt-messagefrom="my calender"
-        adapt-messagecontext="work"
-        adapt-messagetime="16.02.2017.00.00">
-        Renew your driving license ASAP
-    </div>
-
-
-
3.2.4.3 Characteristics
- -

The specific mechanism to apply these defined values has not been decided

- - - - - - - - - - - - - - - - - - - - - - - - - -
CharacteristicValue
Related Concepts:SVG [SVG2] and DOM [DOM4] active
Used in Roles:All elements of the base markup
Inherits into Roles:Placeholder
Value:string text
-
-
-
- - - - +
+

Vocabulary

+
+
-

4. Privacy and Security Considerations

- -

This specification adds context information about content to the document, and should not affect security.

-

Although this specification does not expose personal preferences and personal information, third party user agents or proxy server(s) acting upon our semantic information may need to store personal preferences on how to present content to a specific user. It is recommended that any user agent or proxy server implements best practices to protect all personal preferences and personal information.

+
+

Privacy and Security Considerations

+

This specification adds context information about content to the document, and should not affect security.

+

Although this specification does not expose personal preferences and personal information, third party user agents or proxy server(s) acting upon our semantic information may need to store personal preferences on how to present content to a specific user. It is recommended that any user agent or proxy server implements best practices to protect all personal preferences and personal information.

Any user agent with user settings are recommended to follow best practices to keep user information secure.

-

A. Acknowledgments

This section is non-normative.

- -

The following people contributed to the development of this document.

-

A.1 Participants active in the WAI-Adapt TF at the time of publication

- -
    -
  • Matthew Atkinson (TPG Interactive)
    • -
  • Mike Beganyi (TPG Interactive)
    • -
  • Thaddeus Cambron (Invited Expert)
    • -
  • Michael Cooper (W3C/MIT)
    • -
  • John Foliot (Invited Expert)
    • -
  • Becky Gibson (Knowbility, Inc.)
    • -
  • Charles LaPierre (Benetech)
    • -
  • Roy Ran (W3C/Beihang)
    • -
  • Janina Sajka (Invited Expert)
    • -
  • Lisa Seeman (Invited Expert)
    • -
  • Sharon Snider (IBM Corporation)
    • -
  • Lionel Wolberger (UserWay)
    • -
-
-

A.2 Other WAI-Adapt TF contributors, commenters, and previously active participants

- -
    -
  • Joanmarie Diggs (Igalia)
    • -
  • Richard Schwerdtfeger (Knowbility, Inc.)
    • -
  • Jason White (Educational Testing Service)
    • -
-
-

A.3 Enabling funders

- -

This publication has been funded initially under contract number ED-OSE-10-C-0067, then under contract number HHSP23301500054C, and now under HHS75P00120P00168. The content of this publication does not necessarily reflect the views or policies of the U.S. Department of Health and Human Services, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government. Some of the work on this project has also received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement No.780529 and 643399.

-
-
- - - -

B. References

B.1 Informative references

- -
[DOM4]
- DOM Standard. Anne van Kesteren. WHATWG. Living Standard. URL: https://dom.spec.whatwg.org/ -
[personalization-semantics-1.0]
- WAI-Adapt Explainer. Lisa Seeman-Horwitz; Charles LaPierre; John Foliot; Michael Cooper; Ruoxi Ran; Richard Schwerdtfeger. W3C. 3 January 2023. W3C Working Group Note. URL: https://www.w3.org/TR/adapt/ -
[SVG2]
- Scalable Vector Graphics (SVG) 2. Amelia Bellamy-Royds; Bogdan Brinza; Chris Lilley; Dirk Schulze; David Storey; Eric Willigers. W3C. 4 October 2018. W3C Candidate Recommendation. URL: https://www.w3.org/TR/SVG2/ -
-
\ No newline at end of file +
Acknowledgements placeholder
+ +