Search the space:
This is a draft - please comment....
ISO/IEC 24751 is intended to facilitate the matching of individual user needs and preferences with resources \ [note:interfaces are used to access resources\] that meet those needs and preferences to enable appropriate perception of the resources. This matching might involve finding a suitable resource or interface, or format of a resource, or it might involve adaptation of the resource or its interface. It is intended to address mismatches between personal needs and preferences caused by any number of circumstances, including requirements related to client devices, environments, language proficiency or abilities. The terms and definitions within ISO/IEC 24751 are not judgmental or based on disability classifications, diagnosis or assumptions regarding disability, rather they are descriptions of functions that can be applied by all users; the purpose is not to point out flaws in resources or interfaces with respect to accessibility and adaptability, but to facilitate the discovery and use of the most appropriate resource, configuration or interface for each user. Wiki Markup
In ISO/IEC 24751, it is recognized that individuals experience a disability when there is a mismatch between the individual’s needs (or preferences) and the user experience, service or environment delivered. Disability is therefore not viewed as a personal trait but as a consequence of the relationship between the individual and the environment or resource delivery system. An individual who is blind is not disabled when the resource is delivered in audio, but an individual who does not have the necessary background knowledge to understand the resource, or an individual who is listening to the resource in a noisy environment, is disabled. Given this reframing, a system is accessible when user needs can be addressed or matched (through adaptation, re-aggregation or substitution of resources and user interfaces). Accessibility is determined by the flexibility of the system or environment (with respect to presentation, control methods, structure, access mode, and supports, for example) and the availability of adequate alternative-but-equivalent content and activities. The needs and preferences of a user may arise from the user's context or environment, the technical requirements of the user's device, the tools available (e.g. assistive technologies such as Braille devices, voice recognition systems, alternative keyboards, etc.), the user's background, or a disability in the traditional sense. Accessible systems adjust the user interface or configuration of the system, locate needed resources and adjust the resources to match the characteristics of the resources to the needs and preferences of a user.
ISO/IEC N24751 does not describe how to create accessible content. Other work exists and standards are under development that describe how content and interfaces can be made more accessible.\[\|#_ftn1\]
\\not describe how to create accessible content. Other work exists and standards are under development that describe how content and interfaces can be made more accessible.[1|#_ftn1] Wiki Markup ISO/IEC24751 does not define how to deal with types and roles of Persons, (and two sub-types of Person namely organization and public administration). Other standards exist and are under development that address these and related issues.\[\|#_ftn2\]
\\ Wiki Markup
Approach to providing accessibility (4.3) in a computer-mediated environment in which the digital resources (4.7) and their method of delivery are matched to the needs and preferences of the user
A registry of terms to be used in creating PNP statements, resource descriptions, pull statements\[\|#_ftn3\] and other functions in support of personalization on demand enabled by ICT and networked systems Wiki Markup
AccessForAll (AfA) accessibility
unit of data for which the definition, identification, representation and permissible values are specified by means of a set of attributes
\ [ISO/IEC 11179-1:2004, 3.3.8\] \ [ISO/CEI 11179-1:2004, 3.3.8\] Wiki Markup
dataset, term set
identifiable collection of data
NOTE 1 Disability in an AfA context is not a personal trait but a consequence of the relationship between the user and a resource delivery system.
〈medical perspective〉 any restriction or lack \ [resulting from an *impairment* (4.12)\] of ability to perform an activity in the manner, or within the range, considered normal for a human being Wiki Markup
NOTE 1 This definition of “disability” is included to ensure that users who may have “legal rights” to assistive technologies are served.
set of one or more computers, associated software, peripherals, terminals, human operations, physical processes, information transfer means, that form an autonomous whole, capable of performing information processing and/or information transfer
\[ISO/IEC 14662:2004, 3.1.8\] Wiki Markup
system of signs for communication, usually consisting of a vocabulary and rules
NOTE In this part of ISO/IEC 24751, language refers to “natural languages” or “special languages” but not “programming languages” or “artificial languages”.
\[ISO 5127:2001, 1.1.2.01\] Wiki Markup
Personal Needs and Preferences (PNP) statement
Personal Needs and preferences (PNP) context set
A (named) *dataset* (4.8) of conditions to determine if a PNP statement (4.16) applies\[\|#_ftn4\] Wiki Markup
Personal Needs and preferences (PNP) context name
extent to which a product can be used by specified users to achieve specified goals, with effectiveness, efficiency and satisfaction, in a specified context of use
\[ISO 9241-11:1998, 3.1\] Wiki Markup
The registry will establish a lightweight, minimally formalized process for sanctioning new terms.
\[\|#_ftnref1\] See for example W3C/WAI Web Content Accessibility Guidelines \ [W3C/WAI, WCAG\], ISO 15836, ISO 15706, other standards of ISO/TC 46 and ISO/IEC JTC 1/SC 29, as well as standards being developed by ISO/IEC JTC 1/SC 36.
\\ Wiki Markup \[\|#_ftnref2\] See further ISO/IEC 14662:2004, \ _Information technology --- — Open-edi reference model_ and the ISO/IEC15944 multi-part e-business standard.
\\ Wiki Markup \[\|#_ftnref3\] Pull statements are requests to fill gaps in meeting a PNP statement. Wiki Markup \[\|#_ftnref4\] The stress is on the individual’s perspective. A condition should be clear: for example, an objectively determined condition such as ‘if it is raining’ does not indicate if the user is affected by the rain, as they may be sheltered or have an umbrella. Wiki Markup