Digital Accessibility Reference Library

UNDER CONSTRUCTION
I am still working on adding the material to this, so it is messy and incorrect at the moment

This Library should be seen as a help and not a full descriptive rule how to implement accessibility according to EN 301549.
I wrote this to give clarity in what is included in EN 301549, how to compare it with WCAG 2.1.
It was thought as a “translation” how to use the WCAG 2.1 and EN301549 when testing mobile applications.
To make it easier for Software Testers to get started and to understand the guidelines, also to make it easier to communicate with others in the development process by refereeing to the same document and text during discussions.
It is by no means including all information and it is still one´s own responsibility to study and educate on this topic.

⬤ Perceivable

  • 1.1.1 Non-text Content (A)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
    • WCAG Description & Clarification
      • All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below.
      • Controls, Input If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Success Criterion 4.1.2 for additional requirements for controls and content that accepts user input.)
      • Controls, Input If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Success Criterion 4.1.2 for additional requirements for controls and content that accepts user input.)
      • Test If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content.
      • SensoryIf non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.CAPTCHAIf the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.
      • Decoration, Formatting, InvisibleIf non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.
    • EN 301 549 Requirements & Notes
      • It shall satisfy WCAG 2.1 Success Criterion 1.1.1 Non-text Content. NOTE: CAPTCHAs do not currently appear outside of the Web. However, if they do appear, this guidance is accurate.
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface. 2. The software provides support to assistive technologies for screen reading
    • EN 301 549 Reference number
      • C.11.1.1.1.1
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.2.1 Audio-only and Video-only (Prerecorded) (A)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • Text
    • WCAG Description & Clarification
      • Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded) (Level A): For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such:
      • Prerecorded Audio-onlyAn alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.
      • Video-onlyEither an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.
    • EN 301 549 Requirements & Notes
      • It shall satisfy the WCAG 2.1 Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded). NOTE: The alternative can be provided directly in the software – or provided in an alternate version that meets the success criterion.
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface. 2. The software provides support to assistive technologies for screen reading. 3. Pre-recorded auditory information is not needed to enable the use of closed functions of ICT.
    • EN 301 549 Reference number
      • C.11.1.2.1.1
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.2.2 Captions (Prerecorded) (A)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • Text
    • WCAG Description & Clarification
      • Captions are provided for all prerecorded audio content in synchronised media , except when the media is a media alternative for text and is clearly labeled as such.
    • EN 301 549 Requirements & Notes
      • It shall satisfy the WCAG 2.1 Success Criterion 1.2.2 Captions (Prerecorded). EN 301 549 V2.1.2 (2018-08) ETSI 59 NOTE: The WCAG 2.1 definition of “captions” notes that “in some countries, captions are called subtitles”. They are also sometimes referred to as “subtitles for the hearing impaired”. Per the definition in WCAG 2.1, to meet this success criterion, whether called captions or subtitles, they would have to provide “synchronized visual and / or text alternative for both speech and non-speech audio information needed to understand the media content” where non-speech information includes “sound effects, music, laughter, speaker identification and location”.
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface
    • EN 301 549 Reference number
      • C.11.1.2.2
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.2.3 Audio Description or Media Alternative (Prerecorded) (A)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • Text
    • WCAG Description & Clarification
      • Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A): An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.
        Example
        • A movie with audio description. Describer: A title, “Teaching Evolution Case Studies. Bonnie Chen.” A teacher shows photographs of birds with long, thin beaks. Bonnie Chen: “These photos were all taken at the Everglades.” Describer: The teacher hands each student two flat, thin wooden sticks. Bonnie Chen: “Today you will pretend to be a species of wading bird that has a beak like this.” Describer: The teacher holds two of the sticks to her mouth making the shape of a beak. Transcript of audio based on the first few minutes of ” Teaching Evolution Case Studies, Bonnie Chen” (copyright WGBH and Clear Blue Sky Productions, Inc.)
        • An alternative for time-based media for a training video A company purchases a Training video for use by its employees and puts it on the companies intranet. The video involves explaining use of a new technology and has a person talking and showing things at the same time. Since there is no place to insert audio description of the visual demonstrations during gaps in dialogue, the company provides an alternative for time-based media that all employees, including those who cannot see the demonstrations, can use to better understand what is being presented
    • EN 301 549 Requirements & Notes
      • It shall satisfy the WCAG 2.1 Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded). NOTE 1: The WCAG 2.1 definition of “audio description” says that “audio description” is “also called ‘video description’ and ‘descriptive narration’”. NOTE 2: Secondary or alternate audio tracks are commonly used for this purpose.
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface. 2. The software provides support to assistive technologies for screen reading.
    • EN 301 549 Reference number
      • C.11.1.2.3.1
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.2.4 Captions (Live) (AA)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • Text
    • WCAG Description & Clarification
      • Success Criterion 1.2.4 Captions (Live) (Level AA): Captions are provided for all live audio content in synchronized media.
      • A Web cast A news organization provides a live, captioned Web cast.
      • A music Web cast An orchestra provides Communication Access Realtime Translation (CART) captioning of each real-time Web performance. The CART service captures lyrics and dialog as well as identifies non-vocal music by title, movement, composer, and any information that will help the user comprehend the nature of the audio.
    • EN 301 549 Requirements & Notes
      • It shall satisfy the WCAG 2.1 Success Criterion 1.2.4 Captions (Live). NOTE: The WCAG 2.1 definition of “captions” notes that “in some countries, captions are called subtitles”. They are also sometimes referred to as “subtitles for the hearing impaired”. Per the definition in WCAG 2.1, to meet this success criterion, whether called captions or subtitles, they would have to provide “synchronized visual and / or text alternative for both speech and non-speech audio information needed to understand the media content” where non-speech information includes “sound effects, music, laughter, speaker identification and location”.
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface.
    • EN 301 549 Reference number
      • C.11.1.2.4
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.2.5 Audio Description (Prerecorded) (AA)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • Text
    • WCAG Description & Clarification
      • Success Criterion 1.2.5 Audio Description (Prerecorded) (Level AA): Audio description is provided for all prerecorded video content in synchronized media.
      • A movie with audio description. Describer: A title, “Teaching Evolution Case Studies. Bonnie Chen.” A teacher shows photographs of birds with long, thin beaks. Bonnie Chen: “These photos were all taken at the Everglades.” Describer: The teacher hands each student two flat, thin wooden sticks. Bonnie Chen: “Today you will pretend to be a species of wading bird that has a beak like this.” Describer: The teacher holds two of the sticks to her mouth making the shape of a beak. Transcript of audio based on the first few minutes of ” Teaching Evolution Case Studies, Bonnie Chen” (copyright WGBH and Clear Blue Sky Productions, Inc.)
    • EN 301 549 Requirements & Notes
      • It shall satisfy the WCAG 2.1 Success Criterion 1.2.5 Audio Description (Prerecorded). NOTE 1: The WCAG 2.1 definition of “audio description” says that audio description is “Also called ‘video description’ and ‘descriptive narration’”. NOTE 2: Secondary or alternate audio tracks are commonly used for this purpose
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface.
    • EN 301 549 Reference number
      • C.11.1.2.5
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.3.1 Info and Relationships (A)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • Use a screen reader to ensure that all visual and auditory cues, including but not limited to, headings, lists, form fields, grouped elements, audio signals are programmatically determined or available in text.
    • WCAG Description & Clarification
      • Success Criterion 1.3.1 Info and Relationships (Level A): Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
    • Example
      • A form with required fields A form contains several required fields. The labels for the required fields are displayed in red. In addition, at the end of each label is an asterisk character, *. The instructions for completing the form indicate that “all required fields are displayed in red and marked with an asterisk *”, followed by an example.
      • A form that uses color and text to indicate required fields A form contains both required and optional fields. Instructions at the top of the form explain that required fields are labeled with red text and also with an icon whose text alternative says, “Required.” Both the red text and the icon are programmatically associated with the appropriate form fields so that assistive technology users can determine the required fields.
      • A bus schedule table where the headers for each cell can be programmatically determined A bus schedule consists of a table with the bus stops listed vertically in the first column and the different buses listed horizontally across the first row. Each cell contains the time when the bus will be at that bus stop. The bus stop and bus cells are identified as headers for their corresponding row or column so that assistive technology can programmatically determine which bus and which bus stop are associated with the time in each cell.
      • A form where the labels for the checkboxes can be programmatically determined In a form, the labels for each checkbox can be programmatically determined by assistive technology.
      • A text document A simple text document is formatted with double blank lines before titles, asterisks to indicate list items and other standard formatting conventions so that its structure can be programmatically determined.
    • EN 301 549 Requirements & Notes
      • it shall satisfy the WCAG 2.1 Success Criterion 1.3.1 Info and Relationships. EN 301 549 V2.1.2 (2018-08) ETSI 60 NOTE: In software, programmatic determinability is best achieved through the use of accessibility services provided by platform software to enable interoperability between software and assistive technologies and accessibility features of software. (see clause 11.5 Interoperability with assistive technology).
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface. 2. The software provides support to assistive technologies for screen reading.
    • EN 301 549 Reference number
      • C.11.1.3.1.1
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.3.2 Meaningful Sequence (A)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • Use a screen reader to ensure that the content order must be logical and reflect the visual order.
    • WCAG Description & Clarification
      • Success Criterion 1.3.2 Meaningful Sequence (Level A): When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
      • xample 1: In a multi-column document, the linear presentation of the content flows from the top of a column to the bottom of the column, then to the top of the next column.
      • Example 2: CSS is used to position a navigation bar, the main story on a page, and a side story. The visual presentation of the sections does not match the programmatically determined order, but the meaning of the page does not depend on the order of the sections
    • EN 301 549 Requirements & Notes
      • It shall satisfy the WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence..
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface. 2. The software provides support to assistive technologies for screen reading
    • EN 301 549 Reference number
      • C.11.1.3.2.1
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.3.3 Sensory Characteristics (A)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • Text
    • WCAG Description & Clarification
      • Success Criterion 1.3.3 Sensory Characteristics (Level A): Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound.
      • For requirements related to color, refer to Guideline 1.4.
    • Example
      • Example 1: A schedule of competitive events uses color and shape to distinguish the time of each event A table presents a list of times across the top row and a list of events in the first vertical column. The cell corresponding to the time of a particular event has a specific background color and diamond shaped glyph so it can be identified by color and shape.
      • Example 2: An on-line multi-page survey An on-line multi-page survey uses a link implemented as a green arrow icon placed in the lower right hand corner of the content to move from one survey page to the next. The arrow is clearly labeled with “Next” and the instructions state, “To move to the next section of the survey, select the green arrow icon labeled ‘Next’ in the lower right corner below the last survey question.” This example uses both positioning, color and labeling to help identify the icon
    • EN 301 549 Requirements & Notes
      • it shall satisfy the WCAG 2.1 Success Criterion 1.3.3 Sensory Characteristics.
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface.
    • EN 301 549 Reference number
      • C.11.1.3.3
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.3.4 Orientation (AA)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • Rotate the device and ensure that users can access all content and use all functions regardless of screen orientation.
    • WCAG Description & Clarification
      • Success Criterion 1.3.4 Orientation (Level AA): Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.
    • Example
      • Example 1: Online video site A video is shown in either portrait or in landscape based on the user’s chosen orientation.
      • Example 2: Messaging website A messaging website can display messages in both portrait and landscape orientations.
      • Example 3: eReader web app An eReader web app can display the contents of a book in both portrait and landscape orientation.
      • Example 4: Check deposit in banking app An example where orientation is essential could be a banking app that requires the device be in landscape mode to easily and accurately capture an image of a check for deposit. These paper forms are typically about twice as wide as they are high.
      • Example 5: Piano app An example where orientation is essential could be a piano app that requires the device to be in landscape mode to allow room for enough of the piano keys to be functionally usable. Since a piano app is emulating a physical piano keyboard that needs to retain relative physical characteristics between keys, either too few keys would be available, or the keys would be much too narrow.
    • EN 301 549 Requirements & Notes
      • it shall satisfy the WCAG 2.1 Success Criterion 1.3.4 Orientation.
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface. 2. The software provides support to at least one assistive technology.
    • EN 301 549 Reference number
      • C..11.1.3.4
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.3.5 Identify Input Purpose (AA)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • Make sure input fields assist the user in entering the correct information by utilizing autocorrect, symbols and the relevant keyboard layout.
    • WCAG Description & Clarification
      • Success Criterion 1.3.5 Identify Input Purpose (Level AA): The purpose of each input field collecting information about the user can be programmatically determined when:
      • The input field serves a purpose identified in the Input Purposes for User Interface Components section; and
      • The content is implemented using technologies with support for identifying the expected meaning for form input data.
      Example
      • A contact form using autofill A contact form auto-fills in the fields for name, street, post code, city, telephone number and email address from autofill values stored in the user’s browser. Assistive technology can offer a customized way of identifying particular input fields, for example drawing on a set of symbols / icons that is familiar to the user, to communicate the purpose of the fields visually.
      • An order from with separate billing and shipping address A product order form fills in the address fields for billing address and a separate set of address fields for the shipping address, using the autofill detail tokens ‘billing’ and ‘shipping’
      • A contact form using icons A browser plugin to add icons inserts icons representing the person’s name, home address, telephone number and email address to identify the input purpose visually.
    • EN 301 549 Requirements & Notes
      • It shall satisfy the WCAG 2.1 Success Criterion 1.3.5 Identify Input Purpose.
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface. 2. The software provides support to at least one assistive technology.
    • EN 301 549 Reference number
      • C.11.1.3.5
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.4.1 Use of Color (A)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • Put the phone in Black and White and make sure information, actions and visual elements are distinguishable.
    • WCAG Description & Clarification
      • Success Criterion 1.4.1 Use of Color (Level A): Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
      • This success criterion addresses color perception specifically. Other forms of perception are covered in Guideline 1.3 including programmatic access to color and other visual presentation coding.
    • Example
      • A form that uses color and text to indicate required fields A form contains both required and optional fields. Instructions at the top of the form explain that required fields are labeled with red text and also with an icon whose text alternative says, “Required.” Both the red text and the icon are programmatically associated with the appropriate form fields so that assistive technology users can determine the required fields
      • An examination. Students view an SVG image of a chemical compound and identify the chemical elements present based on the colors and numbers used in the diagram. The text alternatives associated with each element name the color of the element and indicate the element’s position in the diagram. Students who cannot perceive color have the same information about the compound as their classmates. (This technique also satisfies Guideline 1.1 Level A.)
      • Disabled Form elements. Form elements which are disabled via markup or scripting, are greyed out and made inactive by the user agent. When in the disabled state these elements do not receive focus. Assistive technologies can programmatically determine the state of disabled elements and will provide this information to the user as the elements are encountered on the page. The change in color and loss of focus provides redundant, visual information about the state of the control.
    • EN 301 549 Requirements & Notes
      • It shall satisfy the WCAG 2.1 Success Criterion 1.4.1 Use of Color.
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface
    • EN 301 549 Reference number
      • C.11.1.4.1
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.4.2 Audio Control (A)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • Text
    • WCAG Description & Clarification
      • Success Criterion 1.4.2 Audio Control (Level A): If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.
      • Since any content that does not meet this success criterion can interfere with a user’s ability to use the whole page, all content on the Web page (whether or not it is used to meet other success criteria) must meet this success criterion. See Conformance Requirement 5: Non-Interference.
    • Example
      • An audio file begins playing automatically when a page is opened. However, the audio can be stopped by the user by selecting a “silent” link at the top of the page.
    • EN 301 549 Requirements & Notes
      • If any audio in a software plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. NOTE 1: Since any part of a software that does not meet this success criterion can interfere with a user’s ability to use the whole software, all content in the software (whether or not it is used to meet other success criteria) shall meet this success criterion. NOTE 2: This success criterion is identical to the WCAG 2.1 Success Criterion 1.4.2 Audio Control replacing “on a Web page” with “in a software”, “any content” with “any part of a software”, “whole page” with “whole software”, “on the Web page” with “in the software”, removing “See Conformance Requirement 5: Non-Interference” and adding note 1.
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface
    • EN 301 549 Reference number
      • C.11.1.4.2
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.4.3 Contrast (Minimum) (AA)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • Text
    • WCAG Description & Clarification
      • Success Criterion 1.4.3 Contrast (Minimum) (Level AA): The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following:
      • Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1;
      • Incidental Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
      • Logotypes Text that is part of a logo or brand name has no contrast requirement.
    • EN 301 549 Requirements & Notes
      • it shall satisfy the WCAG 2.1 Success Criterion 1.4.3 Contrast (Minimum).
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface.
    • EN 301 549 Reference number
      • C.11.1.4.3
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.4.4 Resize text (AA)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • Increase the text size on the phone and see that it applies to the app as well. Make sure the content is readable.
    • WCAG Description & Clarification
      • Success Criterion 1.4.4 Resize text (Level AA): Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.
    • Example
      • A user with vision impairments increases the text size on a Web page in a browser from 1 em to 1.2 ems. While the user could not read the text at the smaller size, she can read the larger text. All the information on the page is still displayed when the larger font is used for the text
      • A Web page contains a control for changing the scale of the page. Selecting different settings changes the layout of the page to use the best design for that scale.
      • A user uses a zoom function in his user agent to change the scale of the content. All the content scales uniformly, and the user agent provides scroll bars, if necessary.
    • EN 301 549 Requirements & Notes
      • It shall satisfy the WCAG 2.1 Success Criterion 1.4.4 Resize Text. NOTE 1: Content for which there are software players, viewers or editors with a 200 percent zoom feature would automatically meet this success criterion when used with such players, unless the content will not work with zoom. NOTE 2: This success criterion is about the ability to allow users to enlarge the text on screen at least up to 200 % without needing to use assistive technologies. This means that the application provides some means for enlarging the text 200 % (zoom or otherwise) without loss of content or functionality or that the application works with the platform features that meet this requirement.
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface. 2. The software provides support to enlargement features of platform or assistive technology
    • EN 301 549 Reference number
      • C.11.1.4.4.1
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.4.5 Images of Text (AA)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • Text
    • WCAG Description & Clarification
      • Success Criterion 1.4.5 Images of Text (Level AA): If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following:
      • Customizable The image of text can be visually customized to the user’s requirements;
      • Essential A particular presentation of text is essential to the information being conveyed.
      • Logotypes (text that is part of a logo or brand name) are considered essential.
    • Example
      • Styled Headings Rather than using bitmap images to present headings in a specific font and size, an author uses CSS to achieve the same result.
      • Dynamically Generated Images A Web page uses server-side scripting to present text as an an image. The page includes controls that allow the user to adjust the font size and foreground and background colors of the generated image.
      • A quote A Web page contains a quote. The quote itself is presented as italicized text, indented from the left margin. The name of the person to whom the quote is attributed is below the quote with 1.5x the line space and further indented from the left margin. CSS is used to position the text; set the spacing between lines; as well as display the text’s font family, size, color and decoration.
      • Navigation items A Web page contains a menu of navigation links that have both an icon and text to describe their target. CSS is used to display the text’s font family, size and foreground and background colors; as well as the spacing between the navigation links.
      • A logo containing text A Web site contains the organization’s logo in the top left corner of each Web page. The logo contains logotype (text as part, or all, of the logo). The visual presentation of the text is essential to the identity of the logo and is included as a gif image which does not allow the text characteristics to be changed. The image has a text alternative.
      • Representation of a font family A Web page contains information about a particular font family. Substituting the font family with another font would defeat the purpose of the representation. The representation is included as a jpeg image which does not allow the text characteristics to be changed. The image has a text alternative.
      • A representation of a letter A Web page contains a representation of an original letter. The depiction of the letter in its original format is essential to information being conveyed about the time period in which it was written. The letter is included as a gif image which does not allow the text characteristics to be changed. The image has a text alternative.
      • Symbolic text characters A form allows users to enter blocks of text. The form provides a number of buttons, including functions to style the text and check spelling. Some of the buttons use text characters that do not form a sequence that expresses something in human language. For example “B” to increase font weight, “I” to italicize the text and “ABC” to check the spelling. The symbolic text characters are included as gif images which do not allow the text characteristics to be changed. The buttons have text alternatives.
      • Customizable font settings in images of text A Web site allows users to specify font settings and all images of text on the site are then provided based on those settings.
    • EN 301 549 Requirements & Notes
      • It shall satisfy the WCAG 2.1 Success Criterion 1.4.5 Images of Text.
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface. 2. The software provides support to assistive technologies for screen reading
    • EN 301 549 Reference number
      • C.11.1.4.5.1
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.4.10 Reflow (AA)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • 1. Check that the software does not fail the Success Criterion in Table 11.2 Run the application on smaller and bigger screen sizes, note how the content adjusts to fit the new screen size.
    • WCAG Description & Clarification
      • Success Criterion 1.4.10 Reflow (Level AA): Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: Vertical scrolling content at a width equivalent to 320 CSS pixels; Horizontal scrolling content at a height equivalent to 256 CSS pixels.
      • Except for parts of the content which require two-dimensional layout for usage or meaning.
      • 320 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels wide at 400% zoom. For web content which is designed to scroll horizontally (e.g., with vertical text), 256 CSS pixels is equivalent to a starting viewport height of 1024 CSS pixels at 400% zoom.
      • Examples of content which requires two-dimensional layout are images required for understanding (such as maps and diagrams), video, games, presentations, data tables (not individual cells), and interfaces where it is necessary to keep toolbars in view while manipulating content. It is acceptable to provide two-dimensional scrolling for such parts of the content.
    • Mobile
      • Most browsers on mobile operating systems do not combine reflow and zoom in the same way as on desktop browsers. These mobile browsers normally support reflow when changing the orientation of the device — content will be adjusted to the new viewport width. However, these mobile browsers can only magnify content to achieve 1.4.4. Resize Text in manners which do not constrain reflow to a single dimension, for example by using a pinch gesture to scale up content or a double tap on a particular column to make it fill the viewport width. This means that zoomed content in most mobile browsers involves two-dimensional scrolling regardless of what an author does
      • Mobile user agents can offer reflow when users zoom into content, as evidenced by the Dolphin browser for Android. The lack of magnified reflow support in browsers on mobile operating systems can therefore be regarded as a user agent support issue
    • EN 301 549 Requirements & Notes
      • Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: • Vertical scrolling content at a width equivalent to 320 CSS pixels; • Horizontal scrolling content at a height equivalent to 256 CSS pixels; Except for parts of the content which require two-dimensional layout for usage or meaning. NOTE 1: 320 CSS pixels is equivalent to a starting viewport width of 1 280 CSS pixels wide at 400 % zoom. For non-web software which are designed to scroll horizontally (e.g. with vertical text), the 256 CSS pixels is equivalent to a starting viewport height of 1 024 px at 400 % zoom. NOTE 2: Examples of content which require two-dimensional layout are images, maps, diagrams, video, games, presentations, data tables, and interfaces where it is necessary to keep toolbars in view while manipulating content. NOTE 3: This success criterion is identical to the WCAG 2.1 Success Criterion 1.4.10 Reflow replacing the original WCAG 2.1 notes with notes 1 and 2, above.
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface. 2. The software provides support to at least one assistive technology.
    • EN 301 549 Reference number
      • C.11.1.4.10.1
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.4.11 Non-text Contrast (AA)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • Text
    • WCAG Description & Clarification
      • Success Criterion 1.4.11 Non-text Contrast (Level AA): The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):
      • User Interface Components Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;
      • Graphical Objects Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.
    • Example
      • Status icons on an application’s dashboard (without associated text) have a 3:1 minimum contrast ratio.
      • A text input has a dark border around the white editable area.
      • A graph uses a light background and ensures that the colors for each line have a 3:1 contrast ratio against the background.
    • EN 301 549 Requirements & Notes
      • It shall satisfy WCAG 2.1 Success Criterion 1.4.11 Non-text Contrast.
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface. 2. The software provides support to at least one assistive technology.
    • EN 301 549 Reference number
      • C.11.1.4.11
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.4.12 Text Spacing (AA) EN 301 549 Pre-conditions )
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • Text
    • WCAG Description & Clarification
      • Success Criterion 1.4.12 Text Spacing (Level AA): In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: • Line height (line spacing) to at least 1.5 times the font size; • Spacing following paragraphs to at least 2 times the font size; • Letter spacing (tracking) to at least 0.12 times the font size; • Word spacing to at least 0.16 times the font size
      • Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script.
    • Example
      • When spacing is be overridden to the SC’s metrics:
      • Text fits within the bounds of its containing box without being cut off.
      • Text fits within the bounds of its containing box without overlapping other boxes.
    • EN 301 549 Requirements & Notes
      • it shall satisfy WCAG 2.1 Success Criterion 1.4.12 Text spacing.
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface. 2. The software provides support to at least one assistive technology.
    • EN 301 549 Reference number
      • C.11.1.4.12
    • Developer HowTo Link
    • Visual Design Description
      • No Content
  • 1.4.13 Content on Hover or Focus (AA)
    • Category/Label
      • Which category that includes this specific criteria. For easier search
    • How To Test
      • When possible, press and hold to activate the additional content. Make sure the content is still available after applying zoom.
    • WCAG Description & Clarification
      • Success Criterion 1.4.13 Content on Hover or Focus (Level AA): Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:
      • Dismissible. A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content
      • Hoverable. If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing
      • Persistent. The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
      • Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author
      • Examples of additional content controlled by the user agent include browser tooltips created through use of the HTML title attribute.
      • Examples of additional content controlled by the user agent include browser tooltips created through use of the HTML title attribute.
    • EN 301 549 Requirements & Notes
      • Examples of additional content controlled by the user agent include browser tooltips created through use of the HTML title attribute.
    • EN 301 549 Pre-conditions
      • 1. The ICT is non-web software that provides a user interface. 2. The software provides support to at least one assistive technology.
    • EN 301 549 Reference number
      • C.11.1.4.13
    • Developer HowTo Link
    • Visual Design Description
      • No Content

Staticore

, , , ,