W3C

4.8.11.3 The accessible element

Status: Last call for comments. ISSUE-74 (canvas-accessibility) blocks progress to Last Call

Categories
Flow content.
Contexts in which this element may be used:
Where flow content is expected.
Content model:
Flow content, but with no accessible element descendants.
Content attributes:
Global attributes
DOM interface:
interface HTMLAccessibleElement : HTMLElement {
    };

The accessible element contains an accessible, unrendered document or application that represents canvas.

Authors needing to produce an accessible version of canvas may do so by using accessible to create accessible content whose visual rendering is done on canvas. Content within accessible is keyboard focusable but not operable by any other device input. Authors using accessible to produce an accessible canvas maintain keyboard focus within the accessible content when processing other device input canvas. While ensuring the visible rendering of focused content within the accessible is performed on the canvas.

The accessible document or application contained within accessible should accurately convey the semantics of the canvas in an accessible hierarchical form that is directly interoperable with assistive technologies. Interoperability between assistive technologies is achieved through the use of standard interactive content, content with strong host language semantics, and the use of WAI-ARIA attributes.


If the author determines it is not possible to make canvas through the use of accessible content, the author should provide alternative content that may be rendered through the use of CSS media queries or some other means as determined by the user. This alternative content may include the use of fallback content or other content otherwise hidden to the user.

3.2.7 Annotations for assistive technology products (AFA)

Authors may use the (AFA) resource meta data attributes on HTML elements, whose vocabulary is defined in the IMS Global Learning Consortium Access For All specifications, for the purposes user selection of renderable content.

What is left out from Access For All - currently

Education Level as it varies between contexts. Olfactory access mode and hazard. as can't meet CR with these. (need 2 implementations)

Goal is to allow a user to choose content rendered based on user preferences by supplying meta data about resources in the page to allow for content selection. If an author had to provide a UI that allowed the user to choose from multiple UIs to address all users needs the UI would be complicated due to having to support selection of multiple UI features. Example:

Choose one of the following UIs

  • Supports assistive technologies
  • High contrast
  • non-flashing
  • an e-book
    • Premise: Define accessibility media querries to chooose content based on resource meta data in content. example: 3.2.7.1 Access Mode accessMode

    an access mode through modality of a described resource or adaptation is communicated; if external adaptations for the resource are known, the access modes of those adaptations are not included.

    accessmModeValue: auditory, textual, visual

    3.2.7.2 Access Mode Adapted accessModeAdapted

    the access mode of the intellectual content of the resource that is being adapted

    accessmModeValue: auditory, textual, visual

    3.2.7.3 Adaptation type AdaptationType

    the access mode of the intellectual content of the resource that is being adapted
    Recommend remove: haptic as won't pass CR. Don't see how could implement otherwise.

    adaptationTypeValue: audioDescription, caption, e-book, signLanguage, highContrast, transcript, alternativeText, longDescription

    3.2.7.4 AT Interoperable ATInteroperable

    This is a boolean that indicates the resource is compatible with one or more accessibility API. Setting this resource metadata indicates compliance with WCAG 2.0 checkpoints: 1.1.1, 1.3.1, 1.3.2, 2.4.4, 3.1.1, 3.1.2, 3.3.2, 4.1.1, and 4.1.2.

    Boolean Value

    3.2.7.5 Control Flexibility ControlFlexibility

    a single input method which is sufficient to control the described resource

    ControlFlexibilityValue: fullKeyboardControl, fullMouseControl

    3.2.7.8 Display Transformability afa-DisplayTransformability

    a characteristic of display of the described resource that can be programmatically modified

    Recommend ommitting displaytransformability in favor of CSS. This mimimzes impact to HTML 5. DisplayTransformabilityValues: fontSize, fontFace, fontWeight, letterSpacing, wordSpacing, lineHeight, foregroundColour, backgroundColour, cursorPresentation, highlightPresentation, layout, structurePresentation

    3.2.7.10 Has Adaptation HasAdaptation

    Identifier of a resource which is an adaptation for this resource.

    This is a URI. (Rich looking at this to see if can use simply use a source URL)

    3.2.7.11 HazardHazard

    a characteristic of the described resource that must not be delivered to some users.

    HazardValues: flashing, sound, motionSimulation

    3.2.7.12 Is Adaptation of afa-IsAdaptationOf

    Identifier of a resource for which this is an adaptation

    URI.

    3.2.7.13 Language of AdaptationlanguageOfAdaptation

    a language of the intellectual content of the resource [ISO 639-2:1998]

    ISO 639-2:1998 Rich Note: we should use HTML5 definition of langugae. ... also can the lang attribute suffice?